Source: PINT-AE BIS Invoice v1.0.2 Schematron

Rule at a Glance

ID Severity Context (XPath)
BR-18 Fatal (error) ubl:Invoice/cac:TaxRepresentativeParty
Series reference: BR-18  |  Schematron ID: ibr-018

Classification

Master Data — BR-18 governs the seller tax representative party block (IBG-11). A tax representative is a locally registered entity that acts on behalf of a non-resident seller for VAT and e-invoicing purposes. The block is optional — it is only required when the seller is established outside the UAE and has appointed a UAE-resident tax representative to account for VAT. BR-18 activates only when that block is present.

What the Rule Is Checking

BR-18 tests that cac:TaxRepresentativeParty contains a cac:PartyName/cbc:Name element (IBT-062). The rule fires as fatal when the block is present but the name element is absent or empty. An empty string value also fails — the element must carry a non-whitespace legal name.

The rule is conditional: if cac:TaxRepresentativeParty is not present at all on the invoice (the seller is a UAE-registered entity invoicing in their own name), BR-18 does not evaluate. It is only triggered when the ERP or integration layer has explicitly included the tax representative block.

Why This Rule Exists

Under the UAE VAT framework, a non-resident business that makes taxable supplies in the UAE must either register directly or appoint a tax agent. Where a tax agent is appointed, the FTA holds the named tax agent accountable for the correctness of the invoice and the VAT return. The tax representative name on the PINT-AE invoice is the machine-readable link between the invoice and the registered agent.

Without a named tax representative in IBT-062, the FTA clearance system cannot perform the mandatory identity check between the party submitting the invoice through the ASP and the party registered as the agent in the FTA portal. A missing name triggers a fatal rejection before the invoice reaches the PEPPOL network.

Standard / Code List

No code list applies to the name value itself. The tax representative must also supply a UAE VAT registration number in IBT-063 — this is governed by BR-20. If the representative holds a Peppol participant identifier, it may optionally be included in cac:TaxRepresentativeParty/cac:PartyIdentification. See Peppol EAS and ICD participant identifier schemes.

UAE Data Example

PASSES ✓ — non-resident seller with named UAE tax representative
<cac:AccountingSupplierParty>
  <cac:Party>
    <cac:PartyName><cbc:Name>Global Tech GmbH</cbc:Name></cac:PartyName>
    <cac:PostalAddress>
      <cac:Country><cbc:IdentificationCode>DE</cbc:IdentificationCode></cac:Country>
    </cac:PostalAddress>
  </cac:Party>
</cac:AccountingSupplierParty>
<cac:TaxRepresentativeParty>
  <cac:PartyName><cbc:Name>UAE Tax Agents LLC</cbc:Name></cac:PartyName>
  <cac:PostalAddress>
    <cac:Country><cbc:IdentificationCode>AE</cbc:IdentificationCode></cac:Country>
  </cac:PostalAddress>
  <cac:PartyTaxScheme>
    <cbc:CompanyID>100123456700003</cbc:CompanyID>
    <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
  </cac:PartyTaxScheme>
</cac:TaxRepresentativeParty>

FAILS ✗ — TaxRepresentativeParty present but name missing
<cac:TaxRepresentativeParty>
  <!-- cac:PartyName absent — BR-18 fires as fatal -->
  <cac:PartyTaxScheme>
    <cbc:CompanyID>100123456700003</cbc:CompanyID>
    <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
  </cac:PartyTaxScheme>
</cac:TaxRepresentativeParty>

What Your ERP / IT Team Must Ensure

  • Only include cac:TaxRepresentativeParty when the invoicing entity is non-resident and a UAE tax representative has been formally appointed with the FTA — omit the block entirely for UAE-resident sellers.
  • Map the tax representative's legal registered name (as it appears on the FTA portal) to IBT-062; using a trading name or abbreviated name that does not match the FTA record will cause an identity validation failure.
  • Ensure your UBL template does not include a default or placeholder TaxRepresentativeParty block for invoices where no representative exists — a present-but-empty block triggers BR-18 and BR-20 simultaneously.
  • If your organisation has multiple legal entities, each entity's tax representative details must be configured separately in your ERP master data; do not inherit the representative from a related entity's record.
  • Coordinate with your FTA-registered tax agent to confirm the exact legal name string to use — any variation from the registered name, including punctuation or entity suffix differences, may cause rejection.

Related Rules

BR-19 (seller tax representative postal address country code mandatory), BR-20 (seller tax representative VAT identifier mandatory). See also MD 243 Article 5 — Accredited Service Provider obligations and 51 mandatory fields in PINT-AE.