The UAE e-Invoicing Public Consultation and Its Data Dictionary

The document people are searching for is the UAE Ministry of Finance eInvoicing Programme Consultation Paper, subtitled eInvoicing Data Dictionary. It runs to 168 pages, of which the first ten are narrative and the remaining appendix is a use-case-by-use-case field listing.

Its stated objective, in section 1, was to gather feedback from UAE businesses and eInvoicing Service Providers on the proposed elements of the framework, specifically to establish a common understanding of the data elements used in eInvoices, to identify gaps or additional fields needed for operational, regulatory or analytical purposes, and to obtain perspectives from industry experts, accounting firms and service providers.

The file is still served from the Ministry's February 2025 uploads directory and opened normally when we read it on 21 August 2026. It is no longer linked from the Ministry's eInvoicing programme page, which now carries the Guidelines, the mandatory field requirements, the programme introduction and the legislation. The paper survives as a historical document, not as current guidance — and that distinction matters, because parts of it were proposals that the eventual Decisions changed or dropped.

This is the part every republished summary gets wrong, so it is worth stating precisely.

Section 6 of the paper, headed Next steps, sets out a consultation timeline with two entries: "Document release date: [Insert Date]" and "Deadline for feedback: [Insert Date]". Both placeholders went out unfilled in the published PDF. The Ministry document therefore states no release date and no closing date at all.

Dates of 6 February 2025 for release and 27 February 2025 for the deadline circulate widely in advisory-firm alerts. We do not publish them as official, because we cannot point at a Ministry of Finance source that states either one. What can be verified is that the file sits in the Ministry's February 2025 upload path and that the consultation is no longer open.

That it is closed is verifiable two ways. First, the eInvoicing programme page no longer links the paper or any response channel. Second, the Ministry of Finance runs a public consultations register, and as at 21 August 2026 it lists no open e-invoicing consultation of any kind.

The response mechanism described in the paper was a government survey form, with respondents asked to give name, company name, phone number, email address, industry and annual turnover — the last so the Ministry could weigh the impact of issues raised. If you have feedback now, that route is gone; the current channel is the Federal Tax Authority and the Ministry's own contact pages, not the survey link printed in a 2025 PDF.

Reading the consultation next to the Decisions that followed shows how little drifted.

The framework. Section 3 described the UAE's adoption of a Decentralized Continuous Transaction Control and Exchange (DCTCE) model and walked through an eleven-step flow: the supplier passes invoice data to its Accredited Service Provider, that provider validates and converts it to the UAE standard XML, transmits it to the buyer's provider, and in parallel reports a Tax Data Document to the fifth corner, with message-level statuses flowing back at each hop. That is the five-corner model now operating under Ministerial Decision No. 243 of 2025.

The scope. The paper stated that eInvoicing requirements apply not only to taxable persons but to all businesses operating in the UAE regardless of VAT registration status. Article 3 of MD No. 243 of 2025 enacted exactly that, applying the system to any Person conducting Business in the State in respect of every Business Transaction.

The phasing. The paper committed to nothing. It said only that eInvoicing would be rolled out in a phased manner and that a rollout strategy would be communicated in due course. The dates arrived seven months later in Article 5 of MD No. 244 of 2025.

The data dictionary. The paper carried the proposed PINT AE field set, built on the Peppol PINT specification, with each business term identified as IBT-XXX where it comes from the global specification or BTUAE-XX where it is specific to the UAE, and marked M for mandatory, O for optional or C for conditional. The current successor document is the Ministry's UAE Electronic Invoice Mandatory Field Requirements, version 1.0, dated 23 February 2026 — that, not the consultation appendix, is what an implementation should be mapped against.

Section 4(a) of the paper tabulates the common UAE scenarios in which a tax invoice or tax credit note must be issued or retained, each mapped to an appendix of field requirements. Use cases 1, 12, 14, 15 and 16 are given as full field sets; the rest are expressed as additional requirements on top of use case 1 or use case 12.

One small inconsistency in the document is worth knowing if you are counting: the use-case table lists sixteen rows, while the appendix heading in section 7 refers to a list of fifteen. We report the table, which is the operative part.

Sections 5 and 6 set out what the Ministry wanted to hear, under two headings — comprehensiveness (are all required fields included?) and clarity (are the definitions unambiguous?). The response table listed six questions:

1. In the data dictionary, are there any fields missing for your specific business?
2. Are there any conflicts or issues with the existing fields in the data dictionary?
3. Are industry-specific data elements adequately represented?
4. HS codes and service codes are proposed to be optional initially but will become mandatory later — would 4, 6 or 8 digits be practical to report?
5. Do you foresee any problems in reporting specific transactions through the eInvoicing exchange, for example from a practicality or privacy perspective?
6. Are there any fields or terms you find confusing or open to multiple interpretations?

The consultation window has closed, but the questions are still the right readiness checklist. Run your own transaction types against them: if question 1 or 3 produces a gap for your industry, that gap is now yours to solve with your Accredited Service Provider rather than with the Ministry, and it is better found in a mapping workshop in 2026 than at validation in 2027.

The Ministry of Finance keeps a public consultations register listing open and closed consultations with their dates. It is worth knowing what it does and does not show.

It does list a second, later e-invoicing consultation that almost nobody cites: Companies' Feedback on the Ministry of Finance's e-Invoicing Service Provider Accreditation Portal, shown as ended on 31 January 2026. That one was aimed at service providers using the accreditation portal rather than at taxpayers, which is presumably why it left no trail in the advisory press.

It does not list the 2025 data dictionary consultation at all. So the register is not a complete archive of Ministry consultations, and an absence there is not evidence that a consultation never happened — a useful thing to know before telling a client that no consultation took place.

As at 21 August 2026 the register shows no open e-invoicing consultation. If you want to be in the room for the next one — a B2C decision, an Excluded Persons decision and the HS code digit length are all still outstanding — the register is the page to watch, alongside the eInvoicing programme page and the Ministry's financial legislation index.