B2B E-Invoicing – Standards, Formats, and Implementation

The transition to electronic invoicing is not merely a matter of document formatting, but of digital business process design. Treating it purely as a back-office accounting task overlooks the fact that compliance begins at invoice creation — and therefore with the underlying time tracking and operational data from which invoices are generated.

The Definition

The decisive factor is automated machine readability. A standard PDF invoice sent via email is transmitted electronically, but it is not a structured electronic invoice for automated data interchange.

The Formats

Peppol BIS Billing / UBL — pure XML datasets based on the EN 16931 semantic data model. Ideal for end-to-end automated processing, and the format UK contracting authorities are equipped to receive, but unusable for manual human inspection without specialised rendering software. (XRechnung is the equivalent national profile used in Germany; it is not used in UK procurement.)

Note what the UK rules actually require: the Public Procurement (Electronic Invoices etc.) Regulations 2019 oblige contracting authorities to receive and process invoices conforming to EN 16931. They impose no obligation on suppliers to issue structured e-invoices, and there is no UK B2B e-invoicing mandate.

ZUGFeRD from Version 2 onwards (known internationally as Factur-X) — a hybrid format: PDF/A-3 with embedded XML data. Humans read the visual PDF layout, while accounting software automatically extracts and processes the structured XML. In the event of any discrepancies, the structured XML dataset is legally authoritative.

Both approaches comply with standard electronic data interchange principles, provided a fully compliant profile is utilized. Lightweight profiles that omit mandatory tax elements do not suffice for automated VAT processing.

Receiving and Issuing

Modern digital procurement operates across distinct integration stages:

The capability to receive structured electronic invoices allows organizations to automate accounts payable workflows, eliminate manual data entry, and reduce processing errors. While an email inbox can serve as a simple transport layer for XML or hybrid attachments, scalable automated systems connect directly to electronic data interchange (EDI) gateways or Peppol Access Points.

For issuing e-invoices, organizations must ensure their billing software generates compliant structured data schemas matching buyer specifications, whether supplying private sector corporate clients or public sector contracting authorities.

Exemptions and Simplified Invoicing

Simplified arrangements typically apply to:

• Low-value simplified tax invoices (such as petty cash transactions under statutory thresholds);
• Passenger transport tickets;
• Direct consumer transactions (B2C supplies);
• Specific VAT-exempt supplies.

Even where simplified tax invoices are permitted, commercial counterparties operating automated enterprise resource planning (ERP) systems increasingly mandate structured electronic invoices as a contractual condition.

Transmission Channels

In commercial B2B transactions, the transmission protocol is agreed between trading counterparties, provided data integrity and authenticity of origin are maintained throughout.

Archiving and Statutory Record-Keeping

Standard electronic record-keeping principles under UK tax law (HMRC digital record rules, Making Tax Digital regulations, and the Companies Act 2006) require:

• Immutability and data integrity: Records must remain unaltered throughout the statutory retention period;
• Retention period: VAT and commercial transaction records must be retained for at least 6 years from the end of the relevant accounting period;
• Digital links: Unbroken digital links must be maintained between source transactions, time tracking ledgers, and final VAT return submissions;
• Accessibility: Data must be easily retrievable, human-readable upon request, and exportable for HMRC inspection.

Implementation: Step-by-Step Sequence

1. Establish receipt infrastructure. Configure secure ingestion channels, define automated verification workflows, and secure an immutable digital repository for original XML datasets.
2. Audit master data. Ensure accurate buyer reference numbers, VAT registration numbers (VRNs), company registration numbers (CRNs), and standardized address data.
3. Structure outbound billing data at source. Invoice line items must originate from structured operational data rather than being retrofitted from an unlinked document.
4. Select appropriate output profiles. Adopt hybrid formats (ZUGFeRD / Factur-X) where buyers require visual inspection, or pure XML / Peppol BIS Billing 3.0 for automated enterprise pipelines.
5. Conduct integration testing. Execute end-to-end sandbox tests with key clients and suppliers to validate schema parsing and automated ledger posting.
6. Formalize internal procedures. Document electronic billing, data validation, and archiving protocols within internal financial controls and compliance manuals.

The Connection to Project Time Tracking

When billing clients on a time-and-materials or day-rate basis, the e-invoice is only as reliable as the underlying time and attendance data. To produce a compliant, structured e-invoice, billing-relevant attributes must be captured accurately at the point of recording: detailed service descriptions, task breakdowns, billable rates, VAT liability ratings, and specific delivery periods.

Attempting to log hours in unstructured spreadsheets, generate a manual PDF, and subsequently reconstruct an XML payload creates significant operational risk and violates Making Tax Digital digital linking principles. The compliant, automated workflow follows a direct sequence:

Time Entry → Management Approval → Structured Billing Record → Compliant E-Invoice.

Sources and Legal Bases

Statutory Provisions and UK Regulatory Standards

• Value Added Tax Act 1994 (VATA 1994), Schedule 11 — Statutory powers regarding accounting for VAT, invoicing requirements, and electronic record-keeping.
• The Value Added Tax Regulations 1995 (SI 1995/2518), Part III — Detailed statutory rules on VAT invoices, electronic transmission, and mandatory particulars.
• Public Procurement (Electronic Invoices etc.) Regulations 2019 (SI 2019/624) — Transposing EU Directive 2014/55/EU into UK law, mandating that UK contracting authorities accept electronic invoices complying with the standard EN 16931.
• Companies Act 2006, Sections 386–388 — Statutory duty of companies to keep adequate accounting records; Section 388(4) sets retention at 3 years for a private company and 6 years for a public company, with HMRC requiring 6 years for VAT and corporation tax purposes.

HMRC Guidance and Technical Specifications

• HMRC Notice 700/63: Electronic Invoicing — Official rules regarding the transmission, integrity, authenticity, and storage of electronic VAT invoices.
• HMRC Internal Manual: VAT Record Keeping (VREC) — Statutory requirements for business records, electronic storage media, and preservation of digital audit trails under Making Tax Digital (MTD).
• Crown Commercial Service: Peppol in UK Public Procurement — Technical framework and standards for structured electronic document interchange across public sector and commercial supply chains.

Status of review: August 2026. This article provides general regulatory information and does not constitute formal legal or tax advice.