Skip to content
E-invoicing in the UAE (PINT AE)

What JooDax hands over in the UAE: a PINT AE document in the ASP’s folder

JooDax writes a PINT AE document from the Ministry’s field list, refuses it while a field is missing, then places it whole in a folder the ASP’s agent collects.

In the UAE the program talks to neither the Ministry nor the FTA; what it owes is a valid PINT AE document handed to the ASP the customer chose. So the jdx-einvoice-ae module builds that document from the 51 fields of a tax invoice and 49 of a commercial one (the Ministry’s list, version 1.1, 28 October 2026), with codes 380, 381, 480 and 81, the eight flags, the predefined endpoints and line amounts in AED.

Before writing, the module checks the list and names each missing field by its number there. It then writes the file under the invoice number with a .part extension and renames it .xml once complete, so the agent never takes half a file. Any ASP that collects files from a folder works this way.

Not built: any ASP’s API, the official Schematron, non-AED invoices, document-level allowances and charges, reverse-charge lines, disclosed-agent billing, the margin scheme, self-billing, reading status messages, and wiring the module to the programs’ invoices and customers. Non-AED invoices, reverse charge, disclosed-agent billing and the margin scheme are refused rather than written half-way. On 9 November 2026 the module’s rules were checked one by one against the PINT AE Schematron tests, and the gaps found were closed, among them emirate codes in addresses, exemption reasons, a payment account with credit transfer, the TAX scheme with a TIN, and credit-note reasons.

In JooDax

Partly built

The document is built and covered by fourteen tests in the code, and the folder hand-over is built. The document has not passed an official check, and the module is not yet wired to the programs.

crates/jdx-einvoice-ae/src/lib.rs; crates/jdx-einvoice-ae/src/tests.rs

Steps

  1. Invoice data is passed to the module (once it is wired to the programs).
  2. The module checks the Ministry’s fields and refuses the document, naming each missing field by its number.
  3. It computes the tax breakdown and totals and writes the PINT AE XML.
  4. It writes the file as .part, then renames it .xml in the ASP’s folder.
  5. The ASP’s agent collects the file; the ASP validates, exchanges and reports.

Questions and answers

Has an accredited provider accepted a JooDax document?

No; it has not yet been tested with any provider or with the official Schematron, so JooDax does not call it accepted.

Which provider does JooDax work with?

None in particular; the hand-over built is a folder, so it suits any provider whose agent collects XML files from a folder.

Related pages

Related concepts

E-invoicing in the UAE (PINT AE)

Sources

  1. UAE Electronic Invoice Mandatory Fields (vV 1.1) — Ministry of Finance, United Arab Emirates
  2. PINT AE Billing version 1.0.4 (v1.0.4 (PDK 1.4.4, released 29 Jul 2026)) — OpenPeppol AISBL (docs.peppol.eu)
  3. PINT AE Billing 1.0.4 – AE specific PINT rules (jurisdiction aligned rules) (v1.0.4) — OpenPeppol AISBL (docs.peppol.eu)

Checked on: 4 November 2026. What concerns JooDax is taken from the programs’ own code.