PEPPOL-COMMON-R047 The Buyer identifier (BT-46) is "IT01234567890" under scheme "0211", which identifies the Italian VAT number (Partita IVA)
The Buyer identifier (BT-46) is "IT01234567890" under scheme "0211", which identifies the Italian VAT number (Partita IVA). A value in that scheme must be "IT" followed by eleven digits whose last digit is a Luhn-style check digit, and this one is not. The Partita IVA check digit is computed by doubling every second digit and summing the results digit by digit, which catches the transposition that a plain length check does not. Note that a value not beginning with IT passes this rule untested — Peppol only checks what it can recognise. 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.
This rule is implemented and its error payload below is real, but the long-form write-up — normative text, worked example, divergence note — is not written yet. Everything the library knows about this rule is on this page. Ask and we will prioritise it.
- Business term
BT-46- Severity
warning
What the library returns
The exact object in result.errors when this rule fires.
Generated by running @attestwire/en16931, not transcribed:
{
"rule": "PEPPOL-COMMON-R047",
"field": "BT-46",
"severity": "warning",
"message": "The Buyer identifier (BT-46) is \"IT01234567890\" under scheme \"0211\", which identifies the Italian VAT number (Partita IVA). A value in that scheme must be \"IT\" followed by eleven digits whose last digit is a Luhn-style check digit, and this one is not. The Partita IVA check digit is computed by doubling every second digit and summing the results digit by digit, which catches the transposition that a plain length check does not. Note that a value not beginning with IT passes this rule untested — Peppol only checks what it can recognise. 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\": \"0211\", \"value\": \"IT01234567897\" }",
"xpath": "/ubl:Invoice/cac:AccountingCustomerParty/cac:Party/cac:PartyIdentification/cbc:ID",
"docsUrl": "https://attestwire.com/rules/PEPPOL-COMMON-R047"
}
xpath locates the element in the generated UBL document,
which is where a KoSIT or Peppol validator will report the same problem.
A passing value
"identifier": { "schemeId": "0211", "value": "IT01234567897" }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.