SchemaGuard by Ironbark Digital · EN 16931 / Peppol / XRechnung Reference
← All 294 EN 16931 / Peppol Rules & Live Validator
WARNING Official EN 16931 / Peppol / CIUS Rule BT/BG Fields: BT-29

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

Fixture ID: peppolBadDutchIdentifiers · XPath: /ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID

1. Why This Rule Triggers (Diagnostic Message)

The Seller identifier (BT-29) is "12345678" under scheme "0217", which identifies the Dutch establishment number (vestigingsnummer). A value in that scheme must be exactly twelve digits, and this one is not. The establishment number identifies one branch of a company in the Dutch trade register, and it is twelve digits where the company's KVK number is eight. An eight-digit value here is almost always the KVK number, which belongs under scheme 0106. As an electronic address, 0217 is also refused by PEPPOL-EN16931-CL008: it left Peppol's participant scheme list in the same release. 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-R057

Correct seller.identifier, 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

"identifier": { "schemeId": "0217", "value": "000012345678" }
Test & Validate XML / JSON in Live SchemaGuard Validator →