Work snippet
Credit notes, part payments and overpayments between ServiceM8 and Xero
Concept DesignIllustrative integration walkthrough. Business details, figures and records are worked examples.
Most ServiceM8 invoices are paid in full and sync to Xero without fuss. This covers the rest: part payments, credit notes when a job changes, customers who overpay, and cents lost to rounding. Each has a written rule, a Make check compares open balances weekly, and refunds need two approvals.
The problemStatements disagree with invoices after part payments, credits and overpayments.
What changesEach case follows a written rule, and a weekly check compares every open balance.
- Area
- Payments and credits
- 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 standard sync is fine when an invoice is paid once and in full. Anything else depends on which system someone edited first.
A payment taken in the field before a credit note is raised, two part payments on one invoice, a refund after an overpayment: each lands differently in ServiceM8 and Xero. Customers receive statements that disagree with the invoice in their hand, and credit notes sit unapplied while the same customer is being chased.
The bookkeeper fixed these one at a time, from memory, and no two were handled the same way.
- Customer statements that disagree with the invoice
- Credit notes left unallocated while the customer is chased
- Overpayments that nobody refunds
- A cent here and there that stops the reconciliation
- Refunds made with no second check
What good looks likeThe same answer every time, whoever is in the office, and nothing refunded without a second person seeing it.
Discovery findings
What a read-only review checks first: 12 months of invoice balances in ServiceM8 and Xero, and the payment methods in use.
| ID | Finding | Evidence | Risk if left |
|---|---|---|---|
| F1 | Field payments recorded in ServiceM8 only | 14 invoices in 12 months | Customer chased for money already paid |
| F2 | Credit notes raised after payment, never allocated | 9 credits, $6,180 unallocated | Statements overstate what is owed |
| F3 | Overpayments left on the account | 5 customers, $1,240 in total | Money owed back with no owner |
| F4 | Rounding: per line in ServiceM8, per invoice in Xero | 31 invoices out by 0.01 to 0.04 | Reconciliation will not close |
| F5 | Invoices voided after a payment | 3 cases, payment left floating | Unexplained credit on the bank |
| F6 | Refunds and write-offs made by one person | No approval trail | Control gap, and no record of why |
Architecture: Xero overpayment and credit notes
The rules live in one place and the automation only checks and routes. Money never moves without a person: Make compares balances weekly, writes differences to a register, and asks for approval in Slack when a refund or write-off is proposed.
Scroll sideways to see the full drawing
The screens your team will use
Three views carry the whole routine: the invoice as Xero sees it, the weekly comparison, and the approval message that a refund cannot skip.
Payments and credits
History
- Invoice approved and sent
- Part payment taken on site
- Scope reduced, credit raised
- Credit allocated to original invoice first
- Weekly check: both sides 350.00
Rule R1: a credit after a payment is allocated to the original invoice first, then to the oldest open invoice.
Refund proposed on an overpayment. Rule R3 needs two approvals.
Approved, first step. Payment matched on the bank line.
Approved. Refund can be posted.
Nothing is refunded or written off above $100 until both people approve in the thread.
Open invoices where the systems disagreed
| Invoice | Case | ServiceM8 | Xero | Before | After | Rule |
|---|---|---|---|---|---|---|
| INV-5102 | Part payment in ServiceM8 only | 1,430.00 | 2,860.00 | 1,430.00 | 0.00 | R2 |
| INV-5118 | Credit after a job change | 350.00 | 990.00 | 640.00 | 0.00 | R1 |
| INV-5127 | Overpayment unapplied | 0.00 | -220.00 | 220.00 | 0.00 | R3 |
| INV-5133 | Rounding, line against invoice | 1,089.00 | 1,088.99 | 0.01 | 0.00 | R5 |
| INV-5140 | Voided after a payment | 0.00 | -495.00 | 495.00 | 0.00 | R6 |
| Total | 2,785.01 | 0.00 |
Built by the Monday 06:00 scenario. Every row names the rule that closed it.
How it is built
Rules first, then the check, then the approvals. The open differences are cleared only once the rules are signed.
- Module ARule book
Seven cases, each with one written treatment, signed by the bookkeeper and owner.
- Module BBalance extract
Make reads every open invoice balance from ServiceM8 and Xero each Monday, read-only.
- Module CClassifier
Each difference is matched to a case by pattern: field payment, credit timing, overpayment, rounding, void.
- Module DRegister
Differences land with rule, owner and due date; closed rows keep the evidence link.
- Module EApproval thread
Refunds and write-offs over $100 post a Slack card that needs two named approvers.
- Module FOpen items
The current list is cleared following the rules, with a before and after balance for each.
Rules and field mapping
The rule book is short on purpose. If a case is not on it, it is held for a person and the book is updated.
| Rule | Case | Treatment | Approval |
|---|---|---|---|
| R1 | Credit note after payment | Allocate to the original invoice first, then the oldest open invoice | Bookkeeper |
| R2 | Field payment not in Xero | Record against the invoice from the payment reference | Bookkeeper |
| R3 | Overpayment | Hold on the customer, refund or credit within 14 days | Two-step over $100 |
| R4 | Two or more part payments | Each recorded on its own date; no netting | Bookkeeper |
| R5 | Rounding up to $0.05 | Write to the rounding account, listed monthly | None, listed |
| R6 | Void after payment | Payment moved to the replacement invoice before the void | Bookkeeper |
| R7 | Write-off | Only after the reminder steps are finished | Two-step over $100 |
| ServiceM8 | Xero | Check |
|---|---|---|
| Invoice number | Invoice number | Key |
| Invoice total | Total | Equal within 0.01 |
| Amount paid | Amount paid | Equal, or rule R2 |
| Credits on the job | Credit allocations | Equal, or rule R1 |
| Balance | Amount due | Difference goes to the register |
Worked figures
Walkthrough arithmetic: open differences before and after the rules are applied.
Differences by rule
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.
- T1Credit after paymentA test credit is allocated to the original invoice, not the newest one.
- T2Field paymentA payment in ServiceM8 only is flagged as R2 within one weekly run.
- T3OverpaymentA planted overpayment opens an approval card, not a refund.
- T4Two approvalsA refund approved once stays held; approved twice it can be posted.
- T5Rounding cap0.05 is written off by rule; 0.06 goes to a person.
- T6Void orderA voided invoice with a payment is held until the payment is moved.
- T7Read-onlyMake has no rights to post payments or credits in either system.
- T8RerunTwo runs on the same Monday give one set of rows.
- T9EvidenceEvery closed row links to the Xero record that closed it.
Scope
| Area | Included |
|---|---|
| Review | 12 months of invoice balances compared, with every difference and its cause |
| Rule book | Seven written rules, signed by the bookkeeper and owner |
| Weekly check | Make scenario comparing open balances each Monday, read-only |
| Register | Differences with rule, owner and due date |
| Approvals | Slack approval card for refunds and write-offs over $100, two named approvers |
| Open items | Current differences resolved following the rules |
| Not included | Changes to job pricing, payment provider changes, or moving to different software |
Milestones, week by week
- Week 1
Review
- 12 months compared
- Causes listed
- Rule drafts
- Week 2
Rules and check
- Rule book signed
- Weekly check on a copy
- Register built
- Week 3
Approvals and clearing
- Slack approvals live
- Open items cleared by rule
- Week 4
Handover
- SOP and walkthrough
- First clean Monday run
- 14 days of fixes
Handover and keeping it running
Handover pack
- Rule book one page, seven rules, signed
- Weekly SOP what to do with each register row
- Approval guide who approves what, and the limits
- Recorded walkthrough the check, the register and the approval thread
- Ownership list connections and files in the business's name
- 14 days of fixes for defects in the agreed scope
Keep it running
The rules only work if new cases are added to the book, not handled from memory. Anything the classifier cannot place is held, and that is the prompt to write a new rule.
- Monday: clear the register before 10:00
- Monthly: list rounding write-offs and check the total is small
- Quarterly: review approvers and the $100 limit
- 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.