qmetrics
Fatal — invoice rejected Party & address Shared Peppol rule PINT-AE 2026.5

How to fix ibr-020 in UAE e-invoicing

What is ibr-020?

ibr-020 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 a postal address and belongs to the Party & address rule group. An e-invoice that fails ibr-020 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

The Seller tax representative postal address (ibg-12) MUST contain a Tax representative country code (ibt-069), if the Seller (ibg-04) has a Seller tax representative party (ibg-11).
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 a postal address of your UBL 2.1 invoice:

cac:TaxRepresentativeParty/cac:PostalAddress

Business terms referenced

Term ID Field Other rules
IBG-12 Seller tax representative postal address view →
IBT-069 MUST contain a Tax representative country code view →
IBG-04 Seller view →
IBG-11 Seller tax representative party view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
normalize-space(cac:Country/cbc:IdentificationCode) != ''

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