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

How to fix ibr-030 in UAE e-invoicing

What is ibr-030?

ibr-030 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-030 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

If both Invoice line period start date (ibt-134) and Invoice line period end date (ibt-135) are given then the Invoice line period end date (ibt-135) MUST be later or equal to the Invoice line period start date (ibt-134).
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
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:EndDate) and exists(cbc:StartDate) and xs:date(cbc:EndDate) >= xs:date(cbc:StartDate)) or not(exists(cbc:StartDate)) or not(exists(cbc:EndDate))

Worried your invoices fail ibr-030?

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

ibr-085 Start date of line period (ibt-134) MUST be within invoice period (ibg-14). ibr-086 End date of line period (ibt-135) MUST be within invoice period (ibg-14). ibr-co-20 If Invoice line period (ibg-26) is used, the Invoice line period start date (ibt-134) or the Invoice ibr-073 A date MUST be formatted YYYY-MM-DD in (ibt-002), (ibt-007), (ibt-009), (ibt-026), (ibt-072), (ibt-0 ibr-003 An Invoice MUST have an Invoice issue date (ibt-002). ibr-005-ae Frequency of billing (BTAE-06) should be taken from the frequency of billing code list. ibr-029 If both Invoicing period start date (ibt-073) and Invoicing period end date (ibt-074) are given then ibr-067 An Invoice MUST contain maximum one Payment Mandate (ibg-19).

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.