Electronic invoice in Australia
Understand Australia’s Peppol framework, PINT A-NZ requirements, public-sector obligations and voluntary B2B e-invoicing rules.
Australia chose a decentralised Peppol four-corner model aimed at automation and fraud prevention rather than tax control. The Australian Taxation Office does not receive copies of invoices and cannot see their contents. The system is therefore neither a clearance model nor a continuous transaction control regime.
There is no national B2B mandate. The obligation sits with federal government bodies — Non-Corporate Commonwealth Entities — first to be able to receive Peppol invoices, and since 2026 to hit actual usage and automation targets. Private suppliers face no general statutory duty to send, though an individual government buyer may make it a contractual condition.
A slow build on the receiving side, then a sharp turn in 2025–2026 towards measurable usage rather than mere capability.
Federal Peppol rollout begins, with the tax office in the unusual role of network governor rather than data recipient.
Material Non-Corporate Commonwealth Entities had to be able to receive Peppol eInvoices by 1 July 2021, and the remaining NCEs by 1 July 2022.
PINT A-NZ became the mandatory specification, and the older A-NZ Peppol BIS Billing was decommissioned. See PINT A-NZ and formats.
The current binding version. Version 1.1.3 was published on 8 June 2026 but does not become mandatory until later in the year.
NCEs were to work with suppliers so that at least 30% of all invoices received arrive as Peppol eInvoices. The date has passed; no consolidated public report on actual compliance across all NCEs has been published.
Published in June, binding from September — the kind of cadence that makes version tracking part of the operating model rather than a project task.
NCEs must automate both the processing of incoming and the sending of outgoing eInvoices, moving towards touchless workflows. Quarterly progress reports to the Australian Peppol Authority continue throughout.
The federal obligation is on the buyer side. Non-Corporate Commonwealth Entities must be able to receive Peppol eInvoices, and since 2026 must also demonstrate usage and automation. Corporate Commonwealth Entities and Commonwealth Companies are not subject to the same universal coverage — adoption there is recommended rather than required.
No general law requires a supplier to a federal entity to send only Peppol eInvoices. But government buyers can include eInvoicing in new tenders and contracts, agree Peppol with a supplier, and prioritise onboarding of high-volume suppliers. Obligation can therefore arise contractually even where tax law imposes none.
This is the practical point for anyone selling to the Australian Commonwealth: check the contract, not the statute book.
There is no single mandatory schedule across states, territories and local government — adoption is uneven and needs checking jurisdiction by jurisdiction.
The pattern across Australia is consistent: receiving obligations for the public sector, no sending obligation for business.
For domestic B2B transactions Peppol remains voluntary — the ATO's own product register states that eInvoicing is not compulsory. Treasury consulted twice on going further: in 2020–2021 on options for mandatory B2B eInvoicing, and in 2021–2022 on a Business eInvoicing Right under which a buyer could require a supplier to send a Peppol invoice.
Both consultations are closed and neither produced a national B2B mandate. No future date for compulsory domestic B2B eInvoicing has been announced. Treat any roadmap that shows one as speculation.
Business-to-consumer transactions are expressly excluded from the Australian Peppol eInvoicing framework. There is no mandate and no announced timetable for one.
Australia is outside the EU and applies GST, so the EU's ViDA reform creates no Australian obligation. A sale from Australia to an EU buyer is not an intra-EU supply: Australian GST rules apply, plus whatever the buyer's country requires. If the European counterparty falls under a national or future ViDA regime, it is their local rules that may demand a particular European format or channel — which is where the PINT A-NZ compatibility question becomes practical.
Australia runs the standard four-corner model: supplier → supplier's access point → buyer's access point → buyer, with access points locating the recipient's address and supported documents through the Peppol discovery infrastructure.
The ATO frames eInvoicing as a productivity and business-protection measure, not a revenue mechanism. It does not receive copies of invoices and cannot see their contents.
Australian access points must send the Australian Peppol Authority monthly aggregated statistics — active senders, active receivers, and transactions sent and received by document type — within ten business days of month end. That is statistical network reporting, not invoice-level tax reporting: contents, amounts, parties and line items never reach the ATO.
The mandatory local specification is PINT A-NZ Billing, built on UBL 2.1. Access points must support the PINT A-NZ Invoice and Credit Note; self-billing invoice and credit note support is optional.
urn:peppol:pint:billing-1@aunz-1urn:peppol:bis:billingPINT A-NZ is not a declared EN 16931 CIUS. OpenPeppol describes it as a country specification built on global PINT and localised for Australian and New Zealand GST. PINT-EU, by contrast, is expressly a CIUS of EN 16931 and carries its own EN 16931 validation rules — and EN 16931 terminology was removed from the PINT A-NZ documentation. The two share architecture and much semantics, but PINT A-NZ compliance should not be presented as legal EN 16931 compliance.
The practical consequence: sending to a European recipient may require PINT-EU, Peppol BIS Billing 3.0 or a national European CIUS rather than PINT A-NZ. An Australian exporter cannot assume its domestic profile will satisfy a European mandate.
Two different questions, two different answers — and the distinction is worth spelling out in any supplier agreement.
The Australian participant identifier is the Australian Business Number under scheme 0151, the ISO 6523 code for the ABN.
0151:<11-digit ABN> — for example 0151:70598519443
The ABN must also appear as the legal registration identifier of Australian sellers and buyers inside the invoice. Peppol technically supports other schemes for international participants, but for an Australian organisation the ABN under 0151 is the standard and normatively required identifier.
This is where Australia differs sharply from most Peppol countries. Certification by a European or other Peppol Authority is not sufficient to serve Australian end users. A provider must complete the Australian accreditation process with the ATO as Peppol Authority.
It is an additional national accreditation, but not a Slovak-style digitálny poštár or a clearance provider role: the access point remains an ordinary participant in the four-corner network and never forwards invoices to the ATO for registration.
For a provider already accredited in another jurisdiction the testing burden is reduced: instead of full unit and acceptance testing, only interoperability testing against PINT A-NZ is required.
The published requirements impose no obligation to hold an Australian legal entity, an Australian office, a local tax or Peppol representative, or a state delivery mailbox. The procedure expressly provides for applicants without an ABN, who submit a paper form by e-mail — strong confirmation that a foreign entity can be accredited without incorporating in Australia. The applicant must be a registered business in its own jurisdiction and pass checks on legal status and directors.
Australia and New Zealand run a coordinated approach: a shared PINT A-NZ specification, aligned security and accreditation requirements, and a mutual accreditation mechanism. A provider accredited in Australia can separately request mutual accreditation from the New Zealand Peppol Authority — which makes the two markets a single project rather than two.
Australian tax law requires business records, invoices included, to be kept for five years from the date the record was prepared or obtained, or from the completion of the transaction — whichever is later.
That last point is the difference from a clearance country. In Italy or Romania a state platform holds the original for a period; in Australia nothing is held centrally, so the UBL file and its delivery evidence must be retained by the business or its provider.
Australia uses a carrot rather than a stick. There is no fine for failing to send a Peppol invoice, because for private businesses there is no obligation to send one. Instead, federal payment policy rewards adoption.
A fourfold improvement in payment terms is a stronger argument for adoption than most European penalty regimes. Note that this is government payment policy — not an eInvoicing mandate on the supplier.
Australia is a Peppol market with its own specification, its own identifier scheme and its own accreditation — none of which a European setup covers by default:
0151:ABN with the ABN carried as the legal registration identifier0151:70598519443. The ABN must also appear as the legal registration identifier of Australian sellers and buyers inside the invoice itself. Peppol supports other schemes for international participants, but for an Australian organisation the ABN under 0151 is the standard and normatively required identifier.Australia is a Peppol country without a tax-control agenda. The ATO governs the network as Peppol Authority but sees no invoices; there is no clearance, no reporting and no B2B mandate. The obligations are on federal buyers — receiving capability since 2021–2022, a 30% usage target from July 2026 and automated sending and processing by December 2026.
Technically it is its own world: PINT A-NZ Billing in UBL 2.1 rather than Peppol BIS Billing 3.0, the ABN under scheme 0151, and a mandatory version cadence that moves roughly twice a year.
Two traps worth naming. PINT A-NZ is not a declared EN 16931 CIUS, so it should not be assumed to satisfy a European mandate. And Australian accreditation is a genuine additional requirement — a European Peppol certificate alone does not let you serve Australian users, though no Australian company is needed to obtain it.