GST Invoices in Australian Workshop Software: What the System Must Preserve

The ATO's current tax-invoice guidance says a taxable sale below $1,000 needs enough information to establish seven details: that the document is intended to be a tax invoice; the seller's identity; the seller's ABN; the issue date; a brief description of what was sold, including quantity where relevant and price; the GST payable, either separately or through an appropriate GST-inclusive statement; and the extent to which each sale is taxable.

At $1,000 or more, the tax invoice also needs the buyer's identity or ABN. This is especially relevant to mechanical workshops because an ordinary repair can cross that threshold quickly. Customer identity cannot be treated as a decorative header field that may or may not survive the move from booking to invoice.

These requirements describe information that must be clearly ascertainable, not a compulsory visual template. A workshop can use its own branding and document layout, but the design still has to make the seller, buyer where required, supply, price, GST and date understandable. Software quality is therefore visible both in calculation accuracy and in the document a customer or accountant receives.

The ATO says that when a customer requests a tax invoice, a GST-registered supplier must generally provide one within 28 days, unless the sale is $82.50 including GST or less. The $82.50 threshold concerns the obligation to provide a requested tax invoice and the recipient's usual evidence for claiming GST credits; it does not replace the separate information rules for documents the workshop does issue.

A modern workshop will usually provide an invoice for a repair regardless of that low-value exception because the document also explains the work, balance and service history. The practical software question is whether the same dependable document process handles a small counter sale and a multi-thousand-dollar repair without omitting the required identity or tax details.

Registration status also affects the label. A business registered for GST uses the term ‘tax invoice’ and includes GST as applicable. A business that is not registered should issue a standard invoice and should not present GST as though it were being charged. Workshop configuration and document templates need to reflect the actual entity rather than applying one label to every account.

A repair order is the workshop's live operating record. It can contain the customer's concern, vehicle, requested work, promise time, assigned technician, clocked activity, checksheet findings, photographs, videos, recommendations, customer decisions, parts and completion notes. Not all of that belongs on a tax invoice, but the invoice should be derived from the authorised and completed commercial scope.

When the two records are disconnected, reception becomes a human integration. Staff compare a paper job card with messages, ask the technician what was fitted, find the latest approved amount and type the sale again. That creates three risks at once: completed work can be missed, declined work can be charged, and the invoice description or amount can drift from what the customer authorised.

Workshop HQ treats the repair order as the centre of that story. Labour, parts and approval context remain close while the invoice is prepared, so the final commercial record can be reviewed against the work that actually happened. The benefit is not only speed; it is a stronger chain from finding to decision to charge.

A workshop invoice often contains several kinds of line: labour, parts, consumables, outside services and sometimes adjustments. The document needs a reliable relationship between line price, taxable treatment, GST and the amount payable. Showing only a final GST figure makes errors harder to diagnose when the underlying lines do not reconcile.

A strong invoice view makes the ex-GST amount, GST amount and inclusive total understandable in Australian dollars. It also preserves the exact commercial lines so the workshop can explain how the total was formed. If a sale includes different tax treatments, the taxable extent needs to remain clear rather than assuming every line can be handled identically.

Rounding deserves deliberate testing. A ten per cent tax rate does not remove rounding differences across quantities, unit prices, discounts and document totals. The system should apply one documented method consistently so the visible line totals, tax total, invoice total and exported accounting record agree.

Issuing an invoice establishes the amount owed. Recording a payment establishes how much has been received. A single invoice can be unpaid, partly paid or fully paid, and it may receive more than one payment. Treating ‘invoiced’ and ‘paid’ as the same event obscures debtors, deposits, split tenders and later reconciliation.

GST timing adds another layer. The ATO distinguishes cash and non-cash accounting. Under a cash basis, GST is generally attributed as consideration is received. Under a non-cash basis, attribution can arise earlier, including when an invoice is issued. Workshop software should preserve invoice and payment dates accurately, while the business and its adviser determine the applicable GST accounting basis and BAS process.

Workshop HQ keeps invoice totals, recorded payments and the remaining balance visible as separate commercial facts. That operational clarity provides a better foundation for reporting now and for accounting connections as they are released.

Workshop management software owns the operational repair process: vehicle, booking, repair order, technician work, inspection evidence, customer decision, completed labour and parts. Accounting software owns the broader ledger, reconciliation and financial reporting environment. An integration is strongest when it transfers the right commercial result without flattening or duplicating the workshop record.

The design questions extend beyond sending an invoice total. Customer matching, invoice numbers, line descriptions, GST, payment direction, edits, voids, credits, duplicate prevention and failure recovery all need an owner. If both systems can silently change the same field, the workshop may finish with two plausible but different financial records.

Workshop HQ is actively building its integration ecosystem. Burson EzyParts and Repco Navigator Pro are in active setup, and Xero is the next committed accounting connection. Xero is not labelled live today. The intended accounting flow will preserve customer, invoice-line, GST, payment and correction context and will be called available only after provider access and end-to-end release testing are complete.

Real workshops encounter returned parts, pricing mistakes, changed customer details, failed payments and work that needs to be credited or reissued. The important control is not pretending invoices never change; it is making the correction path visible and keeping the resulting records understandable.

A buyer evaluating workshop software should distinguish editing a draft from changing an issued tax document. The demonstration should show who can make each change, what is retained in the timeline or audit history, how the customer receives the corrected document, and how an accounting connection avoids leaving the original and corrected values out of step.

This is one reason Workshop HQ's published integration release standard includes corrections, duplicate risks and recoverable failures. A connection is not complete because the first invoice exports successfully. It is complete when normal exceptions can be understood and recovered without manual guesswork.

The ATO says GST records generally need to be kept for five years, starting from when the record was prepared or obtained or the related transaction or act was completed, whichever is later. Relevant records include sales, tax invoices, GST transactions and documents supporting adjustments, decisions and calculations.

That retention period changes the meaning of software portability. A workshop does not only need a current invoice screen; it needs a practical way to retrieve, read and export the records on which its reporting depends. Backups protect service continuity, while exports and readable documents protect the workshop's ability to use its own historical information.

Migration deserves the same care. When systems change, customer, vehicle, invoice, payment and source context should be analysed and reconciled rather than copied blindly. The original export should be preserved, exceptions should be visible and totals should be checked before the new platform becomes the commercial source of truth.

Consider a repair order containing diagnostic labour, replacement parts and an approved additional service. The customer has approved two recommendations and declined another. A deposit was taken before collection, with the remaining balance paid by card. That one job can reveal whether the platform preserves customer identity, authorised scope, taxable lines, GST totals, partial payment and final balance.

The same scenario also tests the customer-facing record. The amount on the approval should agree with the work moved to the invoice. The declined line should remain part of the decision history without becoming a charge. The invoice should identify the actual seller and buyer as required, and the payment history should reconcile to zero without replacing the issue date.

Workshop HQ's public product tour and capability register publish reproducible tests for this connected path. Reviewers can create representative fictional data, move one repair order through technician evidence and customer decisions, produce the invoice, record payment and compare every amount. That is stronger evidence than accepting separate screenshots of an inspection, invoice and accounting logo.

Workshop HQ is available now to Australian automotive workshops. Its released invoicing workflow supports invoices built from connected repair orders, standalone parts or counter-sale invoices, Australian-dollar GST calculations, visible ex-GST, GST and inclusive totals, payment records and commercial reporting.

Its clearest advantage is the context surrounding the invoice. The technician finding, customer-facing evidence, approve-or-decline response, completed work and final commercial record remain part of one repair story. A workshop is not forced to trade customer transparency for invoice efficiency or reconstruct the charge after the operational work is complete.

The product does not claim that its unfinished Xero connection is already available. It makes a stronger and more useful commitment: Xero is next in the active integration program, the intended data boundary is public, and the connection must pass complete tax, payment, correction and failure testing before release. Current truth and future ambition can both be stated confidently without confusing one for the other.