Peppol e-invoicing in Australia, and what it means for an Odoo build
The single most common mistake is designing an Australian rollout the way a Gulf one is designed. Australia is not a clearance country. Getting that wrong changes the architecture, not just a setting.
The model
Four corners, no clearance step
Who you connect to
You connect to an accredited Peppol access point, not to the ATO. The invoice goes supplier access point to buyer access point and the ATO never sees it. There is no clearance, no government approval, no QR code and no fiscal seal.
Who the authority is
The Australian Taxation Office acts as the Australian Peppol Authority. That is an accreditation and governance role, not an invoice-processing one.
The format
PINT A-NZ Billing, which replaced 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, so a build started against the old profile needs checking.
What counts as a tax invoice
An invoice meeting the A-NZ Invoice Specification is a valid Australian tax invoice even without the words "tax invoice" or "GST invoice", as long as every mandatory field is present. That is a data-completeness problem, not a template problem.
The part most people get wrong
There is no B2B mandate
The obligations sit on Commonwealth government buyers, not on suppliers. 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. They report progress quarterly to the Australian Peppol Authority.
Private-sector B2B use stays voluntary. The proposed Business eInvoicing Right was never enforced. Suppliers are legally free to keep sending PDFs, though the ATO encourages agencies to make e-invoicing a contractual requirement, which is the practical reason most businesses end up adopting it.
What that means commercially: if you sell to federal government, Peppol is a condition of winning work. If you do not, it is an efficiency decision you can take on your own timeline.
On Odoo
What the build actually involves
- 01
Pick an accredited access point
This is a commercial choice with ongoing cost, and it determines the integration surface. It is made before any Odoo work starts.
- 02
Make the data complete
PINT A-NZ has mandatory fields that a default Odoo install does not require: ABN held correctly, the right party identifiers, unit codes, and tax categories that map to the specification rather than to a local label.
- 03
Handle the response path
Post-audit exchange still returns transport-level outcomes. A build that fires and forgets has no way to tell you an invoice never arrived.
- 04
Keep the PDF path alive
Most of your customers will not be on Peppol. The build has to do both, cleanly, without someone choosing manually each time.