Executive Summary

On 1 July 2030, structured e-invoicing becomes the basis for cross-border intra-EU B2B reporting. The VAT in the Digital Age package — Directive (EU) 2025/516, known as ViDA — also switches on near-real-time digital reporting: transaction-level invoice data must reach tax authorities within days of the chargeable event, not at month-end.

Most e-invoicing programmes are being run out of finance. That is the mistake. In distribution, the invoice that carries the risk is not generated in the back office. It is generated at the customer's door, on a van, on a route, on a device that may have had no signal five minutes earlier. If that document is not a valid structured e-invoice at the moment it is produced, no downstream ERP configuration will repair it.

E-invoicing is not a document-format problem. It is an edge-data problem. The organisations that will clear 2030 cheaply are the ones that make the invoice structured at birth — on the device, in the field — and reportable within days, not the ones that convert PDFs after the fact. This article builds on our earlier analysis, EU E-Invoicing Is a Delivery Problem, Not Just Finance, and looks at what the 2030 deadline demands of field data architecture.

The Current State

The mandates are not a single deadline in the future. They are a rolling set of national regimes already arriving, and ViDA is the reason they are accelerating.

The ViDA timeline itself is fixed:

Two numbers define the operational problem. Under the Digital Reporting Requirements, a supplier must transmit transaction-level invoice data to the tax authority within 10 days of the chargeable event. For self-billing and acquisitions, a 5-day extension applies. That is a reporting cadence measured in days, on every transaction — not a quarterly return reconstructed from a ledger.

Meanwhile the pattern in most distribution businesses has not changed. The invoice is generated at the visit: quantities negotiated on the spot, prices adjusted, substitutions agreed, the document printed and handed to the customer. It is created outside the ERP, often offline, and reconciled later. The format, the timing, and the source are all wrong for what 2030 requires.

The Shift

Three changes, taken together, turn e-invoicing from a finance project into a field-operations requirement.

From form to data. A PDF, however tidy, is a picture of an invoice. A structured e-invoice is machine-readable data — XML conforming to EN 16931, updated for B2B and digital reporting in the 2026 revision of the standard. The buyer's system books it without a human retyping a field. Nothing in a scanned or printed document satisfies that definition.

From batch to transaction level. Digital reporting does not aggregate. It reports each transaction as, or shortly after, the invoice is issued. The end-of-day reconciliation ritual — the settlement run, the batch export, the file dropped at midnight — is structurally too slow and too coarse. Compliance becomes a per-invoice property, and per-invoice visibility becomes the baseline for operating the route, as we argued in Why Operational Visibility Is the New Competitive Advantage.

From acceptance to obligation. From 1 January 2030 a recipient can no longer refuse an e-invoice. The argument about "our customers still want paper" ends by regulation. The obligation to be able to issue and receive structured invoices applies to every business in scope, whether or not it calls itself a distribution company.

The consequence is the same in every case: the invoice must be correct, structured, and transmissible at the point it is created. That point is the field device.

Key Findings

1. The deadline is nearer than the 2030 date suggests. National regimes are live now in Belgium, Poland, and France, and in Germany from 2027. A distribution business selling across two or three EU markets meets the structured-invoice requirement years before the cross-border rule lands. Why it matters: the first compliance shock arrives in the current planning window, not in 2030.

2. The field invoice is the hardest case, not the easiest. Back-office invoices are created by a system that already holds structured data. The field invoice is created by a person, at a customer's premises, under time pressure, sometimes offline. Why it matters: the process with the least structure carries the same legal weight.

3. Batch reconciliation does not survive digital reporting. A near-real-time, transaction-level reporting duty cannot be met by a nightly settlement file. Why it matters: the operating rhythm of route accounting must change, not just the output format.

4. One field workflow must satisfy many national formats. Belgium watches Peppol; Poland watches the national KSeF schema; France watches Factur-X; the Gulf watches ZATCA UBL. Why it matters: an e-invoicing capability that is hard-coded per country does not scale across a route network that crosses borders.

5. Offline is non-negotiable, and compliance cannot depend on signal. DSD and van-sales routes routinely pass through areas with poor connectivity. Why it matters: the invoice must be created, validated, and sealed on the device, then transmitted when the network returns — without losing its legal validity.

6. Authenticity and integrity are entity-level trust properties. A legal e-invoice must demonstrate that it genuinely came from the issuer and has not been altered. Under eIDAS and ViDA, a qualified electronic seal (QSeal) provides that guarantee at the entity level. Why it matters: this is infrastructure, not a signature image on a screen.

7. Master data quality becomes a compliance risk. A structured invoice can only be reported if the customer, item, tax, and unit data behind it are clean. Why it matters: dirty master data, which today only slows reporting, becomes a defect that fails a legal document. The wider case for clean, machine-readable operational data is set out in Beyond Data Collection: Engineering Operational Systems for AI Success.

8. Retrofitting is expensive; designing at source is cheap. Converting unstructured field documents into valid structured invoices after the fact means rebuilding the document, re-deriving the tax treatment, and re-establishing its integrity. Why it matters: the cost of the field-invoice gap grows with every year it is left open.

Strategic Implications

The decisions split cleanly into three horizons.

The organising question for an operations leader is not "which e-invoicing vendor does finance prefer". It is "can the invoice be born correct on the device". Everything downstream depends on that answer.

Recommendations

1. Move ownership out of finance alone. Run e-invoicing as a joint programme between finance, IT, and field operations. The legal obligation is financial; the failure point is operational.

2. Treat the field device as the system of record for the invoice. Generate the invoice where the transaction happens, and let the ERP receive a completed, valid document rather than reconstruct one.

3. Design for structured-at-birth. Produce EN 16931-conformant data on the device at the moment of sale, not a PDF that is converted later. Structure is a property of creation, not of filing.

4. Make compliance offline-first. Validate, seal, and queue the invoice locally, then transmit on reconnect. Assume the network will be absent at the worst possible moment and design so that it does not matter.

5. Clean customer, item, and tax master data now. This work has value well beyond compliance; starting it early turns a 2030 risk into an immediate reporting improvement.

6. Choose an architecture that absorbs national formats. Prefer a platform that isolates the country-specific schema behind one field workflow, so a new market does not mean a new app.

7. Instrument reporting latency from day one. Treat "days from chargeable event to reported" as an operational metric, visible to operations, not a finance afterthought.

Looking Ahead

The national waves of 2026 to 2028 will stress field operations before the cross-border rule arrives. Every market that mandates domestic e-invoicing becomes a live test of whether the invoice can be issued correctly at the point of delivery. The teams that treat those waves as rehearsal will be ready for 2030; the teams that treat them as a finance formality will discover the gap at the worst time.

The direction is settled, and it is not reversible. Structured e-invoicing, transaction-level reporting, and mandated acceptance are the operating environment of the next decade. The competitive question is narrow and practical: is your field invoice a legal, structured document at the instant it is created, or a picture of one that someone must fix later? Answer that, and 2030 becomes routine.