E-Invoicing Compliance in Australia: Peppol Without Rekeying
Get invoices into your system without anyone typing them
E-invoicing compliance in Australia means connecting to the Peppol network through an accredited access point, so invoices move between your software and your trading partners' software as structured data. Commonwealth agencies now treat Peppol as the default channel for procurement invoices. No law requires Australian businesses to e-invoice each other.
That leaves most finance teams with two jobs. Send and receive e-invoices for the buyers and suppliers who are ready. Then deal with the PDFs that keep arriving by email, which is where AI extraction with a person approving each invoice does the work.
What is Peppol e-invoicing? Peppol is an international framework for exchanging invoices and other procurement documents through a network of accredited service providers called access points. In Australia the ATO is the Peppol Authority. It sets the Australian invoice specification, accredits access points and cannot see the contents of any e-invoice.
This guide is for the CFO, finance manager or accounts payable lead whose business sells to government, runs several entities, or has an AP inbox that grows faster than the team. Every rule below was checked against ATO, Department of Finance and state government pages on 25 October 2026.
Working out whether this fits your business? Book a free 30-minute review
What do the rules require as at 25 October 2026?
What applies to you depends on who you sell to.
| Who | What applies | Source |
|---|---|---|
| Non-corporate Commonwealth entities (departments and most agencies) | Must be able to receive e-invoices (since 2022). E-invoicing is the default channel for procurement invoices. Target of 30% of invoices received via e-invoice by 1 July 2026. Automated processing and sending of e-invoices by December 2026. | ATO, eInvoicing for government |
| Commonwealth payment terms until 31 December 2026 | 5 calendar days for e-invoices where both sides use Peppol and agreed to it. 20 calendar days for other invoices. | Finance, RMG 417 (current) |
| Commonwealth payment terms from 1 January 2027 | 10 business days for all forms of invoice, Peppol or not. | Finance, Procurement Policy Note |
| NSW Government agencies | All agencies must accept e-invoices (from 1 January 2022). | buy.nsw |
| Other states and territories | All SA and ACT agencies can receive. Most Tasmanian agencies can receive. Many Queensland agencies can receive and send. WA is running a program. Victoria has committed. | ATO, eInvoicing for government |
| Business to business | No mandate. Adoption is voluntary. | ATO; Treasury consultations 2020 to 2022 |
Corporate Commonwealth entities are encouraged to follow both the e-invoicing and payment policies but are not bound by them.
Why does e-invoicing matter to a finance team right now?
The Australian Government has said it will make e-invoicing the default method for exchanging invoices in its procurement. The ATO's guidance tells agencies to ask high-volume suppliers to move to e-invoicing and to raise it at contract renewals. If you hold Commonwealth contracts, expect that conversation.
The government's stated reasons are productivity and disrupting payment redirection scams. A Peppol invoice travels between accredited access points and is routed by ABN, so there is no emailed PDF for someone to alter on the way.
The payment term story changes on 1 January 2027. Under the current Supplier Pay On-Time or Pay Interest Policy, an e-invoice gets a 5 calendar day maximum and anything else gets 20. Under the updated policy, every eligible invoice gets 10 business days, however it arrives.
So the case for Peppol with Commonwealth buyers shifts. The clock only starts once the agency holds a correctly rendered invoice and has accepted delivery. A Peppol invoice is validated by the sending and receiving access points, so missing fields are caught before it lands. With PDFs, the gap often shows up only when the agency sends the invoice back.
PDF by email compared with a Peppol e-invoice
| Metric | PDF by email | Peppol e-invoice | Improvement |
|---|---|---|---|
| How it reaches the buyer | Email attachment to a shared inbox | Access point to access point, routed by ABN | No inbox step |
| Getting data into the system | Keyed by hand or read by OCR or AI | Arrives as structured data | No rekeying |
| Tax invoice format | Depends on the supplier's template | Australian A-NZ specification supports GST | Consistent fields |
| Altered bank details risk | PDF can be edited or spoofed in transit | Sent between accredited providers | Lower exposure |
| Commonwealth term to 31 Dec 2026 | 20 calendar days | 5 calendar days (if both agreed) | Faster for now |
| Commonwealth term from 1 Jan 2027 | 10 business days | 10 business days | Same term |
Is there a B2B e-invoicing mandate in Australia?
No. As at 25 October 2026 we found no law that requires Australian businesses to send or receive e-invoices with each other.
Treasury consulted on options for mandatory business adoption in 2020 and 2021, and then on a proposed Business eInvoicing Right in 2021 and 2022. That right would have let a business require its trading partners to accept e-invoices. We could not find any legislation that followed from either consultation.
The ATO describes e-invoicing as "not a compliance or revenue measure" and says the ATO receives no copy of any e-invoice. Its guidance for businesses says you can adopt e-invoicing at a pace that suits you.
The pressure on private businesses comes from customers. Government buyers are asking their suppliers to move to Peppol, and any private buyer already receiving through Peppol can ask the same.
How do you set up Peppol e-invoicing?
Setup has four parts, and the ATO's own guide for medium and large businesses follows the same order.
1. Count what you send and receive
List your top suppliers and customers by invoice volume, and how each invoice arrives today. Note which ones use purchase orders and whether you match on two or three ways. The ATO suggests starting with a few partners who send high volumes with simple requirements.
2. Choose how you connect
You need software that can produce or take in the invoice data, and an accredited access point to reach the network. Some accounting packages include the access point. Xero, for example, lets an Australian business register for Peppol from inside Xero using its ABN, and received e-invoices land as draft bills. The ATO links to MYOB's step-by-step guides for registering, sending and receiving.
ERPs vary. Some have a connector, some need a separate access point provider and an integration. Check your product on the ATO's eInvoicing Ready product register before you assume either way.
3. Register every entity that invoices
The ABN is the identifier used to route e-invoices in Australia. A group with several trading entities registers each one that sends or receives invoices under its own ABN. Once registered to receive, your access point lists you in the Peppol Directory, which only lists receivers.
The business name in your software should match the Australian Business Register. Xero, for one, says registration needs that match.
4. Onboard trading partners in waves
Use the Peppol Directory to see which suppliers and customers can already receive. Start with high-volume partners, then those with high error rates. Keep the old channels open while each wave moves across.
Running several Xero organisations or a mix of ERP and Xero? Each entity's Peppol registration sits with the system that holds its ledger. Our guide to consolidating multiple Xero organisations covers keeping entity data consistent across them.
Where should your e-invoicing work start?
Supplier PDFs read, checked and coded before anyone opens them
Peppol will not empty your inbox. The Commonwealth's own target was 30% of invoices received by e-invoice by 1 July 2026, which assumes most invoices will still arrive some other way for a while. The ATO reports more than 400,000 Australian businesses on the network, and plenty of your suppliers will not be among them.
Consider a hypothetical group with four trading entities, an ERP at head office and Xero in two acquired subsidiaries. It receives about 3,000 supplier invoices a month and holds Commonwealth and state contracts. Even if a fifth of its supplier invoices moved to Peppol within a year, 2,400 a month would still arrive as PDFs.
For those, AI extraction reads the PDF into the same fields a Peppol invoice would carry. Then the same checks run on both channels, and a person approves before anything posts.
How a supplier invoice reaches payment without rekeying
The AI step lives inside your own tenant, in an Australian region, connected to the ledger you already run. Our data sovereignty guide explains why that matters for supplier bank details and pricing.
For the general mechanics of extraction, accuracy testing and Xero or MYOB integration, see our complete guide to automating invoice processing. This post stays on the e-invoicing and compliance side.
Duplicates, wrong ABNs and changed bank details caught before payment
Two channels create a new failure mode. A supplier moves to Peppol but its old template still emails a PDF copy, and the same invoice arrives twice by different routes. Your controls need to run across both channels, after extraction, on the same fields.
| Control | What it checks | What happens when it fails |
|---|---|---|
| ABN check | Supplier ABN is active and matches the vendor master, using the Australian Business Register's ABN Lookup | Invoice held, AP asked to confirm the supplier |
| GST registration | Supplier is registered for GST if GST is charged | Held for review before any GST credit is claimed |
| Duplicate detection | Same supplier, invoice number and amount, plus near matches across Peppol and email | Second copy blocked and linked to the first |
| PO and receipt match | Two or three way match against the purchase order and goods receipt | Variance routed to the buyer who raised the PO |
| Bank detail change | Remittance details differ from the vendor master | Payment held until AP confirms by phone on a number already on file |
| Approval limits | Amount sits within the approver's delegation | Routed up to the next delegate |
The bank detail rule is the one to get right first. It protects you from payment redirection on the PDF channel, which is the risk Peppol was meant to reduce in the first place.
Selling to government as well as buying? Tender and contract obligations often specify invoicing requirements. Our post on AI for government contractors and tender compliance covers how to keep those obligations visible after award.
How does AI handle invoices safely before it goes live?
The risk with AI on accounts payable is a wrong field reaching a payment run. The control is a staged rollout where the AI runs beside your team first, and nothing pays until it meets an accuracy threshold you set.
In shadow mode, the AI reads every PDF and proposes fields and codes, while your team keeps processing as normal. Each week you compare its output with what your team entered, field by field. When it meets your threshold, it moves to co-pilot mode: it drafts, and a person approves every invoice.
Trusted mode, where low-risk invoices from known suppliers get lighter review, stays a later decision for your finance team. It is never part of a pilot.
Phased rollout for e-invoicing and PDF capture
Each phase ends at an exit point. You can proceed, pause or stop, and you keep everything delivered so far.
Having worked on data platform and reporting programs in mining and energy, the lesson that carries straight over to AP is that master data decides the result. If one supplier sits in the vendor master twice with different ABNs, no extraction model and no Peppol connection will fix the duplicate payment risk. Phase 1 cleans that first.
What should you measure before and after?
Start with a baseline so the result is a number your CFO can check. The figures below are a worked example for the hypothetical group above, not a forecast. Replace them with your own counts.
Worked example: where 3,000 monthly invoices go (illustrative)
Track four numbers from the first week: invoices by channel, invoices sent back to suppliers as incorrectly rendered, duplicates caught before payment, and days from receipt to approval. The last one matters most if you are a Commonwealth supplier, because the agency's clock starts only when it holds a correct invoice.
For the wider cost of manual keying and what automation tends to replace, our honest guide to invoice automation covers the trade-offs. If the work extends into ERP or approval workflow changes, that sits within our process automation service.
Your next step
Pull last quarter's supplier invoices and count them by entity and by channel: Peppol, EDI, portal, PDF and paper. That one table tells you whether to start with Peppol registration, AI on the PDFs, or both.
The lead on every engagement spent 18 years on operations and data systems for BHP, Rio Tinto and Senex Energy, gained while working with previous consulting employers. These companies are not Solve8 clients.
Book a scoping call and leave with a straight answer on which entities to register first, and whether AI on your remaining PDF invoices is worth piloting.
Common Questions
Is e-invoicing mandatory for Australian businesses?
No. As at 25 October 2026 there is no law requiring Australian businesses to e-invoice each other. Commonwealth agencies must be able to receive e-invoices and treat Peppol as the default for procurement, so suppliers to government will be asked to use it.
Do Commonwealth agencies still pay e-invoices within 5 days?
Until 31 December 2026, non-corporate Commonwealth entities must pay eligible e-invoices within 5 calendar days where both sides agreed to use Peppol. From 1 January 2027, all eligible invoices have a 10 business day maximum, whether they arrive by Peppol or another method.
What is a Peppol access point?
An access point is an accredited service provider that sends and receives e-invoices on the Peppol network for your business. Some accounting packages include one in the subscription. Larger ERPs often connect through a separate provider. The ATO accredits access points in Australia.
Can Xero and MYOB send and receive e-invoices?
Yes. Xero lets an Australian business register for Peppol inside Xero using its ABN, and received e-invoices arrive as draft bills. The ATO links to MYOB's own guides for registering, sending and receiving. Check any ERP on the ATO's eInvoicing Ready product register.
What happens to invoices that still arrive as PDFs?
They need to be read into your system some other way. AI extraction can read each PDF into the same fields a Peppol invoice carries, then the same ABN, duplicate, PO and bank detail checks run, and a person approves every invoice before it posts.
Does each entity in a group need its own Peppol registration?
Each entity that sends or receives invoices under its own ABN registers separately, because the ABN is what routes an e-invoice in Australia. Map every ABN to the ledger that holds its bills before you register, especially after acquisitions.
Related Reading:
- Automate Invoice Processing with AI in Australia: Xero and MYOB - The full how-to for AI invoice extraction, accuracy testing and accounting integration.
- Invoice Automation Australia: The Honest Guide - Where invoice automation pays off and where it does not.
- AI for Government Contractors: Tender Compliance - Keeping tender and contract obligations visible when you sell to government.
- Consolidate Multiple Xero Organisations: Guide - Keeping entity data consistent across a group running several Xero files.
Sources: ATO, About eInvoicing (updated 7 July 2026), About Peppol (updated 22 July 2026), eInvoicing for government and eInvoicing by default guidance (both updated 13 October 2026), eInvoicing for businesses (updated 8 October 2025) and Getting started with eInvoicing for medium and large businesses (updated 3 September 2026); Department of Finance, Supplier Pay On-Time or Pay Interest Policy (RMG 417), the updated RMG 417 effective 1 January 2027, and the Procurement Policy Note on Updated Commonwealth Supplier Payment Terms (all accessed 25 October 2026); buy.nsw, e-Invoicing help page; Queensland Government, Queensland Shared Services eInvoicing project (updated 25 June 2025); Treasury, Supporting business adoption of electronic invoicing consultation paper (December 2021); Xero, Send and receive eInvoices with Xero (accessed 25 October 2026).