Xero for Tradies: What It Does Well and Where It Stops

Xero earned its position in Australian trades honestly. As a ledger it is close to the best small business option going, and the list of things it handles without complaint is long: invoicing with online payment links and automated reminders, bank feeds and reconciliation, GST and BAS reporting, payroll with STP filing, receipt capture and expense coding, and dashboards your accountant can log into without you emailing a backup file.

The scale behind it matters for a trade business, because it means your bookkeeper already knows it. Xero reported roughly 2.8 million subscribers across Australia and New Zealand at 31 March 2026 in its FY26 results. Xero does not publish an Australia-only breakout, so treat any "Xero owns X% of the Australian market" figure you see as somebody's estimate rather than a reported number.

In 14 years of operator conversations I have almost never heard a trade owner say Xero was the wrong choice for accounting. What I hear instead is that it stopped being enough somewhere around the point they hired a third tech. If invoicing speed is your immediate bottleneck, that part is solvable inside the ledger and we walk through it in Xero invoicing software for field service businesses.

These are not bugs. They are the edges of what an accounting system is designed to do. But they are edges you will hit, in roughly this order.

1. Xero Projects does not carry a trade workflow. Owners on r/xero who have tried the Projects module describe it breaking down on the things a trade job actually needs: stage payments, progress claims, and materials allocated against a job. The recurring language in those threads is "very basic" and "genuinely tough for construction workflows", and the questions are about replacing Projects rather than tuning it. Worth knowing before you upgrade a plan tier for it, since Projects is bundled into higher tiers and metered per Projects user rather than sold as a flat add-on.

2. The two active tracking category ceiling. Xero caps each organisation at two active tracking categories (four in total counting archived), with up to 100 options each. That is the standard job costing workaround, and it runs out of dimensions the moment you want cost by job, by branch, and by phase at once.

3. There is no quote to order to invoice job stage. A Xero quote becomes an invoice. There is nothing in between where the job lives, gets scheduled, accumulates labour and materials, and gets signed off. That gap is where your whiteboard and your text messages currently sit.

4. Purchase orders cannot sit partially billed. Trade businesses issue a PO to a supplier or subcontractor and get back an invoice covering some of the lines. Owners ask directly whether a Xero PO can be partially billed, find it cannot, and end up tracking the remainder in a spreadsheet outside the ledger.

Do the arithmetic on the workaround and you can see it collapse.

You have two active categories. Say you set one to Job and one to Branch. You are now out of slots, so Phase (rough-in, fit-off, commissioning) has to be folded into the Job option name. Fifty live jobs across three phases is 150 options against a 100 option cap, so you start archiving finished jobs to make room, which means historical reporting stops being comparable. Owners on r/xero describe the next step: reports will not break out by both categories together the way they need, so somebody spends the last two days of the month manually reclassifying lines to produce a job-level margin.

That reclassification pass is the real cost. It is not the licence fee, it is a senior person reconstructing gross margin after the fact from data that was never captured at job level in the first place. If you want the mechanics of capturing cost against a job properly, our guide to integrating QuickBooks and Xero with field service management covers how the job layer feeds the ledger instead of the other way around.

For a decade WorkflowMAX was the default answer when a Xero user asked for job management. Xero retired classic WorkflowMAX on 26 June 2024 and the product moved to BlueRock. If you are still running on the successor, or you migrated and it did not land well, you are not imagining the disruption. Threads from displaced users describe the successor as a train wreck and teams scrambling for something that does billing and project management together, with NextMinute and Abtrac named most often as where people landed.

My read from the conversations I have had since that shutdown: the people who suffered most were the ones who treated WorkflowMAX as an extension of Xero rather than as a separate operational system with its own data. When the product went away, they discovered their job history, their time entries, and their quote templates were not in the ledger at all. If you are choosing a replacement now, ask the export question before the feature question. Can you get your jobs, timesheets, and attachments out in a usable form if this vendor changes hands? Nobody asks that in a demo. Everybody should.

Every listicle on this topic ranks ten tools with the publisher at number one. Less useful than sorting by operator profile, which is how the decision actually gets made.

Solo operator to three techs, reactive work. Quoting on site, invoicing before you leave the driveway, one person doing the scheduling in their head. ServiceM8 and Tradify are built for this shape and neither will overwhelm you in week one.

Four to twenty techs, plumbing, electrical, or HVAC service and maintenance. You now need dispatch, recurring maintenance, asset history, and job-level margin. AroFlo, Fergus, simPRO, and Field Promax all live here. This is the tier where the decision is genuinely close and a real trial with your own jobs beats any comparison table.

Construction and fit-out with subcontractors and progress claims. Your problem is committed cost and retentions, not dispatch. Dedicated job costing tools sit closer to what you need than a service dispatch product.

Compliance-heavy work: mining, civil, government contracts. Prequalification, SWMS, plant inspections, and audit trails drive the choice, and a generic service app will fight you.

Office-based project services billing time. This is the one case where Xero Projects may be enough, since there are no crews, no vans, and no materials against a job.

The honest position is that the tool matters less than whether your foreman will use it on a phone in a roof space. I have watched better software lose to worse software on that single point more than once.

"Integrates with Xero" covers three very different things. A native App Store connection built and maintained by the vendor. A no-code bridge through Zapier or similar, which is a chain of triggers you own and maintain. And a custom build against the Xero API. The maintenance burden runs in that order, cheapest first.

The question to ask in a trial is direction. One-way means invoices push into Xero and nothing comes back, so a contact you edit in Xero drifts out of sync with the job tool. Two-way means a contact created in the field appears in Xero, and a correction made in Xero flows back. Test it in the trial with three deliberately awkward records: a customer with a trading name and a different legal entity name, a job with mixed GST-free and taxable lines, and a part-billed job.

One technical detail worth knowing because it explains month-end behaviour: the Xero API allows 60 calls per minute per tenant alongside a daily per-tenant cap. The minute limit is rarely your problem. The daily cap is what bites at month-end when invoices, contacts, and payments all move at once, which is why an integration that syncs incrementally and pushes only what changed behaves nothing like one that re-sends the whole dataset every run.

Most integration disasters I have been called into were setup problems wearing a software costume. Work through this before the first real invoice moves.

• Map your chart of accounts deliberately. Decide which revenue account each service type hits, and which cost account materials land in. Accept the vendor default and you will be unpicking it at year end.
• Map tax codes explicitly. GST on income, GST free, and BAS excluded need to be right at the line level, not assumed from the customer record.
• De-duplicate contacts first. Two records for the same builder in Xero becomes four after a sync. Clean before you connect, not after.
• Choose auto-push or manual approval, and write it down. Auto-push is faster and unforgiving. Most shops under ten techs should start with manual approval for the first month.
• Run three test jobs end to end, including one with a variation and one with a partial bill, and reconcile them by hand.
• Decide who owns the connection. One named person checks the sync log weekly. Otherwise nobody notices a failed run until BAS time.

The first fortnight after an integration goes live is usually fine. Month two is where the complaints start, and they are remarkably consistent.

Duplicate customers. Field staff create a contact on site because search did not find "Smith Plumbing P/L" when they typed "Smith". Fix it with a naming rule and by restricting contact creation to the office for the first month.

Tax code mismatches on unusual lines. Freight, deposits, and warranty work are where wrong codes hide, and they surface as a BAS variance rather than an error message.

Invoices syncing before they are ready. A tech marks a job complete to clear it off their phone, an invoice drafts, and the customer receives it before the variation is priced. Approval gates exist for exactly this.

Timesheet rounding disputes. Field apps capture time in minutes and payroll wants decimal hours, and a crew that notices a systematic rounding difference will bring it up loudly. Agree the rounding rule in writing before go-live. Our breakdown of 15 minutes in decimal and payroll rounding is the reference I send owners when this comes up.

Partly billed supplier invoices. The Xero PO limitation from earlier resurfaces here, so decide up front whether committed cost tracking lives in the job tool or in a spreadsheet. Undecided means both, badly.

One more thing to plan for on the commercial side: Xero has raised plan prices more than once in recent cycles and has signalled the phase-out of its multi-organisation discount. If you run several entities, price that into the comparison rather than assuming today's bill holds.

Do you need job-level margin, dispatch, or both? If margin is the pain, a job costing tool with a Xero feed solves it. If your problem is knowing where six vans are at 2pm, that is scheduling, and a costing tool will not help. Most service businesses past three techs need both, and that combination narrows the field fast.

Are your techs genuinely mobile? Offline capture, photos against the job, and signature on site are either core to your day or irrelevant. Be honest, because paying for field capability nobody uses is the most common wasted spend I see.

Are you multi-entity or single? Multiple trading entities in Xero changes both the integration mapping and the cost. Ask how the job tool handles two Xero organisations before you get attached to the demo.