UAE validation and troubleshooting
Validate every UAE document before submission. Complyance applies the PINT AE transaction and rules that correspond to the complete Document Type selection.
Validation profile by Document Type
| Customer selection | Official document type code | Validation source |
|---|---|---|
| Tax Invoice + Ordinary | 380 | PINT AE Billing invoice |
| Tax Credit Note + Ordinary | 381 | PINT AE Billing credit note |
| Tax Invoice + Out of Scope | 480 | PINT AE Billing invoice plus the UAE out-of-scope conditions |
| Tax Credit Note + Out of Scope | 81 | PINT AE Billing credit note plus the UAE out-of-scope conditions |
| Tax Invoice + Self-Billed | 389 | PINT AE Self-Billing invoice |
| Tax Credit Note + Self-Billed | 261 | PINT AE Self-Billing credit note |
Invoice rules must not be substituted for credit-note rules, and ordinary rules must not be substituted for self-billing rules. Self-Billed and Out of Scope are mutually exclusive within the Document Type composition. An out-of-scope selection must also reject Export and the other prohibited combinations listed in UAE document type composition.
Read a validation finding
A validation finding should give you the information needed to correct the document:
- Field label: the affected field in your Complyance mapping or document experience
- What failed: a plain-language explanation of the invalid or missing information
- How to fix it: the expected correction, including an allowed choice where applicable
- Official reference: the PINT AE term or rule behind the finding when a regulatory rule applies
Validation payload structures, internal identifiers, field paths, and method names are implementation details and are intentionally excluded from this public guide.
Correct a rejected document
- Confirm that the complete selection appears in UAE document type composition.
- Group the findings by customer-facing field label so each source value is corrected once.
- Correct the value in your source mapping or document configuration.
- Revalidate the complete document. Correcting one field can activate a conditional rule elsewhere.
- Submit only after the complete document passes validation.
Common actionable findings
| Finding | Field label | What to correct | Official reference |
|---|---|---|---|
| Missing issue date | Issue Date | Supply a valid document issue date. | Invoice IBT-002 and credit-note IBT-002 |
| Missing or unsupported currency | Document Currency | Supply an ISO 4217 currency accepted by the selected transaction. | Invoice IBT-005 and credit-note IBT-005 |
| Unsupported VAT category | VAT Category | Choose a category allowed for the selected route. Out-of-scope documents accept Exempt, Outside Scope, or Zero Rated. | IBR-122-AE and PINT AE VAT categories |
| Unsupported unit of measure | Unit of Measure | Choose a unit accepted by the selected transaction. | PINT AE invoice code lists |
| Missing preceding invoice reference | Preceding Invoice Reference | For ordinary credit notes with code 381 or 81, supply the preceding invoice reference unless the Credit Note Reason is Volume Discount. | IBR-055-AE |
Official rule indexes
- PINT AE invoice business rules
- PINT AE invoice Schematron rules
- PINT AE credit-note business rules
- PINT AE credit-note Schematron rules
- PINT AE Self-Billing invoice business rules
- PINT AE Self-Billing invoice Schematron rules
- PINT AE Self-Billing credit-note business rules
- PINT AE Self-Billing credit-note Schematron rules
Use the official rule page when you need the full regulatory test behind a finding. Use the field label and correction guidance in Complyance to correct the affected source value.