Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| Series ref. BR-83 | Fatal (error) | /ubl:Invoice | /cn:CreditNote |
| Schematron ID: ibr-103 | Field: ibt-047 — Buyer legal registration identifier | ||
Classification
Master Data — a cardinality constraint on the identifier that ties the recipient to a registered legal person.
What the Rule Is Checking
The assert is count(cac:AccountingCustomerParty/cac:Party/cac:PartyLegalEntity/cbc:CompanyID) <= 1. One occurrence or none passes at the core layer. Two fail fatally.
The UAE jurisdiction rules narrow when zero is acceptable. Under ibr-136-ae the buyer legal registration identifier must be present where the invoice type code is out of scope of VAT or a credit note related to goods or services. Under ibr-180-ae, once the buyer endpoint scheme identifier is 0235 and the identifier is provided, the buyer legal registration identifier type (BTAE-16) becomes mandatory, and ibr-183-ae limits that type to Commercial/Trade licence, Emirates ID, Passport or Cabinet decision.
Why This Rule Exists
Two registration identifiers for one buyer describe two registered persons receiving one supply, which the recipient cannot resolve and the authority cannot reconcile. The consequence lands on the customer rather than the sender: the buyer's input tax position depends on the invoice naming the entity that actually incurred the cost, and an ambiguous identifier weakens that position at exactly the point it needs to be defensible.
The UAE typing rules make the single-occurrence limit structural rather than stylistic. BTAE-16 declares what kind of identifier ibt-047 holds, and one type field cannot describe two identifiers. Where the buyer is an individual holding an Emirates ID and also a licensed sole establishment, the invoice has to state which capacity the purchase was made in — a determination the seller's onboarding process should make before the first transaction, not the integration layer at transmission time.
Standard / Code List
The scheme attribute (ibt-047-1) falls under ibr-cl-11 and must come from the ISO 6523 ICD list. Where the declared type is Commercial/Trade licence, ibr-101-ae requires the authority name (BTAE-11) to be present. Where the type is Passport, ibr-010-ae requires the passport issuing country code (BTAE-19).
UAE Data Example
PASSES ✓ — a licensed UAE customer on an out-of-scope supply:
<cac:PartyLegalEntity>
<cbc:RegistrationName>Emirates Retail Holdings LLC</cbc:RegistrationName>
<cbc:CompanyID schemeAgencyID="TL"
schemeAgencyName="Trade License issuing Authority">112345679000001</cbc:CompanyID>
</cac:PartyLegalEntity>FAILS ✗ — trade licence and Emirates ID both carried through from the customer master:
<cbc:CompanyID schemeAgencyID="TL">112345679000001</cbc:CompanyID>
<cbc:CompanyID schemeAgencyID="EID">784199012345678</cbc:CompanyID>Omitting the field altogether also fails where ibr-136-ae applies, so a credit note issued against a customer whose master record has no registration identifier is blocked until the master is corrected.
What Your ERP / IT Team Must Ensure
- Capture one registration identifier and its type during customer onboarding, and treat a missing type as an incomplete master record rather than an optional field.
- Run a master data sweep for customers with multiple registration identifiers before go-live; ibr-136-ae will surface them first on credit notes, which are the worst place to discover the gap.
- Populate BTAE-11 for trade licences and BTAE-19 for passports, since ibr-101-ae and ibr-010-ae make each conditional on the declared type.
- Check the invoice type code against the presence of the identifier in the same validation step, so out-of-scope supplies are caught before transmission.
- Validate the scheme attribute against the ISO 6523 ICD list, as ibr-cl-11 requires.
Related Rules
ibr-136-ae makes this identifier mandatory for out-of-scope supplies and credit notes. ibr-180-ae and ibr-183-ae govern the accompanying type. ibr-101-ae and ibr-010-ae add conditional fields by type. ibr-100 applies the same cap to the seller. ibr-104 caps the buyer tax identifier.