The invoice is the first regulated business document to be forced into structured form, not the last. Greece’s tax authority now runs a real-time goods-movement interface alongside its invoice interface, both on the same platform. India’s Invoice Registration Portal forwards the invoice payload to the e-way bill system and the VAT return system without the taxpayer submitting it twice. Peppol, a network built to move invoices between public buyers and their suppliers, now publishes specifications for despatch advices, weight statements and transport booking requests. The pattern is consistent enough to plan around: once a jurisdiction has structured, addressable, machine-validated documents moving through a controlled channel, every adjacent document becomes a candidate for the same treatment.
Planning for e-invoicing beyond invoices matters commercially, not just architecturally. Invoice automation on its own captures roughly a third of the efficiency available across the purchase-to-pay and order-to-cash cycle. If you scope an e-invoicing programme as an invoice programme, you are scoping about a third of the value — and building an integration you will likely rebuild within a few years.
Invoice automation is about a third of the prize
The e-invoicing analyst Bruno Koch has put the invoice’s share of the total optimisation potential at roughly one third, with the remaining two thirds sitting in the surrounding documents: the request for proposal, the tender, the catalogue, the contract, the order and order confirmation, the delivery note, the payment, and the archive. His argument is not that paper substitution is pointless — it is that it stops short. Replacing paper with electronic documents is worth doing, he writes, but a more disruptive approach can “improve the entire financial supply chain by many factors.”
The sharpest number on this comes from analysis at Politecnico di Milano, which put the net benefit of VAT-compliant e-invoicing at €4–12 per invoice, and the benefit of integrating the full trade process at up to €65 per cycle. Those absolute figures date from research presented in 2010 and should be treated as illustrative rather than current. The ratio is the durable part: full-process integration was worth several times what invoice digitisation alone was worth, and nothing since has changed the shape of that gap.
What has changed is who is driving the expansion. In 2010 the argument for extending beyond the invoice was a business case that most organisations declined. In 2026 it is increasingly a legal obligation, and the obligation arrives from tax and customs authorities rather than from procurement teams.
Payments: the invoice already carries the payment instruction
An e-invoice is a payment instruction with tax metadata attached, and the payments industry has been formalising that link for a decade. The Euro Retail Payments Board, chaired by the European Central Bank, ran a working group on electronic invoice presentment and payment (EIPP) that reported in November 2016. It found a fragmented market — half the solutions surveyed operated in a single country, three quarters in one country or one regional bloc — but a clear technical convergence: SEPA credit transfers and direct debits dominated as the settlement instruments, card payments barely registered, and no single invoice syntax was winning among ISO 20022, UBL, UN/CEFACT Cross Industry Invoice and EDIFACT.
That work did not stop at a report. It produced an EIPP Multi-Stakeholder Group, a decision to model the request for payment on ISO 20022 pain.013 and pain.014 messages, and ultimately the European Payments Council’s SEPA Request-to-Pay scheme (EPC014-20), whose first rulebook was issued in November 2020 and whose version 4.0 took effect on 5 October 2025. The scheme explicitly names e-invoice presentment and payment as one of its use cases across B2C, B2B and B2G.
National tax platforms are pulling payment data in from the other direction. Greece’s myDATA payload does not merely record that an invoice was paid; for card transactions it carries terminal-level detail — payment method type, terminal identifier, retrieval reference number, authorisation data, whether the transaction was contactless, and any tip. That is fiscalisation and invoicing meeting in a single schema, which is why the Greek POS-to-cash-register interconnection rules and the invoicing rules ended up as the same compliance project for most retailers.
Procurement: the invoice network was built for public buying
Europe’s e-invoicing infrastructure did not start as an invoicing project. Directive 2014/55/EU is titled “on electronic invoicing in public procurement”, and Peppol’s invoice specifications are maintained by a body called the Post Award Coordinating Community — post-award being the phase after a procurement contract is signed. The same community publishes specifications for purchase orders, order responses, catalogues and despatch advices. Extending from invoice to order on Peppol is not a new integration pattern; it is switching on document types that already exist on a network you are already connected to.
The procurement metadata is often already in the invoice. In Greece, a B2G invoice carries the contracting authority, the contract type and reference code, and a Common Procurement Vocabulary (CPV) code mapped from the material master — the same classification used to publish the tender in the first place. The invoice is functioning as the closing record of a procurement transaction, and the tax authority is collecting it as such.
Logistics: the delivery note is being cleared in real time
The most concrete evidence that e-invoicing pulls in transport is Greece’s digital delivery note, which runs on the myDATA platform beside the invoice. Phase A — digitally issuing the transport document at the moment goods begin to move, transmitting it to the authority, and notifying the recipient — has been in force since December 2025. Phase B extends this to the movement itself: loading, unloading, receipt, and quality and quantity checks. AADE’s published technical specifications now include a dedicated Digital Goods Movement interface with fields for vehicle number, dispatch date and time, packaging type, line-level movement purpose, and a delivery lifecycle event set.
Phase B has been rescheduled more than once — from December 2025, then to May 2026, and on 30 April 2026 AADE restructured it into a staged rollout beginning in October 2026. The slippage is informative rather than reassuring: authorities are finding real-time event tracking harder to deliver than real-time invoice clearance, which is exactly what you would expect, and they are not abandoning it.
India got to the same place by a different route. Under its GST e-invoicing system, a supplier sends the invoice to an Invoice Registration Portal, which returns an Invoice Reference Number and a signed QR code — and then forwards the same payload onward. The GST Network’s advisory on auto-populationconfirms the data is transmitted to the GST system within two days and populates the corresponding tables of the GSTR-1 return. In parallel, the payload populates Part A of the e-way bill, the permit that authorises the physical movement of the goods. One submission, three regulatory outcomes: invoice registration, return prefill, transport authorisation.
On the network side, Peppol Logistics publishes business interoperability specifications for the Advanced Despatch Advice, the Receipt Advice used to confirm what actually arrived, a Weight Statement for bulk goods, and a Transport Execution Plan with Request used to book the transport itself. These are voluntary today in most of Europe. They exist because the buyers and suppliers already exchanging invoices asked for them.
Customs: the EU is replacing declarations with a data hub
Customs is converging on the same architecture as continuous transaction controls — submit structured data to a central government system, receive a release — and it is doing so through two separate instruments.
The first is already law. Regulation (EU) 2022/2399 established the EU Single Window Environment for Customs and, with it, EU CSW-CERTEX, a central system connecting national customs single windows to the Union’s non-customs systems so that certificates, licences and permits held elsewhere can be checked against a declaration automatically. It has applied since 12 December 2022, though the provision giving economic operators a single communication channel does not bite until 13 December 2031.
The second is the reform of the Union Customs Code, on which the Council and the European Parliament reached political agreement on 26 March 2026. It creates an EU Customs Data Hub and a European Union Customs Authority based in Lille. The design intent is to retire the customs declaration as a discrete filing: goods are released once the data submitted to the hub is complete and accurate. Use of the hub becomes mandatory for deemed importers — the e-commerce platforms now treated as the importer of record — from 1 July 2028, with a full transition running well into the 2030s. In the interim, the €150 duty exemption for low-value consignments disappears on 1 July 2026, replaced by a flat €3 per-item duty until the hub can apply normal tariffs. The final text still requires formal adoption, so the dates are firm in direction and provisional in detail.
For a business, the practical consequence is that the commercial invoice, the customs data set and the VAT reporting data set start drawing on one master record. Keeping three inconsistent versions of the same shipment stops being an internal untidiness and starts producing contradictions across three authorities.
Payroll: already inside the tax platform
Payroll is the leg that surprises people, and it is the one where the shift has already happened. Greece’s myDATA is not an invoicing platform with a reporting bolt-on; it is an electronic books platform on which invoices are one document class among several. Businesses transmit income and expense classifications, depreciation, year-end accounting settlement entries — and payroll, submitted monthly. The penalty regime treats failure to transmit payroll records as a distinct offence from failure to transmit invoice summaries, which is a good indication that the authority regards them as equivalent obligations rather than as core plus periphery.
Once payroll, depreciation and adjusting entries are all arriving in structured form, the authority is no longer reconciling a VAT return. It is reconstructing the financial statements. That is a materially different supervisory capability from invoice-level VAT control, and it is the direction other jurisdictions with SAF-T obligations are already travelling in — SAF-T files have always included the general ledger, master data and, in several national variants, payroll.
The connective tissue: one identity, one channel
Extending structured exchange across document types runs into the same bottleneck every time: knowing who the counterparty is, provably, across borders. Every model above depends on it. As Bruno Koch noted years before any of these mandates existed, unique identification of trading partners based on compliant master data is the prerequisite for automated invoicing, not a nice-to-have.
The EU’s answer is the proposed European Business Wallet, published by the Commission on 19 November 2025 as part of its digital package and now in the ordinary legislative procedure. It builds on the European digital identity framework established by Regulation (EU) 910/2014 as amended by Regulation (EU) 2024/1183, and would give every business and public body a single credential for identifying itself, signing and sealing documents, and exchanging them through a qualified electronic registered delivery service with the same legal effect as acting on paper in person. The Commission’s estimate is that broad uptake could unlock up to €150 billion in annual savings for European business — an assumption-heavy number, but one that indicates the scale at which the Commission is thinking about document exchange generally, not invoicing specifically.
Meanwhile Council Directive (EU) 2025/516 sets the tax timetable. Digital reporting requirements for cross-border B2B supplies apply from 1 July 2030, and Member States running domestic real-time transaction reporting must align those systems with the EU model by 1 January 2035. The invoice is the reference implementation. Once thirty-odd national systems have converged on one structured document, standardised addressing and a common validation model, the marginal cost of adding a second document type to that pipeline falls sharply — which is precisely why the second document type keeps arriving.
What this changes about scoping an e-invoicing project
None of the above means you should build for delivery notes and customs data today in a country that does not require them. It means the decisions you make for invoices should not foreclose them.
- Evaluate providers on their document catalogue, not their invoice coverage. Ask which Peppol post-award and logistics profiles they support in production, and whether goods-movement reporting in Greece runs through the same contract and connection as invoice reporting or a separate one.
- Treat master data as the deliverable. Counterparty identifiers, delivery locations, product classifications and CPV codes are what every subsequent document type will need. A programme that hardcodes these into an invoice mapping will pay for them again for every new document.
- Assume one submission will produce several regulatory outcomes. Design the status model accordingly. If a single payload feeds a tax platform, a transport permit and a prefilled return, “accepted” is not one state, and a rejection may land in only one of the three.
- Do not assume retention rules follow the invoice. Archiving obligations across Europe are not harmonised even for invoices, and transport documents, payroll records and customs data sit under different retention periods and different authorities.
- If you operate in Greece, India, or as a deemed importer into the EU, the expansion is not hypothetical. If you operate only under a domestic invoice mandate elsewhere, you have until roughly 2030 before the EU-level convergence starts constraining your architecture.
The organisations that will handle the next decade cheaply are the ones treating e-invoicing as the first implementation of a transaction data pipeline, rather than as a tax filing with an XML attachment.
Frequently asked questions
Does ViDA require reporting of anything other than invoices?
No. Council Directive (EU) 2025/516 covers invoice data: structured e-invoicing and near-real-time digital reporting for cross-border B2B supplies from 1 July 2030, with domestic real-time reporting systems aligning by 1 January 2035. It says nothing about delivery notes, payroll or customs. The expansion into those documents is happening at national level and through separate EU instruments, not through ViDA.
Is Peppol only for invoices?
No. Peppol’s Post Award Coordinating Community maintains specifications for purchase orders, order responses, catalogues, credit notes and despatch advices, and Peppol Logistics adds the Advanced Despatch Advice, Receipt Advice, Weight Statement and Transport Execution Plan with Request. Invoices are simply the document type that most national authorities mandated first, so they dominate live volumes.
Will payroll reporting spread beyond Greece?
It is already broader than Greece, though usually under a different label. Countries with SAF-T obligations require submission of general ledger and master data, and several national SAF-T variants include payroll. Greece’s contribution is to put payroll on the same real-time platform as the invoice rather than in a periodic file, which is a change of cadence rather than of principle.
Does the EU Customs Data Hub replace customs declarations?
That is the stated design intent: goods would be released once complete and accurate data sits in the hub, rather than on submission of a separate declaration to a national authority. It is not yet live. Use becomes mandatory for deemed importers from 1 July 2028 under the agreement reached on 26 March 2026, with the wider transition continuing into the 2030s, and the final legal text still requires formal adoption.
Should we wait for the picture to settle before investing?
Waiting on scope is reasonable; waiting on foundations is not. The mandates that will arrive between 2026 and 2035 differ in which documents they cover, but they agree on what they need underneath: verified counterparty identity, clean master data, structured line-level detail, and an exchange channel with acknowledgements. Those are worth building now regardless of which document type your jurisdiction mandates next.