UK e-invoicing will run on the Peppol network. It uses a standard called EN 16931. Every e-invoice must carry a set list of data fields. Leave one out, and the invoice gets rejected. This guide explains which fields you need and why.
Key Takeaways
- UK e-invoices are built on the EN 16931 standard. Delivery will happen over the Peppol network.
- The specific UK Peppol profile is still under development by the OpenPeppol UK Working Group.
- EN 16931 sets the core fields. Peppol adds a few more of its own.
- The buyer reference or purchase order reference is a must under Peppol. A missing one is the top reason invoices get rejected.
- Special cases like reverse charge need extra fields.
- A missing field means rejection at the Access Point, before the buyer sees it.
The UK e-invoicing mandate is the coming rule requiring structured electronic invoices for business sales. The government gave its confirmation on 23 June 2026. From 1 April 2029, it applies to every B2B and B2G VAT invoice. Behind its the Peppol network, with EN 16931 as the underlying standard. The specific UK Peppol profile is being developed by the OpenPeppol UK Working Group. PINT UK is the widely expected format, but it has not yet been formally mandated.
An e-invoice is structured data. Each required field has a code under EN 16931. The fields come in two layers. There are also some extras for special cases.
These are the core fields. Every invoice must carry them.
| Field | Business term | What it holds |
| Invoice number | BT-1 | A unique number for the invoice |
| Issue date | BT-2 | The date the invoice was issued |
| Invoice type code | BT-3 | The document type, such as 380 for an invoice |
| Currency code | BT-5 | The invoice currency, for example GBP |
| Seller name | BT-27 | The supplier's registered legal name |
| Seller address | BG-5 | The supplier's postal address, with country code |
| Seller VAT number | BT-31 | The supplier's VAT number, where registered |
| Buyer name | BT-44 | The customer's legal name |
| Buyer address | BG-8 | The customer's postal address, with country code |
| Line details | BG-25 | Per line: item, quantity, unit, net price and amount |
| VAT category code | BT-118 | Shows the tax treatment, e.g. S for standard rate |
| VAT rate | BT-119 | The VAT percentage for the category |
| VAT breakdown | BG-23 | Taxable value and tax charged, split by rate |
| Total without VAT | BT-109 | Sum of line amounts before VAT |
| VAT total | BT-110 | The total VAT amount |
| Amount payable | BT-115 | The final total to pay |
Extra Peppol Fields
The Peppol network adds requirements on top of the EN 16931 core. Existing Peppol profiles, including Peppol BIS Billing 3.0, make several optional EN 16931 fields mandatory. The UK-specific profile has not yet been formally confirmed, but these fields are common to all current Peppol profiles and are expected to apply under the UK mandate.
Some sales need more than the standard fields. Here, the VAT code is what matters most.
The fields are checked at the Access Point, before delivery. Your provider runs the invoice against the EN 16931 and Peppol rules. If a field is missing or wrong, the invoice stops there. It never reaches your buyer. That means late payment and rework for you.
The fields also protect your VAT. The VAT codes and breakdown decide how the sale is reported. They also decide how your buyer claims back input VAT. Clean data keeps invoices moving and payments on time.
The mandatory fields are the heart of UK e-invoicing. Start with the EN 16931 core. Add the extra Peppol fields. Code the special cases correctly. The buyer reference and the VAT codes are the two to watch most. The mandate lands in 2029. Getting your data right now will save trouble later.