Rule at a Glance
| ID | Severity | Context (XPath) |
|---|---|---|
| BR-08 | Fatal (error) | ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PartyName |
| Series reference: BR-08 | Schematron ID: ibr-006 | ||
Classification
Master Data — The seller name is a core party identity field. It anchors the invoice to a legal entity registered in the UAE and is part of the minimum identifiable supplier information required by MD 243.
What the Rule Is Checking
BR-08 requires that the invoice contains a non-empty seller name in cac:AccountingSupplierParty/cac:Party/cac:PartyName/cbc:Name (BT-27). The rule fires fatally if the element is absent or carries an empty string.
BT-27 is the seller's trading name as it appears on the invoice. This is distinct from the seller's legal name, which may be carried separately in cac:PartyLegalEntity/cbc:RegistrationName (BT-28). BR-08 requires BT-27 specifically — BT-28 alone does not satisfy it.
Why This Rule Exists
In the UAE e-invoicing framework, the seller's identity on the invoice must be traceable to a Corporate Tax registration. While the CT TIN (BT-AE-003) and VAT number (BT-31) carry the numeric identifiers, BT-27 provides the human-readable name that buyers, auditors, and FTA reviewers use to verify the invoice against supplier master data.
An invoice without a seller name cannot be processed through standard AP workflows and cannot be matched against a supplier record. It also fails the basic evidentiary standard that UAE tax law requires of a valid tax invoice — an invoice that cannot be attributed to a named legal entity has no standing as a deductible document.
Standard / Code List
No code list applies — BT-27 is a free-text string. However, best practice in the UAE context is to use the name exactly as it appears on the Trade Licence or the FTA registration certificate. Inconsistencies between BT-27 and the registered name may not cause BR-08 to fail, but they create reconciliation problems for buyers conducting supplier due diligence.
UAE Data Example
PASSES ✓ — Seller name present:
<cac:AccountingSupplierParty>
<cac:Party>
<cac:PartyName>
<cbc:Name>Contiqa Systems FZ-LLC</cbc:Name>
</cac:PartyName>
</cac:Party>
</cac:AccountingSupplierParty>
FAILS ✗ — PartyName element absent:
<cac:AccountingSupplierParty>
<cac:Party>
<!-- No cac:PartyName -->
</cac:Party>
</cac:AccountingSupplierParty>
FAILS ✗ — PartyName present but Name is empty:
<cac:PartyName>
<cbc:Name/>
</cac:PartyName>What Your ERP / IT Team Must Ensure
- The company name in ERP company code master data must be mapped to BT-27 in the UBL output. Confirm this mapping is explicit — some ERP UBL adapters default BT-27 to the legal entity name (BT-28) while leaving BT-27 blank, which triggers BR-08.
- For companies trading under a brand name different from the legal entity name, populate BT-27 with the trading name and BT-28 with the legal registration name. Both should be present for maximum clarity.
- Multi-entity ERP deployments where a single system generates invoices for multiple UAE legal entities must ensure BT-27 is entity-specific — not a shared system name or blank default.
- After any ERP upgrade or UBL mapper patch, re-run schematron validation on a sample of output invoices to confirm BT-27 is still being populated. Configuration changes can silently break field mappings.
- Self-billing arrangements (where the buyer issues the invoice on behalf of the seller) must still populate BT-27 with the seller's name, not the buyer's. The field identifies who made the taxable supply, regardless of who generated the document.
Related Rules
BR-07 (Buyer reference), BR-09 (Seller postal address), UAE E-Invoicing Master Data Readiness, MD 243 Articles 8–9: Agent and Self-Billing