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

Fixture ID: peppolBadDutchIdentifiers · XPath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cbc:EndpointID

1. Why This Rule Triggers (Diagnostic Message)

The Buyer electronic address (BT-49) is "1234567890" under scheme "0190", which identifies the Dutch government organisation identification number (OIN). A value in that scheme must be exactly twenty digits, and this one is not. The OIN (Organisatie-identificatienummer) is the twenty-digit number the Dutch government issues to public organisations, and it is how many Dutch public bodies are addressed on Peppol. Leading zeros are part of it: stored as a number rather than as text, an OIN loses them and fails this check. Peppol flags this one as a warning rather than a rejection, so the document will be delivered — but a wrong identifier is delivered to the wrong place, or to nowhere. Peppol added this rule in BIS 3.0.21 as a warning, to give senders time to correct their data, and has said the Dutch identifier rules become fatal in a later release. 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-R055

Correct buyer.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": "0190", "value": "00000001234567890000" }