The Decisive Difference
Machine readability and automated digital processing are the key criteria. A standard PDF invoice sent via email is an electronically transmitted document, but it does not constitute an electronic invoice (e-invoice) within the formal definition of electronic invoicing standards and VAT data processing. Under strict data interchange classifications, it is treated merely as an unstructured electronic image or document.
A genuine e-invoice contains billing data in a structured, semantically defined data format in full compliance with standard specifications (such as European Standard EN 16931 or Peppol BIS Billing 3.0). Whether a human-readable visual presentation is included alongside the data payload depends on the specific format selected; it does not determine its underlying data validity.
Formats
Two primary implementations are widely recognised across European and international cross-border trade: pure XML data schemas (such as XRechnung or Peppol UBL), and hybrid formats such as ZUGFeRD / Factur-X, which combine a human-readable PDF/A-3 visual layer with embedded structured XML data. Both approaches conform to the semantic data model of the EN 16931 standard.
Receipt and Issuance
Transition frameworks are rolled out across business and public sectors. In public sector procurement across the UK and Europe, public bodies are legally mandated to accept structured e-invoices conforming to standard schemas. In B2B commerce, organisations increasingly mandate structured electronic invoicing to streamline accounting workflows and align with digital tax reporting (such as HMRC’s Making Tax Digital initiatives). For basic receipt, an organisation must maintain capable digital ingestion channels (such as an automated inbox or a Peppol access point), whilst issuance requires accounting software capable of exporting compliant XML or hybrid files.
Archiving and Record-Keeping
Under HMRC compliance rules and VAT record-keeping requirements (including Section 58 and Schedule 11 of the Value Added Tax Act 1994), the original structured electronic dataset must be securely archived for at least 6 years. Preserving only a converted visual rendering, screen capture, or paper printout does not satisfy HMRC compliance if the invoice was originally created, transmitted, or received as structured electronic data. The integrity and authenticity of the underlying XML data file must remain fully accessible and verifiable throughout the statutory retention period.
- Updated on