E-invoicing in Australia: A compliance guide for finance teams (2026)

E-invoicing in Australia is now an active compliance landscape, and there are two more milestones in 2026. 

Non-corporate Commonwealth Entities (NCEs) are already receiving Peppol e-invoices from suppliers, and by July they need 30% of their inbound invoices flowing through the network. By December, they need fully automated sending and receiving. 

For suppliers, that translates to a practical expectation to get Peppol-capable or risk falling behind your buyer’s procurement requirements.

Here’s how the Peppol framework operates in Australia, what the ATO’s role actually is (and isn’t), current breakdowns of essential compliance requirements and how to get your systems connected.

Key highlights:

• E-invoicing for B2G transactions with NCEs has been active since 1 July 2022, so government agencies are already set up to receive Peppol e-invoices from suppliers.
• There are two milestones landing in 2026. By 1 July 2026, NCEs need at least 30% of received invoices processed via Peppol. By December 2026, NCEs need fully automated sending and receiving capabilities.
• B2B e-invoicing remains voluntary. The proposed Business E-Invoicing Right (BER) was not enacted – the government shifted to encouraging voluntary adoption instead.
• PINT A-NZ is the only accepted Peppol format since 15 May 2025. Peppol BIS 3.0 is no longer supported on the network.

What is e-invoicing in Australia?

E-invoicing in Australia is the exchange of structured invoice data directly between accounting systems via the Peppol network, which is a secure and standardised digital framework overseen by the Australian Taxation Office (ATO). 

Unlike a PDF attached to an email or a scanned document uploaded to a portal, a valid e-invoice is machine-readable XML data that travels from the supplier’s system to the buyer’s system. It arrives ready for automated processing, with no manual re-keying required on either end.

A PDF invoice might be digital, but it still needs a person to open it, read the contents and type the data into an accounting system. An e-invoice skips all of that, because the structured data flows between systems automatically and is validated against the PINT A-NZ specification before it even arrives.

How Australian e-invoicing works under Peppol

Australia uses the Peppol four-corner model. Here’s how it works:

1. The supplier creates an e-invoice in their accounting or enterprise resource planning (ERP) system, where the Access Point validates the data and transmits it across the Peppol network
2. On the other side, the buyer’s Access Point receives the invoice and forwards it into the buyer’s ERP, where it’s ready for matching, approval and payment.
3. Australian businesses are identified on the Peppol network using their ABN (Australian Business Number) as their Peppol Participant Identifier.

The ATO’s role in this process is often misunderstood. As the Australian Peppol Authority (APA), the ATO accredits Access Points, governs the network and sets the Australian requirements for the Peppol standard. What it doesn’t do is receive or read individual invoices. 

Currently there is no central government clearance platform. Invoice data flows strictly between trading partners, and GST is still reported through periodic Business Activity Statements (BAS) rather than invoice by invoice. This is different compared to some countries with similar e-invoicing mandates in Europe. 

Australia’s e-invoicing timeline and current requirements

Australia’s e-invoicing mandate is primarily government-facing, meaning the legal obligations sit with Commonwealth government agencies rather than with all businesses. 

That said, the practical effect on suppliers is real and growing, with more than 400,000 Australian businesses already registered on the Peppol network. 

B2G: What’s required now

All NCEs – like federal government departments and agencies – have been required to be able to receive Peppol e-invoices since 1 July 2022. This is a capability requirement, meaning NCEs need the infrastructure to accept e-invoices, though not every inbound invoice has to arrive via Peppol.

For suppliers, the incentive is the “Pay on Time or Pay Interest” policy, where valid e-invoices submitted to Commonwealth entities are paid within five calendar days rather than standard 30-day terms. That payment acceleration alone has driven significant voluntary adoption among government suppliers, though it’s only valid if both the supplier and the buyer have the capability to send and receive e-invoices. 

Corporate Commonwealth Entities (CCEs) and Commonwealth Corporations aren’t currently in scope, but can adopt e-invoicing voluntarily.

Upcoming and new milestones: 2026

The changes happening this year, according to the Australian Taxation Office, include:

• Starting 1 July 2026, NCEs need at least 30% of all received invoices processed via the Peppol network. This created an expectation that government suppliers become Peppol-capable, since agencies will be actively working with their supplier base to hit this number. 
• By December 2026, NCEs need fully automated processing and sending of e-invoices – end-to-end touchless capability, not just receiving. And on an ongoing basis, NCEs report progress against these targets to the Australian Peppol Authority on a quarterly cycle. More than 80% of NCEs are already reporting volume data, and starting from July 2025 the ATO began requesting details on system capabilities and upgrade plans.

So, what does this mean if your business supplies Commonwealth agencies? 

The compliance obligation sits with the government entity, not with your business. But if your biggest buyer is a federal department aiming for 30% Peppol invoices by mid-year, the practical reality is that your organisation will be expected to send e-invoices regardless if the law technically requires it. Agencies are increasingly including e-invoicing as a contractual expectation in procurement agreements.

B2B: Voluntary, but evolving

B2B e-invoicing in Australia is not currently mandatory. 

The government proposed a Business E-Invoicing Right (BER) framework that would have allowed any business to require its trading partners to send Peppol e-invoices, with a phased rollout by company size from 2023 through 2025. That framework wasn’t enacted, and the government shifted its approach toward voluntary adoption and investment incentives instead.

In practice, many businesses are adopting Peppol anyway for efficiency gains, faster payment cycles and reduced invoice fraud. Government-led adoption tends to precede broader mandates, and finance teams that invest in Peppol capability now are building infrastructure that will likely become standard practice across Australian B2B commerce.

The PINT A-NZ format: What you need to know

PINT A-NZ (Peppol International, Australia-New Zealand variation) has been the only accepted specification for e-invoices on the Australian Peppol network since 15 May 2025. If your system is still generating invoices in Peppol BIS 3.0, those invoices will not be accepted on the network. BIS 3.0 was deprecated and is no longer supported.

PINT A-NZ is a joint standard shared between Australia and New Zealand, which enables cross-border e-invoicing between the two countries on a single specification. Invoices are structured XML data with every required field present and validated at the network level before delivery.

Key data fields in PINT A-NZ

There are several key data fields in PINT A-NZ, some of which are required for interoperability and some that may be suggested or conditional based on your circumstances. Here’s what you need to know. 

Required for interoperability:

• Payment due date: Use a structured date rather than text-based payment terms, as systems can process dates automatically
• Seller GST identifier: Legally required in Australia when a GST branch makes a taxable sale (ABN plus three-digit branch number). In New Zealand, the GST number is required if the supplier is GST-registered (note: NZBN is not the GST number)
• Seller contact email: Buyers need a way to raise issues with an invoice without going outside the system
• Buyer contact email: Many buyers use this to route invoices internally to the person or team responsible for approval or goods receipting
• Payee financial account: Bank account details for credit transfer, which buyers use for fraud risk management and internal control checks
• Item description: In addition to the mandatory item name on each invoice line, a description helps buyers with goods receipting and invoice approval
• Reference number: At minimum, a purchase order number or buyer-assigned reference is mandatory under PINT A-NZ. Buyers may also need contract numbers, project numbers or tender references to match invoices with approved spending and route them for approval
• Remittance information: A reference the buyer can include on their payment to help the seller reconcile it against a specific invoice (often the invoice number itself)
• Invoice attachments: Where buyers need supporting documents like timesheets or delivery notes to process the invoice. Attaching a PDF copy of the same invoice data is discouraged unless it adds information not in the XML
• Invoice note: Free-text field for legal or contractual terms that apply to the transaction. Also serves as a fallback for data that the buyer’s system can’t otherwise display

Recommended (as they support faster processing but aren’t always required):

• Discounts or charges: Document-level and line-level allowances and charges, which enable automated matching
• Seller postal address: Particularly useful where multiple branches or businesses trade under the same ABN or NZBN
• Seller trading name: If it differs from the seller’s legal name, helps buyers identify who the invoice is from
• Seller contact name and telephone: Supplements the required seller contact email
• Buyer contact name and telephone: Supplements the required buyer contact email for internal routing

Conditional (which are useful in specific industries or scenarios):

• Purchase order line reference: Supports PO line-level matching for each invoice line item, particularly important in industries that rely heavily on purchase orders
• Buyer trading name: Some buyers use this for internal verification, distinct from the mandatory buyer name field

Benefits of e-invoicing for Australian businesses

When it comes to the benefits of e-invoicing, Australia has a clear compliance case for government suppliers, the efficiency case is compelling for everyone.

• Faster payment from government buyers. Under the “Pay on Time or Pay Interest” policy, valid e-invoices are paid within five calendar days by Commonwealth entities. Compare that to standard 30-day terms and the cash flow impact is obvious, particularly for small and mid-size suppliers where a 25-day improvement in payment timing changes working capital dynamics entirely.
• Lower processing costs. According to estimated costs calculated by Australian Taxation Office, using Deloitte Access Economics data, the cost of processing a paper invoice is  $30.87 AUD, $27.67 per PDF invoice and just $9.18 per structured e-invoice in Australia. For finance teams handling thousands of invoices per month, that cost difference compounds fast. Research from our partner, Avalara, estimates that full e-invoicing adoption could deliver up to $22.5 billion AUD per year in economy-wide benefits.
• Fewer errors and exceptions. Structured data validation at the network level catches missing fields, incorrect ABNs and formatting issues before the invoice reaches the buyer. Problems surface at submission rather than at month-end, which means less back-and-forth over missing purchase order (PO) references or mismatched line items.
• Reduced fraud risk. Access Point authentication and network-level validation reduce exposure to invoice fraud and business email compromise (BEC) scams. The Australian Government’s $23.3 million investment in the e-invoicing network, announced in the 2024–25 Budget as part of a broader $67.5 million anti-scam funding package, reflects how seriously the government views e-invoicing as a fraud prevention tool.
• Future-readiness. More than 400,000 Australian businesses are already registered on the Peppol network, and government-led adoption is accelerating. The BER framework wasn’t enacted, but it may be revisited in the future. Finance teams that invest in Peppol capability now won’t be scrambling to catch up when the next wave of requirements arrives.

How Australian businesses set up Peppol e-invoicing

Whether you’re supplying Commonwealth agencies or preparing for broader B2B adoption, here’s how to connect to the Peppol network and implement e-invoicing.

1. Confirm your scope and obligations

Start by mapping your exposure:

• If you supply goods or services to NCEs, you are likely expected to be Peppol-capable already, especially with the July 2026 target pushing agencies to drive supplier adoption.
• If your buyers are state or territory government bodies, check whether they’ve enabled Peppol receiving. Many organisations in NSW, South Australia, ACT, Tasmania and Victoria have. 
• For pure B2B transactions, adoption is optional but carries clear efficiency advantages.

2. Choose an ATO-accredited Peppol Access Point

Connecting to the Peppol network requires an ATO-accredited Peppol Access Point provider that handles transmission, validation and routing of your e-invoices. The ATO has a register of accredited Peppol service providers as a starting point.

Before signing up with a standalone provider, check whether your existing accounting software already offers Peppol connectivity. Major platforms have added built-in or connected Access Point capabilities. If your ERP already supports Peppol, then integration is significantly simpler.

3. Register your Peppol Participant ID

Australian businesses are identified on the Peppol network using their ABN as the Peppol Participant Identifier. Registration happens through your Access Point provider, which connects your ABN to the network directory so trading partners can find and route invoices to you. 

You can check whether your existing trading partners are already registered using the Peppol Directory.

4. Configure for PINT A-NZ

Your accounting system or ERP needs to generate and receive invoices in PINT A-NZ format. Work with your software vendor or Access Point provider to:

• Validate that invoice templates output all required PINT A-NZ fields
• Update from BIS 3.0 if your system was configured under the older specification
• Confirm that GST amounts, ABN and payment terms are correctly mapped in the XML structure

If you’re running an ERP like SAP, Oracle or Microsoft Dynamics, check for certified e-invoicing modules that handle PINT A-NZ compliance out of the box.

5. Test and validate

Run end-to-end testing before sending live invoices. 

Generate a test PINT A-NZ invoice, transmit it via your Access Point and confirm receipt and processing at the other end. The ATO and major Access Points often offer test environments for this purpose.

Pay attention to Message Level Responses (MLRs), the structured notifications (accepted, rejected, delivered, failed) that provide traceability for every invoice sent through the network. Test at least one credit note in addition to standard invoices to make sure your system handles both document types correctly.

6. Set up record retention

Australian tax law requires e-invoice records to be retained for a minimum of five years. A PDF rendering of the invoice doesn’t satisfy this requirement on its own, as the structured data is the record. Confirm that your accounting system stores and archives the XML and that records remain readable and accessible to the ATO if requested.

Disclaimer: E-invoicing regulations in Australia are actively evolving. The information in this guide reflects publicly available guidance as of mid-2026. Finance teams making compliance decisions based on these requirements are encouraged to verify current status with the ATO’s e-invoicing portal or seek professional advice

‍