For firms connected to Xero Practice Manager (XPM), jobs created in Nagaris are deployed to XPM so both systems agree on the work being done. This article explains when that happens, how to read the status icons, and how to push or pull changes yourself. If your firm isn't connected to XPM, none of this applies — jobs, tasks and timesheets work entirely inside Nagaris and the XPM controls stay hidden.
The timing depends on how the job was created:
Standalone jobs (created from the Jobs page, the sidebar, or a client group) are submitted to XPM immediately.
Recurring schedule jobs are submitted immediately as each period's job is generated.
Jobs added to an engagement via Add Job to Engagement: if the engagement has already been accepted, the job goes to XPM immediately; if the engagement is still awaiting acceptance, the job is deployed when the client accepts. Jobs built in the Proposal Builder's Jobs tab follow the engagement's acceptance in the same way.
Because adding a job to an accepted engagement deploys straight away, set up the job structure the way you want it before saving.
Services linked to XPM tasks become tasks inside the XPM job. Services with no XPM link are custom services — they carry a Custom badge in service pickers, and the badge's tooltip explains they are shown on the proposal but not created as a task inside an XPM job. Custom services never require a job at all.
Each job's XPM icon (hover for XPM Status: ...) tells you where it is in the pipeline:
Pending — created locally, not yet in XPM.
Submitted — sent to XPM.
Synced — linked and reflecting XPM.
Failed — the submission didn't succeed.
Not Connected — no XPM link.
While a job is Pending, Nagaris blocks actions that would race the submission: tasks can't be completed or reopened (Cannot modify tasks while job XPM status is pending) and Sync From XPM is disabled (Cannot sync while job XPM status is pending).
If jobs are sitting at Pending or Failed, select them on the Jobs page (remember to set the XPM Status filter to Show all (no filter) so you can see them) and click Submit to XPM in the bulk actions bar. You'll see Submitted N jobs to XPM, and the list updates each job's status automatically as XPM confirms over the following seconds.
Changes made in XPM don't appear in Nagaris instantly. To refresh one job, open it and click Sync From XPM (in the header, or under the ... menu once the job is linked) — you'll see Sync from XPM initiated successfully and the page refreshes with XPM's latest data.
To jump across, click Open in XPM on the job page or View in XPM on a job row — both open the job in Xero Practice Manager in a new tab.
The State badge on jobs is your XPM job state list. Changing it in Nagaris saves back to the job (Job state updated). If the dropdown says No states loaded — refresh XPM data, your state list hasn't come across from XPM yet.
Deleting a single job from its row action removes it from Nagaris only. The bulk Delete dialog goes further: when any selected jobs are connected to XPM it shows an Also delete in XPM checkbox and counts how many of the selection are connected — tick it only if you want the XPM copies gone too. This is the safe way to clean up when an engagement created a duplicate of a job you already had in XPM: delete the new Nagaris-created job (without ticking the XPM box if you want to be extra careful) and keep using your existing one.
Timesheets can be logged against any local job, even before it syncs — XPM submission is optional for time tracking.
By default, job lists and timesheet pickers show Submitted only; a job that vanished after creation is usually just Pending behind the filter.
