PEPPOL-EN16931-CL008 — E-Invoice Validation Rule & Fix

Fixture ID: peppolUnroutableScheme · XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID

1. Why This Rule Triggers (Diagnostic Message)

The Seller electronic address (BT-34) uses the scheme identifier "EM", which is not in the Peppol Participant Identifier Scheme list. This is the rule people are most surprised by, because "EM" may well be a perfectly valid CEF Electronic Address Scheme code and satisfy BR-CL-25: the CEN list is the *register* of address schemes, and this one is the subset an access point will actually resolve. A code in the first and not the second gives you a document that passes every validator you can run locally and is refused at the network edge. This is a Peppol BIS Billing 3.0 profile rule: it applies because profile is "peppol-bis-3". It does not apply to the en16931, xrechnung-ubl or xrechnung-cii profiles, whose validators will accept the same document.

2. How to Fix PEPPOL-EN16931-CL008

Set seller.electronicAddress.schemeId to a code from the PEPPOL_EAS_SCHEME_CODES list this package exports — 0002, 0007, 0009, 0060, 0088, 0096 and 77 others. In practice the choice is made for you: it is whichever scheme your counterparty is registered under in the Peppol directory, so look them up rather than guessing.

3. Valid Code / Payload Example

"electronicAddress": { "schemeId": "0088", "value": "7300010000001" }