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
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)
Worried your invoices fail ibr-co-26?
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
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.