attestwireAttestwire › Rule reference › PEPPOL-COMMON-R052
PEPPOL-COMMON-R052 A Danish P-number must be exactly ten digits
noun · Peppol BIS · fatal · BT-29
For a sample invoice, the library reports: The Seller identifier (BT-29) is "123" under scheme "0096", which identifies the Danish chamber of commerce number (P-number). A value in that scheme must be exactly ten digits, and this one is not.
- Business term
BT-29- Severity
fatal
The fix
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.
A passing value
"identifier": { "schemeId": "0096", "value": "1234567890" }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-R052",
"field": "BT-29",
"severity": "fatal",
"message": "The Seller identifier (BT-29) is \"123\" under scheme \"0096\", which identifies the Danish chamber of commerce number (P-number). A value in that scheme must be exactly ten digits, and this one is not. A Danish P-number identifies a production unit — a site — rather than the legal entity the CVR number identifies. It is ten digits with no check digit, so the length and the digits are all a format check can verify. 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.",
"fix": "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.",
"example": "\"identifier\": { \"schemeId\": \"0096\", \"value\": \"1234567890\" }",
"xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyIdentification/cbc:ID",
"docsUrl": "https://attestwire.com/rules/PEPPOL-COMMON-R052"
}
xpath is always a UBL path. On a CII invoice, look for the
matching CII field instead.