How DAY ONE works with Xero, MYOB and QuickBooks

Your accounting platform is not where invoicing goes wrong.

Xero, MYOB and QuickBooks are good at what they were built for: the ledger, bank feeds, payroll, tax reporting. Firms that grow past twenty or thirty people rarely complain about any of that.

What they complain about is the fortnight before the invoice run.

The mistaken diagnosis

The usual reading is that invoicing is an accounting problem, so the fix must be an accounting fix — a better package, a tighter chart of accounts, another add-on bolted onto the ledger.

It is not an accounting problem. By the time work reaches the ledger, every decision that determines whether an invoice is correct has already been made somewhere else: in the contract, in the approval of a timesheet, in the change order nobody logged, in the rate that was agreed on a call and written down nowhere.

An accounting platform receives those decisions. It does not make them, and it cannot reconstruct them. Asking it to is how month end turns into an investigation.

Where the strain actually appears

The pressure points are consistent across professional services firms, and none of them are ledger functions:

• Turning approved time, expenses and milestones into accurate invoices across many concurrent projects.
• Getting multi-step approvals and an audit trail in place before anything reaches the ledger.
• Managing WIP, unbilled time and change orders without a spreadsheet in the middle.
• Running rate cards, partials, retainers and milestone or outcome billing on the same engagement.
• Billing several customer entities while keeping one operational view of the work.

All of them decide what the ledger eventually receives. That is the seam DAY ONE sits in — the operating chain that runs up to an approved invoice, described in more detail on our invoicing and WIP governance page.

What DAY ONE does with GST, and what it does not do with BAS

This distinction is worth stating precisely, because it is the one most often got wrong when people describe an operations platform sitting beside an accounting package.

DAY ONE applies GST on the invoice line as the line is built. Tax detail travels with the charge rather than being reconstructed at posting time, so an approved invoice already carries its tax treatment before it reaches your ledger. That detail posts through to Xero, MYOB or QuickBooks alongside the mapped GL coding.

DAY ONE does not prepare your BAS. That is the ledger’s job, and it should stay the ledger’s job. Your accounting platform remains the system of record for tax reporting and statutory lodgement.

The point is not to duplicate a compliance function that Xero, MYOB and QuickBooks already do well. The point is to connect operations into the finance back end so that what arrives there is clean — invoices traced to time, costs, approvals and contract rules, mapped to your GL structure. BAS preparation stops being an investigation because its inputs stopped being ambiguous.

The mechanism, step by step

Time and costs are captured against a governed record, not a free-text note. Contract logic — T&M, fixed fee, milestone, retainer, or a hybrid of them on one engagement — drives what becomes billable and when.

WIP and exceptions are reviewed before anything is issued, with the reason each item is pending held against the item rather than in someone’s head. Approvals route through whatever governance the firm requires. Then the invoice posts, carrying its source links and its GL mapping with it.

Payment status comes back the other way, so delivery managers can see what is genuinely outstanding without asking finance. Multi-entity firms route to the right accounting organisation while keeping a single operational view.

That handover is the whole design: the ledger receives a finished, defensible artefact instead of a request to work something out. The connector patterns available — replace, coexist, or phase — are set out on the integrations page.

What this costs, and where it does not apply

Governing the chain means agreeing your billing rules, your approval gates and your GL mapping before delivery starts, rather than settling them at invoice time. That is real work, done up front, by people who are usually busy — and some firms will decide they would rather absorb the reconciliation than pay it.

There is a size below which this is not worth doing. If your invoicing is a couple of hours once a month and nobody argues about the result, the discipline costs more than the ambiguity does. The firms this helps are the ones where several projects, several billing models and several approvers already collide every cycle.

It also does not fix bad time capture. Better capture and approvals reduce exceptions; no amount of downstream governance invents a record of work that was never entered.

Which of the three you use matters less than you would think

Xero, MYOB and QuickBooks differ in the details of their tax handling and GL structures, and the mapping is configured accordingly. But the architectural position is identical in all three cases: your accounting platform stays the system of record for the ledger, and DAY ONE governs everything upstream of the approved invoice.

No integration is required to go live. Most teams begin with the accounting connection and add others once the operating flow is stable.

DAY ONE runs on Salesforce; works with your Salesforce org, or available as a bundled edition if you don’t use Salesforce.

Keep the accounting platform you already trust. The question worth putting to it is not whether it can do more, but whether what reaches it each month arrives already correct — and if the honest answer is that someone assembles it by hand, the fix belongs upstream. Our quickstart outline sets out what a first implementation actually involves.