Way4Tech
๐Ÿ‡ฆ๐Ÿ‡บ E-invoicing in Australia

Odoo e-invoicing in Australia

The Australia e-invoicing picture in full: the scheme, the authority behind it, who it binds, and every requirement we map before a build is quoted.

Scheme

eInvoicing, on the Peppol network, using the PINT A-NZ Billing specification

Authority: Australian Taxation Office, acting as the Australian Peppol Authority

Where it stands

Australia uses Peppol post-audit exchange, not clearance: the invoice goes supplier access point to buyer access point and the ATO never sees it. There is no B2B mandate; the obligations sit on Commonwealth government buyers.

Who has to comply

Commonwealth government agencies. All federal agencies have had to be able to receive Peppol e-invoices since 1 July 2022. Non-corporate Commonwealth entities must be receiving at least 30% of invoices by e-invoicing from 1 July 2026 and must be able to process and send e-invoices automatically by December 2026. Private-sector B2B use stays voluntary: the proposed Business eInvoicing Right was never enforced.

Every requirement, in full

5 requirements. Each one has to end up as a field, a document layout, a stored response, or an API call in your Odoo build. This is the list an e-invoicing project in Australia gets costed against.

  1. 1 Peppol four-corner model. You connect to an accredited access point, not to the ATO. There is no clearance step, no government invoice approval, no QR code and no fiscal seal.
  2. 2 PINT A-NZ Billing is the format, replacing the earlier A-NZ Peppol BIS 3.0 profile. PINT A-NZ Billing Process v1.1.2 carries a release date of 21 November 2025.
  3. 3 An invoice that meets the A-NZ Invoice Specification counts as a valid Australian tax invoice even without the words 'tax invoice' or 'GST invoice', provided all mandatory data fields are present.
  4. 4 Compliance sits with the government entity, not the supplier. Suppliers are legally free to keep sending PDFs, although the ATO encourages agencies to make e-invoicing a contractual requirement.
  5. 5 Non-corporate Commonwealth entities report progress quarterly to the Australian Peppol Authority.

Checked Localization notes on this page checked on 22 August 2026.

Rates, formats, thresholds and submission windows change. We configure against the rules in force at build time and confirm every figure with your accountant or tax advisor before sign-off. If a rule moves after go-live, it is a support ticket, not a rebuild. Read more on our Odoo localization service.

How we build e-invoicing for Australia

The delivery method behind the list above. The same four steps on a 10-user rollout and on a multi-company programme, with the depth scaled to the scope.

  1. 1 Requirements first, code second. Each line above becomes a field, a report, or an API call on a written mapping sheet. Anything with no home in Odoo is quoted as a build before the project starts.
  2. 2 Numbering is settled on day one. Invoice sequences are the part that breaks quietly and costs the most to unwind after go-live, so they are signed off before the first test document.
  3. 3 Submission runs from a queue. Retries, idempotency keys, stored responses and an audit trail. A failed send becomes a ticket with evidence, not a missing invoice you find at month end.
  4. 4 Your finance team signs it off. Real documents, in a test database, checked with your accountant or tax advisor before cutover, with a rollback plan in writing.

What we need from you to quote it

Bring these to the first call and you get a scoped, priced e-invoicing plan for Australia instead of a range.

  • โœ“ Your tax registration details and the entity each one belongs to.
  • โœ“ A sample of every document type you issue: invoice, credit note, debit note, self-billing if you use it.
  • โœ“ Any registration, certificate or portal credential the authority has already issued you.
๐Ÿ‡ฆ๐Ÿ‡บ

Scope e-invoicing for your Australia rollout.

Send us the list above with your answers against it. We come back with what is configuration, what is a connector, and what is a build, priced before the project starts.