Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-49 | Fatal (error) | cac:AccountingSupplierParty/cac:Party/cbc:EndpointID |
Schematron ID: ibr-062 | Field: @schemeID on the Seller electronic address (IBT-034) |
||
Classification
Master Data — the seller's electronic address and its scheme live in the supplier's own configuration, set once and emitted on every invoice. A failure here breaks every document the system produces, which also makes it one of the cheapest rules to fix permanently.
What the Rule Is Checking
The exact schematron assert reads: "The Seller electronic address (ibt-034) MUST have a Scheme identifier." Whenever cbc:EndpointID appears under cac:AccountingSupplierParty, it must carry a schemeID attribute. The value inside the element can be perfectly correct; without the attribute naming which registry that value belongs to, validation fails with a fatal error. For UAE participants the scheme is 0235, the code assigned to the UAE Tax Identification Number.
Why This Rule Exists
An electronic address is only meaningful as a pair: a scheme and a value. The digits 1XXXXXXX1 could be a TIN, a GLN or a national company register number — the scheme identifier is what tells the Peppol network which one it is. Routing in the 5-Corner model depends on this pair. When a buyer's Accredited Service Provider looks up where to deliver a document, the SMP lookup is keyed on scheme plus value together. An endpoint without a scheme cannot be resolved, so the network refuses the document before it travels anywhere.
Standard / Code List
Scheme identifiers come from the Peppol Electronic Address Scheme (EAS) list, which draws on the ISO 6523 ICD registry. The UAE entry, 0235, and how it maps to the Corporate Tax TIN are covered in Peppol EAS and ICD Participant Identifiers.
UAE Data Example
PASSES ✓: <cbc:EndpointID schemeID="0235">1XXXXXXX1</cbc:EndpointID> — the UAE TIN with its scheme declared, exactly as the PINT-AE samples show it.
FAILS ✗: <cbc:EndpointID>1XXXXXXX1</cbc:EndpointID> — the mapping populates the element text from the tax registration field but never sets the attribute. This is the typical failure mode: the value was mapped, the attribute was forgotten.
What Your ERP / IT Team Must Ensure
Hard-code the scheme alongside the endpoint value in the supplier configuration — they are one data point, not two. Confirm the extract writes schemeID as an XML attribute rather than a child element, a distinction some generic UBL mapping tools get wrong. If the company operates multiple TINs across entities, each company code needs its own endpoint pair, and the test plan should cover every issuing entity, not just the largest one.
Related Rules
The buyer-side twin of this rule is BR-50 (ibr-063), which is harder to keep clean because the data lives in the customer master rather than your own configuration. GLN-format checking for scheme 0088 endpoints is covered in BR-53 (ibr-068).