Attestwire

Rule reference

BR-CL-26 The scheme identifier on the deliver-to location identifier (BT-71-1) is "9930", which is not in the ISO 6523 ICD list

The scheme identifier on the deliver-to location identifier (BT-71-1) is "9930", which is not in the ISO 6523 ICD list. BT-71 is how an invoice names a delivery point precisely enough to be matched automatically — a warehouse door, a ward, a store — where the postal address alone is ambiguous because several locations share it. That matching is only possible if the receiver knows which registry the identifier belongs to, which is what the scheme says.

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-71
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": "BR-CL-26",
  "field": "BT-71",
  "severity": "fatal",
  "message": "The scheme identifier on the deliver-to location identifier (BT-71-1) is \"9930\", which is not in the ISO 6523 ICD list. BT-71 is how an invoice names a delivery point precisely enough to be matched automatically — a warehouse door, a ward, a store — where the postal address alone is ambiguous because several locations share it. That matching is only possible if the receiver knows which registry the identifier belongs to, which is what the scheme says.",
  "fix": "Set deliverToLocationId.schemeId to an ISO 6523 ICD code — \"0088\" for a GLN, which is what almost every delivery-point identifier in practice is. Drop the schemeId and keep the bare value if the identifier is one you and the buyer agreed privately.",
  "example": "\"deliverToLocationId\": { \"schemeId\": \"0088\", \"value\": \"4304171000002\" }",
  "xpath": "/ubl:Invoice/cac:Delivery/cac:DeliveryLocation/cbc:ID/@schemeID",
  "docsUrl": "https://attestwire.com/rules/BR-CL-26"
}

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
"deliverToLocationId": { "schemeId": "0088", "value": "4304171000002" }

The fix

Set deliverToLocationId.schemeId to an ISO 6523 ICD code — "0088" for a GLN, which is what almost every delivery-point identifier in practice is. Drop the schemeId and keep the bare value if the identifier is one you and the buyer agreed privately.

All 292 rules →

Nearby: BR-DEC-01 — The allowed maximum number of decimals for the document level allowance amount (BT-92) is 2, but allowances[0].amount is 10.005, which has 3; BR-CL-25 — The scheme identifier on the seller electronic address (BT-34) is "0003", which is not in the CEF Electronic Address Scheme (EAS) list; BR-DEC-02 — The allowed maximum number of decimals for the document level allowance base amount (BT-93) is 2, but allowances[0].baseAmount is 100.005, which has 3.

Check this rule against your invoice via the hosted API → https://api.attestwire.com/docs

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