Manaz Afzal Book a consultation

Work snippet

ServiceM8 to Xero month-end tie-out and unbilled jobs register

Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.

This business relies on the built-in ServiceM8 sync to Xero. A nightly Make run compares both systems invoice by invoice and gives every gap a reason; at month end the comparison closes at 0.00 and the register of finished but unbilled jobs is cleared before the books go to the accountant.

The problemThe native ServiceM8 to Xero sync drifts, and nobody can say why the two totals differ.

What changesA nightly match names every difference, and the month closes at 0.00 with an unbilled jobs list.

Area
Month-end close
Tools
ServiceM8 · Xero · Make · Google Sheets · Slack
Typical scope
US$250-600
Timeline
About 4 weeks · fixed milestones

The situation and what was breaking

In theory the systems match. In practice they drifted most months, and the causes came out only when the accountant started asking.

About 120 invoices a month leave ServiceM8 through the native sync. A few are held because an invoice number is already used in Xero, a few because the customer is not linked to a Xero contact, and credit notes are sometimes raised in Xero only. Completed jobs that were never invoiced do not show up anywhere at all.

The office spent the first week of each month rebuilding the gap from two exports, and the answer changed each time it was rebuilt.

  • Xero sales did not match ServiceM8 for the month, with no list of why
  • Invoices held by the sync with nobody told
  • Credit notes raised in one system only
  • Completed jobs left unbilled for weeks
  • The same questions from the accountant every month

What good looks likeOne page at month-end that starts at ServiceM8, ends at Xero, names every difference, and tells someone what to fix this week.

Discovery findings

What a read-only review checks first: three months of ServiceM8 jobs and invoices against Xero, the sync log, and how the office and the bookkeeper close the month.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1Sync holds invoices when the number already exists in Xero6 held in the quarter, none reportedSales understated until someone notices
F2Customers created in ServiceM8 without a Xero contact link11 unlinked customers with open jobsInvoices held, or duplicate contacts created
F3Credit notes raised directly in Xero after a job change4 credits with no ServiceM8 recordThe two totals drift every month
F4Jobs marked Completed with no invoice17 jobs, $24,600 across the quarterRevenue that is never billed
F5Draft invoices left unapproved9 drafts older than 7 daysCash collected late
F6No written month-end routineThree different exports in useA different answer each time

Architecture: ServiceM8 Xero integration

Nothing replaces the native sync. A Make scenario reads both systems each night into a match workbook, and anything that does not tie goes to a register with an owner. The month-end statement is a view of the same data, so it cannot disagree with the nightly check.

Scroll sideways to see the full drawing

Tie-out architectureServiceM8 and Xero are read nightly by Make into a Google Sheets match engine, which feeds an exceptions register, a month-end statement and a Slack digest.020040060080jobs + invoicesinvoices + creditsstaged rowsunmatchedtied totalsnamed itemsfix at sourceA · SOURCEServiceM8Jobs, invoices,completed statusB · LEDGERXeroInvoices, creditnotes, paymentsC · NIGHTLY 02:00MakeRead-only API pullboth systemsD · MATCH ENGINESheets modelMatch on invoice no.then job and amountE · EXCEPTIONSRegisterReason, owner,action, due dateF · MONTH-ENDStatementSigned at 0.00the native sync is leftexactly as it iseach difference gets one reasonand one ownerDATA FLOW · NIGHTLYManaz Afzal
Read-only nightly extract, match engine and registerSolid: live data path · Dashed: exception path

The screens your team will use

The office works in two places: the tie-out workbook and the exceptions register. The Make scenario runs on its own at 02:00 and only reports when something needs a person.

Google Sheets · Tie-out · OctoberLive

Statement, ServiceM8 to Xero

LineInvoicesAmount
Invoiced in ServiceM8118191,230.00
Less: held, number already used in Xero2(2,410.00)
Less: held, customer not linked2(1,470.00)
Less: credit note in Xero only1(950.00)
Expected in Xero113186,400.00
Sales in Xero113186,400.00
Difference0.00

Starts at ServiceM8, ends at Xero. The difference is 0.00 because every item is named.

Google Sheets · Exceptions register6 items

Open and closed this month

JobReasonAmountOwnerStatus
20511Completed, never invoiced6,240.00OfficeDue Fri
20527Awaiting parts sign-off2,180.00OpsOpen
20533Invoice in draft 9 days1,420.00OfficeApprove
INV-4471Number clash, held1,180.00BookkeeperFixed
INV-4480Customer not linked860.00BookkeeperFixed
CN-0192Credit in Xero only950.00BookkeeperMirrored

One row per difference, with a reason from a fixed list, an owner and a due date.

Make · Scenario · Nightly tie-outLive
matchno matchCLKSchedule02:00 dailySM8List invoicesmonth to date118[ ]Iteratorone per rowXSearch Xeroby invoice no.118ROWAdd match rowSheets!Add exceptionRegister5#Slack digest08:00 summary

Read-only on both systems. The scenario writes only to the workbook and the register, never to ServiceM8 or Xero.

How it is built

Built in the order the money moves, each module tested on a copy of the workbook before the next one starts.

Module-level build6 modules
  1. Module ARead-only connections

    A ServiceM8 API key and a Xero connection with read scopes only, both owned by the business.

  2. Module BNightly extract

    Make pulls month-to-date invoices, credit notes and Completed jobs into staging tabs, replacing the night before.

  3. Module CMatch engine

    Invoice number first, then job number and amount within 0.01, then a manual pairing column for the rare edge case.

  4. Module DReason codes

    Every unmatched row gets one reason from a fixed list of seven, so the register can be counted and trended.

  5. Module EUnbilled jobs

    Completed jobs with no invoice after 2 business days are added with value, technician and owner.

  6. Module FStatement and sign-off

    The month-end view is locked on sign-off and saved as a PDF beside the reports for the accountant.

Field mapping and rules

The match key and the reason codes are the contract. They are agreed in week 1 and do not change without a note in the change log.

What is read, and how it is matched
ServiceM8XeroRule
Invoice numberInvoice numberPrimary key; exact match after trimming prefixes
Job numberReferenceSecondary key when the number differs
Invoice totalTotalMust agree within 0.01
Customer (company UUID)Contact IDMust be linked; unlinked rows are reason R2
Job status Completed + dateNoneCompleted with no invoice after 2 business days is reason R5
Credit (negative invoice)Credit noteMatched to the original invoice; Xero-only credits are reason R3
Reason codes
CodeReasonOwnerFix
R1Number already used in XeroBookkeeperRenumber at source, re-sync
R2Customer not linkedBookkeeperLink contact, re-sync
R3Credit in one system onlyBookkeeperMirror the credit, note the job
R4Amount differsOfficeCorrect the side that is wrong
R5Completed, not invoicedOfficeInvoice this week or note why
R6Draft over 7 daysOfficeApprove and send
R7Timing, crosses month-endBookkeeperListed, no action

Worked figures

Walkthrough arithmetic for one month, from first pass to signed statement.

October tie-outWalkthrough figures
Invoices compared118ServiceM8 month
Matched first pass109by number
Matched second pass4job + amount
Reconciling items5each with a reason
Unbilled jobs3$9,840 listed
Difference0.00signed off

Items by reason code

R1 Number clash2
R2 Not linked2
R3 Credit one side1
R5 Not invoiced3
R6 Old draft1

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.

  • T1Totals agreeThe staged ServiceM8 total equals the ServiceM8 report for the same dates.
  • T2Xero side agreesThe staged Xero sales total equals the Xero sales report, ex credits shown separately.
  • T3Number clashA planted duplicate number lands as R1, not as a match.
  • T4Unlinked customerA test customer with no Xero link lands as R2.
  • T5Credit one sideA Xero-only credit lands as R3 against the right invoice.
  • T6Unbilled jobA job completed 3 business days ago with no invoice lands as R5.
  • T7RoundingA 0.01 difference matches; a 0.02 difference does not.
  • T8Rerun safeRunning the scenario twice gives identical rows, with no duplicates.
  • T9Read-onlyScopes checked: no write access to ServiceM8 or Xero.
  • T10Sign-off lockAfter sign-off the statement view cannot be edited without an override note.

Scope

AreaIncluded
DiscoveryRead-only review of three months of invoices, the sync log and the current month-end routine, with written findings
Nightly extractMake scenario reading ServiceM8 and Xero, read-only, into staging tabs
Match engineTwo-pass match, reason codes and a manual pairing column
Exceptions registerOwners, due dates, statuses and a Slack digest at 08:00 when anything is open
Unbilled jobsCompleted jobs with no invoice listed after 2 business days
Month-end statementLocked view, sign-off line and PDF for the accountant
Source fixesContact links and numbering clashes fixed for the open items
Not includedChanges to job pricing, the native sync settings beyond numbering and links, or moving to different software

Milestones, week by week

  1. Week 1

    Review and rules

    • Findings for three months
    • Match key and reason codes agreed
    • Read-only connections set
    20% of the fee
  2. Week 2

    Extract and engine

    • Nightly scenario on a copy
    • Two-pass match tested
    • Register built
    35% of the fee
  3. Week 3

    Live month

    • Scenario live at 02:00
    • Open items worked with owners
    • Slack digest on
    30% of the fee
  4. Week 4

    Sign-off and handover

    • First signed statement at 0.00
    • SOP and walkthrough
    • 14 days of fixes start
    15% of the fee

Handover and keeping it running

Handover pack

  • Month-end SOP one page, run in the first two business days
  • Reason code guide what each code means and who fixes it
  • Recorded walkthrough the workbook, the register and the scenario
  • Ownership list every connection and file in the business's name
  • Change log where match rules and codes are versioned
  • 14 days of fixes for defects in the agreed scope

Keep it running

The scenario is read-only, so the risk of leaving it running is low. What drifts is people: a new staff member who creates customers without a Xero link, or a credit raised in the wrong place.

  • Weekly: clear the register to zero items older than 7 days
  • Monthly: sign the statement before reports go to the accountant
  • Quarterly: check the Make connection and the Xero app connection are still valid
  • Optional support hours at US$35 per hour, agreed in writing

Typical scope for this kind of project: US$250-600

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