Xero for Construction — What It Can't Do (And What That Means for Job Margin)

Xero isn't the problem. The gap between Xero and the site is.

If you're running a construction business doing $15m–$80m in revenue, you almost certainly use Xero. Your bookkeeper set it up, your accountant loves it, and for what it was designed to do — financial accounting, BAS, payroll, bank reconciliation — it does the job well. That's not going to change.

But at some point, someone asked Xero to also be the system of record for job margin, variation tracking, subcontractor compliance, progress claims, and real-time cost visibility at job level. And that's where things start to quietly fall apart. Not loudly. Not in a way that's obvious until month-end, when your accountant says the job was 14% margin and your project manager says it was under 8%.

This article isn't about replacing Xero. It's about understanding the honest boundary between what Xero does brilliantly and where, structurally, it hits a wall — and what that boundary means for how your business manages job-level profitability.

What Xero does brilliantly (and don't replace it for these)

Before we get into the limitations, let's be fair. Xero is an excellent finance system. It handles the following beautifully, and for most Australian construction businesses there's no compelling reason to replace it for any of this:

• Standard accounting and BAS. Clean double-entry, accurate GST, quarterly BAS lodgements that don't cause drama. This is what Xero was built for.
• Payroll, including award interpretation. Via Xero Payroll or KeyPay integration, most Australian EBA award rates can be handled. The payroll capability alone is reason enough to keep Xero.
• Bank reconciliation and feeds. Xero's bank feed integration is genuinely one of the best in the market. Live feeds, smart transaction matching, minimal manual intervention.
• Cashflow and reporting at entity level. P&L, balance sheet, cashflow — your accountant can see what they need, in the format they need, at month-end.
• Accounts payable and purchase orders for straightforward procurement workflows.
• Integration ecosystem. Xero's App Marketplace connects to hundreds of tools — construction add-ons, document management, reporting dashboards. The integration flexibility is real.

None of this is going away. If someone is telling you to replace Xero with a "better" accounting system, be sceptical. The problem almost never lives there.

Where Xero starts to creak in construction

Here's where it gets specific. These aren't vague complaints about "limitations" — each one has a concrete operational consequence on how your jobs run.

Tracking categories cap at two active, with ≤100 options each

Xero allows two active tracking categories — typically used for project codes and cost centres. Each category can hold up to 100 options before performance degrades. For a builder managing 30–50 active jobs at any time, with multiple cost codes per job, this runs out fast. And when it does, your job costing has to be approximated — which means your margin reports are approximated too.

The practical workaround is to archive old job codes and recycle the slots. That works at low job volumes. At mid-market scale it becomes a manual overhead that someone manages and nobody documents. When that person leaves, the coding logic goes with them.

Variation management doesn't exist as a concept

Xero has no native concept of a variation order. A variation that's approved on site — a scope change, an instruction to proceed, a change to materials — doesn't appear anywhere in Xero until someone manually creates a transaction. In the meantime, your cost report doesn't include it. Your margin calculation doesn't include it. Your project manager and your accountant are looking at different pictures of the same job.

Progress claims and retentions are manual by design

You can manage progress claims in Xero — but only manually. There's no native progress claim workflow, no retention tracking by job, no automated release schedule when defect liability periods close. At a handful of jobs, this is manageable. At 30+ jobs across multiple clients, it's a recurring audit risk and a cash flow problem waiting to happen. Retention that should have been released 90 days ago gets missed because it's in a spreadsheet that someone updates when they remember to.

Real-time job margin isn't possible

This is the most consequential gap. Xero gives you margin at month-end, once the books are closed and reconciled. Construction needs margin daily — at job level, before the variation becomes a write-off, before the subcontractor cost growth becomes locked in. By the time Xero can tell you a job is in trouble, the opportunity to correct it has usually passed.

Subcontractor compliance is completely outside Xero's scope

Insurance expiry, licence currency, induction status, Safe Work Method Statements, EBA compliance documentation — none of this lives in Xero. For most construction businesses it lives in a spreadsheet that a contracts administrator maintains, or in a dedicated compliance platform that isn't connected to anything. The risk is real: a subcontractor on site with expired PI insurance is a liability exposure that no P&L report will catch.

The gap nobody talks about: site-to-office data flow

The limitations above aren't really Xero's fault. They're the symptom of a structural problem that sits upstream: construction is a physical business, and work happens on site. Xero is a finance system, and it lives in the office. The distance between those two things is where most of the operational pain lives.

Think about where information is born in a construction business. A variation is agreed verbally on site. A material delivery is accepted by a site supervisor. Hours are worked by a subcontractor crew. A scope change is approved over the phone. None of this information starts in a system. It starts in someone's memory, or on a piece of paper, or in a WhatsApp message — and it has to travel through human hands before it reaches anywhere that a finance system can see it.

This is why data gets entered twice — or three times, or four. The docket is written on site. Someone enters it into a spreadsheet in the office. The spreadsheet gets reconciled at month-end and entered into Xero. Each step is a delay, a potential error, and a disconnect between what's happening on the job and what the finance system thinks is happening.

Xero alone can't fix that. No accounting system can. The problem isn't bookkeeping — it's the flow of operational information from where it's created to where it needs to go.

Three honest paths forward

There are three realistic options for construction businesses that have hit these limits. None of them is automatically right — the fit depends on your job complexity, your revenue, your existing systems, and how your operations team actually works. Here's an honest description of each.

Worth noting: these options sit on a spectrum, and the right answer for most businesses changes over time. A business at $20m today might be at Option A. In three years at $45m, it might need Option C. The question to keep asking is: where is the operational constraint — and is the fix proportionate to the scale of the problem?

The question to ask before you change anything

Here's the mistake most construction businesses make when they reach this point: they start with the platform question. "Should we replace Xero?" "Do we need an ERP?" "What does this other builder our size use?" Those are all the wrong starting questions.

The right starting question is operational: how does work actually flow through our business, and where does data fall on the floor? Specifically — where is information created on site that never makes it into any system? Where are variations being agreed that don't appear in the cost report for weeks? Where are subcontractor costs being committed before anyone in the office has visibility?

That mapping exercise — tracing how work flows from site to finance — is what tells you whether you have a Xero problem, an operational tool gap, or a process design problem. In our experience, it's usually a combination of all three, but one of them is almost always primary. And the platform decision follows from that answer, not the other way around.

If you're trying to work out whether you've outgrown Xero or just need to fill the gap around it, that's the same question the questions-before-you-buy framework helps with — applied to your existing systems rather than a new purchase.

The businesses that get this right don't start with a product. They start by understanding exactly where information travels on site, where it stalls, and what it costs them to have it arrive in Xero three weeks late. Once you can see that clearly, the solution — whether it's a configuration change, an add-on, or a new platform — becomes obvious. And usually cheaper than you feared.