As part of the 2025 Budget the UK government confirmed its intention to introduce mandatory e-invoicing for VAT invoices.
For many UK finance teams, this will mark a shift away from emailing PDFs toward exchanging invoice data in a way that can be processed automatically between financial systems.
This change won’t just affect technology, it will affect the day-to-day reality of the Accounts Payable↗ process. How invoices arrive, how they’re validated, how approvals work, and how quickly exceptions are resolved, will all change. However, with an expected go-live date of April 2029, UK businesses have enough time to prepare themselves.
Quick facts
- The government has chosen to mandate e-invoicing for all VAT invoices from 2029.
- VAT invoices are typically issued for B2B and B2G transactions (not generally B2C).
- A more detailed implementation roadmap is due at Budget 2026, with stakeholder collaboration starting January 2026.
- PDFs, Word docs, images, HTML invoices, and OCR outputs don’t count as e-invoices for the policy definition used in the consultation response.
This article explains what the mandate means, who’s likely to be affected, what’s still to be defined, and how to prepare your business. We’ll also show how Moss can support the AP foundations you’ll want in place well before 2029.
What ‘e-invoicing’ means in practice (and why PDFs don’t count)
A common misconception is that e-invoicing is simply sending an invoice via email. In reality, e-invoicing is about structured invoice data being exchanged digitally in a standardised way so it can be received and processed directly by the buyer’s finance system.
That’s different from sending a PDF or image attachment, even though that feels ‘digital’. The core idea is facilitating and promoting machine-readable data that enables automation, consistency, and better controls. Normal documents that still require manual steps (opening, reading, re-keying, or OCR↗ interpretation) take more time to process, and are more prone to errors.
In the government’s definition, formats like PDF/Word, images (JPEG), HTML invoices, and OCR outputs aren’t treated as e-invoices, because they don’t exchange structured data system-to-system.
If your business is currently receiving invoices via a shared mailbox, saving PDF attachments, and typing data into your accounting system, you’re definitely not alone. This has become the standard invoice processing workflow for most SMEs. But it’s something that the new mandate is designed to move away from.
One practical way businesses already exchange structured invoice data is via Peppol↗. Peppol is a widely used framework and network for sending e-invoices and other procurement documents as machine-readable data. Instead of building one-off integrations, organisations connect through certified Peppol Access Points (the 'four-corner' model), which enables consistent exchange across many trading partners.
What the UK has announced so far
While the technical details are still to be decided, the UK government has indicated that mandatory e-invoicing will be introduced for VAT invoices starting in 2029. Design and implementation will be settled upon in collaboration with stakeholders and the software market . It has also signalled that a more detailed roadmap is expected as part of future budget planning. At this point the operating model, standards, and other specifics will be clarified.
Professional bodies and industry commentators have welcomed the longer lead time to prepare. The underlying message is that 2029 is not far away in systems and process terms. This is particular true for businesses with complex supplier bases, multiple entities, or fragmented finance tooling.
Which businesses are likely to be impacted
If you issue or receive VAT invoices in the UK, you should assume that these changes will affect you in some form. In most organisations, this will mean that Accounts Payable and Procurement↗ will feel the change first, as that’s where invoice volume, supplier diversity, and operational friction tend to be highest.
Businesses that invoice the public sector or work heavily in B2B supply chains should be especially alert, since interoperability and compliance requirements often cascade through tightly woven supplier networks.
Some of the smallest businesses might find themselves outside the initial scope of the e-invoicing changes due to the focus on VAT invoicing. Even then, many small suppliers will still need to align in practice if their larger customers require e-invoices as the default.
What’s still not fully defined (and why you shouldn’t wait)
Mandates like this usually start with policy intent and timelines, and then tighten into specific technical requirements later on. Remaining open questions typically include which standards are mandated, what “compliance” looks like in day-to-day operations, how cross-border and mixed-transaction scenarios are handled, and how exceptions and credit notes should be represented and tracked.
It’s tempting to delay action until every detail is published. But the most time-consuming work is usually not the final format decision. The hard part is getting invoice operations into a shape where structured data can flow cleanly. This requires consistent master data, reliable approvals, a strong audit trail, and a finance stack that doesn’t depend on manual re-keying.
In other words, there’s a lot you can do now that will still be the right move regardless of which exact standard becomes dominant.
The practical work that will pay off before 2029
If you’re looking for somewhere to start, begin by assessing your current invoice lifecycle end-to-end. Where do invoices enter your organisation today? What percentage arrive as PDFs, arrive already structured, or are created via supplier portals?
You should also ask yourself how many handoffs happen between “inbox” and “posted to ledger”? Each manual handoff is a risk point for errors, delays, and weak controls. But these are exactly the pain points e-invoicing is meant to reduce.
From there, focus on invoice data quality and process discipline. E-invoicing only works smoothly when the receiving side can reliably validate fields and route invoices correctly. That means getting consistent about supplier identities, purchase order↗ matching where applicable, VAT coding logic, and handling common exceptions such as partial deliveries, disputed line items, and missing references. If these are messy today, e-invoicing won’t magically fix them. It will simply surface them faster and more frequently.
Supplier readiness matters too. Even if your internal AP process is clean, you’ll still need to enable suppliers in waves. Most businesses find it effective to start with the suppliers that create the bulk of invoice volume (or the highest value), because that’s where automation and standardisation deliver the biggest immediate returns.
Finally, pressure-test your systems. Can you ingest e-invoice data, validate it automatically, route approvals, and keep a defensible audit trail end to end? If the answer is ‘not without spreadsheets and re-keying’, then you’re not e-invoice-ready yet.
Timeline: how to plan your work across 2026–2029
Most organisations benefit from treating 2026 as a foundation year, even before the full implementation roadmap is final. Use it to map processes, fix obvious control gaps, and consolidate invoice intake and approvals.
In 2027, you can typically move into supplier enablement and system hardening—reducing reliance on manual capture and building robust exception workflows. In 2028, you want to be testing at scale, expanding supplier coverage, and ensuring your team can run the process reliably under real-world conditions. By the time 2029 arrives, you ideally want the mandate to feel like a formalisation of how you already operate—not a frantic transformation.
Here's a quick checklist you can follow to help prepare for the start of e-invoicing. These steps are applicable regardless of the specifics of the final standard:
- Consolidate invoice intake (reduce “shared mailbox chaos”)
- Clean supplier master data (names, VAT IDs, payment terms)
- Define validation rules (PO match, VAT logic, tolerances)
- Standardise approvals + exception handling
- Ensure your stack can ingest structured data, not just store attachments
- Plan supplier onboarding in waves (top volume/value first)
