Open the last audit where you tested a sample of purchase invoices. Click through them one by one. Every single one looks different. The layout's different, the wording's different, and the total is never in the same place twice. One firm's invoice is a tidy table. The next is a scanned photo of a printout. With coffee stains to finish it off. You already know the fields you're hunting for, so you find them, copy them, and move on. Then you do it again on the next one. And the next.

That whole ritual exists for one reason: invoices carry the same required information, but no two companies agree on how to present it.

E-invoicing is what happens when that finally gets fixed.

The invoice was always data; we just kept printing it

By law, an invoice has to carry a fixed set of details. Who sent it, who receives it, the invoice number, the issue and due dates, the line items, the VAT. Those fields are mandatory. What was never fixed is the wrapping around them: the template, the colors, where each field lands on the page.

So, for decades we've taken structured information, poured it into a good-looking PDF, emailed it, and then asked the receiving side to read it back off the page and re-enter it. Machines use data to make documents readable for humans. Humans then feed those documents back to machines to turn them into data again.

An e-invoice skips the middle step. You get an XML file instead of a PDF.

XML is a plain text format that puts a label on every piece of information it carries. A PDF shows you the characters "12,500.00" sitting somewhere near the bottom right of the page, and you work out from its position that it's the total. XML spells it out: this value is the total amount, this one is the VAT, this date is the due date. Same information, every field named, so software can find the total without guessing where it sits on the page.

A PDF can still be generated from the XML for anyone who wants to look at a document. The XML file is what the sender issued, and the PDF is a rendering of it.

Peppol, and the clock the EU is running

If every company invented its own XML, we'd be right back where we started. So Europe settled on a shared standard, and Peppol is the network most of the continent uses to move these files between businesses. One agreed structure, one way to move it, with a European standard underneath it (EN 16931) so an invoice issued in Rotterdam can be read automatically by a system in Zagreb.

The deadline comes from the VAT in the Digital Age reform. By 2030, cross-border B2B trade inside the EU has to run on structured e-invoicing, and from then on the XML file is the invoice that counts. The PDF becomes a printout of it. Countries aren't waiting for the deadline. The Netherlands has used Peppol for business-to-government invoicing for years and both Belgium and Croatia went live for B2B this year.

Why auditors feel this first

Most conversations about e-invoicing are about businesses issuing and paying invoices. But auditors sit downstream of all of it, and the evidence you test is exactly the thing that's changing shape.

The problem that lands on your desk is simple. An XML invoice is unreadable to a human as it arrives. Open one and it looks like code. The information is all there, but not in a form you'd want to squint at during a late close.

So, people built a workaround. Some firms have built small internal converters that turn each XML into a PDF, download it, then feed that PDF into whatever tool they work in. It gets the job done, but it's a detour, and it quietly brings back the copy-and-reformat problem that e-invoicing was meant to end.

How RobotX fits in

"With the introduction of mandatory XML e-invoicing in Croatia, we needed a solution that could work with XML invoices in a practical way. RobotX allows us to upload the original XML file and instantly displays it in a clear, invoice-like format that is easy for auditors to review. It removes the need for manual conversions and makes the entire audit process more efficient."

— Vedrana Miletić, Audit Partner UHY Rudan

Flex and Flow take XML invoices directly. Drop the file in the way you'd drop in any other document. No converting to PDF first, no download-and-re-upload detour. RobotX reads the structure and shows you a clean, readable invoice in a consistent layout, so the human-friendly view and the underlying data sit in the same place.

There's also a separate converter for XML files in general, not only Peppol invoices. It flattens any XML file into a plain Excel table, one column per field, so you can work with the contents in a sheet.

Today the invoice view covers the Peppol standard. That's the format most of Europe is moving to, so it's the one we support first. Several countries have brought their own along the way, though. Italy, Poland, and Germany each run a national format, so "standardized" comes with an asterisk for a while yet, and anyone auditing across borders will meet more than one flavor of the same idea. Support for more country formats is on the way. Until then, the general XML converter will still open the file and lay the data out for you.

If XML invoices are starting to show up in your client files, or you can see them coming, this is a good moment to watch how it works in practice. We're happy to walk you through it.

See how RobotX handles e-invoices →