Xero has native Peppol e-invoicing in the regions where national programmes pushed for it, chiefly Australia, New Zealand and Singapore. UK organisations have not had the same sending capability inside Xero, so a UK business that needs to send a Peppol invoice does it through a certified Access Point connected to Xero rather than from a button in Xero.
That is a smaller difference than it sounds. Xero stays your system of record either way. What changes is where the conversion, validation and delivery happen, and how much of your data has to be right for it to work.
Why the answer depends on your region
Xero built e-invoicing where its customers were compelled to have it. Australia and New Zealand ran co-ordinated national adoption programmes with government backing, and Singapore did something similar. In those markets sending a compliant invoice from inside Xero became a reasonable expectation.
The UK did not have that programme until recently. With the mandate now confirmed and specifications still being finalised, the UK is at the stage those markets were at some years ago. That is the whole reason the experience differs, and it is also why anything you read on a forum from an Australian Xero user may not describe your options.
What the flow looks like in practice
Nothing about how you work in Xero changes. You raise the invoice the way you raise every other invoice. The difference is what happens after you approve it.
Two things about step two are worth dwelling on, because they are where projects succeed or stall.
The first is validation. A Peppol invoice is checked against the specification before it goes anywhere, and a document that fails validation does not get delivered. This is a feature rather than an obstacle: it means the buyer never receives something their system cannot process. It does mean a first attempt often surfaces gaps in your Xero data that nobody had noticed, because Xero itself was perfectly happy with them.
The second is that delivery is confirmed. Unlike emailing a PDF and hoping, the network returns a delivery outcome. You know whether it arrived.
Where Xero data meets Peppol requirements
This is the substance of the work. Xero is a flexible system and lets you record things loosely. The Peppol specification is strict. The mapping between the two is where the effort goes.
None of this is difficult individually. What makes it a project rather than a task is that it has to be true for every invoice, not most of them, and the exceptions tend to live in the accounts you invoice least often.
Xero will happily raise an invoice that the network will refuse to deliver. Finding those before they matter is most of the work.
Tracking categories: useful, but not what you think
Tracking categories come up in almost every Xero conversation we have, so it is worth being clear about where they sit.
They are a Xero reporting dimension. They let you split a profit and loss by channel, region or brand without restructuring your chart of accounts, and they are genuinely valuable for that. They are not a Peppol field and they do not travel to your buyer.
They still matter here, for an indirect reason. The logic that decides which tracking category an invoice gets is usually the same logic that knows which entity is selling, which cost centre applies and which buyer reference belongs on the document. If that logic is already reliable in your Xero setup, the Peppol mapping has something solid to build on. If tracking categories are applied inconsistently or by hand, that is a signal about the rest of the data too.
Our Xero integration page covers how we apply tracking categories automatically from source order data, which is the same mechanism that feeds the reference fields a compliant invoice needs.
The consolidation question
This one is specific to Xero and catches people out.
Xero organisations selling at volume through Shopify or WooCommerce often consolidate orders into batched invoices, by day or by channel, to stay within transaction limits while keeping line level detail. That is a sensible pattern and we build it regularly.
It interacts with Peppol in a way worth thinking about early. A consolidated invoice is a perfectly valid Peppol document, and if your buyer is happy to receive one invoice covering many orders then nothing needs to change. Where it breaks down is with buyers who match invoices to individual purchase orders, which is normal in public sector and in larger retail relationships. Those buyers expect one invoice per order, and a consolidated document will sit unmatched in their approval queue.
- Direct to consumer volume where no buyer PO exists
- Account customers billed on a statement basis
- Any buyer who has agreed to periodic invoicing
- Public sector buyers, almost without exception
- Retailers matching invoice to purchase order
- Any buyer whose remittance references their own PO number
In practice most businesses need both, which means the rule sits at customer level rather than being a single global setting.
What to do now if you are on Xero
If nobody has asked you for Peppol yet, connecting today is not the priority. Four checks are, and all of them are useful regardless of what happens with the mandate.
Want to know how far off you are?
We are a certified Peppol Access Point and we connect Xero to order flows, retailer trading and finance systems. A short call usually tells you whether this is a two week job or a longer one.
Talk to the team