qmetrics
Fatal — invoice rejected Invoice lines & items Shared Peppol rule PINT-AE 2026.5

How to fix ibr-044 in UAE e-invoicing

What is ibr-044?

ibr-044 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 allowances and charges and belongs to the Invoice lines & items rule group. An e-invoice that fails ibr-044 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

Each Invoice line charge (ibg-28) MUST have an Invoice line charge reason (ibt-144) or an invoice line charge reason code (ibt-145).
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 allowances and charges of your UBL 2.1 invoice:

cac:AllowanceCharge[cbc:ChargeIndicator = true()]

Business terms referenced

Term ID Field Other rules
IBG-28 Invoice line charge view →
IBT-144 MUST have an Invoice line charge reason view →
IBT-145 view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)

Worried your invoices fail ibr-044?

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.