PINT AE: The UAE E-Invoice Specification with Sage (UAE E-Invoicing)

PINT AE localises the international Peppol invoice for the Emirates: the 51 mandatory fields for an electronic tax invoice and 49 for a commercial invoice, the UAE-specific codelists and identifiers, and the validation rules every transmission must pass. It is published with the Peppol Authority Specific Requirements (PASR), which carry the local decisions.

For implementers, PINT AE is the document you map to. The field-mapping exercise is literally a walk through the PINT AE data dictionary: each element traced to a source in your ERP, each codelist value traced to a tax code or master-data value. The MOF mandatory-fields v1.0 (23 February 2026) is the readable entry point; the full specification is the working document.

Version discipline matters. Specifications evolve: new fields, tightened rules, clarified codelists. Assign ownership for tracking PINT AE and PASR updates, because a specification change with a compliance date is a project with a deadline, and the network will enforce the new rules whether you tracked them or not. Sage's UAE footprint spans Sage 200, Sage 300 and Sage Intacct across mid-market businesses. Integration patterns vary by product: API-based connectors for the cloud products, file or agent-based flows for the desktop line. Your ASP will confirm which pattern it supports for your exact Sage product and version.

Work through these in order.

Version drift is the Sage-specific risk: an old, unpatched desktop version may lack the API surface the connector needs. Confirm version compatibility in writing before the project plan is signed.

Mapping without tax advice is the quietest pitfall: every ERP tax code must resolve to exactly one PINT AE category, and the person doing it needs the VAT legislation open, not just the field list. Designated Zone scenarios, reverse charge and zero-rated versus exempt distinctions are where 'close enough' codes become misreported positions.

Numbering discipline is the next: sequential, gap-free series per entity, separate series for credit and debit notes, documented void handling. Validators and the FTA both read numbering as a completeness signal.

Finally, the moving target: PINT AE, the PASR and FTA guidance will evolve, especially in the first two years. Assign someone to track publications now, because a specification change with a compliance date is a project with a deadline, and the network enforces the new rules whether you tracked them or not. Pilot where you can: a bounded pilot with real invoices finds every one of these problems while they are still cheap.

In a review, the authority asks for records, not narratives: the transmitted documents, the validation history, the correction trail from original through credit note, the monthly reconciliations, and the archive. Each should be producible within a timeframe the request respects.

Correction trails deserve emphasis: every credit and debit note referencing its original, every resubmission logged with its rejection. A ledger that matches the network record is the strongest position a business can hold.

Keep the rule-change log too: which PINT AE or guidance updates arrived, when, and what changed in your process in response. It shows a compliance function that tracks its obligations, which is exactly what a reviewer wants to see.