Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

ID Severity Context (XPath)
BR-10 Fatal (error) ubl:Invoice/cac:AccountingSupplierParty/cac:Party/cac:PostalAddress
Series reference: BR-10  |  Schematron ID: ibr-009

Classification

Master Data — The seller country code is the minimum required content within the seller postal address block enforced by BR-09. It establishes the supplier's jurisdictional location and is the critical field for VAT place-of-supply determinations and cross-border transaction classification.

What the Rule Is Checking

BR-10 requires that the seller's postal address block contains a non-empty country code in cac:PostalAddress/cac:Country/cbc:IdentificationCode (BT-40). The rule fires fatally if the cac:Country element is absent from the postal address, or if cbc:IdentificationCode within it is empty.

BR-10 is a child constraint of BR-09: an invoice that fails BR-09 (no postal address) will also fail BR-10 (no country code within that address). However, BR-10 can fail independently — when the postal address structure is present but BT-40 is omitted from within it.

Why This Rule Exists

The country code is the single most important field within the seller address block from a tax compliance perspective. UAE VAT rules distinguish domestic supplies, intra-GCC supplies, exports, and reverse-charge imports — distinctions that depend fundamentally on whether the supplier is established in the UAE or abroad. Without BT-40, neither the buyer's AP system nor the FTA can automate this classification.

In the Authority Mirror View™ framework, the FTA's digital tax authority receives structured transaction data and mirrors it against registered entity data. BT-40 is one of the fields used to confirm that the invoicing entity's self-declared location matches the FTA's registration record. A missing or incorrect country code breaks this verification chain.

Standard / Code List

BT-40 must be a valid ISO 3166-1 alpha-2 code. For UAE-registered suppliers, this is always AE. The full list of valid codes is defined in the ISO 3166 standard. See the reference post ISO 3166 Country Codes in UAE E-Invoicing for the UAE-relevant subset and GCC codes used in cross-border transactions.

Common UAE context values:

Code Country Context
AEUnited Arab EmiratesStandard UAE supplier
SASaudi ArabiaGCC supplier (reverse charge may apply)
GBUnited KingdomNon-GCC foreign supplier
INIndiaNon-GCC foreign supplier

UAE Data Example

PASSES ✓ — Country code present within postal address:
<cac:PostalAddress>
  <cbc:CityName>Abu Dhabi</cbc:CityName>
  <cac:Country>
    <cbc:IdentificationCode>AE</cbc:IdentificationCode>
  </cac:Country>
</cac:PostalAddress>

FAILS ✗ — PostalAddress present but no Country element:
<cac:PostalAddress>
  <cbc:CityName>Dubai</cbc:CityName>
  <!-- No cac:Country -->
</cac:PostalAddress>

FAILS ✗ — Country element present but IdentificationCode is empty:
<cac:PostalAddress>
  <cac:Country>
    <cbc:IdentificationCode/>
  </cac:Country>
</cac:PostalAddress>

FAILS ✗ — Invalid code (not ISO 3166-1 alpha-2):
<cbc:IdentificationCode>UAE</cbc:IdentificationCode>
<!-- "UAE" is the alpha-3 code — must be "AE" -->

What Your ERP / IT Team Must Ensure

  • Confirm that the country code in ERP address master data is stored as ISO 3166-1 alpha-2 (two letters), not alpha-3 (three letters) or the country's full name. Many legacy ERP configurations store "UAE" or "United Arab Emirates" and require a mapping to "AE" at the UBL output stage.
  • For the UBL mapping, cac:Country/cbc:IdentificationCode must be emitted as a child of cac:PostalAddress, not as a standalone element at the party level. The XPath context in the schematron is specific — a country code placed at the wrong nesting level will trigger BR-10.
  • Review your UBL template to confirm that cac:Country is always emitted even when other optional address fields (street, city, postal code) are absent. A minimal-address scenario where only BT-40 is populated is valid and satisfies both BR-09 and BR-10.
  • For invoice templates serving multiple geographies, the country code derivation logic must be entity-driven, not hard-coded. A UAE legal entity must emit AE; a UK entity must emit GB. Hard-coding AE in a global template is a common error that produces incorrect data for non-UAE legal entities.
  • Include BR-10 in your pre-go-live schematron test suite with explicit test cases covering: absent Country element, empty IdentificationCode, and alpha-3 code. These three failure modes account for the majority of BR-10 errors in practice.

Related Rules

BR-09 (Seller postal address mandatory), BR-11 (Buyer name mandatory), ISO 3166 Country Codes in UAE E-Invoicing, UAE E-Invoicing: Cross-Border and Export Transactions