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

> From April 2029 every UK B2B VAT invoice must be a structured e-invoice sent over Peppol. PDFs stop counting. What is confirmed, what is open, what to do now.

<QuickAnswer>
From April 2029 every UK VAT invoice between businesses, and from businesses to
the public sector, must be a structured e-invoice. The government confirmed in
June 2026 that invoices will travel over the Peppol network through certified
access points. PDFs will no longer count, and there is no real-time HMRC
reporting in 2029.
</QuickAnswer>

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

| Item | Status | Source |
| --- | --- | --- |
| Scope: all B2B and B2G VAT invoices | Confirmed, Budget 2025 | [GOV.UK consultation response](https://www.gov.uk/government/consultations/promoting-electronic-invoicing-across-uk-businesses-and-the-public-sector/outcome/promoting-electronic-invoicing-across-uk-businesses-and-the-public-sector-consultation-response) |
| Start date: April 2029 | Announced, Budget 2025 | GOV.UK consultation response |
| Network: Peppol | Confirmed, 23 June 2026 | [OpenPeppol announcement](https://peppol.org/uk-einvoicing-mandate-expected-in-2029-2/) |
| Model: decentralised four-corner, no government portal | Confirmed, 23 June 2026 | OpenPeppol, [Sovos](https://sovos.com/regulatory-updates/vat/uk-confirms-adoption-of-peppol-as-the-framework-for-its-upcoming-e-invoicing-mandate/) |
| Real-time reporting to HMRC | Not in 2029 | GOV.UK consultation response |
| PDFs, Word, images and HTML | Not e-invoices | GOV.UK consultation response |
| B2C invoices | Out of scope | GOV.UK consultation response |

## 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](/guides/e-invoicing/peppol-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.

| | United Kingdom | France | Germany | Poland | Belgium |
| --- | --- | --- | --- | --- | --- |
| Start | April 2029 | 1 September 2026 | 1 January 2027 (issuing, large) | 1 February 2026 | 1 January 2026 |
| Network | Peppol, four-corner | Certified platforms (PDP) | None mandated | KSeF government portal | Peppol |
| Tax authority in the flow | No | Yes, via platforms | No | Yes, clearance | No |
| Real-time reporting | Not in 2029 | Yes, e-reporting | No | Yes, by design | From 2028 |
| Format | EN 16931, PINT UK expected | Factur-X, UBL or CII | XRechnung or ZUGFeRD | FA(3) XML | Peppol BIS Billing 3.0 |

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](/guides/e-invoicing/peppol-vs-e-invoicing-mandates)
guide explains why the network and the format are separate questions.

## What changes for accounts receivable and accounts payable

| | Accounts receivable (you send invoices) | Accounts payable (you receive invoices) |
| --- | --- | --- |
| The obligation | Issue every B2B and B2G VAT invoice as a structured e-invoice | Be able to receive structured e-invoices from suppliers |
| What breaks first | Missing customer VAT numbers or Peppol IDs, and invoices that fail validation | Invoices that arrive structured but still go to a person to key in |
| Data to fix | Customer master data, buyer PO references, VAT codes per line | Supplier master data, PO and goods receipt matching rules |
| The win | Fewer disputes and faster payment, because the buyer's system can auto-match | Fewer manual touches per invoice and better fraud controls |

## 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.

```xml
<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](https://www.gov.uk/guidance/record-keeping-for-vat-notice-70021).
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](/e-invoicing) 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](/guides/e-invoicing/does-your-erp-support-peppol)
   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](/blog/peppol-solved-the-invoice-not-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](https://www.gov.uk/government/consultations/promoting-electronic-invoicing-across-uk-businesses-and-the-public-sector/outcome/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](https://peppol.org/uk-einvoicing-mandate-expected-in-2029-2/), OpenPeppol
- [UK confirms adoption of Peppol](https://sovos.com/regulatory-updates/vat/uk-confirms-adoption-of-peppol-as-the-framework-for-its-upcoming-e-invoicing-mandate/), Sovos, 24 June 2026
- [Electronic invoicing (VAT Notice 700/63)](https://www.gov.uk/guidance/electronic-invoicing-notice-70063), HMRC

## Related reading

- [Peppol in the UK: access points, Peppol IDs and the NHS](/guides/e-invoicing/peppol-uk)
- [European e-invoicing mandate timeline](/e-invoicing)
- [Does your ERP support Peppol?](/guides/e-invoicing/does-your-erp-support-peppol)
- [UBL vs X12 vs EDIFACT](/guides/e-invoicing/ubl-vs-x12-vs-edifact)
- [EDI Inspector](/edi-inspector), free in-browser reader for EDI and invoice files

## Common questions

### Is e-invoicing mandatory in the UK?

Not yet, but it will be. The government announced at Budget 2025 that every VAT invoice for business-to-business and business-to-government sales must be a structured electronic invoice from April 2029. The legislation has not been passed. The implementation roadmap is due at the Budget on 28 October 2026. Until 2029, e-invoicing is only required where a buyer such as NHS England demands it in its contracts.

### When does UK e-invoicing become mandatory?

April 2029. That is the date announced at Budget 2025 for all B2B and B2G VAT invoices. The government may phase the start by business size, and confirmation of any phasing is expected in the roadmap published with the Budget on 28 October 2026.

### Will PDF invoices still be valid in the UK after 2029?

Not for B2B or B2G VAT invoices. HMRC's definition of an e-invoice excludes PDFs, Word documents, scanned images and HTML. A PDF can still be sent as a human-readable copy, but the legal invoice will be the structured data file exchanged between the two businesses' systems.

### Does the UK use Peppol for e-invoicing?

Yes. On 23 June 2026, in the Tax Update 2026 policy paper, the government confirmed Peppol as the core interoperability network for UK e-invoicing. It is a decentralised four-corner model: each business connects through its own certified Peppol access point, and there is no central government portal.

### Do I have to report invoices to HMRC in real time?

No. The government has said real-time reporting will not be introduced alongside the 2029 mandate. It may come later, and if it does it will be built on the same e-invoicing infrastructure. In 2029 the obligation is to exchange structured invoices with your trading partners, not to clear them with HMRC.

### Does the UK e-invoicing mandate apply to small businesses?

It applies to VAT invoices, so any VAT-registered business issuing invoices to other businesses or the public sector is in scope. Businesses that are not VAT registered and sales to consumers are outside it. Whether small businesses get a later start date is one of the questions the 28 October 2026 roadmap is expected to answer.

### What format will UK e-invoices use?

The expected basis is the European standard EN 16931 delivered as Peppol BIS Billing 3.0, with a UK-specific Peppol International (PINT) specification being developed by the OpenPeppol UK Working Group to carry UK VAT rules. PINT UK has not been formally mandated yet.