attestwireAttestwire › Rule reference › PEPPOL-COMMON-R053
PEPPOL-COMMON-R053 A Danish SE number should be DK followed by eight digits
noun · Peppol BIS · warning · BT-46
For a sample invoice, the library reports: 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.
- Business term
BT-46- Severity
warning
The fix
Correct buyer.identifier, or change its scheme identifier if the value belongs to a different register. A check digit failing almost always means one digit was transposed or dropped in transcription — compare it against the source register rather than re-typing it.
A passing value
"identifier": { "schemeId": "0198", "value": "DK12345678" }What the library returns
The full error returned by @attestwire/en16931. It includes the rule ID,
affected field and suggested correction. Developers can use this object in their application:
{
"rule": "PEPPOL-COMMON-R053",
"field": "BT-46",
"severity": "warning",
"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 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. 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.",
"fix": "Correct buyer.identifier, or change its scheme identifier if the value belongs to a different register. A check digit failing almost always means one digit was transposed or dropped in transcription — compare it against the source register rather than re-typing it.",
"example": "\"identifier\": { \"schemeId\": \"0198\", \"value\": \"DK12345678\" }",
"xpath": "/ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID",
"docsUrl": "https://attestwire.com/rules/PEPPOL-COMMON-R053"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.