UK e-invoicing requirements: a checklist for finance teams

From 1 April 2029, VAT-registered persons in the UK will need to be able to issue and receive VAT invoices as e-invoices, unless a specific exemption applies. The government has also decided that Peppol will be the UK’s core interoperability framework. The requirements reach both your sales ledger and your purchase ledger. The detailed rules are due between October 2027 and April 2028, according to the roadmap for e-invoicing implementation published on 28 October 2026.

This checklist separates what gov.uk has confirmed from what is still to be published. Every source was checked on 13 November 2026. Nothing here is tax advice.

What are the e-invoicing requirements in the UK today?

Today, e-invoicing is optional for most UK businesses, and HMRC’s rules for electronic VAT invoices are in VAT Notice 700/63. The main points:

• It is your choice. The notice says it is up to you whether you issue paper or electronic VAT invoices.

• Your customer has to agree. Under section 4.1, you may invoice electronically where your customer agrees and the authenticity of origin, integrity of content and legibility of the invoice can all be ensured.

• The content is the same as a paper invoice. Section 3.1 says electronic invoices must carry the same information as paper VAT invoices.

• Keep invoices for 6 years. Section 5.4 says you must normally keep copies of all invoices you issue and receive for 6 years.

One public sector case goes further. The consultation response records that public bodies covered by the 2023 procurement legislation must accept e-invoices that comply with BS EN 16931.

What will the UK e-invoicing requirements be from 1 April 2029?

These points are confirmed on gov.uk:

• VAT invoices issued in a specified electronic format. The Budget 2026 document sets this out from 1 April 2029.

• Issuing and receiving. The roadmap says VAT-registered persons, including public sector bodies, must be able to do both, so AP teams need to be able to take e-invoices in.

• Peppol as the core framework. The roadmap lists the Peppol core interoperability framework as already decided. Businesses will not need to become Access Points, and most are likely to connect through their accounting software, finance system or e-invoicing software provider. Businesses will need to check that their provider supports the UK requirements.

• The content and timing of VAT invoices stay the same. The roadmap says the move to e-invoicing does not change when a VAT invoice must be issued or what it must contain.

• A business identifier. To send and receive e-invoices through the Peppol network, all e-invoicing users will need to register a business identifier as part of their Peppol participant identity. The roadmap says software providers will usually handle the technical setup.

The legislation is not yet in place. In the roadmap, published on 28 October 2026, the government said it intended to introduce the primary legislation in Finance Bill 2026, and that it is expected to become law in spring 2027, subject to Parliamentary approval. The secondary legislation may not conclude until autumn 2028 or early 2029.

What is not yet confirmed?

• How EDI will fit. The government intends that EDI can continue alongside the framework, but businesses using EDI will also need to be able to exchange e-invoices through the framework. Further work will determine how that operates, with guidance due in autumn 2027.

• The technical standard. The UK will build on established international standards, including those already used within the Peppol framework, and may need a limited number of UK-specific requirements. No standard has been named. A technical consultation is planned for spring 2027.

• Which identifier. The decision is due between October 2027 and April 2028.

• Exact exemptions. They will be tightly defined and limited. Guidance for specific groups is due by the end of 2027.

• Penalties. The government plans to use the existing VAT invoicing penalties framework as a basis, as far as possible. Details of taxpayer obligations and compliance guidance are due by April 2028.

• Digital reporting. A separate consultation closes on 20 January 2027, and the government has not decided whether to introduce it. The consultation document says any future digital reporting would be separate from the e-invoicing requirements that start in April 2029, and would need separate policy decisions.

What should finance teams check now?

The roadmap says there is no need to begin implementing before the detailed requirements are published, but that you should begin planning. These are our suggestions for what that planning covers:

1. Tell the people involved. The roadmap suggests making sure finance, tax, procurement and digital teams are aware, and speaking to your accountants or advisers.

2. Map how invoices reach you. Count PDFs by email, paper, portals, EDI and structured invoices. The mix tells you how big the change is.

3. Check how invoice data reaches your ledger. Ask whether your ERP or AP software can take structured invoices and post them with your nominal codes, tax codes and dimensions intact. Do not assume there is an API: one UK client’s accounting system has no API, so approved invoices are transferred in a daily CSV bulk upload file emailed to the finance team.

4. Check you can send structured sales invoices. Find out what your billing system can produce and send.

5. Ask your software providers for their plan. Ask each one whether it will support the UK requirements and provide Peppol access. Our guide to Peppol access points in the UK explains how that works. The roadmap says several software providers have committed to including e-invoicing products in their core package at no additional cost once e-invoicing is required, and many SMEs will not need to buy separate software. Larger companies may prefer something integrated with their ERP.

6. Review your supplier master data. Note which suppliers already send structured invoices, and which are likely to keep sending PDFs because they are outside the requirement. The roadmap says invoices from businesses that are not VAT registered will not have to be e-invoices.

7. Keep matching and approvals in place. Structured data removes keying, but each e-invoice still has to be matched, where there is a purchase order, and approved, so your controls need to run on every one.

When will the detailed rules be published?

The roadmap sets out these stages:

• Budget 2026 to October 2027. Detailed design and a consultation on technical standards.

• October 2027 to April 2028. Key requirements published, covering scope, exclusions, standards, guidance, business identifiers and requirements for service providers.

• April 2028 to April 2029. A communications campaign, preparation, testing and onboarding.

• 1 April 2029. The requirements take effect.

Our guide to the UK e-invoicing mandate covers the background, and what Peppol is explains the network.

Where Stratas fits

Stratas receives Peppol, UBL and XML invoices alongside PDFs. Each invoice is validated, approved and posted to your ERP in one workflow. Stratas has 100+ ERP integrations.