European e-invoicing mandates: why EN 16931, XRechnung and Veri*factu fail on ERP master data.

From forgiving PDFs to strict XML

A PDF invoice is forgiving. If your ERP prints unit of measure "Kart." instead of "XCT", leaves the buyer’s VAT number on the second address line, or has a one-cent rounding difference between the sum of line items and the invoice subtotal, a human accounts-payable clerk still processes it.

A structured electronic invoice—governed by European standard EN 16931 and national profiles such as Peppol BIS Billing 3.0, Germany’s XRechnung / ZUGFeRD 2.x, or Spain’s Veri*factu billing-record schema—is validated by machine before it ever reaches a person. If a single required semantic field (`BT-*`) is missing or a single mathematical rule (`BR-CO-*`) fails by €0.01, the access point or tax authority gateway rejects the document outright—blocking revenue collection until the underlying ERP record is corrected.

The European regulatory calendar

For multi-entity businesses operating across Europe, domestic mandates and the EU-wide VAT in the Digital Age (ViDA) directive converge over the next four years:

Statutory timelines as enacted through March 2025 (EU ViDA) and December 2025 (Spain RDL 15/2025 extension). Primary legal citations listed below.

Worked example: the BR-CO-10 rounding trap

One of the most common reasons an ERP’s XML export fails Peppol or XRechnung validation is Rule BR-CO-10 of EN 16931: the document-level sum of invoice line net amounts (BT-106) must equal the exact sum of the individual rounded line net amounts (Σ BT-131), where each BT-131 is rounded to two decimal places in the XML.

Consider a three-line wholesale invoice where each line bills 333 units of a fastener at a net price of €0.0310 per unit (333 × €0.0310 = €10.323 unrounded):

Under EN 16931 Schematron rules BR-CO-10 and BR-CO-15, header totals must be computed from the rounded 2-decimal line values (or bridged via BT-114 RoundingAmount).

Four ERP master-data fields that break

Beyond rounding logic, four master-data gaps cause the majority of schema rejections during e-invoicing rollouts:

1. Custom units of measure instead of UN/ECE Recommendation 20 codes. EN 16931 requires every invoiced quantity (BT-129) to carry a standard unit code (BT-130) from UN/ECE Rec 20 / Rec 21 (such as C62 for piece, KGM for kilogram, HUR for hour). Free-text ERP units like "Stück", "pcs", "caja" or "day" fail schema validation unless mapped in the item master.
2. Missing or malformed Buyer VAT / Endpoint IDs. Peppol routing requires a valid participant identifier (BT-49) and properly formatted VAT registration number (BT-48, prefixed with the two-letter ISO country code) on the billing entity, not buried in a free-text comment field.
3. Unmapped VAT exemption reason codes. When an invoice line carries 0% VAT (intra-Community supply, reverse charge or export), EN 16931 rules BR-AE-*, BR-IC-* and BR-G-* require both the exact tax category code (BT-151: AE, K, G) and an explicit exemption reason or legal reference (BT-120 / BT-121).
4. Missing Buyer Reference (BT-10). Both XRechnung (where BT-10 carries the Leitweg-ID or buyer reference) and Peppol BIS Billing 3.0 require either a buyer reference (BT-10) or a purchase order reference (BT-13) on every invoice header.

SQL pre-flight audit on ERP tables

Before connecting an e-invoicing gateway, run a pre-flight SQL audit against your ERP billing tables over the last 90 days of invoices to quantify exactly which records would fail EN 16931 validation today:

WITH invoice_rollup AS (
  SELECT
    h.invoice_id,
    c.vat_id                                                 AS bt_48_buyer_vat,
    h.buyer_reference                                        AS bt_10_buyer_ref,
    ROUND(SUM(l.qty * l.net_unit_price), 2)                  AS unrounded_header_sum,
    SUM(ROUND(l.qty * l.net_unit_price, 2))                  AS sum_of_rounded_bt131,
    COUNT(*) FILTER (WHERE u.unece_rec20_code IS NULL)       AS unmapped_uom_lines
  FROM erp_invoice_headers h
  JOIN erp_invoice_lines l USING (invoice_id)
  LEFT JOIN erp_customers c ON h.customer_id = c.erp_customer_id
  LEFT JOIN ref_uom_unece_map u ON l.erp_uom_code = u.erp_uom_code
  GROUP BY 1, 2, 3
)
SELECT
  COUNT(*)                                                                  AS total_invoices_checked,
  COUNT(*) FILTER (WHERE bt_48_buyer_vat IS NULL OR bt_48_buyer_vat = '')   AS missing_bt48_vat,
  COUNT(*) FILTER (WHERE bt_10_buyer_ref IS NULL OR bt_10_buyer_ref = '')   AS missing_bt10_ref,
  COUNT(*) FILTER (WHERE unmapped_uom_lines > 0)                            AS fails_unece_uom,
  COUNT(*) FILTER (WHERE unrounded_header_sum <> sum_of_rounded_bt131)      AS fails_brco10_rounding
FROM invoice_rollup;

Sources & regulatory references

• OpenPeppol / CEN EN 16931: Peppol BIS Billing 3.0 Specification & EN 16931 Schematron Rules — definitions of semantic terms (BT-*), calculation rules (BR-CO-10, BR-CO-15), and UN/ECE Recommendation 20 unit code lists.
• Council of the European Union: VAT in the Digital Age (ViDA) Package — adopted 11 March 2025; establishes mandatory intra-EU B2B structured e-invoicing and Digital Reporting Requirements (DRR) from 1 July 2030.
• Federal Ministry of Finance (Germany): Wachstumschancengesetz (BGBl. 2024 I Nr. 108) — mandatory B2B e-invoice receipt from 1 January 2025 and phased issuance from 1 January 2027 / 2028.
• Agencia Tributaria (Spain): Sistemas Informáticos de Facturación (Veri*factu) — Real Decreto 1007/2023, Real Decreto 254/2025, Orden HAC/1177/2024 and Real Decreto-ley 15/2025 (effective 1 January 2027 for corporations and 1 July 2027 for self-employed professionals).