The UK government has confirmed that e-invoicing is set to become mandatory for VAT-registered businesses from 1 April 2029, subject to the implementation approach set out in the Budget 2026 roadmap. If your organisation issues VAT invoices, this change will affect how you exchange invoice data with customers and suppliers. 

It is worth being clear about what e-invoicing actually means in this context. It is not simply sending a PDF by email. The mandate requires the exchange of structured invoice data directly between financial or accounting systems, enabling invoices to be processed automatically without manual handling. 

Formats such as PDF, Word, HTML, scanned images and files processed through optical character recognition do not qualify under the government’s definition. The shift is from invoices as documents to invoices as structured, machine-readable data. That distinction matters because it changes not just how invoices are sent, but how the whole process of raising, receiving and reconciling them works. For many organisations, it will require a more fundamental rethink of finance operations than the headline date might suggest.

The current timeline for implementation is as follows: 

• From January 2026: the government works with stakeholders to co-design the technical and operational approach 
• Budget 2026: the government commits to publish a full implementation roadmap, setting out technical standards and transitional arrangements 
• 2027 to 2028: businesses prepare internal systems, clean master data, and establish standards-based connectivity 
• From 1 April 2029: VAT invoices issued by VAT-registered businesses for B2B and B2G transactions must be structured e-invoices 

Whether the transition will be a full switch-on or phased rollout is yet to be confirmed but Budget 2026 roadmap should clarify this.

SEEBURGER’s white paper explores the likely technical architecture in some detail. The government has indicated a preference for a decentralised, four-corner model, where businesses exchange invoices through their own software providers or networks rather than routing everything through a central government platform.

One of the key points the whitepaper raises is that technical readiness alone is not enough. For e-invoicing to work at scale, the data on invoices needs to be consistent, accurate, and interpretable by both parties’ systems. 

Invoices reference core business information, including buyers, sellers, delivery and billing locations, products and services, and related orders. If that data is inconsistent or ambiguous, invoices are more likely to fail automated validation, require manual intervention, or create downstream issues in finance and supply chain systems. In practice, this often comes down to whether trading partners are using the same identifiers to refer to the same things. A location referenced one way in an order and another way on an invoice, or a product identified differently across systems, can be enough to break an automated process. Cleaning up that data before 2029 is as important as choosing the right software. 

This is where GS1 standards have a role to play. They provide a common language for identifying and referencing the business data that already appears on invoices and across related processes. In an e-invoicing context, they can help organisations identify trading partners and locations consistently, reference products and services in a structured and unambiguous way, align invoice data with ordering and supply chain information and support interoperability across systems, sectors and borders. That role applies regardless of which compliant platform or network a business uses.