Attestwire

Rule reference

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

The scheme identifier on the seller electronic address (BT-34) is "0003", which is not in the CEF Electronic Address Scheme (EAS) list. EAS is a narrower list than the ISO 6523 ICD list used for party identifiers, so a code that is valid as a party scheme can still be invalid here — the access point routes on this pair, and a scheme it does not know is an undeliverable address.

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": "BR-CL-25",
  "field": "BT-34",
  "severity": "fatal",
  "message": "The scheme identifier on the seller electronic address (BT-34) is \"0003\", which is not in the CEF Electronic Address Scheme (EAS) list. EAS is a narrower list than the ISO 6523 ICD list used for party identifiers, so a code that is valid as a party scheme can still be invalid here — the access point routes on this pair, and a scheme it does not know is an undeliverable address.",
  "fix": "Set seller.electronicAddress.schemeId to an EAS code: \"0204\" German Leitweg-ID, \"9930\" German VAT identifier, \"0088\" GLN, \"0192\" Norwegian organisation number, \"0106\" Dutch KvK/OIN, \"EM\" email address.",
  "example": "\"electronicAddress\": { \"schemeId\": \"0204\", \"value\": \"04011000-1234512345-06\" }",
  "xpath": "/ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cbc:EndpointID/@schemeID",
  "docsUrl": "https://attestwire.com/rules/BR-CL-25"
}

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": "0204", "value": "04011000-1234512345-06" }

The fix

Set seller.electronicAddress.schemeId to an EAS code: "0204" German Leitweg-ID, "9930" German VAT identifier, "0088" GLN, "0192" Norwegian organisation number, "0106" Dutch KvK/OIN, "EM" email address.

All 292 rules →

Nearby: 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; BR-CL-24 — The attachment on supporting document 1 declares the mime code "application/zip" (BT-125-1), which EN 16931 does not admit; 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.

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.