EN16931 / XRechnung / Peppol BIS 3 Validator

PEPPOL-EN16931-CL008: Electronic address identifier scheme must be from the codelist "Electronic…

fatal UBL auto-fix

What this error means and how to fix it

A Peppol BIS Billing 3.0 rule (OpenPeppol): an extra requirement for invoices sent over the Peppol network, for example electronic addresses (BT-34, BT-49), the business process (BT-23) or code values. This is an error: the invoice is rejected until it is fixed.

Check your invoice against PEPPOL-EN16931-CL008 — free

Runs the KoSIT validator 1.6.3, unmodified · result in seconds · the file is not stored · No file at hand? Try a sample invoice

Automatic fix: 9 € per file (excl. VAT where applicable). When the party's electronic address scheme (BT-34-1/BT-49-1) is not in the EAS code list (e.g. XRechnung's 'EM' e-mail), the Peppol address is derived from the invoice itself: an existing EAS-scheme identifier of the party (GLN only with a valid GS1 check digit), the German buyer's Leitweg-ID (0204), the VAT identifier in countries with a VAT-based EAS code (DE 9930, AT 9914, NL 9944, FR 9957 …), or a Finnish business ID turned into an OVT code (0216). Optional, Peppol profile only; the customer confirms the address. The result page shows which errors the repair removes and whether the corrected file then passes — before you pay. Many files? Pilot and Repair API.

Rule text

[PEPPOL-EN16931-CL008]-Electronic address identifier scheme must be from the codelist "Electronic Address Identifier Scheme"

Automatic repair

When the party's electronic address scheme (BT-34-1/BT-49-1) is not in the EAS code list (e.g. XRechnung's 'EM' e-mail), the Peppol address is derived from the invoice itself: an existing EAS-scheme identifier of the party (GLN only with a valid GS1 check digit), the German buyer's Leitweg-ID (0204), the VAT identifier in countries with a VAT-based EAS code (DE 9930, AT 9914, NL 9944, FR 9957 …), or a Finnish business ID turned into an OVT code (0216). Optional, Peppol profile only; the customer confirms the address.

This rule is in the deterministic set of our repair engine (UBL 2.1; measured 2026-10-23: XRechnung 15 broken test invoices accepted after repair, 45 valid invoices unchanged; Peppol BIS Billing 3: 10 official examples unchanged, 40 mutated invoices: 36 accepted after repair, 4 rejected as expected — one documented limit, two with the repair parameter switched off, one where no address could be derived; profile conversion of 33 XRechnung test invoices to Peppol: 30 accepted). For UN/CEFACT CII (Factur-X / ZUGFeRD EN 16931 XML, XRechnung CII) the engine repairs the totals chain, VAT breakdown, rounding, decimals and element order (measured 2026-10-24: 53 valid CEN and XRechnung CII invoices unchanged; 28 broken invoices: 27 accepted after repair, 1 rejected as expected because a VAT exemption reason cannot be derived). Single files: 9 € on the result page; many files: the Repair API — see Pricing.

Where the rule is checked (XPath context and test)
SyntaxSeverityContext (XPath)Test (XPath)
Peppol-UBLfatalcbc:EndpointID[@schemeID]some $code in $eaid satisfies @schemeID = $code

Source: Peppol BIS Billing 3.0 Schematron, UBL (OpenPeppol, docs.peppol.eu validation artefacts 3.0.21).

Check your invoice against this rule