Manaz Afzal Book a consultation

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.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1Completed jobs with no invoice14 of 274, $19,760Revenue never billed
F2Jobs invoiced twice3 jobs, $4,210 duplicatedDisputes and credit notes
F3Invoices typed in Xero with no job number22 in three monthsNo way to match automatically
F4Completed then reopened jobs9 jobsStatus no longer means finished
F5Quotes converted to jobs twice2 casesDuplicate jobs, then duplicate invoices
F6No daily view of unbilled workOwner checks by feelLate 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

Billed-once controlMake reads completed ServiceM8 jobs and Xero invoices daily, matches by job number, lists unbilled and double-billed jobs, and blocks duplicate drafts.020040060080completedinvoicesno invoicetwo invoiceslistlisthold draftA · FIELDServiceM8Completed jobs,job numbersB · LEDGERXeroInvoices andreferencesC · 06:30 DAILYMake matchJob number,then amountD · UNBILLEDNot invoicedOwner, age, valueE · DOUBLEBilled twiceDraft blocked,void proposedF · MORNINGSlack list07:00 to officeevery Xero invoice must carrythe job number in Referencereopened jobs leave the listuntil completed againCONTROL · DAILY 06:30Manaz Afzal
One completed job, one invoice, checked from both sidesSolid: live data path · Dashed: exception path

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.

ServiceM8 · Job 20644Live

Job

StatusCompleted 11 Oct
TechnicianTech 07
Job value2,340.00
Xero invoiceINV-7021
Invoices found1
CheckBilled once

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.

Slack · #office07:00
MK
Billed-once check

Morning list for 14 Oct.

3 completed jobs not invoiced · $5,41020651 (2 days) · 20655 (1 day) · 20658 (1 day)
Open list
MK
Billed-once check

Duplicate held.

Job 20640 has two invoicesINV-7015 synced and INV-7019 typed in Xero. INV-7019 left in draft.
Void INV-7019Keep both, note why

One message a day. Nothing is posted when both lists are empty.

Google Sheets · Three-month matchLive

Completed jobs against Xero

MonthCompletedBilled onceNot billedBilled twiceValue at risk
July8881528,640.00
August9287506,180.00
September9488419,150.00
Total27425614323,970.00
After the fix274274000.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-level build6 modules
  1. Module AReference rule

    Every invoice carries the job number in Reference, in both the sync and hand-typed invoices.

  2. Module BBacklog match

    Three months of completed jobs matched to invoices by number, then customer and amount.

  3. Module CDaily check

    Make reads completed jobs and invoices at 06:30 and writes the morning list.

  4. Module DDuplicate guard

    A second draft for the same job number is held and flagged before approval.

  5. Module EReopened jobs

    Jobs moved back from Completed drop off the list until completed again.

  6. 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.

Match rules
PassKeyResult
1Job number in Xero ReferenceMatched
2Customer and amount within 1%Proposed, a person confirms
3No matchNot billed list
AnyTwo invoices on one job numberBilled twice list, later draft held
Fields read
ServiceM8XeroUse
Job numberReferenceKey
Completed dateInvoice dateAge on the list
Job totalInvoice totalPass 2
CustomerContactPass 2
StatusStatusReopened and voided excluded

Worked figures

Walkthrough arithmetic: a three-month backlog and the first two weeks of the daily check.

Backlog and daily checkWalkthrough figures
Completed jobs checked274three months
Not billed14$19,760
Billed twice3$4,210
Hand invoices given job numbers22pass 1 matchable
Daily lists, 2 weeks104 days empty
Duplicates held1before approval

Backlog by outcome

Billed once256
Not billed14
Billed twice3
Reopened9

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

AreaIncluded
BacklogThree months of completed jobs matched, each outcome cleared or noted
Reference ruleJob number on every invoice, sync and hand-typed
Daily checkMake scenario at 06:30, morning list at 07:00
Duplicate guardLater drafts held for the same job number
Morning messageSlack, silent when empty
Not includedChanges to pricing, technician workflows, or moving to different software

Milestones, week by week

  1. Week 1

    Backlog match

    • 274 jobs matched
    • Lists for the office
    25% of the fee
  2. Week 2

    Clear and rule

    • Backlog cleared
    • Reference rule live
    25% of the fee
  3. Week 3

    Daily check

    • Check and guard live
    • Morning message
    35% of the fee
  4. Week 4

    Handover

    • SOP
    • Walkthrough
    • 14 days of fixes
    15% of the fee

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.

Related work snippets

Next step

Bring me the work that repeats.

I scope it in writing, test it against your current process on your own data and hand over everything I build.

Book a consultation