Manaz Afzal Book a consultation

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.

What a read-only review checks firstWeek 1
IDFindingEvidenceRisk if left
F1Field payments recorded in ServiceM8 only14 invoices in 12 monthsCustomer chased for money already paid
F2Credit notes raised after payment, never allocated9 credits, $6,180 unallocatedStatements overstate what is owed
F3Overpayments left on the account5 customers, $1,240 in totalMoney owed back with no owner
F4Rounding: per line in ServiceM8, per invoice in Xero31 invoices out by 0.01 to 0.04Reconciliation will not close
F5Invoices voided after a payment3 cases, payment left floatingUnexplained credit on the bank
F6Refunds and write-offs made by one personNo approval trailControl 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

Credits and payments control flowServiceM8 and Xero balances are compared weekly by Make; differences go to a register classified by rule; refunds and write-offs route to two approvers before the bookkeeper posts them in Xero.020040060080balancesbalancesclassifyrule appliedrefund > $100approvedbookkeeper postsA · FIELDServiceM8Invoices, fieldpayments, creditsB · LEDGERXeroBalances, creditallocationsC · MONDAY 06:00Make checkEvery open invoiceboth sidesD · RULE BOOKRules R1-R7One answer per caseE · REGISTERDifferencesRule, owner, statusF · APPROVALTwo-stepBookkeeperthen ownerMake never posts money;it compares and routesrounding up to $0.05 iswritten off by rule, listed monthlyCONTROL FLOW · WEEKLYManaz Afzal
Weekly balance check, rule classification and two-step approvalSolid: live data path · Dashed: exception path

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.

Xero · Invoice INV-5118Live

Payments and credits

CustomerCommercial account 214
Invoice total3,790.00
Paid 12 Sep, field card2,800.00
Credit CN-0207, job change640.00
Allocated toINV-5118 (rule R1)
Amount due350.00
ServiceM8 balance350.00
Difference0.00

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.

Slack · #finance-approvals2 of 2
MK
Make check

Refund proposed on an overpayment. Rule R3 needs two approvals.

Customer 388 · overpaid INV-5127Refund $220.00 to the card used. Proposed by the bookkeeper.
ApproveHoldOpen in Xero
BK
Bookkeeper

Approved, first step. Payment matched on the bank line.

OW
Owner

Approved. Refund can be posted.

Status: approved twiceBookkeeper posts the refund in Xero and the register closes the row.

Nothing is refunded or written off above $100 until both people approve in the thread.

Google Sheets · Weekly balance comparisonLive

Open invoices where the systems disagreed

InvoiceCaseServiceM8XeroBeforeAfterRule
INV-5102Part payment in ServiceM8 only1,430.002,860.001,430.000.00R2
INV-5118Credit after a job change350.00990.00640.000.00R1
INV-5127Overpayment unapplied0.00-220.00220.000.00R3
INV-5133Rounding, line against invoice1,089.001,088.990.010.00R5
INV-5140Voided after a payment0.00-495.00495.000.00R6
Total2,785.010.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-level build6 modules
  1. Module ARule book

    Seven cases, each with one written treatment, signed by the bookkeeper and owner.

  2. Module BBalance extract

    Make reads every open invoice balance from ServiceM8 and Xero each Monday, read-only.

  3. Module CClassifier

    Each difference is matched to a case by pattern: field payment, credit timing, overpayment, rounding, void.

  4. Module DRegister

    Differences land with rule, owner and due date; closed rows keep the evidence link.

  5. Module EApproval thread

    Refunds and write-offs over $100 post a Slack card that needs two named approvers.

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

The rule book
RuleCaseTreatmentApproval
R1Credit note after paymentAllocate to the original invoice first, then the oldest open invoiceBookkeeper
R2Field payment not in XeroRecord against the invoice from the payment referenceBookkeeper
R3OverpaymentHold on the customer, refund or credit within 14 daysTwo-step over $100
R4Two or more part paymentsEach recorded on its own date; no nettingBookkeeper
R5Rounding up to $0.05Write to the rounding account, listed monthlyNone, listed
R6Void after paymentPayment moved to the replacement invoice before the voidBookkeeper
R7Write-offOnly after the reminder steps are finishedTwo-step over $100
What the weekly check reads
ServiceM8XeroCheck
Invoice numberInvoice numberKey
Invoice totalTotalEqual within 0.01
Amount paidAmount paidEqual, or rule R2
Credits on the jobCredit allocationsEqual, or rule R1
BalanceAmount dueDifference goes to the register

Worked figures

Walkthrough arithmetic: open differences before and after the rules are applied.

Differences cleared by ruleWalkthrough figures
Open invoices checked412both systems
Disagreed235.6% of open
Difference before$2,785.01total
Difference after0.00each by a rule
Refunds approved twice3all logged
Rounding written off$0.37listed

Differences by rule

R1 Credit timing8
R2 Field payment6
R3 Overpayment3
R5 Rounding4
R6 Void2

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

AreaIncluded
Review12 months of invoice balances compared, with every difference and its cause
Rule bookSeven written rules, signed by the bookkeeper and owner
Weekly checkMake scenario comparing open balances each Monday, read-only
RegisterDifferences with rule, owner and due date
ApprovalsSlack approval card for refunds and write-offs over $100, two named approvers
Open itemsCurrent differences resolved following the rules
Not includedChanges to job pricing, payment provider changes, or moving to different software

Milestones, week by week

  1. Week 1

    Review

    • 12 months compared
    • Causes listed
    • Rule drafts
    20% of the fee
  2. Week 2

    Rules and check

    • Rule book signed
    • Weekly check on a copy
    • Register built
    30% of the fee
  3. Week 3

    Approvals and clearing

    • Slack approvals live
    • Open items cleared by rule
    35% of the fee
  4. Week 4

    Handover

    • SOP and walkthrough
    • First clean Monday run
    • 14 days of fixes
    15% of the fee

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.

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