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

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

What is ibr-133-ae?

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

What the official rule says

VAT scheme code, if provided in (IBT-095-1) or (IBT-031-1) or (IBT-048-1) or (IBT-063-1) or (IBT-102-1) or (IBT-118-1) shall be 'VAT' except when Seller tax registration identifier (IBT-032) is provided.
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: 

cac:TaxScheme/cbc:ID

Business terms referenced

Term ID Field Other rules
IBT-095-1 — view →
IBT-031-1 — view →
IBT-048-1 — view →
IBT-063-1 — view →
IBT-102-1 — view →
IBT-118-1 — view →
IBT-032 Seller VAT registration identifier view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron) 
. = "VAT" or exists(//cac:AccountingSupplierParty/cac:Party/cac:PartyTaxScheme/cbc:CompanyID[ string-length(normalize-space(.)) = 10 and starts-with(normalize-space(.), "1") and translate(normalize-space(.), "0123456789", "") = ""])

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

ibr-178-ae Tax scheme code, if provided in (IBT-031-1) shall not be 'VAT' when Seller tax registration identifi aligned-ibrp-001-ae Specification identifier (ibt-024) MUST start with the value 'urn:peppol:pint:billing-1@ae-1' or 'ur aligned-ibrp-sr-12 Seller tax identifier (ibt-031) MUST occur maximum once ibr-001 An Invoice MUST have a Specification identifier (ibt-024). ibr-001-ae Credit note reason code [BTAE-03] value should be from the Reasons for credit note code list. ibr-004 An Invoice MUST have an Invoice type code (ibt-003) / A Credit note MUST have a Credit note Type cod ibr-007-ae When Invoice Transaction-type code (BTAE-02) has value 1XXXXXXX (Free trade zone), then Beneficiary ibr-049 A Payment instruction (ibg-16) MUST specify the Payment means type code (ibt-081).

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.