Peppol E-Invoicing Australia: How It Works (2026 Guide)

What Peppol e-invoicing means in Australia

Peppol e-invoicing in Australia is the exchange of structured, machine-readable invoices across the Peppol network, with the Australian Taxation Office acting as the national Peppol Authority. Instead of emailing a PDF that a buyer's accounts-payable team re-keys, the supplier's software sends a UBL document through a certified Access Point directly into the buyer's finance system. The result is faster payment, fewer keying errors and an auditable trail on both sides.

Two things decide whether an Australian invoice is accepted on the network: the profile it is built to, and the identifier it is addressed with. Since 15 May 2025 the profile is PINT A-NZ and nothing else, and the identifier is your ABN under Peppol scheme 0151. Everything below explains those two facts and what follows from them.

If you are new to the underlying mechanics, start with how e-invoicing works over Peppol. For our Australian accreditation listing, the current government targets and the ABN registration path, see the Australia e-invoicing country page. This guide focuses on the Australian specifics.

Who runs Peppol e-invoicing in Australia, and what does the ATO do?

The Australian Taxation Office is Australia's Peppol Authority, and OpenPeppol lists it in that role on its own register. The ATO accredits the service providers operating in Australia, co-governs the national invoice profile with New Zealand, and publishes the guidance businesses and agencies follow.

Every Peppol country has a national Peppol Authority — the body that signs the Peppol Authority agreement with OpenPeppol and takes responsibility for who may operate in its jurisdiction. In Australia that role sits with the Australian Taxation Office (ATO), and OpenPeppol's Peppol Authorities register names the ATO as Australia's authority with a published contact address for eInvoicing enquiries.

In practice the ATO does four things that affect you directly:

• Accredits Peppol service providers operating in Australia, and publishes them on a public register. What that accreditation covers — and what it does not — is set out in ATO eInvoicing accreditation explained.
• Co-governs PINT A-NZ with New Zealand's Ministry of Business, Innovation and Employment (MBIE), so one profile serves both countries.
• Runs the eInvoicing Ready programme with accounting and ERP software vendors, so a business can check whether its own software already produces conforming documents.
• Publishes adoption guidance for business and for Commonwealth agencies.

This is a lighter-touch model than the clearance regimes emerging in the Gulf and parts of Europe. Australia relies on the open Peppol four-corner network, where documents travel supplier-to-buyer through certified providers. It does not route every invoice through a government platform for approval before it reaches the buyer — which is exactly what Oman's Fawtara and Saudi Arabia's ZATCA do. If you operate in both regions, that difference is the main thing to design around.

The four-corner model, applied to Australia

The supplier only ever connects to its own Access Point (C2). Discovery of the buyer's Access Point happens automatically through the Peppol SMP and SML lookup, so no supplier ever integrates point-to-point with a buyer. Add a new customer and you address the invoice to their ABN; the network finds the route.

The transport between C2 and C3 is AS4, the Peppol eDelivery profile, secured with certificates issued under the Peppol PKI. That is infrastructure your provider operates, not something you configure per customer. The same architecture is explained in what is a Peppol Access Point, and the questions worth asking a provider before you sign are in accredited Peppol service providers in Australia.

One consequence is worth stating plainly, because it catches first-time senders: the buyer's Access Point validates what you send. Passing your own system's checks proves nothing if those checks are the wrong ones.

Which invoice profile does Australia accept in 2026?

PINT A-NZ, and only PINT A-NZ. It is the Australia-New Zealand specialisation of the Peppol International model, built on Peppol BIS Billing 3.0 and governed jointly by the ATO and New Zealand's MBIE. The legacy ANZ Peppol BIS profiles were retired on 15 May 2025.

The transition ran in two steps:

Both dates have passed, and there is no dual-running period left. A document on the retired profile is not a document with a minor defect; it is a document on a profile the network no longer accepts. The detail is in PINT A-NZ is now the only accepted profile in Australia, and the profile itself is explained in PINT A-NZ explained.

What PINT A-NZ inherits from its European ancestor matters as much as what it changes:

• The syntax is UBL 2.1 — an invoice or a credit note, as published in the Peppol BIS Billing 3.0 specification.
• The semantic model is EN 16931, the European standard on the core elements of an electronic invoice, so field names and cardinalities are familiar to anyone who has implemented a European Peppol profile.
• The rules, code lists and identifiers are A-NZ-specific, covering GST, payment means and the ABN.

That inheritance is also the trap. Because PINT A-NZ descends from BIS Billing 3.0, an invoice can look correct and pass a system validating against the European artefacts, then be rejected by an Australian buyer validating against PINT A-NZ. The two are related, not interchangeable. If you want the conceptual distinction between the European baseline and the jurisdiction-specific PINT profiles, see Peppol vs PINT.

The practical check is short: ask your provider which artefacts it validates against, and ask it to name the profile and customisation identifiers it stamps on your documents. Those two identifiers sit in the document itself, so you can read them from a sent file without asking anyone. If they still name a legacy A-NZ profile, the document is on a profile that no longer exists on the network.

Credit notes and self-billing move with the invoice. The 15 May 2025 retirement covered the profile, not one document type within it, so a business that migrated its invoices and left credit notes on the old artefacts has migrated half of its traffic. Self-billing — where the buyer raises the document on the supplier's behalf, common in agriculture, recruitment and freight — is its own A-NZ profile and needs its own confirmation. Both are worth naming explicitly when you ask a provider what it supports, because "we support PINT A-NZ" is a claim about invoices unless you say otherwise.

How does the ABN work as a Peppol address?

Your Australian Business Number is your Peppol address. The Peppol code lists carry it as electronic address scheme 0151, "Australian Business Number (ABN) Scheme", with the Australian Taxation Office as issuing agency. Registering the ABN on an SMP is what makes you findable on the network.

The Peppol ISO 6523 ICD code list describes scheme 0151 in the registry's own words: the ABN "will be a unique identifier for a business to interact with Government (Commonwealth, State and Local) throughout Australia and is the supporting number for the Goods and Service Tax (GST)". It records the ABN as established by A New Tax System (Australian Business Number) Act 1999, and names the Australian Taxation Office as the issuing agency. So the identifier Peppol routes on is the same number the Australian tax system already runs on — there is no separate Peppol number to obtain.

Three things follow:

1. The ABN is what routes the document — not a company name, not an ACN. A free-text customer name in a "Peppol ID" field is the most common reason a first send fails to address.
2. Registration is a publication step. Your Access Point publishes your ABN on an SMP (Service Metadata Publisher), and the SML (Service Metadata Locator) makes that record discoverable. Until that is done, other participants cannot find you, and nobody can send you anything.
3. Registration says what you can receive. The SMP record lists the document types and profiles you accept. If it advertises the wrong profile, senders will build the wrong document.

New Zealand participants use the NZBN under its own scheme, on the same network and the same profile — which is why one provider can cover both markets. That is the subject of trans-Tasman eInvoicing with one provider.

How is GST handled in an Australian Peppol invoice?

GST is carried in the EN 16931 tax model PINT A-NZ inherits: a tax category code, the taxable base and the tax amount, with A-NZ rules checking that line, tax and document totals reconcile. Australia's GST rate is 10%, and mixed supplies are handled per line.

There is no special "GST field". The tax is expressed the same way EN 16931 expresses any indirect tax, which is why an implementation team that has done a European Peppol project recognises the structure immediately. What differs is the set of business rules applied on top. Three things trip up first-time implementers:

• Mixed supplies. GST-free and taxable lines on the same invoice need correct per-line tax categories. A single header-level rate cannot describe an invoice that mixes them, and the totals will not reconcile.
• Rounding. A-NZ rules check that line amounts, tax amounts and document totals agree to the cent. ERP rounding settings that round at a different point in the calculation are a common source of failures that look like arithmetic errors.
• Payment details. Australian payment instruments — BPAY, PayID, BSB and account number — map to specific UBL payment-means structures rather than to a free-text note. Putting a BSB in a comment field means the buyer's system does not see it.

Getting these wrong produces Schematron error-level rejections rather than warnings, and an error-level rejection stops the document. Our guide to invoice validation errors you can prevent covers the ones we see most often.

Does a Peppol e-invoice replace anything you lodge with the ATO?

No. Peppol is a delivery channel between trading partners, not a reporting channel to the tax office. The invoice travels from your Access Point to your customer's. Australia has no clearance step, so nothing goes to the ATO for approval before the buyer receives it.

This is the point at which people who have implemented in the Gulf or in Latin America expect something that is not there. Under a clearance model, the authority sees and approves the invoice before it is valid. Under Australia's model, the ATO's role is to run the framework — accreditation, the profile, the guidance — not to sit in the transaction. Documents go supplier → provider → provider → buyer.

Two consequences, both practical:

• Your GST reporting obligations are unchanged. Business activity statements and the records you keep for them work exactly as before. E-invoicing changes how the invoice arrives, not what you report or when.
• There is no government copy to reconcile against. Your audit trail is the one your Access Point keeps — the message identifiers, the transmission receipts and the validation results. Ask a prospective provider how long it retains those, and how you get at them, because in Australia there is no central platform to fall back on.

If your business also invoices in a clearance jurisdiction, the two models sit side by side rather than replacing one another. Oman's Fawtara is the closest example in our own work: the Fawtara five-corner model explained sets out what the extra corner does and why Australia does not have it.

Is e-invoicing mandatory in Australia?

No general B2B mandate applies in Australia as at August 2026. Commonwealth government agencies can receive Peppol e-invoices, and eligible e-invoices are paid faster than paper or PDF under Commonwealth supplier-payment policy. If you sell to government, the capability is effectively required already.

The distinction that matters is between an obligation to issue and an obligation to receive, and between the public sector and the private sector. Australia's position, stated as plainly as the sources allow:

We state no future mandate date, because no general B2B mandate date has been announced. Where a page tells you Australia is mandating B2B e-invoicing on a specific date, ask it for the instrument. What does exist is a stated adoption target for government: the ATO has published a target for Commonwealth agencies to receive 30% of invoices through eInvoicing by 1 July 2026, with automated processing targeted by December 2026 — the background is in Australia eInvoicing in 2026: the ATO target.

Payment terms are the practical lever, not penalties. Under the Commonwealth's supplier-payment policy, eligible e-invoices are paid faster than paper or PDF — commonly quoted as five business days for eligible invoices. Thresholds and eligibility have changed over time, so confirm the policy that applies to your contract with the Department of Finance or the Digital Transformation Agency rather than relying on a figure in an article, including this one. What suppliers to government need in place is set out in eInvoicing for Australian government suppliers.

The commercial reading: if you sell to government, e-invoicing capability is effectively required today. If you sell B2B, it is a cash-flow and competitive advantage now, and a plausible obligation later.

What does an Australian supplier do now?

Six steps, in order: choose an accredited provider, register your ABN on the SMP, confirm your software emits PINT A-NZ, layer your validation, open the receiving path, and write down what happens when a send fails. The last two are where most teams under-invest.

• [ ] Choose an Access Point provider on the ATO's register, and check the register yourself rather than taking a claim at face value. What accreditation actually covers is explained in ATO eInvoicing accreditation explained; the shortlisting questions are in how to choose a Peppol Access Point.
• [ ] Register your ABN as a Peppol participant and confirm the SMP record advertises PINT A-NZ, invoices and credit notes.
• [ ] Confirm your software issues PINT A-NZ — ideally software on the ATO's eInvoicing Ready list, or a provider that maps your output for you.
• [ ] Layer your validation: UBL 2.1 schema, then EN 16931 rules, then A-NZ rules, blocking on error. Catching a rejection before the document leaves is an order of magnitude cheaper than after.
• [ ] Open the reception path so inbound Peppol invoices post into accounts payable automatically. Being able to send is half the job, and buyers increasingly expect you to receive.
• [ ] Document the exception path — what happens when a send fails, who is told, and how a disputed invoice is corrected with a credit note on the same profile.

A useful test of readiness: send a real invoice to a real buyer, and watch the acknowledgement come back. A test-bed pass proves the document is valid; a completed exchange proves the addressing, the SMP record and the reception path all work together.

Common Australian pitfalls

1. Sending on a retired profile. Anything still emitting legacy ANZ Peppol BIS is emitting a profile that was withdrawn on 15 May 2025.
2. Validating against the European artefacts. The document passes at your end and is rejected at the buyer's. This is the single most expensive mistake on this list, because everything looks correct locally.
3. Using the wrong identifier. The ABN under scheme 0151 routes the document; an ACN or a free-text name does not.
4. Assuming PDF-by-email is "e-invoicing". It is not. Only a structured document exchanged over the network qualifies, and a PDF attached to a Peppol message is an attachment, not the invoice.
5. Ignoring the reception side, then discovering a Commonwealth buyer expects to send you a document you cannot receive.
6. Rounding drift between the ERP and the validator, which surfaces as intermittent rejections nobody can reproduce.

Where Australia sits in the wider Peppol picture

Australia was among the first countries outside Europe to adopt Peppol as its national e-invoicing framework, and it sits inside a widening Asia-Pacific cluster: New Zealand on the shared PINT A-NZ profile, Japan's PINT JP, Singapore's InvoiceNow and Malaysia's MyInvois alongside it.

For a business trading across those markets, the useful generalisation is that the network is shared and the profiles are not. One Access Point connection reaches all of them; the document your system produces has to change per jurisdiction. That is the work an Access Point provider should be absorbing on your behalf, and it is a fair question to put to one before signing. The global position is tracked in our e-invoicing mandates 2026 tracker.

How GoRoute helps

GoRoute operates a certified Peppol Access Point and SMP (Peppol ID POP000991) and is listed on the ATO's Peppol service provider for Australia, listed on the ATO's register under ClayDesk LLC. We passed Peppol Testbed conformance for PINT A-NZ Billing — invoice and credit note — and A-NZ self-billing, alongside Peppol BIS Billing 3.0, the PINT packs for Oman, the European Union, Japan, Malaysia and Singapore, and the German XRechnung CIUS. One REST API covers Australian issuance, reception and cross-border flows.

If you are weighing providers, read how to choose a Peppol Access Point, check the ATO register yourself, then book a demo.

Sources: ATO eInvoicing; OpenPeppol — Peppol Authorities; Peppol BIS Billing 3.0 specification and its ISO 6523 ICD code list for ABN scheme 0151; Department of Finance and the Digital Transformation Agency for Commonwealth supplier-payment policy. Profile transition dates as published on our PINT A-NZ profile page. Reviewed 28 August 2026.