Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

ID Severity Context (XPath)
BR-11 Fatal (error) ubl:Invoice/cac:AccountingCustomerParty/cac:Party
Series reference: BR-11  |  Schematron ID: ibr-007

Classification

Master Data — The buyer name is a mandatory party identification field that anchors the invoice to a specific legal entity on the customer side. Without it, neither the FTA's data platform nor the buyer's AP system can unambiguously match the incoming invoice to a registered business entity.

What the Rule Is Checking

BR-11 requires that the cac:AccountingCustomerParty/cac:Party block contains a non-empty buyer name in either cac:PartyName/cbc:Name (BT-44, trading name) or cac:PartyLegalEntity/cbc:RegistrationName (BT-45, legal name), or both. The rule fires fatally if neither element is populated.

BT-44 and BT-45 serve related but distinct purposes. BT-44 is the buyer's trading name — the name under which it operates commercially. BT-45 is the buyer's legally registered name as it appears on the trade licence or corporate registration. For most UAE businesses, both are present and often identical. Where they differ — as with large groups that trade under a brand name distinct from the holding company — both fields should be populated.

Why This Rule Exists

UAE Corporate Tax law (Federal Decree-Law No. 47 of 2022) requires that a tax invoice identifies the recipient where applicable. The buyer name on a PINT-AE invoice creates a direct audit trail from the document to a legal entity in the FTA's Corporate Tax register, enabling the FTA's Continuous Controls Environment™ to perform real-time matching between supplier output tax and buyer input tax claims.

In the Authority Mirror View™ framework, the FTA holds a digital mirror of every registered taxpayer. When a PINT-AE invoice arrives via the 5-Corner Peppol network, the buyer name (BT-44 or BT-45) is one of the fields cross-referenced against the CT registration database. An invoice with no buyer name cannot be subjected to this verification and may be rejected at the Access Point level before it reaches the buyer at all.

Standard / Code List

No code list governs BT-44 or BT-45 — both are free-text fields. The buyer name should match the name on the buyer's UAE trade licence or FTA registration certificate. For Arabic-named entities, the name should be provided in the same script and transliteration convention used in official registration documents. PINT-AE does not mandate a specific language, but inconsistency between the invoice name and the FTA-registered name may trigger manual review.

UAE Data Example

PASSES ✓ — Trading name in PartyName (BT-44):
<cac:AccountingCustomerParty>
  <cac:Party>
    <cac:PartyName>
      <cbc:Name>Emirates Steel Arkan PJSC</cbc:Name>
    </cac:PartyName>
  </cac:Party>
</cac:AccountingCustomerParty>

PASSES ✓ — Legal entity name in PartyLegalEntity (BT-45):
<cac:AccountingCustomerParty>
  <cac:Party>
    <cac:PartyLegalEntity>
      <cbc:RegistrationName>Emirates Steel Arkan PJSC</cbc:RegistrationName>
    </cac:PartyLegalEntity>
  </cac:Party>
</cac:AccountingCustomerParty>

PASSES ✓ — Both fields populated (recommended for audit-grade invoices):
<cac:Party>
  <cac:PartyName>
    <cbc:Name>ESA Steel</cbc:Name>
  </cac:PartyName>
  <cac:PartyLegalEntity>
    <cbc:RegistrationName>Emirates Steel Arkan PJSC</cbc:RegistrationName>
  </cac:PartyLegalEntity>
</cac:Party>

FAILS ✗ — CustomerParty present but no name in either field:
<cac:AccountingCustomerParty>
  <cac:Party>
    <cac:PostalAddress>
      <cac:Country><cbc:IdentificationCode>AE</cbc:IdentificationCode></cac:Country>
    </cac:PostalAddress>
    <!-- No PartyName or PartyLegalEntity -->
  </cac:Party>
</cac:AccountingCustomerParty>

What Your ERP / IT Team Must Ensure

  • Confirm that the customer master record in your ERP contains a non-empty name field that is mapped to either cac:PartyName/cbc:Name (BT-44) or cac:PartyLegalEntity/cbc:RegistrationName (BT-45) in your UBL output template. A customer record with a blank or whitespace-only name will pass ERP-level validation but fail the PINT-AE schematron check.
  • For UAE-registered buyers, populate BT-45 with the exact legal name from the trade licence. This creates the strongest match against the FTA's CT registration database and reduces the likelihood of reconciliation queries from the buyer's accounts payable team.
  • Where your ERP customer master distinguishes between "ship-to" and "bill-to" party names, ensure the UBL mapper uses the bill-to (invoiced) party name for BT-44/BT-45, not the delivery address name. Delivery party information maps to separate UBL elements and must not be confused with the accounting customer party.
  • For government buyers (B2G), confirm that the buyer name matches the official entity name used by the relevant emirate or federal authority. Government entities often have both an Arabic name and an official English transliteration — use whichever is on the purchase order or the FTA registration.
  • Include BR-11 in your regression test suite with a test case that specifically sends an invoice with an empty <cbc:Name/> element (whitespace only) — some schematron validators treat an empty element differently from an absent one, and both should fail BR-11.

Related Rules

BR-10 (Seller country code mandatory), BR-12 (Buyer postal address country code), UAE E-Invoicing Master Data Readiness, 51 Mandatory Fields in PINT-AE