Rule reference

PEPPOL-COMMON-R041 The Seller electronic address (BT-34) is "991825828" under scheme "0192", which identifies the Norwegian organisation number (Enhetsregisteret)

The Seller electronic address (BT-34) is "991825828" under scheme "0192", which identifies the Norwegian organisation number (Enhetsregisteret). A value in that scheme must be exactly nine digits, the last of which is a modulus-11 check digit, and this one is not. Norway's organisasjonsnummer carries its own check digit, and Norway is one of the jurisdictions where Peppol is the mandatory channel for public-sector invoicing — so a transposed digit here is not a warning about data quality, it is an invoice that cannot be delivered. Peppol flags this fatal: the identifier is what an access point resolves to find your counterparty, so a value that fails its own check digit 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.

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-34
Severity
fatal

What the library returns

The exact object in result.errors when this rule fires. Generated by running @attestwire/en16931, not transcribed:

TeachingError
{
  "rule": "PEPPOL-COMMON-R041",
  "field": "BT-34",
  "severity": "fatal",
  "message": "The Seller electronic address (BT-34) is \"991825828\" under scheme \"0192\", which identifies the Norwegian organisation number (Enhetsregisteret). A value in that scheme must be exactly nine digits, the last of which is a modulus-11 check digit, and this one is not. Norway's organisasjonsnummer carries its own check digit, and Norway is one of the jurisdictions where Peppol is the mandatory channel for public-sector invoicing — so a transposed digit here is not a warning about data quality, it is an invoice that cannot be delivered. Peppol flags this fatal: the identifier is what an access point resolves to find your counterparty, so a value that fails its own check digit 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.electronicAddress, 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": "\"electronicAddress\": { \"schemeId\": \"0192\", \"value\": \"991825827\" }",
  "xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID",
  "docsUrl": "https://attestwire.com/rules/PEPPOL-COMMON-R041"
}

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

the shape this field expects
"electronicAddress": { "schemeId": "0192", "value": "991825827" }

The fix

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

Arrived from a stack trace? The docsUrl on every error links straight here. Something wrong on this page — tell us.