UK e-invoicing from April 2029: what OpenText VIM for SAP needs from Peppol and EDI

HMRC published its e-invoicing implementation roadmap on 28 October 2026, alongside the Autumn Budget. The date announced at Budget 2025 holds: from 1 April 2029, VAT-registered businesses and public bodies must be able to issue and receive VAT invoices as e-invoices, unless a specific exemption applies. Peppol is the interoperability framework. HMRC doesn't sit in the invoice flow and doesn't clear invoices before the buyer sees them.

For an SAP shop running OpenText VIM, the UK model asks less of AP than Spain's does. There's no buyer status report to the tax authority in the 2029 design. The work lands on the inbound side instead: what arrives, through which door, and whether VIM treats it as the invoice.

A PDF stops being an e-invoice. The roadmap is explicit. Invoices shared as digital files but not as structured data are not e-invoices, and it lists PDF, word-processed documents, JPEG images, HTML invoices on a web page or in an email, and fax images. If your UK supplier invoices reach VIM today as PDFs read by capture, then from April 2029 that PDF is at best a copy for in-scope domestic VAT invoices. The structured message is the invoice.

That changes the capture plan. Volume on the PDF path should fall as suppliers move to Peppol, and for a while the same invoice may arrive both ways. Decide which one VIM treats as the source of truth. We'd pick the structured one.

EDI can stay, but not on its own. HMRC's stated intention is that businesses can keep existing EDI arrangements alongside the new framework. The same paragraph adds the condition: businesses using EDI must also be able to exchange e-invoices through the Peppol-based framework. A UK buyer with a mature EDI community may end up running both. EDI with the partners who already use it. Peppol with everyone else.

In VIM terms, that's two inbound channels feeding one process: same document types, same duplicate check, same exception reasons, same Chart of Authority. If the two channels map fields differently, AP sees two versions of the same supplier, and the exception statistics split along a line nobody chose. We covered inbound e-invoices as a channel before. The UK is the first mandate on our list that formally expects EDI and Peppol to coexist.

You need to be findable. To send and receive through Peppol, every organization registers a business identifier as part of its Peppol participant identity, so trading partners can route invoices to it. Which identifiers the UK accepts is among the requirements HMRC plans to publish between October 2027 and April 2028. With several UK company codes in SAP, the practical question is how each legal entity maps to a participant identity, and how an inbound invoice reaches the right company code in VIM.

What the roadmap leaves open. Detailed scope, exemptions, standards, identifier rules and service-provider requirements are due between October 2027 and April 2028. HMRC has also opened a separate consultation on digital reporting of e-invoice data, which OpenText's summary says closes on 20 January 2027. No decision has been taken, so "no reporting" describes 2029, not necessarily later years. Keep the VIM design able to report a status one day without building for it now.

What OpenText has said. OpenText's 10 November update says it is a certified Peppol Access Point, plans to seek accreditation with the UK Peppol Authority ahead of April 2029, and supports EDI and Peppol side by side for the same customer through its Trading Grid platform. That's the network side. Mapping, document types and channel determination inside VIM are still your SAP configuration.

A short list for this winter. None of it waits on the final technical rules:

  1. List every UK company code that receives VAT invoices, and how each supplier sends today: EDI, PDF, paper, or already Peppol.
  2. Decide which EDI partners stay on EDI and which move to Peppol. That call belongs to procurement as much as IT.
  3. Sketch how a Peppol invoice and an EDI invoice from the same supplier would land in VIM: document type, channel, duplicate check fields.
  4. Name who owns the Peppol participant identity for each UK legal entity.

Everyone in scope starts on the same day, with no phasing by size. That leaves nearly two and a half years, which is plenty if the channel decisions are made early and without a rush.

McCloy Data

Thought leadership on OpenText, SAP, and practical content and finance automation - from the McCloy Data team.

https://www.mccloydata.com
Previous
Previous

New adaptive scopes will skip inactive mailboxes unless you say otherwise

Next
Next

When someone leaves, Copilot chats stay in an inactive mailbox