qmetrics
Fatal — invoice rejected TRN & registration UAE-specific rule PINT-AE 2026.5

How to fix ibr-132-ae in UAE e-invoicing

What is ibr-132-ae?

ibr-132-ae is a fatal validation rule in the UAE's Peppol PINT-AE e-invoicing specification — one of the UAE-specific rules. It is checked against a postal address and belongs to the TRN & registration rule group. An e-invoice that fails ibr-132-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

VAT identifier [IBT-031, IBT-048, IBT-063, BTAE-14] should be TRN [VAT registration number] and must be 15 digits, starting with 1, ending with 03.
UAE impact: this is a fatal rule specific to the UAE PINT-AE profile — an invoice failing it is rejected at the Accredited Service Provider gateway before it ever reaches the FTA. A rejected invoice means resubmission delays, and late transmission risks the AED 100-per-invoice penalty under Cabinet Decision No. 106 of 2025.

Where it applies

This rule is checked against a postal address of your UBL 2.1 invoice: 

cac:Party[cac:PostalAddress/cac:Country/cbc:IdentificationCode = 'AE']/cac:PartyTaxScheme[cac:TaxScheme/normalize-space(upper-case(cbc:ID)) = 'VAT']/cbc:CompanyID

Business terms referenced

Term ID Field Other rules
IBT-031 Seller VAT Identifier view →
IBT-048 Buyer VAT identifier view →
IBT-063 Seller tax representative tax identifier view →
BTAE-14 Principal ID view →

Field names are derived automatically from the official rule corpus.

Why this happens

Every VAT identifier on a UAE e-invoice — the seller's TRN (IBT-031), the buyer's TRN (IBT-048), the tax representative's (IBT-063) and the additional seller VAT field (BTAE-14) — must be the FTA-issued Tax Registration Number: 15 digits, starting with 1 and ending with 03. Billing systems most often break this rule by exporting a trade licence number, a truncated TRN, or a TRN with spaces or dashes in it.

How to fix it

1. Open your customer/company master data and find the TRN field feeding this XML element. 2. Confirm it is exactly 15 characters with no spaces, dashes or 'TRN' prefix. 3. Cross-check the number against the FTA's TRN verification service. 4. Re-export the invoice and re-validate.

Rejected vs compliant XML

✕ Rejected

<cac:PartyTaxScheme>
  <!-- 5 characters, not a valid 15-character TRN -->
  <cbc:CompanyID>13579</cbc:CompanyID>
  <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
</cac:PartyTaxScheme>

✓ Compliant

<cac:PartyTaxScheme>
  <cbc:CompanyID>135790246801003</cbc:CompanyID>
  <cac:TaxScheme><cbc:ID>VAT</cbc:ID></cac:TaxScheme>
</cac:PartyTaxScheme>
Technical test condition (Schematron) 
string-length(.) = 15 and starts-with(., "1") and ends-with(., "03") and matches(., "^[0-9]+$")

Worried your invoices fail ibr-132-ae?

Upload your UBL XML — qmetrics runs 40+ core PINT-AE pre-submission checks (TRN, VAT math, addresses, totals and more) in one second. Your file is validated in memory and never stored.

Related rules

aligned-ibrp-sr-12 Seller tax identifier (ibt-031) MUST occur maximum once ibr-056 The Seller tax representative party (ibg-11) MUST have a Seller tax representative Tax identifier (i ibr-103-ae When the Invoiced item VAT category code (ibt-151) is VAT reverse charge, then Buyer VAT identifier ibr-104 Buyer tax identifier (ibt-048) MUST occur maximum once. ibr-133-ae VAT scheme code, if provided in (IBT-095-1) or (IBT-031-1) or (IBT-048-1) or (IBT-063-1) or (IBT-102 ibr-134-ae Seller VAT Identifier (IBT-031) MUST be there, except when the Invoice type code (IBT-003) is 'Out o ibr-135-ae Either Buyer identifier (IBT-046) or Buyer VAT identifier (IBT-048 ) MUST be present when the Invoic ibr-176-ae When Invoice transaction type code [BTAE-02] is XXXXX1XX (Disclosed agent billing), then the value i

Rule text sourced from the official OpenPeppol PINT-AE validation artifacts (version 2026.5), refreshed weekly. Explanations are qmetrics' own guidance, not official FTA/MoF text.