UK E-Invoicing Mandate 2029: What Peppol Means for You

The UK is the last large European economy to set a date for mandatory e-invoicing. It has now set one, picked a network, and ruled out the most expensive option, real-time clearance with the tax authority. What it has not done yet is publish the rulebook. That arrives with the Budget on 28 October 2026.

This page separates what is confirmed from what is still open, and we update it when the roadmap lands.

The timeline

What is confirmed

What is still open until 28 October

• Phasing. Whether large businesses go first and smaller ones follow, as in Germany, France and Ireland. Most observers expect some phasing.
• The data standard. The working assumption is EN 16931 delivered as Peppol BIS Billing 3.0, with a UK flavour called PINT UK carrying domestic VAT rules such as reverse charge cases. The OpenPeppol UK Working Group is drafting it. It is not yet mandated.
• Legislation. The April 2029 date is policy, not law. The roadmap is expected to set out how and when the legal requirement is made.
• Legacy networks. The government has said it will keep talking to stakeholders about existing systems that cannot interoperate with Peppol. Large retail and construction supply chains run on EDI and supplier portals today, so this matters more than it sounds.
• Northern Ireland. How the Windsor Framework interacts with the mandate for goods moving between Northern Ireland and the EU.

How the four-corner model works

Peppol is a network, not a piece of software. Every business that sends or receives invoices connects through a certified access point. Your access point and your customer's access point talk to each other. Neither of you needs to know which provider the other uses.

In words: you (corner 1) create the invoice, your access point (corner 2) validates it and finds your customer in the Peppol directory, your customer's access point (corner 3) receives it, and your customer's finance system (corner 4) imports it.

The UK chose this over a central clearance platform like Italy's SdI or Poland's KSeF. HMRC does not sit in the middle of each transaction. Our guide to Peppol in the UK covers access points, Peppol IDs and how to check whether a customer is already on the network.

How the UK differs from the EU mandates

UK teams with European entities will recognise most of this, but the UK has picked a lighter design than its neighbours.

The UK model is closest to Belgium's: Peppol as the network, no clearance, no portal. That makes it the cheapest version of a mandate to comply with, and it means a UK business already on Peppol for an EU customer is most of the way there. Our Peppol is not e-invoicing guide explains why the network and the format are separate questions.

What changes for accounts receivable and accounts payable

What a UK Peppol invoice looks like

This is a trimmed Peppol BIS Billing 3.0 invoice from a UK supplier to a UK customer at the 20% standard rate. Party names, addresses and payment details are cut for length.

<Invoice xmlns="urn:oasis:names:specification:ubl:schema:xsd:Invoice-2"
  xmlns:cac="urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2"
  xmlns:cbc="urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2">
  <cbc:CustomizationID>urn:cen.eu:en16931:2017#compliant#urn:fdc:peppol.eu:2017:poacc:billing:3.0</cbc:CustomizationID>
  <cbc:ProfileID>urn:fdc:peppol.eu:2017:poacc:billing:01:1.0</cbc:ProfileID>
  <cbc:ID>INV-10482</cbc:ID>
  <cbc:IssueDate>2029-04-03</cbc:IssueDate>
  <cbc:DueDate>2029-05-03</cbc:DueDate>
  <cbc:InvoiceTypeCode>380</cbc:InvoiceTypeCode>
  <cbc:DocumentCurrencyCode>GBP</cbc:DocumentCurrencyCode>
  <cbc:BuyerReference>PO-55120</cbc:BuyerReference>
  <cac:OrderReference>
    <cbc:ID>PO-55120</cbc:ID>
  </cac:OrderReference>
  <cac:AccountingSupplierParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9932">GB123456789</cbc:EndpointID>
      <!-- name, address, legal entity -->
    </cac:Party>
  </cac:AccountingSupplierParty>
  <cac:AccountingCustomerParty>
    <cac:Party>
      <cbc:EndpointID schemeID="9932">GB987654321</cbc:EndpointID>
      <!-- name, address, legal entity -->
    </cac:Party>
  </cac:AccountingCustomerParty>
  <cac:TaxTotal>
    <cbc:TaxAmount currencyID="GBP">240.00</cbc:TaxAmount>
    <cac:TaxSubtotal>
      <cbc:TaxableAmount currencyID="GBP">1200.00</cbc:TaxableAmount>
      <cbc:TaxAmount currencyID="GBP">240.00</cbc:TaxAmount>
      <cac:TaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>20</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:TaxCategory>
    </cac:TaxSubtotal>
  </cac:TaxTotal>
  <cac:LegalMonetaryTotal>
    <cbc:LineExtensionAmount currencyID="GBP">1200.00</cbc:LineExtensionAmount>
    <cbc:TaxExclusiveAmount currencyID="GBP">1200.00</cbc:TaxExclusiveAmount>
    <cbc:TaxInclusiveAmount currencyID="GBP">1440.00</cbc:TaxInclusiveAmount>
    <cbc:PayableAmount currencyID="GBP">1440.00</cbc:PayableAmount>
  </cac:LegalMonetaryTotal>
  <cac:InvoiceLine>
    <cbc:ID>1</cbc:ID>
    <cbc:InvoicedQuantity unitCode="EA">48</cbc:InvoicedQuantity>
    <cbc:LineExtensionAmount currencyID="GBP">1200.00</cbc:LineExtensionAmount>
    <cac:Item>
      <cbc:Name>Stainless steel hinge, 100mm</cbc:Name>
      <cac:ClassifiedTaxCategory>
        <cbc:ID>S</cbc:ID>
        <cbc:Percent>20</cbc:Percent>
        <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
      </cac:ClassifiedTaxCategory>
    </cac:Item>
    <cac:Price>
      <cbc:PriceAmount currencyID="GBP">25.00</cbc:PriceAmount>
    </cac:Price>
  </cac:InvoiceLine>
</Invoice>

Four lines do most of the work:

• EndpointID schemeID="9932" is each party's Peppol ID, here a UK VAT number. This is how the access points route the invoice.
• BuyerReference and OrderReference carry the customer's purchase order number. Peppol requires a buyer reference or an order reference on every invoice, and it is the field the buyer's system matches on.
• TaxCategory S at 20 is the UK standard rate. Zero-rated, exempt and reverse charge lines use other category codes, which is the area PINT UK is expected to tighten.
• CustomizationID says which rulebook the invoice follows. When PINT UK is published this identifier will change, which is one reason not to hard-code a format before the roadmap.

Why PDFs stop working

Most UK businesses already call what they send an "e-invoice". It is usually a PDF attached to an email. Under the mandate that is no longer the invoice.

An e-invoice in HMRC's sense is a data file, normally XML, built to a published structure. The buyer's system can read the supplier, the VAT breakdown, every line, and the purchase order reference without a person opening anything. You can still send a PDF alongside it so someone can read it, but the XML is the legal document.

This is the bigger change for most finance teams. It is not new data. A UK VAT invoice already has to carry the same fields under VAT Notice 700/21. What changes is that every field must be machine readable and must pass validation before it is delivered.

Who is already doing this

UK e-invoicing over Peppol is not new. NHS England has required suppliers to trade over Peppol for years under its eProcurement strategy, covering orders and invoices, with GS1 GLNs as the identifiers. Suppliers to NHS trusts are the most prepared group in the country.

Businesses with EU subsidiaries are also ahead. Belgium mandated Peppol for B2B in January 2026, and Germany and France are mid-rollout. Our country-by-country timeline has the dates.

What to do before 2029

1. Find out what your finance system already supports. Xero, Sage, Business Central and NetSuite all have Peppol routes at different levels of maturity. Our ERP Peppol support guide has the list.
2. Clean your customer and supplier master data. Peppol routes on identifiers. For UK businesses that will usually be a VAT number (scheme 9932) or a GS1 GLN (scheme 0088). Missing or wrong VAT numbers fail at routing.
3. Fix purchase order references. Automated matching depends on the invoice quoting the buyer's PO number correctly. If your customers' POs arrive as PDFs and get re-keyed, errors here flow straight into rejected invoices.
4. Map every invoice you issue. Self-billing, credit notes, invoices raised from portals and anything issued by a third party all need a structured route.
5. Wait for 28 October before buying. Phasing and the PINT UK spec will change what "compliant" means for your size of business. Prepare data now, sign contracts after the roadmap.

The part the mandate does not cover

The mandate is VAT law, so it covers invoices only. A purchase order creates no VAT event, which means nothing in the 2029 rules touches it. In April 2029 a UK supplier's invoice will be validated XML, while the order it is matched against will very often still be a PDF in a shared inbox.

That gap is where invoice rejections will come from. If the PO number, the quantities or the prices on the invoice don't match the order, automated matching fails no matter how compliant the XML is. We wrote about why ordering was left behind in Peppol solved the invoice, nobody solved the order. OrderSync works on that side: it turns emailed and PDF purchase orders into structured orders in your ERP, so the data your invoices are built from is right in the first place.

Sources

• Promoting electronic invoicing across UK businesses and the public sector: consultation response, HMRC and Department for Business and Trade
• UK Government announces Peppol as core interoperability network, OpenPeppol
• UK confirms adoption of Peppol, Sovos, 24 June 2026
• Electronic invoicing (VAT Notice 700/63), HMRC

Related reading

• Peppol in the UK: access points, Peppol IDs and the NHS
• European e-invoicing mandate timeline
• Does your ERP support Peppol?
• UBL vs X12 vs EDIFACT
• EDI Inspector, free in-browser reader for EDI and invoice files