E-Invoicing Mandates and Peppol: Adapting P2P Workflows

“An e-invoicing mandate does not clean up a purchase order; it exposes it. Fix the order and the supplier data first, and the structured invoice becomes the easy part.”
| Statistic | Source |
|---|---|
| IBFD ViDA dossier, reviewed 16 November 2026: a news item dated 2 November 2026 on a Belgian law for ViDA’s first stage. | IBFD ViDA dossier, 2026 |
| European Commission: Digital Reporting Requirements for cross-border B2B transactions from 1 July 2030. | European Commission ViDA page, 2026 |
| Commission Germany page, updated October 21, 2026: domestic B2B issuing duty from 1 January 2027 above EUR 800,000 turnover, and from 1 January 2028 for all others except the domestic SME scheme. | European Commission, Germany page, 2026 |
| International Tax and Public Finance, 2025: Italy’s 2019 mandate is estimated to have cut its 2019 VAT loss by about €2.2 billion to €2.6 billion against 2018. | Heinemann and Stiller, 2025 |
| Swedish Defence Materiel Administration, January 2024: order number in OrderReference, order line number in OrderLineReference. | FMV supplier instructions, 2024 |
One source’s dated statement per row; not tax or legal advice, and no trend is drawn across rows.
- Belgium: VAT-registered businesses send and receive1 January 2026
- Poland: most businesses start KSeF e-invoicing1 April 2026
- France: all receive; large and medium-sized issue1 September 2026
- Germany: businesses above EUR 800,000 must issue1 January 2027
- Poland: all remaining businesses start KSeF1 January 2027
- France: all other businesses must issue1 September 2027
- Germany: all others, except the SME scheme, must issue1 January 2028
Not a complete calendar; dates as published on the Commission’s country pages (read 20 November 2026). Bars count months from 1 January 2025. Poland’s largest businesses, above PLN 200 million revenue, started on 1 February 2026. France page marked unverified; Poland page shows no verification. Confirm with tax advisers. Source: European Commission, Digital Building Blocks eInvoicing country page, 2026; European Commission, Digital Building Blocks eInvoicing country page, 2026; European Commission, Digital Building Blocks eInvoicing country page, 2026; European Commission, Digital Building Blocks eInvoicing country page, 2026.
What do e-invoicing mandates and Peppol require of procurement and AP teams?
According to OpenPeppol’s page on core invoice usage specifications, CEN technical committee TC434 published EN 16931 on 28 June 2017 as a semantic data model for a core invoice, and countries, groups or organisations may restrict its many optional elements in their own specification, called a CIUS.
According to a 2011 deliverable of the PEPPOL project, PEPPOL began in May 2008 as a 42-month pilot under the European Commission’s Competitiveness and Innovation Programme, drawing on BII profiles whose key aspect was standardized semantics rather than syntax. In a 2017 study for the Commission’s DG GROW, the European standard holds only the information elements an invoice needs for legal, including fiscal, compliance and interoperability, and may also serve invoicing between private sector enterprises.
In a 2021 governance deliverable of FENIX, an EU-funded logistics project, Peppol is described as a network of access points where sender and receiver may choose their service providers independently, with no roaming agreements or charges allowed between the two access points. Its place in the order-to-payment flow is covered in the Journal’s guide to procure-to-pay architecture.
In IBFD’s ViDA dossier, the first ViDA pillar is a real-time reporting system, transaction by transaction, based on e-invoicing. In this guide’s method, record for each country whether invoices pass only between the parties, are reported to a tax platform or must be cleared, and the route the buyer receives them through, and have tax advisers confirm each entry.
Which mandate dates should a P2P plan track?
According to the Commission’s summary page on the VAT in the Digital Age package, the package was adopted on 11 March 2025, and Digital Reporting Requirements will affect cross-border B2B transactions from 1 July 2030. Ask tax advisers what that reporting will require of each entity as a buyer of intra-EU supplies, not only as a seller.
According to the Commission’s eInvoicing country page for Germany, last updated October 21, 2026, an email address meets the German receiving duty that has applied since 1 January 2025; issuing domestic B2B e-invoices becomes mandatory from 1 January 2027 for businesses with turnover above EUR 800,000 and from 1 January 2028 for all remaining businesses, except those under the domestic SME scheme. The register below adds the formats the page names.
| Country and page date | B2B duties as published | Format or route named | Source |
|---|---|---|---|
| Germany, updated October 21, 2026 | Receive since 1 January 2025; issue domestic B2B e-invoices from 1 January 2027 above EUR 800,000 turnover, from 1 January 2028 for all others except the domestic SME scheme | XRechnung primary; ZUGFeRD (Profile XRechnung) accepted; Peppol BIS Billing 3.0 also supported | Commission page for Germany, 2026 |
| Belgium, updated October 16, 2026 | From 1 January 2026, VAT-registered businesses exchange structured e-invoices; e-reporting intended by 2028 | Peppol by default; alternatives only by mutual agreement and if convertible to EN 16931 | Commission page for Belgium, 2026 |
| France, updated October 19, 2026, marked unverified | All receive from 1 September 2026, when large and medium-sized businesses also issue; all others issue from 1 September 2027 | An approved private platform, or a solution connected to one | Commission page for France, 2026 |
| Poland, updated October 16, 2026, no verification shown | KSeF from 1 February 2026 above PLN 200 million revenue, most businesses from 1 April 2026, all others from 1 January 2027 | KSeF, for businesses with a registered office or fixed establishment in Poland | Commission page for Poland, 2026 |
Commission summaries of national law read 20 November 2026, not the law itself or a complete list; confirm each entry with tax advisers.
Routes differ too: under the Commission’s Belgium page, Peppol is the default track and no party can force its contracting partner to use an alternative; under the Commission’s France page, marked unverified, businesses in scope must choose a private accredited platform or a compatible solution connected to one; and under the Commission’s Poland page, which shows no verification, businesses with a registered office or fixed establishment in Poland must use KSeF for B2B transactions.
In IBFD’s ViDA dossier, last reviewed 16 November 2026, Member State implementation dates may vary; its news items include a Belgian law for ViDA’s first stage (item of 2 November 2026) and a Bulgarian ministry proposal for domestic e-invoicing (item of 25 September 2026). That Belgian item is not the start of Belgian B2B e-invoicing: under the Commission’s Belgium page, that began on 1 January 2026. Log each item as enacted, announced or proposed, with its official text.
Why do governments mandate structured e-invoices?
The Commission’s stated reason is tax control: according to the Commission’s ViDA page, real-time digital reporting for cross-border trade, based on e-invoicing, will give Member States granular information to step up the fight against VAT fraud, especially carousel fraud.
In a 2025 study in International Tax and Public Finance, Heinemann and Stiller use gaps in trade data for Italy’s imports from other EU countries as a proxy for cross-border VAT fraud. According to the same study’s abstract, e-invoicing, introduced comprehensively in Italy in 2019, cut the Italian VAT loss that year by about €2.2 billion to €2.6 billion against 2018, the authors estimate. Read it as evidence about why tax authorities mandate e-invoicing, not about buyers’ costs.
How do Peppol rules change purchase-order matching?
Under the Peppol BIS Billing 3.0 specification, a buyer reference or purchase order reference must be provided, the unique purchase order number should be the order reference, and with it at header level, line references can give order line numbers. In the same specification’s invoice verification requirements, the document traces to a single related purchase order and each invoice line to a single related order line.
In this guide’s method, that means one purchase order per invoice, split invoices where a supplier bills several orders, and an order line number on every ordered line. Set two- or three-way rules per order type, tolerances, units of measure fixed on the order and a route for charges without an order line, such as freight. Match credit notes to the invoice they correct, and give spend without an order a buyer reference that routes to an approver.
As one buyer’s example, under the Swedish Defence Materiel Administration’s January 2024 invoicing instructions, Peppol invoices must carry the order number in OrderReference and the order line number in OrderLineReference, while direct orders use BuyerReference and AccountingCost. In the same FMV instructions, a scanned or PDF invoice counts as a paper invoice for that buyer. Publish your own rules per entity, including which hybrid formats you accept.
How should services purchase orders be structured for e-invoices?
In the 2017 study for DG GROW, information some sectors need beyond the core model may travel as unstructured text, which cannot be processed automatically and requires human intervention. In this guide’s method, give services orders lines the invoice can repeat in structured fields, such as a milestone, monthly fee or role rate, each with a period and acceptance step. Check time-and-materials lines against service entries from approved timesheets, and state whether value-limit orders match by value consumed or by quantity times rate.
For German invoices, according to The Invoicing Hub’s summary of a German finance ministry letter dated October 15, 2026, structured data must describe the nature, scope and content of the supply well enough to verify its VAT treatment, and detailed timesheets may go in an embedded attachment if not necessary for that check. Treat it as a report by a news site that lists e-invoicing provider sponsors, and confirm it with a German tax adviser.
In this guide’s method, an accepted milestone is billed as an ordinary invoice against its order line, unlike progress invoices settled by a final invoice. Under OpenPeppol’s list of processes that BIS Billing 3.0 does not explicitly support, partial and final invoicing is out of scope, as those invoices do not require all mandated information, and self-billing needs a specific set-up because of the prior agreement and acceptance procedure under Directive 2006/112/EC.
According to the same news report on the German letter, end invoices may summarise earlier partial payments in the field BT-113 until the end of June 2030. List progress-billing and self-billing contracts, including evaluated-receipt settlement, check that your provider supports them and agree each flow with tax advisers.
How should supplier enablement and access-point selection work?
Start with your own receiving set-up. Under OpenPeppol’s core invoice usage specification, buyer and seller electronic addresses are mandatory because an invoice cannot be sent across the Peppol network without them. In this guide’s method, register a receiving identifier for every buying legal entity and each document type you accept, prove it with a test invoice from a live supplier, and publish a ‘how to invoice us’ sheet per entity.
Then record each supplier’s route rather than assuming Peppol: a Peppol participant identifier where Peppol is the route, otherwise its national format and channel, plus validated tax and legal identifiers and its national phase. Sequence waves with the Journal’s method for running supplier onboarding, by phase, volume and readiness. For German entities, list legacy EDI flows and decide with a German tax adviser which EN 16931 formats and syntaxes each entity must be able to receive, and until when legacy flows may continue.
In this guide’s method, test an access point as P2P infrastructure: the formats, routes and country rules it receives and validates for each entity, its validation reports, an approver rendering, ERP delivery, and an exit that moves every entity’s registrations without a receiving gap. Ask suppliers for their route and identifier, not a change of provider.
Which validation controls should run before an invoice is posted?
Under the BIS Billing 3.0 validation rules, each document is validated in stages: syntax first, then compliance with EN 16931, such as valid currency, country and tax codes, mandatory elements and correct calculations, then Peppol’s general rules and country rules triggered by the seller’s country code. Run the same checks on inbound invoices before matching, and log each rejection by supplier, rule and owner.
In this guide’s method, classify recurring rejections by who must fix them: the supplier for its own billing errors, with a clear rejection reason; the buyer for data it supplied, such as the entity identifier, buyer reference or order line; and ERP owners for mapping EN 16931 VAT category codes and units to ERP codes, with tax approval.
According to The Invoicing Hub’s report on the same letter, the German guidance separates technical validation from tax validity, and business rule errors do not automatically void an e-invoice for tax purposes if the statutory details are accurate. Route validity and input VAT questions to tax advisers, and agree with them which failures to return, query or accept with an internal correction. Keep rejected files with reason and timestamp, agree when payment terms start for a rejected invoice, and check each wave for duplicates across channels.
What should a mandate-readiness plan for P2P contain?
In this guide’s proposal, readiness is a set of workflow changes, each with evidence that it works; plan the automation behind it with the Journal’s guide to procurement automation architecture.
| Workflow step | What to change | Evidence that it works |
|---|---|---|
| Jurisdiction register | Countries, duties, route, status, official source and date read | Reviewed with tax advisers on a cycle |
| Entity receiving set-up | Receiving identifier per legal entity and document type; invoicing sheet per entity | Test invoice received per entity |
| Access point | Routes and country rules, validation reports, approver rendering, ERP delivery, exit | End-to-end test per country and route; exit without a receiving gap |
| Baseline | First-pass match and exception rates per entity before wave 1 | Rates compared after each wave |
| Supplier master data | Route, format, national phase, tax and legal identifiers | Suppliers validated before each wave |
| Purchase orders | One order reference per invoice; lines in billing units | Valid order and line references on arrival |
| Services orders | Milestone, period or role-rate lines; value-limit rule; timesheets attached where tax checks allow | Service entries posted before invoices arrive |
| Spend without an order | Buyer reference routed to an approver and cost object | No manual lookup |
| Validation | Syntax, EN 16931 and country rules before matching; rejections classed by owner | Rejection log by owner, supplier and rule |
| Matching | Receipts and service entries against order lines; two- or three-way rules, tolerances, units, unordered charges, credit notes | First-pass match rate by order type |
| Exceptions | Structured rejection responses where supported; payment-term start agreed; cross-channel duplicate checks | Repeat errors per supplier and age of open exceptions tracked; rejected files kept with reason and timestamp |
| Records | Structured original kept with its attachments | Retrieval test against retention periods |
This guide’s proposed method, not a legal checklist or market standard; tax advisers decide scope, validity and retention.
How will AI agents change e-invoice processing in P2P?
Frequently asked questions
Is Peppol the same as an e-invoicing mandate?
Not by itself. A mandate is a government’s legal duty; according to OpenPeppol’s page on core invoice usage specifications, Peppol’s invoice specification restricts EN 16931 so that business partners can start e-invoicing without prior bilateral agreements.
When must German companies send B2B e-invoices?
According to the Commission’s eInvoicing country page for Germany, last updated October 21, 2026, businesses above EUR 800,000 turnover must issue domestic B2B e-invoices from 1 January 2027 and all remaining businesses from 1 January 2028, except those under the domestic SME scheme; receiving has applied since 1 January 2025. Confirm the current rules with a German tax adviser.
Can one invoice cover several purchase orders under Peppol?
Plan on one order per invoice: under the Peppol BIS Billing 3.0 specification, the invoice traces to a single related purchase order at document level. Ask suppliers to split invoices that span several orders.
Do e-invoicing mandates reduce invoice processing errors?
No source acquired for this guide measures processing errors before and after a mandate. In a 2025 peer-reviewed study of Italy’s 2019 mandate, the estimate concerns cross-border VAT fraud: a fall in the Italian VAT loss of about €2.2 billion to €2.6 billion in 2019 against 2018. Track your own rejection and exception rates.
Sources
- VAT in the Digital Age (ViDA) — European Commission, Directorate-General for Taxation and Customs Union, European Commission, Taxation and Customs Union website; living policy page read November 20, 2026, 2026. Contextual evidence (official report): ViDA adopted on 11 March 2025 and published on 25 March 2025; since entry into force on 14 April 2025 Member States can introduce mandatory e-invoicing under specific conditions; Digital Reporting Requirements for cross-border B2B transactions from 1 July 2030; domestic real-time reporting aligned with the EU model by 1 January 2035; real-time reporting to fight VAT fraud, especially carousel fraud.
- BMF publishes additional guidance on mandatory German e-invoicing — The Invoicing Hub, The Invoicing Hub, e-invoicing news site, article of October 20, 2026; read November 20, 2026, 2026. Contextual evidence (news): Reported content of the ministry letter of October 15, 2026: structured data must describe the nature, scope and content of the supply; detailed timesheets may sit in an embedded attachment if not necessary for that control; end invoices may summarise earlier partial payments in BT-113 until end of June 2030; business rule errors do not automatically void an e-invoice for tax purposes. The site lists e-invoicing provider sponsors.
- Software building blocks enabling cross-border VCD (PEPPOL Deliverable 2.3) — PEPPOL consortium (editor: Maria A. Wimmer), PEPPOL pilot project, co-funded by the European Commission ICT Policy Support Programme, revision of January 6, 2011; read November 20, 2026, 2011. Historical evidence (official report): PEPPOL was a 42-month pilot under the Commission's Competitiveness and Innovation Programme that began in May 2008; the key aspect of the BII profiles behind PEPPOL's business interoperability specifications was standardized semantics rather than syntax.
- eInvoicing in Germany — European Commission, Digital Building Blocks, European Commission, Digital Building Blocks eInvoicing country page; content last updated October 21, 2026; read November 20, 2026, 2026. Contextual evidence (official report): Germany: receive EN-compliant e-invoices as of 1 January 2025, an email address being sufficient; issue domestic B2B e-invoices from 1 January 2027 above EUR 800,000 turnover and from 1 January 2028 for all remaining businesses except the domestic SME scheme; XRechnung primary, ZUGFeRD (Profile XRechnung) accepted, Peppol BIS Billing 3.0 additionally supported.
- eInvoicing in Belgium — European Commission, Digital Building Blocks, European Commission, Digital Building Blocks eInvoicing country page; content last updated October 16, 2026; read November 20, 2026, 2026. Contextual evidence (official report): Belgium: B2B e-invoicing mandatory from 1 January 2026 for VAT-registered businesses, exchanged directly between their systems; Peppol as the default track, with no party able to force an alternative on its partner; e-reporting intended by 2028.
- eInvoicing in France — European Commission, Digital Building Blocks, European Commission, Digital Building Blocks eInvoicing country page, marked unverified; content last updated October 19, 2026; read November 20, 2026, 2026. Contextual evidence (official report): France: all businesses must be able to receive B2B e-invoices from 1 September 2026, when large and medium-sized businesses must also issue them; all others issue from 1 September 2027; businesses in scope choose a private accredited platform.
- eInvoicing in Poland — European Commission, Digital Building Blocks, European Commission, Digital Building Blocks eInvoicing country page, no verification shown; content last updated October 16, 2026; read November 20, 2026, 2026. Contextual evidence (official report): Poland: KSeF e-invoicing from 1 February 2026 for revenue above PLN 200 million, most businesses from 1 April 2026 and all remaining businesses from 1 January 2027; KSeF required for B2B transactions of businesses with a registered office or fixed establishment in Poland.
- Peppol BIS Billing 3.0 — OpenPeppol AISBL, Post-Award Coordinating Community, OpenPeppol AISBL, Peppol specification documentation, version 3.0.21; read November 20, 2026, 2026. Foundational evidence (official report): Peppol BIS Billing is a CIUS of EN 16931; a buyer reference or purchase order reference must be provided; the unique purchase order number as the order reference and order line numbers at line level; tracing to a single related purchase order and order line; partial and final invoicing out of scope and self-billing needing a specific set-up; validation stages and country rules triggered by the seller's country.
- Use of Core Invoice Usage Specification — OpenPeppol AISBL, OpenPeppol AISBL, page modified August 26, 2026; read November 20, 2026, 2026. Contextual evidence (official report): CEN TC434 published EN 16931 on 28 June 2017 as a semantic data model; a CIUS restricts its optional elements; the Peppol CIUS lets partners start without prior bilateral agreements; buyer and seller electronic addresses are mandatory for transmission; every receiver must support the Peppol CIUS.
- Instructions on how invoices should be labelled — Swedish Defence Materiel Administration (FMV), Försvarets materielverk (FMV), supplier instructions dated January 29, 2024; read November 20, 2026, 2024. Contextual evidence (official report): Peppol invoices carry the contract or purchase order number in OrderReference ID and the order line number in OrderLineReference LineID; direct orders use the LandaID in BuyerReference and the AO in AccountingCost; a scanned or PDF invoice is considered a paper invoice.
- Digitalization and cross-border tax fraud: evidence from e-invoicing in Italy — Marwin Heinemann; Wojciech Stiller, International Tax and Public Finance 32(1) (2025) 195-237, Springer and International Institute of Public Finance; abstract record on IDEAS/RePEc; read November 20, 2026, 2025. Current empirical evidence (peer reviewed journal): Trade data gap for imports to Italy from other EU countries as a proxy for cross-border VAT fraud; a significant decline after mandatory e-invoicing; an estimated cut in the Italian VAT loss of about €2.2 billion to €2.6 billion in 2019 compared with 2018.
- Study on the practical application and implementation of the European e-Invoicing standard — PwC EU Services for the European Commission, DG GROW, European Commission, DG GROW, final report of July 18, 2017; read November 20, 2026, 2017. Foundational evidence (official report): The European standard holds only the essential information elements for legal, including fiscal, compliance and interoperability; it may also be used between private sector enterprises; unstructured text cannot be processed automatically and requires human intervention.
- FENIX D2.5 Governance Structure — FENIX consortium (main author: Polytechnic University of Bari), FENIX, EU-funded logistics data-sharing project; deliverable D2.5 delivered December 31, 2021; read November 20, 2026, 2021. Contextual evidence (official report): Peppol is an eDelivery network of access points through which public and private entities reach trading partners; sender and receiver may choose their service providers independently, with no roaming agreements or charges allowed between the access points.
- VAT in the Digital Age (ViDA) Tax Dossier — IBFD, IBFD research platform, tax dossier last reviewed November 16, 2026; read November 20, 2026, 2026. Contextual evidence (industry analysis): The first ViDA pillar as real-time transaction-by-transaction reporting based on e-invoicing; Member State implementation dates may vary; a Belgian law implementing the first stage (2 November 2026); a Dutch announcement of mandatory domestic e-invoicing and digital reporting (14 September 2026); a Bulgarian ministry proposal for mandatory domestic e-invoicing (25 September 2026).