How E-Invoicing Evolved: From Paper and EDI to Digital Tax Reporting

This is not a straight replacement of paper by PDF. It is the gradual layering of data formats, exchange networks and tax reporting.

8-minute read ｜ English edition ｜ History & foundations ｜ Sources checked 9 October 2026

“E-invoicing” often bundles several changes together: turning a paper invoice into a digital file, enabling business systems to exchange structured data, connecting trading partners through networks, and giving tax authorities more timely transaction information. These developments reinforce one another, but they are not the same thing. The history helps companies identify which layer they actually need to change.

1. Paper invoices: a record of a transaction

Before digital business systems became common, invoices recorded the parties, goods or services, amounts and taxes on paper. They supported reconciliation, payment, bookkeeping and tax filing. But moving a paper invoice into another company’s system generally required rekeying. Mail, fax and manual handoffs also made cross-company exchange cumbersome.

Scanning a paper invoice or saving it as a PDF improves delivery and storage. Yet an image or visual document may still need to be read by a person. OCR can extract text, but it does not by itself guarantee consistent field meanings, complete data or compliance with a jurisdiction’s required format. The digital file was an important transition, not the end of automation.

2. EDI: invoices become messages exchanged between systems

The important change in Electronic Data Interchange (EDI) was not simply faster delivery. It was an agreement on how computers should arrange and interpret business fields. The United Nations Economic Commission for Europe describes EDI as computer-to-computer interchange according to a message standard with minimum human intervention. Purchase orders, invoices and customs declarations can all be exchanged this way.

UN/EDIFACT work began in the late 1980s. UNECE records that the syntax rules were approved as an ISO standard in 1987. A UN/CEFACT standards presentation identifies the first two UN/EDIFACT standard messages—purchase order and invoice—as published in 1989. Shared message structures made it possible to exchange transaction data without treating each invoice as a freely formatted document.

3. Standards define both meaning and syntax

As trade spread across industries, countries and software, a message format alone was not enough. “Date,” “tax amount” and “buyer identifier” need consistent business meanings, while systems also need rules for expressing the data in a machine-readable syntax such as XML. One layer defines what an element means; another defines how it is encoded.

EN 16931 is a useful example. The European Commission says the standard defines core e-invoice elements and supports consistency and interoperability across systems. Directive 2014/55/EU on electronic invoicing in public procurement required relevant public authorities to receive and process compliant invoices for contracts within scope by April 2019, with a transition deadline for smaller local authorities through April 2020. This concerned public procurement in scope; it should not be recast as a universal EU B2B e-invoicing mandate at that time.

Standards make it easier to align invoice data, but they do not replace tax law or automatically determine who must issue an invoice, when it must be issued, how tax is calculated or where data must be reported. Interoperability and regulatory obligations are separate questions.

4. Networks turn point-to-point links into discoverable connections

As the number of trading partners grows, maintaining custom links or dedicated connections can become expensive. Interoperability networks such as Peppol use common specifications and service providers to connect senders with receivers. In OpenPeppol’s four-corner model, the seller connects to one access point and the buyer to another. The Service Metadata Locator (SML) and Service Metadata Publisher (SMP) help discover participant addresses and receiving capabilities.

The network answers how a participant can be found and how a message can be delivered. It does not necessarily mean that a tax authority has already reviewed or cleared the invoice. Some countries can add tax reporting or control processes to a network; others use different architectures. Keep the transmission network separate from tax control.

5. Digital tax reporting expands the focus to transaction data

Tax authorities increasingly seek more timely transaction data. Policy has therefore expanded from accepting electronic formats to digital reporting, real-time or near-real-time submissions, and—under some regimes—pre-issuance validation or clearance. Terminology, transaction coverage and effective dates vary. A clearance model from one country should not be assumed to apply everywhere, and sending an invoice through a network alone does not prove that every reporting obligation has been met.

The European Union’s VAT in the Digital Age (ViDA) package offers a dated policy example. As checked for this article, the package was adopted in March 2025 and is being phased in. The European Commission’s timeline says digital reporting requirements for relevant cross-border B2B transactions begin on 1 July 2030. By 1 January 2035, Member States that operate domestic digital real-time transaction reporting obligations must align their systems with the EU framework. These are future phased requirements, not rules already fully in force across the EU in 2026.

One evolution, three layers

These layers overlap and coexist. Before upgrading, companies should map the data format, partner connection and reporting timeline required for each market. Then define the roles of ERP, tax engines, e-invoicing providers and archiving systems. Instead of asking only “Do we need e-invoicing?”, ask: what data does each transaction require, through which network, reported to whom, and with what audit trail?

Scope and sources

This article uses standards history, EU public procurement rules and the ViDA timeline to explain the direction of change. It is not a complete compliance guide for any country. Invoice definitions, transaction scope, authorisation mechanisms and effective dates vary; verify current requirements with the relevant tax authority. Historical facts and editorial analysis are stated separately, and scheduled dates are not described as obligations already in force.

1. UNECE, Executive Guide on UN/EDIFACT — EDI definition, message scope and development.
2. UNECE, UN/EDIFACT Syntax Implementation Guidelines — syntax rules approved as an ISO standard in 1987.
3. UN/CEFACT, Semantics introduction — first purchase order and invoice messages published in 1989.
4. European Commission, eInvoicing in public procurement — Directive 2014/55/EU, EN 16931 and applicable deadlines.
5. OpenPeppol, Peppol Interoperability Framework — four-corner model, access points and participant discovery.
6. European Commission, VAT in the Digital Age (ViDA) — adoption and phased 2030/2035 timeline.

E-Invoicing: From an Invoice to Digital Transaction Infrastructure | Article 02
Global Business Insight
This article is general information about standards and policy developments, not legal, tax or accounting advice.