E-Invoicing, Peppol and the End of the Traditional Invoice?
When an invoice stops being a document and becomes Trusted Data
For decades, Accounts Payable has been process evolution built around the same remarkably simple assumption, a supplier sends you an invoice.
Paper became PDF. Post became email. Filing cabinets became document management systems. OCR and AI then became increasingly sophisticated at reading those documents.
But fundamentally, we have continued doing the same thing.
A supplier creates information. They turn it into a document. We receive the document — and then spend time and technology turning it back into data.
That model is beginning to change.
And regulatory change could accelerate that transition dramatically (Note E-Invoicing Mandates)
The invoice is becoming structured data
A PDF invoice may look digital. But from a process perspective, it can still behave very much like paper. The information has to be received, interpreted, extracted, classified, validated and entered into another system before it can become useful transactional data.
A structured electronic invoice is fundamentally different. The supplier doesn't simply send an electronic picture of an invoice. They send the invoice data in a defined, machine-readable structure.
Supplier. Buyer. Invoice number. Purchase order. Line items. Tax. Currency. Payment terms. Totals.
The receiving system knows not only what the information says, but what each piece of information means. That seemingly subtle distinction has enormous implications for Accounts Payable.
Regulation is accelerating the change
This isn't simply a technology trend. Governments around the world are increasingly making structured e-invoicing part of the tax and regulatory infrastructure.
And the pace is accelerating.
France entered a major new phase on 1 September 2026. All businesses must now be capable of receiving electronic invoices, while large and mid-sized organisations are required to issue them and provide relevant e-reporting data. Smaller businesses follow for issuance in September 2027.
Germany introduced its B2B e-invoicing framework from January 2025, with transitional arrangements for issuance running through 2026 and, for some businesses, 2027.
In the UK, mandatory e-invoicing for B2B and B2G VAT invoices is scheduled from April 2029.
Across the EU, VAT in the Digital Age — ViDA — takes this further. From 1 July 2030, cross-border B2B transactions will become subject to new Digital Reporting Requirements based on mandatory e-invoicing.
For multinational organisations, this is no longer something sitting on a distant regulatory roadmap. It is becoming an architectural issue today.
But there is a problem: one world, multiple mandates
The direction of travel may be clear. The implementation isn't necessarily uniform.
Different countries can have different mandates, timelines, data requirements, tax reporting requirements, invoice formats, clearance/reporting models, platforms, networks and archiving requirements.
For a business operating in one country, that is a compliance project. For a multinational operating across 10, 20 or 50 jurisdictions, it becomes an interoperability problem. And that distinction matters.
The objective shouldn't be to build another point-to-point integration every time another government introduces a mandate.
The strategic question should be: How do we create an Invoice-to-Pay architecture capable of accommodating multiple countries, formats, networks and regulatory regimes without continually rebuilding the AP infrastructure?
This is where Peppol becomes particularly interesting.
Peppol: Connect once, reach many
Peppol isn't simply an invoice format and it isn't a government portal. It is an interoperability framework and network that standardises how electronic business documents can be structured, addressed, validated and securely exchanged between organisations.
The Peppol four-corner model allows a buyer and supplier to use their respective accredited service providers rather than both having to belong to the same proprietary network.
OpenPeppol describes the principle simply: Connect once, reach all.
The specifications provide a shared digital language while the network and governance framework provide the mechanism for trusted exchange. Peppol is increasingly international rather than simply European, with adoption extending to markets including Singapore, Australia, New Zealand and Japan. That should be significant for any Finance Leader responsible for a multinational Invoice-to-Pay environment.
What does this mean for Accounts Payable?
Potentially, something much bigger than compliance.
If an invoice arrives as correctly structured, machine-readable data through a trusted exchange mechanism, we can begin removing entire layers of activity traditionally associated with AP.
Instead of: Receive → Read → Extract → Interpret → Key → Validate
We move towards: Receive structured data → Validate → Enrich → Match → Control → Post
And increasingly: Receive → Validate → Orchestrate.
That means less dependence on OCR, less manual data entry, fewer interpretation errors, better matching, faster processing, better tax data, improved auditability and potentially much higher levels of straight-through processing.
But importantly, structured data should not automatically be assumed to be Trusted Data.
Structured Data + Validation + Enrichment + Controls = Trusted Data
This is where Part 2 of this series becomes important. Receiving structured information removes much of the need to interpret the document. It doesn't remove the need to validate the transaction.
Is the supplier genuine? Does the PO exist? Were the goods or services received? Are the quantities and prices correct? Is the tax treatment appropriate? Are the bank details trusted? Is the transaction duplicated? Does it comply with company policy?
The opportunity is therefore to combine structured e-invoice data with internal enterprise data, external data enrichment and strict declarative guard rails. Only then should validated information be released into the ERP, ledger, payment process or reporting environment.
The destination remains the same: Trusted Data.
Data that Finance Leaders can rely upon when closing the books, completing returns, making regulatory filings and signing accounts.
The multinational challenge
For CFOs of multinational organisations, I believe there is an important strategic lesson here. Don't treat every new e-invoicing mandate as an isolated tax compliance project.
Doing so risks creating another collection of country-specific platforms, integrations and processes. Instead, organisations should be asking: “What global e-invoicing and Invoice-to-Pay architecture do we need to support the jurisdictions in which we operate today — and those that will mandate structured electronic invoicing tomorrow?”
That means understanding compliance, connectivity, interoperability, data, controls and scalability. That is a much bigger conversation than replacing PDFs with XML.
At CloudConnect, we see the opportunity differently
E-invoicing should not simply be another input channel. It should become part of a broader intelligent document and data orchestration strategy. Whether information arrives as a PDF, structured e-invoice, Peppol message, EDI transaction, portal submission or another digital format, the objective should be consistent: Receive it. Understand it. Structure it. Enrich it. Validate it. Control it. Connect it.
And ultimately: Turn it into Trusted Data.
Perhaps, therefore, we are approaching the end of the invoice as we have traditionally understood it. Not the end of the commercial transaction. Not the end of the legal or tax record. But increasingly, the end of the invoice as a document that somebody in Accounts Payable needs to read.
And that could fundamentally change the role of AP.
To learn more about CloudConnect technology and services, explore our website and schedule a FREE consultation.
Missed the previous blogs in the "Future of Accounts Payable" series?
Part 2 - THE FUTURE OF ACCOUNTS PAYABLE | Is Touchless Invoice Processing Already Becoming an Outdated Ambition?
NEXT IN THE SERIES
Part 4 – From Invoice to Payment: Open Banking and the New Payment Infrastructure
If structured e-invoicing transforms how trusted financial data enters Accounts Payable, what happens when payment infrastructure becomes equally connected, digital and increasingly real-time?
Reference links
European Commission – VAT in the Digital Age (ViDA)
French Tax Authority – Electronic Invoicing Reform
German Federal Ministry of Finance – E-Invoicing FAQ
HMRC – Transformation Roadmap
OpenPeppol – Interoperability Framework
Comments