qmetrics
Fatal — invoice rejected Document structure Shared Peppol rule PINT-AE 2026.5

How to fix ibr-cl-16 in UAE e-invoicing

What is ibr-cl-16?

ibr-cl-16 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 payment details and belongs to the Document structure rule group. An e-invoice that fails ibr-cl-16 is rejected by the Accredited Service Provider gateway before it reaches the FTA.

What the official rule says

Payment means in an invoice (ibt-081) MUST be coded using UNCL4461 code list
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 payment details of your UBL 2.1 invoice:

cac:PaymentMeans/cbc:PaymentMeansCode

Business terms referenced

Term ID Field Other rules
IBT-081 Payment means type code view →

Field names are derived automatically from the official rule corpus.

Technical test condition (Schematron)
( ( not(contains(normalize-space(.),' ')) and contains( ' 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 70 74 75 76 77 78 91 92 93 94 95 96 97 98 ZZZ Z01 Z02 Z03 Z04 Z05 Z06 Z07 Z08 ',concat(' ',normalize-space(.),' ') ) ) )

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