qmetrics
Fatal — invoice rejected References & codes Shared Peppol rule PINT-AE 2026.5

How to fix ibr-cl-01 in UAE e-invoicing

What is ibr-cl-01?

ibr-cl-01 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 invoice document and belongs to the References & codes rule group. An e-invoice that fails ibr-cl-01 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

The document type code (ibt-003) MUST be coded by the invoice and credit note related code lists of UNTDID 1001.
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 invoice document of your UBL 2.1 invoice:

cbc:InvoiceTypeCode | cbc:CreditNoteTypeCode

Business terms referenced

Term ID Field Other rules
IBT-003 Invoice type code view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
(self::cbc:InvoiceTypeCode and ((not(contains(normalize-space(.), ' ')) and contains(' 380 480 ', concat(' ', normalize-space(.), ' '))))) or (self::cbc:CreditNoteTypeCode and ((not(contains(normalize-space(.), ' ')) and contains(' 81 381 ', concat(' ', normalize-space(.), ' ')))))

Test your invoice against ibr-cl-01 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.