PEPPOL-COMMON-R040 — E-Invoice Validation Rule & Fix

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

1. Why This Rule Triggers (Diagnostic Message)

The Seller electronic address (BT-34) is "7300010000002" under scheme "0088", which identifies the GS1 Global Location Number. A value in that scheme must be digits only, with a GS1 mod-10 check digit in the last position, and this one is not. A GLN is self-checking by design: the final digit closes a weighted sum to a multiple of ten, which is what lets a scanner reject a misread barcode rather than route a pallet to the wrong dock. The same digit rejects a mistyped invoice address here, before an access point tries to resolve it. Peppol flags this fatal: the identifier is what an access point resolves to find your counterparty, so a value in the wrong form is undeliverable. 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-COMMON-R040

Correct seller.electronicAddress, or change its scheme identifier if the value belongs to a different register. A failing check digit or length almost always means a digit was transposed, dropped or added in transcription — compare it against the source register rather than re-typing it.

3. Valid Code / Payload Example

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