Xero Tracking Categories for Job Costing: Setup and Limits

Yes, up to a ceiling you can work out in advance. Xero's tracking categories let you tag income and expense lines with a job, a branch or a cost code, then report on them. That is genuine segmentation, and for a lot of trade businesses it is enough.

Job costing itself is simple to describe and hard to keep clean: every direct material, labour hour, subcontractor invoice and applied overhead lands against the job that consumed it, so you can compare the quote to the actual before the next quote goes out. Xero's own construction guidance says the same thing, assign a job code and record each expense against it as it happens.

Xero is a very good ledger. It is not a job costing engine, and it has never claimed to be. In my 14 years talking to shop owners, the mistake I see is not choosing Xero, it is asking the ledger to answer questions it was never structured to answer, then blaming the software when month end turns into a reclassification exercise. Xero reported roughly 2.8 million subscribers across Australia and New Zealand at 31 March 2026 in its FY26 results, so in the AU market this is the ledger most trade businesses are already sitting on. The question is what you build on top of it.

The mechanics take about ten minutes. The decisions take longer.

1. Go to Accounting > Advanced > Tracking categories and create your first category. Name it for the dimension, not the job, for example Job Type or Branch.
2. Add the options inside it. Options are the values you will tag against, such as Service Call, Install, Warranty, Maintenance Contract.
3. Tag at line level. Each invoice line, bill line and spend money line carries one option from each active category. Sales, purchases and manual journals all support it.
4. Tag during bank reconciliation as well, otherwise cash coded straight off the feed drops out of the tracked view entirely.
5. Report from Profit and Loss with a tracking option filter, or from the Tracking Summary report for a quick per-option view.
6. Archive options for finished work instead of deleting them. Archiving preserves the history in past reports. Deleting does not.

Step 4 is where most setups quietly fail. Untagged transactions do not throw an error, they just sit outside the report and make your margin look better than it is.

Competitor posts assert that Xero "only allows two tracking categories" and leave it there. Here are the constraints separated out, all of them documented in Xero's own Accounting API reference and help centre.

The category ceiling. Xero caps every organisation at 2 active tracking categories, four in total counting archived, with up to 100 options each. Two active is the hard number.

The option ceiling. One hundred options per category is Xero's recommended limit, and going past it slows report loading. For a service business running 150 tickets a month, a per-job option list burns through that in under three weeks.

One option per line, and no cross-break. A transaction line takes one option from each active category, never two from the same one. And this is the limit that hurts most in practice: owners on r/xero consistently describe hitting the ceiling when they need branch and job and phase at once, then finding reports will not break out by both categories together, which leaves manual reclassification as the only way to get a job-level margin.

Three dimensions is the natural shape of a trade business. Xero gives you two.

Treat two active categories as a budget and spend them on the two dimensions that actually explain your margin variance.

For most field service shops that is:

• Category 1: Job Type. Install, Service Call, Warranty, Maintenance Contract, Quoted Works. Five to eight options that never change.
• Category 2: Crew or Branch. Your dispatch teams, vans or depots. Ten to twenty options, stable across years.

What this deliberately does not do is create an option per job. The construction-flavoured advice you will find elsewhere uses a per-job code like Warehouse Renovation, and that works fine when you run five concurrent projects a year. It collapses the moment you are running dozens of short jobs a month, because option count, not category count, becomes the binding constraint.

Job-level detail belongs where the job lives, on the work order. If you want per-job material, labour and margin, build it into a job cost sheet driven by your field data and let Xero hold the roll-up. That split keeps the ledger fast and the job data honest.

Run Profit and Loss and filter by a tracking option to see gross margin for installs versus service calls, or for your north crew versus your south crew. Compare periods side by side rather than looking at a single month, because one bad warranty job distorts a month and disappears across a quarter.

The Tracking Summary report gives you a faster read across all options in one category. Use it as a hygiene check: any option showing a suspiciously round or suspiciously small number usually means bills are being coded inconsistently by whoever enters them.

One caution worth flagging. Payroll allocation is uneven. Leave, allowances and rate overrides do not always carry a tracking category cleanly, so labour cost by category is often the weakest line in the report. If labour is your largest cost, and in service work it usually is, that gap matters more than the category limit does.

Stop expanding tracking categories when any two of these are true:

• You need a third dimension. Job plus phase plus branch means you have already outgrown the model.
• Your option list is drifting toward 100 and nobody is archiving closed work.
• Somebody spends more than an hour a month reclassifying coded transactions to answer a job margin question.
• Bills arrive covering part of a purchase order. Threads on r/xero from trade owners describe asking whether a Xero purchase order can be partially billed, finding it cannot, and dropping back to manual tracking outside the ledger.
• Two different people code the same type of bill to different options.

That last one is the real tell. A tracking structure only works while it is applied identically by everyone touching a bill, and the fix is upstream of Xero. When the cost data starts at the technician's job card instead of at a bookkeeper's keyboard, coding consistency stops being a discipline problem.

Xero Projects. Xero's own answer. It records time and costs per job, tracks budget against actual, and invoices from the tracked data. Xero Gold partner Liston Newton lists it at $10 per month for the first user plus $7 per additional user, and is upfront that it adds bookwork because everything has to be entered correctly. Owners on r/xero who tried it for trade work describe it as very basic and genuinely tough for construction workflows, particularly around stage payments, progress claims and materials against a job.

WorkflowMax / WFM by BlueRock. Worth knowing that this market is unsettled. Since WorkflowMAX moved to BlueRock, threads describe the successor as a train wreck and teams actively shopping, with displaced users naming NextMinute and Abtrac as where they landed. It was always built around time-based billing, which suits professional services better than a shop billing flat rate and materials.

A field service system feeding Xero. Australian trade threads show the same pattern repeatedly: Xero is the assumed ledger, and owners bolt a job management app on top rather than running Xero alone. The job app owns scheduling, materials, labour and job margin. Xero owns the ledger, GST and BAS. Note that the advisory firms telling you to leave Xero are usually selling the replacement, which does not make them wrong, but you deserve to know.

The question nobody answers: if the job is costed in the field app, does anything useful survive the trip to the ledger?

In our own Xero integration, the sync pulls active Xero contacts and inventory items into Field Promax and imports Xero quotes as estimates, and it runs incrementally so only what changed since the last run comes across. That detail matters more than it sounds. The Xero API allows 60 calls per minute per tenant alongside a daily per-tenant cap, and the daily cap is what bites at month end when invoices, contacts and payments all move at once. An integration that re-sends everything behaves very differently at 4pm on the 30th than one that pushes only deltas.

Going the other way, a completed work order becomes a draft accounts receivable invoice in Xero with each product line matched to its Xero item, including partial billing by approved work-complete visit. That last part is what makes progressive billing workable, and it is worth reading alongside our take on when to invoice, before or after the job.