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

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

What is ibr-181-ae?

ibr-181-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 the seller (supplier) party block and belongs to the TRN & registration rule group. An e-invoice that fails ibr-181-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

When scheme identifier (IBT-034-1) is '0235' and Seller legal registration identifier (ibt-030) is provided, then Seller legal registration identifier type (BTAE-15) MUST be present
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 the seller (supplier) party block of your UBL 2.1 invoice:

cac:AccountingSupplierParty/cac:Party

Business terms referenced

Term ID Field Other rules
IBT-034-1 scheme identifier view →
IBT-030 Seller legal registration identifier view →
BTAE-15 Seller legal registration identifier type view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
not(cbc:EndpointID[@schemeID = "0235"]) or not(cac:PartyLegalEntity/cbc:CompanyID) or  cac:PartyLegalEntity/cbc:CompanyID/@schemeAgencyID

Test your invoice against ibr-181-ae now

Upload your UBL XML — we check all 302 PINT-AE rules including this one, in one second. Your file is validated in memory and never stored.

Related rules

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.