qmetrics
Fatal — invoice rejected References & codes UAE-specific rule PINT-AE 2026.5

How to fix ibr-154-ae in UAE e-invoicing

What is ibr-154-ae?

ibr-154-ae is a fatal validation rule in the UAE's Peppol PINT-AE e-invoicing specification — one of the UAE-specific rules. It is checked against the invoice document and belongs to the References & codes rule group. An e-invoice that fails ibr-154-ae is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

Invoice Transaction-type code (BTAE-02) must be provided from the Invoice Transaction Type Code List. It should be a string consisting of no more than 8 characters, exclusively comprising of 0 and 1. The value in this field should be based on the sequence of transaction present in the invoice (as per list order), If applicable '1', and if not applicable '0' .
UAE impact: this is a fatal rule specific to the UAE PINT-AE 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
BTAE-02 Invoice transaction type code view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
(matches(cbc:ProfileExecutionID, "^[01]{8}$"))

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