What the UK Mandate Actually Means
The mandate is confirmed. The timeline is set.
What the UK mandate actually means and what you need to think about
The UK government has confirmed it: mandatory e-invoicing is coming on 1 April 2029. For end-users and finance teams, that's a 2029 problem. For software vendors and service providers, the clock is already ticking.
If your platform invoices UK businesses, or if your customers do, this mandate will touch your product. Here's what you need to understand, and what to do about it now.
The UK's 2029 mandate requires structured electronic invoices for B2B transactions. That means PDF invoices, even well-formatted ones, will no longer be legally compliant for in-scope transactions. Invoices will need to be machine-readable, structured data, exchanged via an approved network.
The UK is expected to align with international Peppol standards, consistent with the approach already adopted across Europe, Singapore, Australia, and New Zealand. Full details are still being finalized, but the direction is clear.
If your platform invoices UK businesses, or if your customers do, this mandate will touch your product.
Why 2029 Sounds Far Away (But Isn't)
Here's the reality for software vendors: your customers will start asking about compliance in 2027. Enterprise procurement cycles for infrastructure changes run 12-24 months. Certifications, testing, and onboarding take time. And if you're building Peppol capability yourself from scratch, you're looking at 12+ months of development, testing, and accreditation work.
The vendors who move in 2026 will have a compliant, production-ready solution by 2027 and a competitive advantage over those who wait.
What Compliance Requires at the Infrastructure Level
For a software vendor to send and receive e-invoices on the Peppol network (the expected UK framework), you need two things:
1. Peppol Certified Access Point (AP)
This is the certified gateway that connects your platform to the Peppol network. You either build and certify your own, or you connect via a pre-accredited infrastructure provider. Building your own takes 12+ months and requires ongoing OpenPeppol certification maintenance, security audits, and compliance updates. Most software vendors choose to partner with an AP provider.
2. Peppol Certified Service Metadata Publisher (SMP)
This is the registry that makes your customers discoverable on the Peppol network, so other participants can find and send invoices to them. Often overlooked, but essential. Without SMP, your customers can't receive.
The Build vs. Buy Decision
This is the question most product teams are wrestling with right now. We published a detailed white paper on this, but the short answer:
- Building your own AP may make sense if you process a very high volume of >100M invoices/year, have a dedicated compliance engineering team, and have 12-18 months of runway before you need to be live.
- Partnering with a pre-accredited infrastructure provider makes sense for everyone else. You get instant time to market, guaranteed compliance, and zero maintenance overhead on certifications as standards evolve.
For the UK mandate specifically: given that full requirements are still being finalised, partnering with a provider who stays current with regulatory changes is a lower-risk path. If you want to read and in depth analysis on the buy vs build decision, download our whitepaper.
UK Versus Europe Connection
The UK mandate doesn't exist in isolation. Belgium went live on 1 January 2026 with mandatory e-Invoicing using the Peppol netwoork. France is manadating B2B e-invoicing from September 2026, again using the Peppol network. Germany has been phasing in since 2025. Many other countries will follow. The EU's EN 16931 standard is being updated mid-2026.
If your platform or business operates across European markets, or if your customers do, you need a single, unified infrastructure that handles multiple networks and jurisdictions without requiring you to build separate integrations for each country. Arratech provides this structure.
What to Do Right Now
1. Audit your current invoicing infrastructure. Can it produce structured Peppol-format invoices today? If not, how long would it take?
2. Talk to your largest UK customers. Some will already be asking questions. Getting ahead of their concerns builds trust.
3. Evaluate your AP/SMP options. If you're going the partnership route, start now, onboarding, testing, and integration take time even with a pre-accredited provider.
4. Watch the HMRC guidance closely. The mandate framework is still being defined. A good infrastructure partner will keep you updated automatically.
The mandate is confirmed. The timeline is set. The vendors who treat this as a 2026 infrastructure decision, not a 2028 scramble, will be in the strongest position when April 2029 arrives.
Arratech provides Peppol certified Access Point and SMP infrastructure for software vendors and service providers and we will be accredited in UK well before the deadline.
FAQs
The UK government has signalled that it will align with international standards and will most likely adapt to the Peppol Network, the same network already mandatory in Belgium, Germany, Australia, and Singapore and used in many other countries. Full technical specifications are still being finalised by HMRC, but the direction is clear: structured XML invoices exchanged via an approved network, consistent with the EN 16931 European standard. This is good news for vendors already connected to Peppol elsewhere. Slovakia, Belgium, and the UK are all expected to use the same underlying infrastructure model, meaning you can work with one Peppol Access Point infrastructure provider such as Arratech and cover all of them. Arratech monitors HMRC guidance continuously and will update customers as the UK framework is confirmed.
No and this is one of the strongest arguments for acting now. Peppol is a single network with country-specific configurations, not a collection of separate systems. Through working with an infrastructure provider such as Arratech, you can cover UK, Belgium, Germany, France, Slovakia, and many other mandate markets through one connection. The invoice format (EN 16931 XML) is the same European standard across all of them. The difference between countries is which Peppol Authority accredits providers, which syntax variants are accepted, what additional reporting obligations apply. Arratech's unified API handles this per-country complexity automatically, so your platform doesn't need a separate integration for each jurisdiction.
The demand from your customer does not correlate with the deadline of 2029, it's that your enterprise customers will start asking about what you are doing to stay compliant already in 2027, and procurement cycles for infrastructure changes run 12–24 months. The practical answer is almost always to partner with a dedicated experienced Peppol Access Point provider rather than build your own. Building and certifying your own Peppol AP takes 12+ months, requires ongoing OpenPeppol certification maintenance, and demands a dedicated compliance engineering function. Partnering gives you the certainty of being live well before deadline, compliance updates being handled by your partner and provides one simple connection for the increasing complexity as each country implements its own flavor of Peppol Network. The vendors who are ready in 2027 are the ones making the partnership decision in 2026.
Glossary
A Service Metadata Publisher (SMP) is a registry on the Peppol network that stores essential details about a business or organisation — such as which types of electronic documents (e-documents) it can receive (e.g., e-invoices, purchase orders) and how those documents sho
If your organisation wants to receive e-documents via Peppol, it must be registered in an SMP. Without this registration, other companies and government agencies cannot find the technical information they need to deliver documents to you.
The Service Metadata Locator (SML), the only central component in the Peppol eDelivery Network. It keeps track of where each participant’s Service Metadata Publisher (SMP) is located. When a sender wants to deliver an electronic document, their Access Point queries the SML to find the correct SMP address for the recipient. The SMP then provides the detailed technical information needed to send the document securely and correctly.
A DNS record type formerly used for SML lookups (pointing one domain name to another) that is being deprecated in this context.
A DNS record type that replaces CNAME in the new lookup method. It supports more advanced and flexible routing for metadata resolution.
More Stories
The Peppol network is often described as a “four-corner model”, but what does that actually mean in practice? This article breaks down the Peppol transport model in a simple way, showing how electronic invoices move securely from sender to receiver through trusted Access Points. Learn how the Peppol infrastructure enables reliable document exchange without complex one-to-one integrations, and why the model has become the foundation for modern e-invoicing across Europe and beyond.
EN 16931 is being updated ERP providers and software vendors in the Peppol network need to be ready.
The revised EU e-invoicing standard is expected mid-2026, bringing stricter validation rules, expanded data requirements, and new implications for Peppol and e-invoicing platforms. Read the blog to understand what’s changing and how to prepare.
The UK’s mandatory e-invoicing mandate starts on 1 April 2029, but software vendors need to prepare now. Businesses that invoice UK companies should assess Peppol readiness, Access Point and SMP infrastructure, and build-vs-buy options well ahead of compliance deadlines.
Ready for a simple connection to the future of e-Invoicing?
Join the next generation of e-Invoicing infrastructure from Arratech.
Cut costs, stay compliant, and integrate effortlessly.