Prepare early for the UK mandate—without rework
1st April 2029 is closer than it looks! Time is on your side, but not to waste. Use the lead-in to align UK plans with pan-European mandates, standardise on EN16931, and be ready before the rush.
What's behind the mandate
and why preparing early pays off
The UK is moving toward mandatory e-invoicing for VAT invoices from April 2029, with Peppol now announced as the core interoperability network. This gives businesses, software providers, and service providers a clearer direction for planning, while important details — including the final operating model, technical specifications, and the role of legacy systems — are still being shaped through stakeholder engagement. Preparing early helps businesses align systems, data, and processes step by step instead of reacting under time pressure once the final requirements are published.
Compliance and automation—two sides of one design
The UK mandate is a trigger to modernise. Build for VAT compliance and you’ll unlock automation, visibility and scale for Finance and IT.
VAT compliance
Design for EN16931, the UK timeline, and Peppol as the announced core interoperability network, then scale across Europe via interoperable e-invoicing frameworks. Apply country-specific rules, validations, and status handling with unified monitoring and optional compliant archiving. A managed, global framework like the SEEBURGER E-Invoicing Hub reduces maintenance effort while keeping pace with changing regulations.
- Country rules, validation & reporting handled centrally
- Certified Peppol connectivity for reliable exchange
- Real-time status visibility and audit trail across invoices
- Coverage across 35+ countries via one hub
Process automation & optimisation
Move from manual handling to “data-first” straight-through processing. Use structured invoice data for matching, posting and approvals inside your ERP (e.g. SAP ECC/S/4HANA) with a central cockpit for exceptions rather than keystrokes. One platform consolidates inbound, outbound and reporting to simplify the IT landscape and cut cycle times.
- Touchless posting and faster non-PO approvals
- Fewer errors, fewer disputes, quicker closes
- Unified monitoring for Finance and IT
- Scalable interfaces you can reuse across countries
Preparing for UK e-invoicing: what Peppol means for your next steps
The UK government has announced Peppol as the core interoperability network for e-invoicing in the UK. This gives businesses a clearer direction for planning ahead of the 2029 mandate: Peppol connectivity, structured invoice data, and interoperable exchange should now be part of readiness discussions. At the same time, the final operating model has not yet been published. The UK still needs to define how Peppol will work in practice, how legacy systems will be handled, and whether any authority-facing reporting or oversight layer will be added.
Confirmed direction
Peppol will be the core interoperability network for UK e-invoicing. For businesses, this means Peppol readiness is no longer just a useful option based on public-sector experience. It is now part of the government’s stated direction of travel for the 2029 mandate.
What this means in practice:
- Greater focus on structured, standardised invoice data across inbound and outbound processes
- Increased importance of supplier onboarding and readiness for interoperable exchange
- A shift towards more automated validation, matching, and exception handling
- The need to assess existing ERP, AP, and AR setups for compatibility with Peppol connectivity
- Consideration of scalable integration, monitoring, and service-provider capabilities for future rollout
Still open: four-corner or five-corner?
Peppol is commonly associated with a four-corner model, where the supplier and buyer each use their own service provider and exchange invoices through an interoperable network. The UK has not yet confirmed whether this will remain a pure four-corner setup or whether an additional authority-facing layer will be added.
What this means in practice:
- Prioritise solutions that support reliable exchange today while remaining adaptable to future regulatory changes
- Expect that reporting, audit, or clearance requirements could introduce an additional compliance layer
- Favour architectures that allow extensions without disrupting existing invoice flows
- Ensure visibility and control across invoice processing, regardless of how the final model evolves
What to prepare now
Even before the final technical specifications are published, businesses can act on the direction already confirmed: structured invoice data, interoperable networks, and scalable onboarding will matter. Early preparation helps avoid last-minute remediation once the implementation roadmap and detailed guidance are available.
Key areas to focus on include:
- Improving invoice data quality and consistency across systems and partners
- Reducing manual touchpoints in approval and posting processes
- Strengthening auditability and transparency across AP and AR
- Assessing readiness for Peppol connectivity and structured data exchange
- Establishing central monitoring and exception handling capabilities
- Designing scalable integration patterns that can support UK and international requirements from a single platform
The solution: The SEEBURGER E-Invoicing Hub
The SEEBURGER E-Invoicing Hub is a cloud service that automates invoice exchange end-to-end and gives Finance and IT real-time control across countries—built for changing mandates, interoperable networks and deep ERP integration.

Global compliance framework
The central hub handles country rules, reporting and digital signatures, with real-time monitoring and optional compliant archiving, so you stay ahead of evolving mandates without adding maintenance burden.

Advanced processing & Peppol connectivity
The hub delivers format conversion, validation, and visualisation with universal connectivity, including a certified Peppol Access Point. This enables reliable, interoperable invoice exchange through the network now confirmed as central to the UK’s e-invoicing direction.

Seamless ERP integration
Embeds into SAP ECC/S/4HANA and other ERPs to enable a central cockpit, data-first automation, and structured status handling, reducing manual work and supporting compliant invoice processes.
As a certified Peppol Access Point with many years of experience, SEEBURGER’s E-Invoicing Hub provides a central, secure gateway to the global Peppol network. This network is increasingly essential for compliant B2B e-invoicing and e-procurement, acting as the default framework in many countries, such as Belgium. It is a key channel in France and Germany.
The SEEBURGER E-Invoicing Hub simplifies this connection, enabling you to easily exchange invoices, orders, and other procurement documents. It supports the latest Peppol Business Interoperability Specifications and leverages our deep expertise in the underlying AS4 protocol.
Native SAP integration: from invoice to posting
With deep SAP expertise and certified add-ons/adapters, we embed e-invoicing inside SAP ECC and S/4HANA, so AP works in one cockpit, exceptions are handled where teams operate, and invoices flow touchlessly from receipt to posting and payment. You gain real-time status tracking, data-first automation, workflows for non-PO approvals, and the ability to return Peppol status messages for full process compliance.
Key benefits for Finance & IT
- Faster acceptance, fewer loops: A central SAP cockpit shows end-to-end status, so teams resolve exceptions quickly instead of chasing black-box processes
- No re-keying: Data-first automation posts structured invoices straight into SAP, reducing errors and cycle time
- Quicker approvals: Automatic workflows route non-PO invoices through SAP to accelerate period close
- Lower tech debt: Delivered via certified SAP add-ons/adapters, avoiding one-off custom code and easing upgrades
Your SAP path to compliant automation
Plan
E-invoicing succeeds in SAP when the landscape is understood first: AP/AR flows, company codes and trading partners in ECC or S/4HANA, the EN16931 syntaxes to be supported, such as UBL/CII, and connectivity requirements, including Peppol as the UK’s announced core interoperability network.
With clear roles, KPIs and exception policies defined inside SAP, Finance gains a clear target state while IT establishes a reusable integration pattern—covering interfaces, error handling, and transports—that scales beyond the UK.
Build
The capability comes to life inside SAP rather than in a side-portal. Validations, mappings and tolerance checks provide data-first posting, duplicate detection and tax/ID controls reduce avoidable rejections, and non-PO approvals follow familiar SAP workflow/Fiori.
Connectivity to Peppol and accurate business partner identifiers anchor reliable exchange.
The outcome is fewer exceptions for Finance and a predictable, low-customisation footprint for IT.
Run
Day-to-day operations revolve around a single SAP cockpit showing real-time status visibility, actionable messages and alerts. Supplier onboarding progresses in waves, while touchless rate, exception rate and cycle time offer a shared view of performance.
As requirements evolve, rules and transports move in a controlled manner.
Finance benefits from real-time visibility and quicker closes, while IT benefits from stable operations and a model that extends cleanly across entities and countries.
Beyond SAP: unified connectors on one platform
If SAP isn’t the only ERP in scope, the same Hub approach extends to Microsoft Business Central and others, consolidating inbound, outbound and reporting on one unified SaaS platform with central monitoring.
From mandate to measurable impact
Be part of our global network of industry-leading customers.
Roles that make e-invoicing succeed
One mandate, three perspectives. A central e-invoicing hub aligns Finance and IT on compliance, automation and control without adding complexity.
Cash, compliance and control sit at the top of the agenda, but fragmented tools and manual exceptions erode margins. The E-Invoicing Hub standardises invoice data (EN16931), applies country rules centrally and feeds clean, auditable information into your ERP, reducing rework, write-offs and late-payment risk.
With real-time visibility over touchless rates, exceptions and cycle time, Finance gets faster closes and stronger cash discipline while staying ready for the UK timeline and parallel EU changes.
Multiple point integrations, bespoke mappings and one-off country fixes are costly to build and harder to run. A central hub provides a single connectivity and compliance layer—Peppol and other channels, validations, reporting, monitoring—exposed to SAP ECC/S/4HANA through reusable interfaces.
The result is a simpler architecture with fewer customisations, predictable upgrades and a platform that scales from UK requirements to wider European roll-outs without refactoring.
Day-to-day pain comes from mismatches, missing data and portal hopping. With the E-Invoicing Hub embedded in SAP, invoices arrive structured, validated and ready for posting, while non-PO approvals flow through familiar workflows. Acknowledgements/statuses messages, such as in Peppol, are visible in one place.
Exceptions are handled with clear reasons and context, shrinking resolution times and disputes.
Teams spend less time chasing and more time improving first-time-right and supplier/customer experience.
Across Europe: key e-invoicing roll-outs
International business: The landscape is complex, but our E-Invoicing Hub is your single, trusted route to guaranteed compliance in 35+ countries.
Applies to: All VAT invoices
Architecture: Structured e-invoices exchanged via interoperable standards and transmission mechanisms; Peppol has been announced as the core interoperability network, while the final operating model is still to be defined
Timeline: Mandatory e-invoicing from April 2029; detailed rollout timing and implementation approach expected in the Budget 2026 roadmap
Formats & transmission: Final technical specifications are still pending; businesses should prepare for structured e-invoices, EN16931 alignment where relevant, and Peppol-based interoperability
Penalties: Expected to be published at Budged 2026
Archiving: VAT records generally must be kept for at least 6 years for tax purposes; specific e-invoicing archiving requirements have not yet been defined
Applies to: All companies established in France and subject to VAT
Architecture: Y-model (schéma en Y) via accredited private platforms, officially called plateformes agréées, which exchange invoices and transmit required data to the French tax administration
Timeline: Mandate begins 1st September 2026, when large and medium companies must start issuing e-invoices and ALL companies must be able to receive them. The issuing mandate extends to all remaining businesses on 1st September 2027
Formats & transmission: Accepted formats are UBL, CII, and the hybrid Factur-X. Direct exchange is prohibited; all transmissions must go through accredited PAs which report invoice data to the state’s central hub, the PPF
Penalties: A fine of €15 per invoice for e-invoicing non-compliance and a fine of €250 per transmission for e-reporting failures
Archiving: A 10-year retention period is standard practice to cover the full statute of limitations for tax audits
Learn more about the French e-invoicing reforme!
Applies to: All German businesses engaging in domestic B2B transactions. Exemptions exist for small-value invoices and transport tickets
Architecture: Decentralised (without a central platform)
Timeline: The first mandatory step is on 1st January 2025, when all businesses must be technically capable of receiving e-invoices. Mandatory issuance is then phased in, starting 1st January 2027, for larger companies and becoming universal by 1st January 2028
Formats & transmission: In compliance with EN16931, the most common formats are XRechnung (XML) and the hybrid ZUGFeRD/Factur-X, while there is no mandated channel; exchange can happen via email, APIs, private networks, or PEPPOL
Penalties: The primary consequence of non-compliance is the potential inability to deduct the associated input VAT; general fines for invoicing violations can also apply
Archiving: A strict 10-year retention period is required, compliant with the GoBD principles for digital documents
Applies to: All Belgian-established taxpayers, including members of a single VAT group; excludes B2C transactions, certain VAT-exempt B2B transactions, and non-established taxpayers
Architecture: “Big bang” approach based on Peppol
Timeline: A universal go-live date of 1st January 2026 with a complementary near real-time e-reporting system is scheduled for 2028
Formats & transmission: Invoices must comply with EN16931 and use the PEPPOL BIS format; PEPPOL is the default transmission network, but direct EDI is permitted if the format is compliant
Penalties: Administrative fines begin at €1,500, rising to €5,000 for subsequent violations of technical requirements
Archiving: A 10-year retention, with special cases extending to 15 or 25 years
Applies to: All taxpayers required to issue invoices under Polish VAT rules, including foreign businesses with a fixed establishment in Poland where that establishment participates in the transaction
Architecture: Central clearance via KSeF
Timeline: February 1, 2026 for businesses with 2024 sales above PLN 200 million including VAT, and April 1, 2026 for others; KSeF penalties are deferred until January 1, 2027
Formats & transmission: Structured XML invoices compliant with the official KSeF schema; invoices are submitted to the central KSeF platform, where they receive a unique KSeF number and are made available to the recipient
Penalties: KSeF penalties are deferred until 1st January 2027; fine levels depend on the type of infringement and should be checked against the applicable VAT Act provisions
Archiving: KSeF will also serve as the official state archive, storing all cleared e-invoices for a period of 10 years
Applies to: The B2B mandate covers companies and professionals in Spain for domestic B2B transactions. SII applies to monthly VAT filers, including large businesses above €6,010,121.04 turnover, REDEME taxpayers and VAT groups. VERI*FACTU applies separately to taxpayers using covered invoicing software, subject to regulatory exclusions.
Transaction scope: The B2B mandate covers domestic B2B transactions. SII covers VAT ledgers for issued and received invoices. VERI*FACTU covers billing records generated and preserved through compliant invoicing systems.
Timeline: Spain introduced the B2B e-invoicing mandate through Law 18/2022. Rollout begins after the implementing regulation is approved: one year later for businesses and professionals with annual turnover above €8 million and two years later for all others. VERI*FACTU applies separately from 1 January 2027 for corporate income taxpayers and from 1 July 2027 for other affected taxpayers.
Formats & transmission: The B2B model combines interoperable private platforms with a public solution. Structured e-invoices and invoice status information are core elements, with further technical details to follow.
Penalties: Non-compliance with B2B e-invoicing obligations may lead to penalties under the applicable legal framework. VERI*FACTU and SII penalties are calculated under separate rules.
Archiving: The standard legal retention period for invoices and tax-related documents in Spain is 6 years.
Applies to: VAT-taxable businesses carrying out cross-border trade with other businesses (B2B) within the EU
Architecture: EU ViDA digital reporting based on structured e-invoicing for cross-border B2B transactions; no Netherlands-specific central clearance platform has been announced
Timeline: As of 1st July 2030
Formats & transmission: Businesses must use structured e-invoices aligned with the European standard; Dutch transmission rules and technical infrastructure are not yet specified
Penalties: Not yet published
Archiving: VAT administration records for 7 years and 10 years for records related to immovable property
Applies to: Public-sector e-invoicing is established for suppliers to public authorities; any broader B2B e-invoicing obligation should be treated as pending until final national rules are confirmed
Architecture: Decentralised exchange using EHF/Peppol infrastructure for public-sector e-invoicing; no general domestic B2B clearance platform should be assumed
Timeline: Public-sector e-invoicing is already established; timeline for any broader B2B obligation should be confirmed against final Norwegian legislation
Formats & transmission: EHF/Peppol-based exchange is central in public-sector e-invoicing; detailed requirements for any broader B2B mandate should be checked once final rules are published
Penalties: Not yet confirmed for a broader B2B e-invoicing mandate
Archiving: Use the general Norwegian bookkeeping and accounting retention rules unless specific e-invoicing archiving requirements are published
Applies to: VAT-taxable businesses carrying out cross-border B2B transactions within the EU under ViDA; Ireland has no confirmed domestic B2B e-invoicing mandate in force for all businesses
Architecture: EU ViDA digital reporting based on structured e-invoicing for cross-border B2B transactions; no Ireland-specific central clearance platform has been announced for domestic B2B e-invoicing
Timeline: 1st July 2030 for EU cross-border B2B digital reporting requirements under ViDA; domestic real-time reporting alignment by 1st January 2035 only applies if Ireland introduces or operates such a system
Formats & transmission: Structured e-invoices aligned with the European standard; national transmission rules for a domestic B2B mandate are not yet specified
Penalties: Not yet published for a domestic B2B e-invoicing mandate
Archiving: Use the standard Irish VAT and accounting record-retention rules unless specific e-invoicing archiving requirements are published
Applies to: VAT-taxable businesses carrying out cross-border B2B transactions within the EU under ViDA; no final domestic B2B e-invoicing mandate details should be assumed unless confirmed by Slovak legislation
Architecture: EU ViDA digital reporting based on structured e-invoicing for cross-border B2B transactions; domestic architecture still subject to national implementation
Timeline: July 1, 2030 for EU cross-border B2B digital reporting requirements under ViDA; domestic alignment requirements apply by January 1, 2035 where Slovakia introduces or operates domestic real-time digital reporting
Formats & transmission: Structured e-invoices aligned with the European standard; national transmission rules and technical infrastructure are still to be specified
Penalties: Not yet published for a Slovakia-specific B2B e-invoicing mandate
Archiving: Use the general Slovak tax and accounting retention rules unless specific e-invoicing archiving requirements are published
Scope: EU-wide VAT reform framework, not a single-country mandate
Applies to: Cross-border intra-EU B2B transactions, with further measures for platform economy rules and single VAT registration across the EU
E-invoicing timeline: Mandatory e-invoicing and digital reporting requirements for cross-border B2B transactions from 1st July 2030
Architecture: EU-level digital reporting based on structured e-invoices for cross-border B2B transactions, with Member States required to align domestic digital reporting systems with the EU model by 2035
Business impact: UK businesses trading with EU partners should design invoice data, ERP interfaces, reporting logic, and compliance monitoring with ViDA in mind to avoid separate country-by-country projects later
Strategic takeaway: Build the UK setup as part of a scalable European e-invoicing and digital reporting architecture, not as an isolated compliance project
Your partner for the UK e-invoicing mandate
UK organisations deserve a reliable, secure path to e-invoicing reform. SEEBURGER is a global leader in business integration (B2B/EDI), founded in Germany in 1986. With nearly 40 years of experience, we help more than 14,000 customers connect applications, automate processes, and orchestrate data flows with confidence.
Our commitment to the UK is long-term. We combine local expertise with a global operations footprint to support Finance and IT through design, rollout and steady-state operations across all industries and company sizes.
For SAP ECC and S/4HANA, our native connector and certified extensions bring e-invoicing inside SAP. Finance teams benefit from Peppol status message, allowing them to manage exceptions without leaving SAP, improve first-time acceptance, and safeguarde cash flow.
The SEEBURGER E-Invoicing Hub is built for EN 16931, interoperable networks, and evolving UK guidance, with certified Peppol Access Point capability and a global compliance framework that scales across Europe. This means one platform for UK readiness today and a clear route for future mandates.
Ready to comply with confidence?
Build on the UK’s confirmed Peppol direction and position your business for a smoother 2029 transition.
Seamless Peppol connectivity
Connect via SEEBURGER’s certified Peppol Access Point to exchange structured invoices securely, at scale, and with full visibility.
International format safeguards
Protect outbound and inbound flows and transformations across 35+ jurisdictions.
Compliance, and then some
Go beyond basic compliance with monitoring, audit trails, alerts, and proactive legal change management built in.
Get ready for the UK’s 2029 shift to structured e-invoicing. See what’s confirmed, what’s still open, and how Finance and IT can align early to reduce risk and enable automation.
The UK has confirmed mandatory e-invoicing for all VAT invoices from 2029. This blog explains what’s officially decided, what still evolves, and how Finance and IT can prepare without rebuilding twice. We cover scope, likely Peppol alignment, and practical steps for 2026–2028 so you’re ready on day one, including data, connectivity, and…
Learn how the SEEBURGER E-Invoicing Hub helps you ensure compliance and automate your invoicing processes efficiently. Country-specific requirements, Peppol connectivity and seamless integration with SAP are at the core.