qmetrics
Fatal — invoice rejected Allowances & charges Shared Peppol rule PINT-AE 2026.5

How to fix ibr-033 in UAE e-invoicing

What is ibr-033?

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

What the official rule says

Each Document level allowance (ibg-20) MUST have a Document level allowance reason (ibt-097) or a Document level allowance reason code (ibt-098).
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 = false()]

Business terms referenced

Term ID Field Other rules
IBG-20 Document level allowance view →
IBT-097 Allowance reason view →
IBT-098 Coded allowance reasons view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron) 
((exists(cbc:AllowanceChargeReason) or exists(cbc:AllowanceChargeReasonCode)) and not(exists(ancestor::cac:InvoiceLine|ancestor::cac:CreditNoteLine))) or (ancestor::cac:InvoiceLine | ancestor::cac:CreditNoteLine)

Worried your invoices fail ibr-033?

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-031 Allowance (ibg-20) MUST have an allowance amount (ibt-092). ibr-041 Each Invoice line allowance (ibg-27) MUST have an Invoice line allowance amount (ibt-136). ibr-042 Each Invoice line allowance (ibg-27) MUST have an Invoice line allowance reason (ibt-139) or an Invo ibr-sr-30 Allowance reason (ibt-097) MUST occur maximum once aligned-ibrp-032 Each Document level allowance (ibg-20) MUST have a Document level allowance VAT category code (ibt-0 aligned-ibrp-ae-01-ae An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document aligned-ibrp-ae-06 In a Document level allowance (ibg-20) where the Document level allowance VAT category code (ibt-95) aligned-ibrp-e-01 An Invoice that contains an Invoice line (ibg-25), a Document level allowance (ibg-20) or a Document

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.