qmetrics
Fatal — invoice rejected Amounts & totals Shared Peppol rule PINT-AE 2026.5

How to fix ibr-053 in UAE e-invoicing

What is ibr-053?

ibr-053 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 Amounts & totals rule group. An e-invoice that fails ibr-053 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

If the Tax accounting currency code (ibt-006) is present, then the Invoice total Tax amount in accounting currency (ibt-111) MUST be provided.
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:

/ubl:Invoice | /cn:CreditNote

Business terms referenced

Term ID Field Other rules
IBT-006 Tax accounting currency view →
IBT-111 Invoice total Tax amount in accounting currency view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
every $taxcurrency in cbc:TaxCurrencyCode satisfies exists(//cac:TaxTotal/cbc:TaxAmount[@currencyID=$taxcurrency])

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