Peppol e-invoicing in Australia now runs on PINT A-NZ, and Commonwealth agencies face 2026 targets. Here is what that means for SAP S/4HANA, ECC and Business One users, and a 6-step rollout plan.
By SAVIC SAP Practice · 125+ S/4HANA Cloud implementations · Nov 9, 2026 · 11 min read
SAP Peppol E-Invoicing in Australia: The Short Answer
SAP Peppol e-invoicing in Australia means sending and receiving structured invoices from SAP in the PINT A-NZ format through an ATO-accredited Access Point. B2B e-invoicing is voluntary, but Commonwealth agencies must reach 30% Peppol invoice receipt by 1 July 2026 and fully automated sending and receiving by December 2026 — and they pay eligible e-invoices within five days. For most SAP landscapes, a focused rollout takes 6 to 12 weeks.
How Peppol E-Invoicing Works in Australia
Peppol is an international standard for exchanging invoices between finance systems. Australia adopted it in 2019, and the ATO became the country's Peppol Authority on 31 October 2019.
The model is a "four-corner" network:
- Your SAP system creates the invoice as structured data.
- Your Access Point validates it and sends it across the Peppol network.
- Your customer's Access Point receives it.
- Your customer's finance system imports it — no re-keying, no PDF.
Two details matter for SAP teams. First, your ABN is your Peppol participant ID, so ABN data quality in SAP becomes critical. Second, the ATO governs the network but does not receive or see your invoices. There is no clearance step, unlike e-invoicing regimes in Saudi Arabia or Malaysia — GST is still reported through your Business Activity Statement.
The ATO has confirmed that a compliant e-invoice is a valid tax invoice. Read the ATO's own guidance on eInvoicing in Australia.
Is E-Invoicing Mandatory in Australia? The 2026 Timeline
For businesses, no. For the Australian Government, increasingly yes. Here is where things stand:
| Date | What applies |
|---|---|
| 31 Oct 2019 | ATO becomes Australia's Peppol Authority |
| 1 Jul 2022 | Non-corporate Commonwealth entities must be able to receive Peppol e-invoices; eligible e-invoices paid within 5 days |
| 15 May 2025 | PINT A-NZ becomes the only accepted format; A-NZ BIS Billing 3.0 retired |
| 1 Jul 2026 | Target: at least 30% of invoices received by Commonwealth agencies via Peppol |
| Dec 2026 | Target: Commonwealth agencies automate receiving and start sending Peppol e-invoices |
| B2B | Voluntary — no national B2B mandate has been legislated |
The five-day payment term comes from the Department of Finance's Supplier Pay On-Time or Pay Interest Policy (RMG 417). Other invoices are paid within 20 days. If you invoice the Commonwealth, e-invoicing cuts your payment cycle by two weeks.
The practical implication: "voluntary" does not mean "optional for long". Large buyers — government first, then their supply chains — are moving their accounts payable onto Peppol. Suppliers who can't send e-invoices will increasingly be the exception that slows the queue.
Benefits of Peppol E-Invoicing for Australian SAP Users
The compliance case is modest today. The business case is not. For organisations already running SAP, Peppol removes the last manual step between two ERP systems.
- Faster payment from government: eligible e-invoices to Commonwealth agencies are paid in 5 days, not 20. For a supplier billing A$2 million a year to government, that is roughly two weeks of working capital released.
- Fewer disputes: structured data means no misread totals, missing purchase order numbers or invoices lost in a shared inbox.
- Lower processing cost: on the receiving side, matching a structured invoice against a purchase order costs a fraction of keying a PDF.
- Better fraud controls: invoices arrive only from registered Peppol participants identified by ABN, which makes fake-invoice scams harder.
- Cleaner audit trail: every invoice has a delivery status, so "we never received it" stops being a reason for late payment.
In practice, the benefits compound once both sending and receiving run through SAP. The finance team's work shifts from processing invoices to resolving the exceptions — which is where their time should have gone in the first place.
PINT A-NZ: The Format Your SAP System Must Produce
PINT A-NZ is the Peppol International invoice specification for Australia and New Zealand. Since 15 May 2025 it is the only format the network accepts. If your SAP e-invoicing was built for the older BIS Billing 3.0, it needs updating.
An Australian e-invoice has to satisfy two sets of rules at once:
- PINT A-NZ technical rules — structure, code lists, validation.
- ATO tax invoice rules — supplier ABN, GST amounts, dates and description of supply.
In SAP terms, most failures trace back to three places: missing or invalid ABNs on customer and vendor master records, GST tax codes that don't map cleanly to PINT tax categories, and units of measure or item descriptions that were never designed to leave the system. SAVIC sees the same pattern across e-invoicing work in every country: the format is the easy part. The master data is the project.
SAP E-Invoicing Options in Australia by Product
Your route to Peppol depends on which SAP product you run.
| SAP product | Typical approach | Watch out for |
|---|---|---|
| SAP S/4HANA (Public or Private Cloud) | SAP Document and Reporting Compliance (eDocument Australia) with SAP's Peppol service or a connected Access Point | Release level and required SAP notes; PINT A-NZ support in your version |
| SAP ECC 6.0 | Integration with an Access Point provider, via middleware or SAP Integration Suite | ECC mainstream maintenance ends 31 Dec 2027 — design it to be reused after migration |
| SAP Business One | Add-on or connector from an Access Point provider | Version compatibility and per-document pricing |
| SAP Ariba / SAP Business Network | SAP Business Network's Peppol integration for Australia and New Zealand | Which documents flow through the network versus directly from ERP |
SAP documents its e-invoicing coverage under SAP Document and Reporting Compliance. For a deeper look at how DRC works across countries, see our SAP DRC enterprise guide.
Receiving Supplier E-Invoices: The Half Most Projects Skip
Most Australian e-invoicing projects start with sending, because that is what customers ask for. The bigger return is usually on the other side.
When suppliers send Peppol e-invoices, the data arrives structured. In SAP, that means invoices can be matched to purchase orders and goods receipts automatically, with exceptions routed to accounts payable — instead of someone keying a PDF. ATO figures put the cost of processing a paper invoice at around A$30, against about A$9 for a structured e-invoice.
Our view: if you are touching SAP billing for Peppol anyway, scope receiving at the same time. The Access Point, master data and testing effort are largely shared, and accounts payable automation is where finance teams feel the difference.
What SAVIC Has Learned from PINT-Based E-Invoicing Elsewhere
Australia is not the first PINT country. Singapore's InvoiceNow runs on the same Peppol International family, and SAVIC delivers it for SAP S/4HANA, ECC and Business One — see our InvoiceNow guide for SAP users. In the UAE, SAVIC is implementing SAP Document and Reporting Compliance for Leader Healthcare Group ahead of mandatory e-invoicing.
Three lessons carry straight over to Australia:
- Decide the order with S/4HANA first. Companies that treat e-invoicing as a separate project often build it twice — once on ECC, again on S/4HANA. Across 125+ S/4HANA Cloud implementations, the cheapest e-invoicing is the one designed into the migration.
- Clean master data before mapping. ABNs, tax codes and customer contact data cause more test failures than the XML itself.
- Give rejections an owner. A daily report of rejected or undelivered e-invoices, with a named person in finance, prevents silent payment delays.
How to Implement SAP Peppol E-Invoicing: A 6-Step Plan
1. Confirm your scope
List who you invoice (Commonwealth agencies, large corporates, overseas customers) and who invoices you. Decide whether you are sending, receiving or both.
2. Choose an Access Point
Pick an ATO-accredited Access Point that supports your SAP product, PINT A-NZ, your volumes, and both directions if you need them.
3. Clean your master data
Validate every customer and vendor ABN, check GST tax codes map to PINT tax categories, and register your own ABN as a Peppol participant.
4. Map your invoice types
Cover tax invoices, credit notes and adjustment notes. Foreign-currency invoices, partial credits and intercompany billing cause most test failures.
5. Test end to end
Send test invoices to real trading partners, confirm delivery and rejection messages flow back into SAP, and check the five-year retention of the XML.
6. Go live and monitor
Run a hypercare period with a daily rejection report, then hand monitoring to your SAP support team.
Peppol and Your SAP ECC 2027 Plans
SAP ECC mainstream maintenance ends on 31 December 2027. Many Australian companies will face their S/4HANA migration and their customers' e-invoicing demands in the same 18 months. That is an argument for planning both together. See our ECC to S/4HANA migration options.
Why SAVIC
SAVIC Technologies has delivered 125+ S/4HANA Cloud implementations for 485+ customers in 15+ countries. That is the base we write from. Not press releases. In Australia, we operate as SAVIC PTY LTD from 34 Sampson Road, Mitchell Park SA 5043 (+61 449 799 134), backed by our APAC teams in Singapore and Malaysia who already deliver PINT-based e-invoicing.
We scope Peppol as part of the wider SAP picture — Access Point selection, master data, PINT A-NZ mapping, accounts payable automation and your S/4HANA timeline. See our SAP services in Australia, or compare options in our guide to the top SAP implementation partners in Australia.
Frequently Asked Questions
Is e-invoicing mandatory in Australia?
Not for business-to-business invoicing. B2B e-invoicing in Australia is voluntary, and the proposed Business eInvoicing Right was never enacted. The obligations sit with non-corporate Commonwealth entities, which must be able to receive Peppol e-invoices and are working towards 2026 targets. Businesses that sell to the Australian Government have the strongest reason to adopt now, because eligible e-invoices are paid within five days.
What is Peppol e-invoicing in Australia?
Peppol is the international standard and network Australia adopted for e-invoicing. Businesses exchange structured invoices between their finance systems through accredited Access Points, instead of emailing PDFs. The ATO is Australia's Peppol Authority: it accredits Access Points and governs the network, but it does not receive or see the invoices. Your ABN is used as your Peppol participant ID.
What is PINT A-NZ?
PINT A-NZ is the Peppol International invoice specification used in Australia and New Zealand. It became available in November 2024 and has been the only accepted format since 15 May 2025, replacing the earlier A-NZ Peppol BIS Billing 3.0. An e-invoice must meet both the PINT A-NZ technical rules and the ATO's GST tax invoice requirements. Any SAP e-invoicing solution you use must produce PINT A-NZ.
Do I need a Peppol Access Point to send e-invoices in Australia?
Yes. Peppol e-invoices can only be sent and received through an ATO-accredited Access Point. For SAP users, the Access Point is either SAP's own service, used through SAP Document and Reporting Compliance, or a third-party provider integrated with SAP. The choice depends on your SAP product, invoice volumes and whether you also need to receive supplier e-invoices.
Does SAP support Peppol e-invoicing in Australia?
Yes. SAP Document and Reporting Compliance supports Australian Peppol e-invoicing in the PINT A-NZ format for SAP S/4HANA, and SAP Business Network integrates with Peppol for Australia and New Zealand. SAP ECC and SAP Business One are usually connected through an Access Point provider's integration or add-on. Confirm the exact release requirements and SAP notes for your system before you scope the project.
How long do e-invoices need to be retained in Australia?
At least five years, the same as other tax records. For a Peppol e-invoice, the structured XML is the record — not a PDF rendering of it. Make sure your SAP archiving and Access Point retention settings keep the XML, its status messages and any attachments for the full period.
How long does an SAP Peppol e-invoicing project take?
For a single Australian company code with standard invoice types, a focused SAP Peppol project typically takes 6 to 12 weeks. That covers Access Point onboarding, ABN and master-data clean-up, PINT A-NZ mapping and end-to-end testing. Multiple entities, receiving supplier e-invoices, self-billing or very high volumes add time.
Should we implement Peppol before or after moving from SAP ECC to S/4HANA?
If your S/4HANA go-live is close, build Peppol on S/4HANA as part of the migration so you only do it once. If you need e-invoicing sooner — for example, to get paid faster by Commonwealth agencies — connect ECC through an Access Point integration that can be reused after migration. Either way, remember SAP ECC mainstream maintenance ends on 31 December 2027.
Last reviewed: Nov 2, 2026 by SAVIC SAP Practice
Frequently Asked Questions
Is e-invoicing mandatory in Australia?
Not for business-to-business invoicing. B2B e-invoicing in Australia is voluntary, and the proposed Business eInvoicing Right was never enacted. The obligations sit with non-corporate Commonwealth entities, which must be able to receive Peppol e-invoices and are working towards 2026 targets. Businesses that sell to the Australian Government have the strongest reason to adopt now, because eligible e-invoices are paid within five days.
What is Peppol e-invoicing in Australia?
Peppol is the international standard and network Australia adopted for e-invoicing. Businesses exchange structured invoices between their finance systems through accredited Access Points, instead of emailing PDFs. The ATO is Australia's Peppol Authority: it accredits Access Points and governs the network, but it does not receive or see the invoices. Your ABN is used as your Peppol participant ID.
What is PINT A-NZ?
PINT A-NZ is the Peppol International invoice specification used in Australia and New Zealand. It became available in November 2024 and has been the only accepted format since 15 May 2025, replacing the earlier A-NZ Peppol BIS Billing 3.0. An e-invoice must meet both the PINT A-NZ technical rules and the ATO's GST tax invoice requirements. Any SAP e-invoicing solution you use must produce PINT A-NZ.
Do I need a Peppol Access Point to send e-invoices in Australia?
Yes. Peppol e-invoices can only be sent and received through an ATO-accredited Access Point. For SAP users, the Access Point is either SAP's own service, used through SAP Document and Reporting Compliance, or a third-party provider integrated with SAP. The choice depends on your SAP product, invoice volumes and whether you also need to receive supplier e-invoices.
Does SAP support Peppol e-invoicing in Australia?
Yes. SAP Document and Reporting Compliance supports Australian Peppol e-invoicing in the PINT A-NZ format for SAP S/4HANA, and SAP Business Network integrates with Peppol for Australia and New Zealand. SAP ECC and SAP Business One are usually connected through an Access Point provider's integration or add-on. Confirm the exact release requirements and SAP notes for your system before you scope the project.
How long do e-invoices need to be retained in Australia?
At least five years, the same as other tax records. For a Peppol e-invoice, the structured XML is the record — not a PDF rendering of it. Make sure your SAP archiving and Access Point retention settings keep the XML, its status messages and any attachments for the full period.
How long does an SAP Peppol e-invoicing project take?
For a single Australian company code with standard invoice types, a focused SAP Peppol project typically takes 6 to 12 weeks. That covers Access Point onboarding, ABN and master-data clean-up, PINT A-NZ mapping and end-to-end testing. Multiple entities, receiving supplier e-invoices, self-billing or very high volumes add time.
Should we implement Peppol before or after moving from SAP ECC to S/4HANA?
If your S/4HANA go-live is close, build Peppol on S/4HANA as part of the migration so you only do it once. If you need e-invoicing sooner — for example, to get paid faster by Commonwealth agencies — connect ECC through an Access Point integration that can be reused after migration. Either way, remember SAP ECC mainstream maintenance ends on 31 December 2027.
