Mandatory e-Invoice Fields in Australia: Peppol & PINT A-NZ Data Requirements Explained

By Annapoorna

|

Updated on: Aug 10th, 2026

|

13 min read

social iconssocial iconssocial iconssocial icons

Send an e-invoice in Australia, and it travels over the Peppol network in an e-invoice format spec called PINT A-NZ, where leaving out any mandatory field means it simply won't validate. This article runs through every field you need, the optional ones worth adding, and what the ATO expects on ABN and GST.

Key Takeaways

  • Peppol PINT A-NZ is the e-invoice format spec Australia uses, with the ATO serving as the Australian Peppol Authority (APA), governing the framework locally.
  • Missing one mandatory field can also lead your invoice to failed validation.
  • Your ABN pulls double duty; it's also your address on the Peppol network.
  • No "tax invoice" wording needed. A Peppol e-invoice still counts as one, so long as the mandatory data is there.
  • B2B e-invoicing isn't mandatory in Australia, though Commonwealth agencies had to process 30% of invoices via Peppol by 1 July 2026 while they should automate sending and receiving by December 2026.

Mandatory e-Invoice Fields in Australia

PINT A-NZ became the mandatory Peppol format spec in Australia on 15 November 2024 as it replaced the A-NZ Peppol BIS Billing 3.0, which was phased out in May 2025. Mandatory e-invoice fields are the data elements that must appear in a PINT A-NZ e-invoice for it to validate on the Peppol network and stand as a valid tax invoice. Leave one out, and the invoice won't get through.

So how does e-invoicing work in practice? Your accounting software builds the invoice as structured data, sends it to a certified access point, and that access point checks every mandatory field before passing it to your buyer's software. The fields fall into three groups: invoice, buyer and seller fields.

Invoice Information Fields

These describe the document itself and what you're billing for.

FieldWhat it means
Invoice numberA unique identifier for the invoice
Issue dateThe date you issued the document
Invoice type code380 for an invoice, 381 for a credit note
Currency codeAUD for domestic Australian invoices; use the appropriate ISO 4217 code for cross-border.
Line detailsPer line: description, quantity, unit price and net amount
Document totalsTotal excluding GST, the GST amount and the total payable

Seller Information Fields

Seller nameYour registered business or trading name
Seller ABNYour Australian Business Number, carried as the seller tax identifier with a tax scheme code of 'GST'
Seller addressYour business address
Seller electronic addressYour ABN again, this time as your Peppol network address

One point worth knowing is that if you operate a GST branch, the branch registration number goes here instead. That's your parent entity's ABN with the three-digit branch number tacked on the end.

Buyer Information Fields

Buyer nameThe customer's identity
Buyer electronic addressThe customer's ABN, which routes the invoice to them
Buyer ABNRequired on sales of $1,000 or more, under ATO tax invoice rules
Buyer addressNeeded for processing in most cases

For sales under $1,000, the ATO doesn't insist on the buyer's ABN. Most businesses include it anyway, since it saves reworking the invoice if the customer later asks for a full tax invoice.

Optional e-Invoice Fields in Australia

Not every field is compulsory, but some are near-essential in practice. The ATO calls these required for interoperability. Peppol won't reject you for leaving them out, but your buyer may struggle to process or pay you.

  • Payment terms and due date
  • Bank account details for payment
  • Delivery address and delivery date
  • Seller and buyer contact details
  • Free-text notes
  • Attachments, such as timesheets or supporting paperwork

Some suppliers can't send all fields because their accounting software doesn't support them. If you're the buyer, it pays to ask what your suppliers can actually provide rather than assume.

Reference Number Requirements

Reference fields are where a lot of businesses slip up. A Peppol e-invoice must carry either a buyer reference or a purchase order reference. One or the other. If neither is sent, the invoice fails validation.

  • Buyer reference - a code the buyer gives you so the invoice routes to the right place internally
  • Purchase order reference - the PO number, where one exists
  • Contract reference - optional, but handy for matching against agreements

So a PO number isn't strictly mandatory on its own. What is mandatory is that one of those two reference fields is filled. Many government buyers ask for the PO number specifically, so check what your customer expects.

GST Field Requirements

GST in Australia sits at 10%, and the e-invoicing compliance guidelines under PINT A-NZ handle it in a particular way.

  • Every invoice line needs a tax category code and a tax rate
  • The tax scheme must be set to GST
  • GST amounts appear at document level, not on individual lines
  • A tax subtotal is required for each category used

The common tax category codes are S for standard-rated supplies, Z for GST-free sales, E for exempt, and O for anything outside the scope of GST. Getting the category right matters, because it drives how the sale is treated.

Two details are worth noting. Where GST works out to a fraction of a cent, rounding rules apply; round to the nearest cent on a single taxable sale. And if you deal in wine equalisation tax or luxury car tax, keep those separate from your GST lines.

Automating e-Invoicing with ClearTax

ClearTax, a reliable global e-invoicing solution provider, that could help businesses comply with e-invoicing:

  • Seamless ERP & POS Integration: Invoices are sent automatically and routed over the Peppol network, ensuring compatibility with local requirements.
  • Real-Time Compliance Verifications: Validates invoices against local regulations and invoice formats.
  • Cloud-Based e-Invoicing Portal: Facilitates easy monitoring, reconciliation, and management of e-invoices.
  • Automated Compliance and Reporting Alerts: These alerts keep businesses updated with the latest regulations, minimising the risks of delays and inaccuracies.

Conclusion

Ensure your Australian invoice includes the invoice, seller and buyer fields, a buyer or PO reference, and correct GST categories. Add the optional fields your customers need. Do that, and your invoices will move through Peppol and get paid on time.

Frequently Asked Questions

What are the mandatory fields in an e-invoice?

The invoice number, issue date, invoice type code, currency, line details and totals. Plus the seller's name and ABN, the buyer's name and electronic address, a buyer or PO reference, and the GST fields.

What happens if the mandatory fields are not filled out?

The invoice fails validation at the Peppol access point and never reaches your buyer. It also may not qualify as a valid tax invoice, which affects your customer's GST credit claim.

Is an ABN required on an e-invoice?

Yes, the seller's ABN is mandatory on every tax invoice. The buyer's ABN is required for sales of $1,000 or more. Your ABN also acts as your Peppol network address.

Is a PO number mandatory on a Peppol e-invoice?

Not on its own. Peppol requires either a buyer reference or a purchase order reference. Many government buyers ask for the PO number specifically, so check with your customer.

What is the difference between mandatory and optional e-invoice fields?

Mandatory fields must be present, or the invoice fails validation. Optional fields, like payment terms and bank details, aren't required by Peppol but often help your buyer process and pay you faster.

Do both the buyer and seller ABN need to appear on an e-invoice?

The seller's ABN always. The buyer's ABN is required for sales of $1,000 or more, though most businesses include it regardless.

What are the GST fields required on an e-invoice?

A tax category code and tax rate on each line, the tax scheme set to GST, a tax subtotal per category, and the GST amount at the document level.

About the Author
author-img

Annapoorna

Manager - Content
social icons

I preach the words, “Learning never exhausts the mind.” An aspiring CA and a passionate content writer having 8+ years of hands-on experience in deciphering jargon in Indian GST, Income Tax, off late also into the much larger global compliance ecosystem spanning SEA, GCC, USA and EU. I love curating content in various forms to the interest of tax professionals, and enterprises, both big and small. While not writing, you can catch me singing Shāstriya Sangeetha and tuning my violin ;). Read more

Index