qmetrics
Fatal — invoice rejected Dates & periods Shared Peppol rule PINT-AE 2026.5

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

What is ibr-co-20?

ibr-co-20 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 each invoice line and belongs to the Dates & periods rule group. An e-invoice that fails ibr-co-20 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

If Invoice line period (ibg-26) is used, the Invoice line period start date (ibt-134) or the Invoice line period end date (ibt-135) MUST be filled, or both.
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 each invoice line of your UBL 2.1 invoice:

cac:InvoiceLine/cac:InvoicePeriod | cac:CreditNoteLine/cac:InvoicePeriod

Business terms referenced

Term ID Field Other rules
IBG-26 Invoice line period view →
IBT-134 Start date of line period view →
IBT-135 Invoice line period end date view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
exists(cbc:StartDate) or exists(cbc:EndDate)

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