Xero + ServiceM8 Integration for Tradies: Why Materials Double Up and What to Do About It

The native ServiceM8-to-Xero integration is one of the main reasons trades businesses pick ServiceM8 in the first place. Job management in one app, accounting in the other, and a built-in sync that's supposed to keep them talking to each other. When it works, it's great. When it doesn't — and particularly when it comes to materials and inventory — it creates a mess that takes longer to clean up than it would have taken to enter everything manually.

This article covers the specific integration problems that keep cropping up for Australian trades businesses, why ServiceM8 support is often limited help, and what you can actually do about it — including why the "just turn it off" advice you see online doesn't work the way people think it does.

The Core Problem: It's All or Nothing

Here's what most people don't realise until they're already dealing with duplicates: the ServiceM8-Xero sync is not granular. There is no toggle in ServiceM8's integration settings that lets you say "sync invoices and contacts but leave materials alone." It's one integration, and it syncs everything — job data, customer records, invoices, payments, and materials — as a single connected workflow.

If you turn the integration off, you lose automated invoice creation, contact syncing, and payment reconciliation along with the material sync. There's no middle ground.

This matters because the material duplication problem is real, but the solution isn't as simple as flipping a switch. You have to understand what's actually causing the duplicates, then decide which trade-off works for your business.

The Material Duplication Problem

Here's the scenario that plays out in trades businesses across Sydney every week.

A plumber in Castle Hill buys fittings from Tradelink, logs them in ServiceM8 as materials used on a job, and invoices the client. The job syncs to Xero. So far, so good. But the same fitting was already in Xero as a purchased item from a different supplier. Now there are two entries for essentially the same thing — one with the Tradelink purchase data, one created by the ServiceM8 sync — and they don't match. The inventory count is wrong. The cost-of-goods-sold report is off. The BAS calculation needs manual adjustment.

Why it happens. The native sync treats every line item pushed from ServiceM8 as a new entry in Xero unless it finds an exact SKU match. If your business doesn't use SKUs consistently — and most Australian trades businesses don't — there's nothing to match against. The result is a growing list of near-duplicate inventory items that an accountant or bookkeeper has to reconcile manually.

The variants we see most often:

Duplicate inventory items. The same copper fitting or electrical switch appears under slightly different names because one was entered in ServiceM8 by a technician in the field and another was imported from a supplier invoice in Xero. ServiceM8 creates a new item in Xero; Xero already had one. Now there are two.
Unit mismatches. ServiceM8 pushes "1 box of screws" as a single line item. Xero has screws tracked per unit. The sync maps them wrong, and the quantity never reconciles.
GST classification drift. The plumbing supplies are GST-free in one system but GST-inclusive in the other, and no one notices until the BAS is due.

For a small operation, this is an annoyance that gets fixed at end of month. For a business doing fifty-plus jobs a week across Greater Sydney, it's a recurring data integrity problem that costs real time and money.

How CSV and XLSX Imports Make It Worse

Here's a common scenario that amplifies the problem.

Your material prices have gone up. Your supplier sends a new price list. You download your Xero item catalogue as a CSV, update the prices, and re-import it. Clean enough.

But ServiceM8 has already created its own versions of those items in Xero — with different internal IDs, possibly different names, and no link back to the items you just updated. Now you have two sets of items with different prices. The next job that syncs from ServiceM8 uses the ServiceM8-created item (with the old price), not the one you just updated. Your margins are wrong, and you don't know until you run a profit report at end of month.

The root issue: ServiceM8 and Xero don't share a single source of truth for inventory items. ServiceM8 creates items in Xero as needed during the sync, but those items aren't linked back to your master item records. Any bulk update you do on the Xero side — price changes, category reorganisation, account code updates — won't flow back to the ServiceM8-created duplicates. You end up maintaining two item catalogues that look similar but aren't connected.

The ServiceM8 Support Problem

When the duplication issue gets bad enough that you raise a support ticket, here's what typically happens.

First response is a knowledge base article. ServiceM8 support is responsive in the sense that you'll get a reply within a business day. But the reply is almost always a link to a help article about SKU mapping or item synchronisation that you've already read. The assumption is that the problem is configuration, not the integration itself.

If you push further, you get the "it's by design" answer. The behaviour that creates duplicates — creating new Xero items when no SKU match exists — is intentional. It's meant to be helpful. In practice, for businesses that aren't strict about SKUs (which is most of them), it creates the exact problem you're trying to solve.

Advanced troubleshooting requires partner-level access. ServiceM8 doesn't expose its API configuration in the UI. If there's a deeper mapping issue, an API integration specialist needs to get involved — and ServiceM8 directs you to their partner network rather than handling it internally. That means another billable engagement to fix something that the native integration was supposed to handle.

None of this is unique to ServiceM8. Native integrations between job management and accounting platforms are notoriously brittle because the two systems model data differently. But when you're a trades business owner trying to get invoices out the door, the "it's complicated on our end" explanation doesn't help much.

What You Can Actually Do

Because the sync is all-or-nothing, you have three real options. Each involves a different trade-off.

Option 1: Live With It and Clean Up Periodically

This is what most trades businesses end up doing. Keep the native sync running for everything — invoices, contacts, payments — and accept that materials will need periodic cleanup.

The workflow: Once a month (or quarter), your bookkeeper or accountant runs a reconciliation on the Xero item catalogue. They identify duplicates, merge them, and adjust any cost-of-goods-sold entries that went to the wrong item. It's not elegant, but it works, and it doesn't require changing any systems.

When this makes sense: Small to medium businesses where the monthly cleanup takes an hour or two. If your material catalogue is relatively stable and you're not doing high-volume purchasing, the cleanup cost is manageable.

The risk: If you're also doing CSV price updates from suppliers, the cleanup gets more complex. Each import can create new inconsistencies that need to be caught manually.

Option 2: Replace the Entire Sync With a Custom Integration

This is the nuclear option, and it's the only way to get full control. Instead of using the native ServiceM8-Xero sync at all, you build a custom integration layer — typically with n8n or a custom Node.js server — that handles the entire sync on your terms.

How it works:

Disable the native ServiceM8-Xero integration entirely
Build a custom workflow that handles contact creation, invoice generation, payment reconciliation, AND material mapping — everything the native sync was doing
In your custom workflow, add the material lookup-and-match logic that the native sync skips: before creating a line item in Xero, check whether it already exists, and use the existing ID if it does
Set up a scheduled reconciliation that catches any items that slipped through

The trade-off: This is a significant build. You're replacing a free, built-in integration with a custom system that needs to be built, tested, and maintained. It's the right call for a business doing high volume with complex materials, but it's overkill for a smaller operation.

Where n8n fits: Self-hosted n8n is the most cost-effective way to build this. No per-transaction pricing, full control over the logic, and you can add as many lookup sources as you need — Xero's item catalogue, supplier price lists, a master materials spreadsheet. The setup cost is a few days of configuration; after that, the ongoing cost is negligible.

Where Zapier fits: If you don't have someone technical who can set up n8n, Zapier can handle the same workflow. The trade-off is per-task pricing, which adds up at scale. For a business doing under 50 jobs a month, it's usually cheaper than the cleanup time. Beyond that, n8n wins on cost.

Option 3: Manage Materials Outside the Sync

This is the pragmatic middle ground that most businesses don't realise is available.

Keep the native sync running for invoices, contacts, and payments — the parts that work well. But change how you handle materials so they don't flow through the sync in a way that creates duplicates.

The approach: Instead of adding materials as line items in ServiceM8 jobs, use a single "Materials — see attached" line item on the job, and manage the detailed material breakdown outside of ServiceM8 — in Xero directly, or in a separate purchasing system. The job still syncs, the invoice still goes to Xero, but the individual material items never enter ServiceM8, so the sync never creates duplicates.

When this works: If your materials are standard and your pricing is consistent, this is a clean solution. It requires your team to change how they enter job data — materials get recorded separately rather than inside the ServiceM8 job — but it eliminates the duplication problem at the source.

The downside: You lose the per-job material tracking inside ServiceM8. If you need to know exactly which materials went to which job for warranty or compliance purposes, this approach won't work for you.

Option 4: Add AI for the Messy Edge Cases (Optional)

If you go with Option 2 (custom integration), AI can help with the material matching problem — but only for the edge cases that a deterministic lookup can't handle.

AI-assisted material matching. A technician writes "3m of 15mm copper pipe — the usual Type B from Reece" in the job notes. A traditional lookup can't match that against a Xero item called "Copper Tube Type B 15mm x 6m." An AI prompt, given the full Xero item catalogue as context, can make the connection and map it correctly.

AI-powered description normalisation. If your team enters materials differently — "Tap washer" vs "Washer, tap" vs "Brass tap washer 15mm" — an AI step can normalise the description before the lookup runs.

Only where ambiguity exists. The key is to use AI as a fallback, not the primary path. Ninety percent of line items will match cleanly with a well-configured lookup. For the ten percent that don't — the unusual materials, the bespoke supplies, the one-off purchases — route them through an AI step rather than letting them become duplicates.

We use this hybrid approach in most of our n8n + AI workflows at Proanalytica. The AI handles the edge cases. The deterministic workflow handles everything else.

What Most Trades Businesses Should Do

If you're a small to medium trades business in Sydney, start with Option 1 (periodic cleanup) and see how much time it actually takes. If it's an hour a month, don't over-engineer a solution. If it's a full day every week, it's time to move to Option 2 or 3.

If you're processing more than a hundred jobs a month and the duplication problem is costing real money, invest in a custom integration (Option 2). The upfront cost is real, but the long-term saving in reconciliation time and accurate reporting is significant.

If your team can change how they enter materials, Option 3 (manage materials outside the sync) is the simplest fix — no new software, no custom builds, just a process change.

How We Can Help

At Proanalytica Technologies, we build these integrations for trades businesses across Greater Sydney. Whether it's a full n8n-based replacement for the native sync, a lighter Zapier workflow, or just advice on how to structure your materials process to avoid the duplication problem in the first place, we design around how your team actually works.

Get in touch if you're spending more time reconciling Xero than doing the work that actually bills.