For suppliers to government and large enterprise, and the finance teams who receive their invoices

Peppol eInvoicing Integration: Connecting Your ERP to the Network Properly

Peppol is not a nicer way to email a PDF. It is an international network and document standard that moves an invoice as structured data, from your system to your customer’s system, through accredited access points. In Australia the ATO acts as the Peppol Authority: it accredits access points and sets the Australian specification, but it does not see or store your invoices. Your customer’s accounts payable system receives the invoice as fields, not as a picture, and can process it without anyone retyping it.

For many small businesses, the e-invoicing feature already built into their accounting software is all they need, and we will say so. The work starts when your invoices come out of an ERP with no native Peppol support, when a government or enterprise customer rejects invoices for missing references, or when you want supplier e-invoices to land in accounts payable already matched to the purchase order and goods receipt. This page covers how the network works, what goes wrong in the data, and how to integrate it so invoices get paid rather than bounced.

Review Your eInvoicing Setup (03) 9003 0111

The Shape of a Peppol Integration

4 corners

Sender, two access points, receiver

You connect to your access point once, and it reaches every registered receiver

1 identifier

Your ABN on the network

Participants are found by ABN, so it must match your invoices and the customer’s records

2 document types

Invoices and credit notes

Both must map cleanly from the ERP, and credit notes are where most first builds fail

2 paths

Peppol or PDF per customer

Until every customer is registered, each invoice needs a reliable routing decision

Why Peppol Works Differently from What You Have Now

Most finance teams compare Peppol with emailed PDFs or with retailer EDI. It is neither, and the differences decide how the integration should be built.

A PDF is a picture, an e-invoice is data

An emailed PDF has to be opened, read and keyed, or scanned with character recognition that guesses at the layout. A Peppol e-invoice carries the supplier ABN, buyer reference, line items, quantities, unit prices, tax category and totals as defined fields that the receiving system reads directly. That means the buyer can validate it automatically against the purchase order, and the invoice can be rejected within minutes for a real data problem, rather than sitting in someone’s inbox for a fortnight before anyone notices it was addressed to the wrong cost centre.

EDI is bilateral, Peppol is a network

Retail EDI is set up partner by partner. Each retailer publishes its own specification, testing and certification, and connecting to a second retailer is largely a second project. Peppol works more like the phone network. You connect once, through one accredited access point, and can exchange invoices with any business or agency registered on the network in Australia, New Zealand and other Peppol countries, using a shared specification. You still need clean data, but you do not need a separate mapping for every customer.

Government buyers are already set up to receive

Non-corporate Commonwealth entities have been required to be able to receive Peppol e-invoices since 1 July 2022, and many state agencies and large enterprises receive them too. For suppliers, the Commonwealth supplier pay on time policy offers faster payment for eligible e-invoices, typically within five days. Check the current terms and thresholds, because scope and conditions are set by policy and can change. Even where faster payment does not apply, an invoice that arrives as data is less likely to be lost or keyed wrongly at the agency end.

The sender is identified, not just an email address

Invoice redirection scams work by sending a convincing PDF from a spoofed or compromised mailbox with new bank details. On Peppol, an invoice arrives through accredited access points from a sender registered against an ABN, which makes impersonation considerably harder. It does not remove fraud risk entirely, since a genuine supplier can still be compromised or send altered bank details, but it removes the easiest route. Bank detail changes should still be verified out of band, whatever channel an invoice arrives on.

How a Peppol Integration Is Put Together

Six components. Some come ready made in your accounting platform, some have to be built around an ERP. Knowing which is which is most of the scoping.

One route onto the network

Access point connection

Every participant connects through an accredited access point. If you use Xero, MYOB or another cloud platform with e-invoicing built in, the platform is effectively your access point and there is little to integrate. If invoices are produced in an ERP without native support, you contract an access point provider and send them invoice data through its API or file interface. Choose on interface quality, delivery status reporting, credit note support and how rejections are returned, not on price per invoice alone, because those details decide how much exception handling you build.

Know who can receive

Registration and directory lookup

Your access point registers your ABN as a participant, along with the document types you can send and receive. Before sending, the integration should look up the customer’s ABN through the network’s service metadata and directory, which tells you whether they are registered and for which documents. Cache the result with a date and refresh it regularly, because customers join over time. A customer who is registered for invoices but not for credit notes is a real case and needs a defined fallback rather than a failed send.

Invoices that validate first time

Outbound mapping from the ERP

The ERP invoice is mapped to the current A-NZ specification, known as PINT A-NZ and earlier as A-NZ Peppol BIS Billing 3.0. That means supplier and buyer ABNs, the buyer reference or purchase order number the customer requires, line quantities with valid unit codes, the tax category and rate for each line, document level allowances and charges such as freight, and totals that reconcile exactly. Validation runs before sending, so an invoice that would be rejected is held and corrected inside your business rather than bouncing from the customer.

Supplier invoices ready to approve

Inbound into accounts payable

Received e-invoices arrive as data, so there is no character recognition step. The integration matches supplier ABN to the vendor record, finds the purchase order from the order reference, and compares lines with the order and the goods receipt in a three way match. Matching invoices go straight to approval or posting within tolerance. Price variances, quantity shortfalls, invoices for goods not yet receipted and unknown suppliers go to an exception queue with the reason stated, so AP staff work problems rather than data entry.

Reversals that reconcile

Credit notes and adjustments

Credit notes are a separate document type on Peppol, not a negative invoice. Each one should reference the original invoice number, carry the same tax categories as the lines it reverses, and be sent only to customers registered to receive credit notes. ERPs often produce credits as negative invoices or as unlinked journal adjustments, and both cause rejections or unmatched balances at the buyer. Map credit notes deliberately, test partial credits, price adjustments and full reversals, and confirm with your accountant how adjustment notes should be handled for GST.

Evidence for every invoice

Status, archive and reconciliation

Each outbound invoice gets a delivery status back from the access point, and some receivers send business level responses such as acknowledgement or rejection. The integration writes that status against the invoice in the ERP so credit control can see whether an overdue invoice was delivered at all. The structured document, any rendered copy and the transmission evidence are retained under your normal record keeping, since tax records generally need to be kept for five years. Confirm the exact retention approach with your accountant.

Common Peppol Situations, Before and After

Task	Traditional	Integrated Properly	Notes
Invoice a federal agency	PDF emailed to a shared AP inbox	Sent over Peppol with buyer reference	May qualify for faster payment under the supplier pay on time policy. Check current terms and the agency’s required reference fields.
ERP has no Peppol feature	Rekey invoices into a portal	ERP invoice mapped to access point API	The ERP stays the record. The integration converts, validates, sends and writes delivery status back against the invoice.
Customer not on the network	Guess, then resend by email	Directory lookup routes to PDF	Each invoice goes one way only, so customers never receive a duplicate through both channels.
Invoice rejected for missing PO	Discovered when payment is overdue	Held before sending, or alerted at rejection	Customers that require an order number are flagged in the customer record so the ERP cannot release an invoice without one.
Issue a partial credit	Negative invoice confuses the buyer	Credit note linked to original invoice	Tax categories match the original lines, so the customer’s ledger and your GST records both reconcile.
Receive a supplier e-invoice	Printed, keyed and matched by hand	Three way matched to PO and receipt	Only variances, unreceipted goods and unknown suppliers need a person, and each arrives with the reason attached.
Supplier changes bank details	Accepted from an emailed letter	Held for callback verification	Peppol identifies the sender, but bank detail changes still need out of band confirmation before payment runs.
Invoice a New Zealand customer	Separate emailed process	Same Peppol route and specification	NZ uses Peppol with the shared A-NZ specification, so trans-Tasman invoicing can use the same integration with currency and tax handled correctly.

What Causes Rejections and Rework

ABN mismatches

The ABN on the invoice, the ABN registered on the network and the ABN in the customer’s vendor master all have to agree. Groups with several entities often invoice from one ABN and register another, or customers set you up under a parent company. Check every customer’s registered ABN through the directory before go live, and make the supplier ABN on each invoice come from the legal entity that issued it, not from a single default in the ERP.

Missing buyer reference or order number

Government agencies and many enterprises require a buyer reference, a purchase order number, or both, and will reject or park invoices without them. The ERP often holds the PO number in a free text field, if at all. Make the required reference a mandatory field per customer, captured when the sales order is created, and validate it before the invoice leaves. This single rule prevents a large share of the rejections we see.

Tax categories and GST codes

Each invoice line must carry a tax category and rate that the specification recognises, and your ERP’s internal tax codes have to translate to them correctly. Taxable, GST free and out of scope items are not interchangeable, and freight or surcharges need their own treatment. If your codes are already inconsistent, Peppol will expose it quickly. Fix the code mapping first, and confirm treatments for unusual items with your accountant.

Rounding and totals that do not add up

The specification checks that line totals, allowances, charges, tax totals and the payable amount reconcile. ERPs that calculate GST per line and round differently from the document total, or that apply discounts after tax, produce invoices that fail validation by a cent. Decide whether tax is calculated per line or per document, apply it consistently, and test with real invoices that include discounts, freight and mixed tax lines.

Units of measure and quantities

Peppol expects recognised unit codes, and the buyer will match quantities against its purchase order. If you sell by the carton and the customer orders by the each, the invoice can be correct and still fail matching. Agree the invoicing unit with key customers, map ERP units to standard codes, and avoid zero or fractional quantities used as workarounds for charges that should be allowances or separate lines.

Building what the platform already does

If your invoices come out of Xero, MYOB or another cloud platform with e-invoicing included, switch on the built in feature, register, and test with one customer before considering anything custom. Confirm that your plan or edition includes it and that credit notes are supported. Integration work is justified when the invoice originates in an ERP without support, when volumes need automated AP matching, or when rejection handling has to be systematic.

How Yes AI Approaches Peppol Integration

Check what you already have

We look first at whether your accounting or ERP platform supports Peppol natively and what your customers actually require. If switching on a built in feature solves it, we tell you, and help you test it with your first customer.

Data quality before the build

We run a sample of your real invoices and credit notes through specification validation, and check customer ABNs against the directory. The report shows exactly which fields, tax codes and rounding rules would cause rejections, before anything is built.

Built and monitored by us

Mapping, validation, routing between Peppol and PDF, and status write back run on a managed cloud automation layer we operate, connected to your chosen access point, with alerts on every rejection and failed delivery sent to the person who can fix it.

Handed over with records intact

You receive the field mapping, the validation rules, the customer routing table and the archive arrangement in plain documentation, so your finance team and auditor can see how every invoice was produced, validated and delivered.

From PDF by Email to Peppol That Gets Paid

Five steps. Outbound invoicing from an ERP to a first group of customers is typically live in four to eight weeks, with inbound AP matching following as a second phase.

Assess platform and customers

Confirm native support, choose an access point if needed, and look up which customers and suppliers are registered and for which documents.

Validate real invoices

Run a sample of invoices and credit notes against the specification and fix ABNs, references, tax codes, units and rounding at source.

Build outbound and routing

Map invoices and credit notes, validate before sending, route each invoice to Peppol or PDF, and write delivery status back to the ERP.

Go live with one customer group

Start with government or one enterprise customer, monitor every delivery and response, then widen as rejection rates settle.

Add inbound AP matching

Receive supplier e-invoices, match to purchase orders and goods receipts, and route exceptions to a queue with reasons.

FAQ

Is e-invoicing mandatory for Australian businesses?

As of late 2026, business to business e-invoicing in Australia is voluntary. Non-corporate Commonwealth entities have been required to be able to receive Peppol e-invoices since 1 July 2022, and many agencies and large enterprises prefer or encourage it, sometimes through their supplier terms. Policy is evolving, so check the current position with the ATO and your major customers before planning around it. This is general information, not legal or tax advice, and your accountant can confirm how it applies to you.

What is a Peppol access point and do we need our own?

An access point is the accredited service that sends and receives e-invoices on your behalf. You do not run one yourself. If your accounting platform supports e-invoicing, it provides access point connectivity as part of the feature. If your invoices come from an ERP without support, you contract a third party access point provider and connect your ERP to it. The ATO accredits access points in Australia but does not see the invoices passing between them.

How do we find out whether a customer can receive Peppol invoices?

Look up their ABN on the Peppol network. Access point providers and accounting platforms offer a lookup that queries the network’s directory and service metadata, showing whether the business is registered and which document types it accepts. Build that check into the invoicing process rather than relying on a one off spreadsheet, refresh it regularly, and record the result against the customer so each invoice is routed to Peppol or PDF consistently.

Is Xero or MYOB e-invoicing enough, or do we need an integration?

For a business that raises invoices in Xero, MYOB or a similar cloud platform with built in e-invoicing, the native feature is usually enough. Confirm your plan or edition includes it, register, and test with one customer. An integration is worth considering when invoices originate in a separate ERP or industry system, when you need received e-invoices matched automatically to purchase orders and goods receipts, or when rejections and dual running with PDF need to be managed systematically.

Why was our e-invoice rejected?

The usual causes are a missing or wrong buyer reference or purchase order number, an ABN that does not match the customer’s records, a tax category that does not fit the line, totals that differ by rounding, an invalid unit of measure, or a credit note sent as a negative invoice. Your access point or the receiver normally returns a reason. Fix the cause at source in the ERP rather than editing the outgoing document, otherwise the same error returns on the next invoice.

Do we still need to send PDFs?

Yes, for customers who are not on the network, and possibly as a courtesy copy where a customer asks. The important rule is that each invoice is formally issued through one channel, so the customer cannot pay it twice from an emailed PDF and a Peppol document. Route each invoice by customer registration status, mark the PDF clearly where a copy is also sent, and review the routing table as customers join the network.

How long should we keep e-invoices for the ATO?

Tax records generally need to be kept for five years, and an e-invoice is a tax record like any other. Keep the structured document as sent or received, a readable rendering if your systems produce one, and the delivery evidence from your access point. Do not rely on the access point to hold your archive indefinitely, since retention periods vary by provider. Confirm your record keeping obligations and format with your accountant.

Find Out What Peppol Would Take for Your Business

Book a call. We check whether your current platform already covers it, validate a sample of your real invoices against the specification, look up your key customers on the network, and give you a plain answer and, if needed, a priced plan.

Book an eInvoicing Review (03) 9003 0111

All discussions held in confidence. Australian-based consultants.