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

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

Fixture ID: peppolBadDanishSecondary · XPath: /ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID

1. Why This Rule Triggers (Diagnostic Message)

The Buyer identifier (BT-46) is "12345678" under scheme "0198", which identifies the Danish ERSTORG number (SE number). A value in that scheme must be "DK" followed by eight digits, and this one is not. The SE number is the CVR number in its VAT-registration guise, and in this scheme it is always written with the "DK" prefix — unlike scheme 0184, which accepts the bare form as well. Peppol flagged this rule a warning until BIS 3.0.21 made it fatal for every profile, mandatory from 17 August 2026, so a document that passed with a warning before then is now refused. 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-R053

Correct buyer.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": "0198", "value": "DK12345678" }
Test & Validate XML / JSON in Live SchemaGuard Validator →