qmetrics
Fatal — invoice rejected TRN & registration Shared Peppol rule PINT-AE 2026.5

How to fix ibr-co-26 in UAE e-invoicing

What is ibr-co-26?

ibr-co-26 is a fatal validation rule in the UAE's Peppol PINT-AE e-invoicing specification, inherited from the shared Peppol layer. It is checked against the seller (supplier) party block and belongs to the TRN & registration rule group. An e-invoice that fails ibr-co-26 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

In order for the buyer to automatically identify a supplier, the Seller identifier (ibt-029), the Seller legal registration identifier (ibt-030) and/or the Seller Tax identifier (ibt-031) MUST be present.
UAE impact: this is a fatal rule from the shared Peppol layer, enforced in the UAE 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-029 Seller identifier view →
IBT-030 Seller legal registration identifier view →
IBT-031 Seller VAT Identifier view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
exists(cac:PartyTaxScheme/cbc:CompanyID) or exists(cac:PartyIdentification/cbc:ID) or exists(cac:PartyLegalEntity/cbc:CompanyID)

Test your invoice against ibr-co-26 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.