An invoice that’s right the first time, and chases itself after.
Built from what’s already on the job — the accepted quote, the hours, the receipts. The words the ATO wants, your ABN, GST on its own line and your bank details are on every one, without anybody having to remember.
Tax Invoice
INV-0847
Spark & Wire Electrical · ABN 51 824 753 166
BSB
063-502
Account
1084 7291
The compliance bits aren’t optional, so they aren’t a checkbox.
The words “Tax Invoice”, your ABN, GST broken out on its own line, your BSB and account, and the client’s own purchase-order reference are frozen onto the invoice the moment it’s issued. Edit the job a fortnight later and the issued invoice doesn’t move — a document you’ve already sent is evidence, not a live view.
Invoice numbers come from a per-organisation sequence allocated at issue, not when the draft is started — so there are no gaps left by drafts nobody sent.
A draft whose total would fall below zero is refused before a number is allocated. A negative tax invoice is a credit note, and that’s a different document.
Edit a line while someone else is issuing it and the edit is refused rather than landing on a numbered invoice. One of the two wins, cleanly.
Built from the work, not typed out a second time.
Converting an accepted quote copies its lines onto a draft. From there you pull in the hours and the approved variations that have landed on the job since. A quote’s scope is only ever copied onto one invoice, so billing the same job progressively can’t bill the same work twice.
Delete a line that came from a time entry and that entry is released — it’s billable again, and nothing is stranded.
Bin a draft raised by mistake and everything it consumed goes back on the shelf, so a fresh conversion re-bills exactly the same scope.
Bill one stage of a staged job and the other stages keep their own hours, quote and variations for their own invoice.
If hours were held back because their timesheet week hasn’t been signed off, the count is reported on the spot — missing hours read as unapproved, never as never logged.
On site · Corio
SyncedPaid, part-paid, chased or voided.
Payments go onto a ledger under the invoice, so a part payment leaves it sent with the balance still owing and nobody is told anything yet. It settles when the payments cover the total — and only then does whoever raised it hear about it and the client get a receipt. The job itself reaches paid once every invoice on it has settled.
You can’t record more than is still owing, and you can’t date a payment in the future — with “today” judged on your own calendar, not UTC.
Overdue invoices are chased automatically, for the balance still owing rather than the original total, and each reminder fires once.
A sent invoice with no money against it can be cancelled, which releases the time and variations it pulled and emails the client a void notice if they were sent it.
Who it’s for.
The same feature reads differently depending on which end of the business you’re standing at.
The office
Converts, issues and sends. Finds out why hours are missing from a bill while it’s still a draft, rather than from the client three weeks later.
The crew on site
Builds a do-and-charge invoice on the job and records a payment taken on the spot. Sending and cancelling stay with the office, where they belong.
Whoever chases the money
Every payment is a row with a date, a method and a reference. The overdue chase runs without anybody remembering to run it.
Next door.
The parts of the system this one hands off to.
Send one and see.
Fourteen days, your own ABN and bank details on it, your own jobs behind it.