Job software, accounting software or expense tracking: what tradies actually need

Three tools, three different jobs

The confusion is worth naming up front, because it costs tradies money in both directions — paying for overlapping tools, or expecting one tool to do something it was never built for.

Job management software runs the work: quoting, scheduling, dispatch, job notes and getting an invoice out from site. Accounting software runs the ledger: income and expenses in one set of books, BAS and tax returns, payroll if you have staff, and the file your accountant opens. Expense tracking runs the money you spend: reading the bank feed, sorting each transaction, capturing GST on it and surfacing what looks deductible while the year is still going.

Each does its own job well and none of them does the other two. A quoting tool does not know that the Bunnings card swipe on Tuesday was for a job; a ledger knows the amount but not whether it was claimable; an expense tool has no idea what you quoted.

What job management software is for

ServiceM8, Tradify and simPRO are the names you will hear most in Australia, and they solve the problem of running work rather than running books. Quote from site, schedule a week, dispatch a second van, capture job notes and photos, then turn the completed job into an invoice without going home first.

They differ mostly in size and platform rather than in kind — some are built around scheduled service calls with several techs out at once, some around the quote-job-invoice loop of a small crew, and some around complex job costing for businesses running dozens of staff. Field-app platform support varies too, which matters if your crew is not all on the same phones.

What none of them replaces is the ledger. They push invoices into accounting software rather than being it, which is why the standard Australian setup is a pair, not a single product.

What accounting software is for

Xero and MYOB sit at the bottom of the stack. Everything ends up here: income, expenses, GST, payroll, and the reports your accountant works from. Once you are registered for GST or paying anyone, this layer is doing real work and most businesses want it.

What it will not do is fill itself in. A ledger is a place for decisions that have already been made — it holds the categorised, GST-coded, substantiated version of your year and is completely indifferent to how that version came to exist. Until something else makes those decisions, they stay yours, which is how a set of books can be expensive and still be three months behind.

Under the $75,000 GST turnover threshold with no staff, a full double-entry ledger is more machinery than a simple return needs, and that is worth raising with your accountant. The records behind the return are a different matter — those do not scale down.

What expense tracking does that neither is built for

Both of the layers above are organised around what you send out — quotes, invoices, returns. Job software can attach costs to a job, and a ledger will hold anything you put in it, but neither is built around the thing that actually leaks money for tradies: spending that lands all day and gets classified months later, if at all.

That is the gap: reading the bank feed as it arrives, telling job spending apart from personal, capturing GST per transaction, attaching receipts to the lines they back, and flagging what looks deductible while you can still do something about it. A ledger will hold all of that once someone has decided it; deciding it is the work.

This is why the three do not collapse into two. Expense tracking is not a cheaper accounting package — it is the layer that arrives at the ledger with the decisions already made.

It is also the one that pays back soonest. Job software is deferrable: you can quote from a template. A ledger is deferrable for a while: a simple return does not need double entry. But the claim you can substantiate is the claim you keep, and that holds on day one, under every threshold, with or without a ledger. What the ATO asks for is adequate records — a shoebox and a spreadsheet both qualify. What decides the size of your claim is whether the decision about each transaction gets made while you still remember it, which is the part worth handing to something that does it for you.

Which combination fits which business

One person, under the GST threshold, invoicing from a phone: expense tracking, and you can genuinely defer the rest. Quotes can be a template and a simple return does not require a general ledger — but the spending still has to be sorted and substantiated, so that is the piece to start with rather than the piece to add last. Adding job management here is buying scheduling software to schedule yourself.

One to five people, GST registered: accounting software and expense tracking together are the core, with job management earning its place the moment quoting and scheduling stop fitting in your head. The ledger holds the year; the expense layer is what reaches it already decided, which is the difference between a quarter that reconciles and a quarter that gets rebuilt.

Six or more, or complex job costing: the full stack, and the question shifts from which products to whether they talk to each other properly. At this size the integration between layers costs more in wasted hours than any single subscription does.

What moves with size is how much software sits above the records. What does not move is the records themselves — which is the opposite of the order most people buy in, and the reason a trade business can own three subscriptions and still leave deductions on the table.

Where they overlap, and how not to pay twice

Job management tools all issue invoices, and so does accounting software — run both and you decide once where invoices are raised, then let that tool push to the other. Raising them in both places is the most common way small trade businesses end up reconciling their own data against itself.

Accounting software imports bank feeds too, so the overlap looks real. The difference is what happens to a line after it arrives: a feed sitting in a ledger waiting to be coded is a task, not an answer. The question is never whether the transactions are there — it is whether anything has decided what they were. If that decision keeps arriving as a quarterly backlog, the feed is not the part you have covered.

The test for any layer is the same: if removing it would not create work somewhere else, it is not earning its subscription.