Work snippet
ServiceM8 to Xero: every completed job billed once
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
A field service business with a handful of technicians and an external accountant. The last quarter’s completed jobs are matched to Xero by hand first; after that a daily Make check flags any completed job that has no invoice, or more than one, on a morning list with the reason.
The problemSome completed jobs are never invoiced and a few are invoiced twice, once from each system.
What changesEvery completed job has exactly one Xero invoice, or it is on the morning list with a reason.
- Area
- Job to invoice
- Tools
- ServiceM8 · Xero · Make · Google Sheets · Slack
- Typical scope
- US$300-700
- Timeline
- About 4 weeks · fixed milestones
The situation and what was breaking
The jobs were finished but billing was patchy: a few never invoiced, a few invoiced twice, and it came to light only when customers queried their statements.
Technicians mark jobs Completed in the field. The office raises the invoice later, sometimes from ServiceM8 and sometimes straight in Xero when a customer calls. Over three months that produced jobs with no invoice, and a handful with two: one synced from ServiceM8 and one typed in Xero.
Nobody could say which, because the only check was the owner's sense that the month felt light.
- Completed jobs with no invoice, found weeks later
- Two invoices for one job, one from each system
- Invoices raised in Xero with no job link
- Customers disputing a second invoice
- Month-end figures that move after the fact
What good looks likeTell me every morning which finished jobs are not billed, and stop a job being billed twice.
Discovery findings
What a read-only review checks first: a match of every job marked Completed in three months against Xero invoices, by job number, customer and amount.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Completed jobs with no invoice | 14 of 274, $19,760 | Revenue never billed |
| F2 | Jobs invoiced twice | 3 jobs, $4,210 duplicated | Disputes and credit notes |
| F3 | Invoices typed in Xero with no job number | 22 in three months | No way to match automatically |
| F4 | Completed then reopened jobs | 9 jobs | Status no longer means finished |
| F5 | Quotes converted to jobs twice | 2 cases | Duplicate jobs, then duplicate invoices |
| F6 | No daily view of unbilled work | Owner checks by feel | Late billing, slower cash |
Architecture: ServiceM8 Xero sync
The rule is one completed job, one invoice. Make checks it every morning from both sides, and a guard stops the second invoice before it is approved.
Scroll sideways to see the full drawing
The screens your team will use
The office starts the day with one message, and the job card shows the invoice link the check relies on.
Job
History
- Quote accepted
- Completed on site, photos attached
- Invoice synced to Xero
- Daily check: one invoice
The job number travels to Xero in the Reference field, which is what lets the check match.
Morning list for 14 Oct.
Duplicate held.
One message a day. Nothing is posted when both lists are empty.
Completed jobs against Xero
| Month | Completed | Billed once | Not billed | Billed twice | Value at risk |
|---|---|---|---|---|---|
| July | 88 | 81 | 5 | 2 | 8,640.00 |
| August | 92 | 87 | 5 | 0 | 6,180.00 |
| September | 94 | 88 | 4 | 1 | 9,150.00 |
| Total | 274 | 256 | 14 | 3 | 23,970.00 |
| After the fix | 274 | 274 | 0 | 0 | 0.00 |
Each not-billed job was invoiced or noted, and each duplicate was voided with a credit note where it had been sent.
How it is built
Clear the three months first, then switch on the daily check, then the guard.
- Module AReference rule
Every invoice carries the job number in Reference, in both the sync and hand-typed invoices.
- Module BBacklog match
Three months of completed jobs matched to invoices by number, then customer and amount.
- Module CDaily check
Make reads completed jobs and invoices at 06:30 and writes the morning list.
- Module DDuplicate guard
A second draft for the same job number is held and flagged before approval.
- Module EReopened jobs
Jobs moved back from Completed drop off the list until completed again.
- Module FMorning message
One Slack post at 07:00 when either list has items, silent when both are empty.
Field mapping and rules
Matching is strict on purpose. A guess that is wrong does more harm than an item left on the list.
| Pass | Key | Result |
|---|---|---|
| 1 | Job number in Xero Reference | Matched |
| 2 | Customer and amount within 1% | Proposed, a person confirms |
| 3 | No match | Not billed list |
| Any | Two invoices on one job number | Billed twice list, later draft held |
| ServiceM8 | Xero | Use |
|---|---|---|
| Job number | Reference | Key |
| Completed date | Invoice date | Age on the list |
| Job total | Invoice total | Pass 2 |
| Customer | Contact | Pass 2 |
| Status | Status | Reopened and voided excluded |
Worked figures
Walkthrough arithmetic: a three-month backlog and the first two weeks of the daily check.
Backlog by outcome
QA and testing checklist
Every check runs in a copy or on test records first, and each one is ticked with evidence before go-live.
- T1UnbilledA test job completed yesterday with no invoice appears on the list.
- T2Billed onceA synced job does not appear.
- T3DuplicateA second draft with the same job number is held.
- T4ReopenedA reopened job leaves the list.
- T5Hand invoiceAn invoice typed in Xero with the job number matches in pass 1.
- T6No numberAn invoice without a job number goes to pass 2.
- T7SilenceEmpty lists post nothing.
- T8Read-onlyThe check has no rights to approve or void.
Scope
| Area | Included |
|---|---|
| Backlog | Three months of completed jobs matched, each outcome cleared or noted |
| Reference rule | Job number on every invoice, sync and hand-typed |
| Daily check | Make scenario at 06:30, morning list at 07:00 |
| Duplicate guard | Later drafts held for the same job number |
| Morning message | Slack, silent when empty |
| Not included | Changes to pricing, technician workflows, or moving to different software |
Milestones, week by week
- Week 1
Backlog match
- 274 jobs matched
- Lists for the office
- Week 2
Clear and rule
- Backlog cleared
- Reference rule live
- Week 3
Daily check
- Check and guard live
- Morning message
- Week 4
Handover
- SOP
- Walkthrough
- 14 days of fixes
Handover and keeping it running
Handover pack
- Office SOP what to do with each line on the morning list
- Reference rule card for anyone typing an invoice in Xero
- Match log every day's result kept
- Recorded walkthrough the job card, the check and the message
- Ownership list connections in the business's name
- 14 days of fixes for defects in the agreed scope
Keep it running
The check depends on one habit: the job number in Reference. If hand-typed invoices start appearing without it, pass 2 grows, and the weekly count shows it.
- Daily: morning list cleared by noon
- Weekly: count of pass 2 matches should stay near zero
- Monthly: duplicates held, reviewed
- Optional support hours at US$35 per hour, agreed in writing
Typical scope for this kind of project: US$300-700
About 4 weeks · fixed milestones. The systems health check (US$150, fixed) comes first and confirms the scope. Extra hourly work is US$35 per hour, agreed before it starts. After handover, a set block of hours each month is available at the same rate, agreed in writing.
Discuss an engagement.
Outline the operational problem through the contact form. I respond with a recommended starting point, including whether the US$150 systems health check is the appropriate first step.