.jpg)
Businesses often search for the “FTA e-invoicing guidelines,” but the UAE’s core Electronic Invoicing Guidelines are published through the Ministry of Finance (MoF). The Federal Tax Authority still has an important role in registration, tax-data reporting and administration, but the FTA itself directs businesses to the MoF portal as the official source for information on the introduction of UAE e-invoicing.
The current main guidance document is the UAE Electronic Invoicing Guidelines V1.1, dated June 1, 2026. It needs to be read alongside the relevant Ministerial Decisions, later amendments, PINT-AE requirements and penalty rules because one important deadline printed in the V1.1 PDF has already been superseded.
The distinction between the FTA and Ministry of Finance is worth understanding because both organisations appear throughout UAE e-invoicing material.
The Ministry of Finance sets and publishes the policy framework. Its official eInvoicing portal hosts the implementation Guidelines, Ministerial Decisions, ASP material, mandatory-field guidance and programme updates.
The Federal Tax Authority is involved in implementation and administration. Its role includes matters such as tax registration, Tax Identification Numbers, EmaraTax, and receiving the tax data generated through the e-invoicing framework.
The FTA makes the source hierarchy particularly clear on its UAE e-Invoicing page: businesses are directed to the Ministry of Finance portal as the official source of information regarding the introduction of e-invoicing.
For implementation teams, that means an old FTA presentation, vendor summary or downloaded PDF should not be treated as the final source if the MoF has subsequently published an amendment.
The UAE framework is spread across several documents that perform different jobs.
The practical UAE Electronic Invoicing Guidelines V1.1 are therefore a starting point rather than the only document a project team should read.
That matters whenever a later legal amendment changes something printed in the Guidelines.
The June 2026 Guidelines still show July 31, 2026 as the deadline for businesses with annual Revenue of AED 50 million or more to appoint an Accredited Service Provider.
That is no longer the current date.
In May 2026, the Ministry of Finance amended the first appointment deadline to:
October 30, 2026
The mandatory implementation date for this group remains:
January 1, 2027
The Ministry confirmed the amendment in its eInvoicing decision update and reconfirmed the October deadline again in September 2026.
This is a useful reminder that compliance teams should not download the Guidelines once and assume every date inside them will remain current. The Guidelines need to be read together with later Ministerial Decisions and amendments.
The current Guidelines state that Electronic Invoicing applies broadly to a Person conducting Business in the UAE in respect of Business Transactions, unless the Person or transaction is specifically excluded.
VAT registration is not the deciding test. A Person making a Business Transaction in the UAE can fall within the e-invoicing scope even if that Person is not VAT registered.
The framework covers business and government transaction flows such as transactions between businesses and transactions involving government entities. Supplies involving consumers who are not acting in Business are currently outside the mandatory framework.
This distinction matters because businesses should not use their VAT-registration status as a shortcut for deciding whether they need to prepare for e-invoicing.
For a broader explanation of the current rollout and scope, see HAL’s verified UAE E-Invoicing guide.
Ministerial Decision No. 243 of 2025 identifies specific exclusions rather than providing a blanket exemption for particular industries.
Current exclusions include certain Government Entity activities carried out in a sovereign capacity where they do not compete with the private sector. The Decision also excludes specified international airline passenger transactions where an Electronic Ticket is issued, specified ancillary airline services, and certain international air-cargo transactions supported by an Airway Bill.
The air-cargo exclusion is temporary and applies for a prescribed 24-month period. Specified financial services that are exempt from VAT or subject to zero-rating under the relevant financial-services rule are also excluded.
Consumer transactions are dealt with separately through the implementation framework. Businesses should therefore avoid assuming that every excluded activity comes from the same provision or that an entire company is necessarily excluded because one transaction type falls outside the system.
A UAE Electronic Invoice is not simply a PDF version of the existing tax invoice.
The current Guidelines state that Electronic Invoices are issued, transmitted and received in XML format. They also state explicitly that UAE Electronic Invoices will not feature a QR code or barcode.
Invoice content follows the applicable PINT-AE requirements. PINT-AE is the UAE implementation built on the Peppol International model for Billing and defines how structured invoice information is represented for the UAE framework.
The Ministry’s mandatory-field material groups required information into areas such as invoice details, seller information, buyer information, document totals, tax breakdown and invoice-line data. Businesses do not need to memorise every field, but their ERP or invoicing system needs to make the necessary information available to the ASP.
The important implementation question is therefore not:
“Can our system create a PDF invoice?”
It is whether the current finance environment can reliably generate and extract the structured data required for the applicable invoice scenario.
For more background on the network and PINT terminology, see HAL’s Peppol E-Invoicing guide.
The Guidelines use the Tax Identification Number (TIN) as a key part of participant identification.
For businesses already registered with the FTA for a tax type, the Guidelines state that the TIN is the first 10 digits of the TRN. A Person that falls within the e-invoicing scope but is not otherwise required to register for a tax type will need to register with the FTA to obtain a TIN.
The Peppol Participant Identifier used in the UAE is constructed using:
0235 + the 10-digit TIN
Tax Groups require particular care. Each Tax Group member uses its own TIN for e-invoicing rather than simply using the first 10 digits of the Tax Group representative’s TRN.
The Guidelines also state that each Tax Group member is onboarded separately for Electronic Invoicing and may onboard with a different ASP.
The UAE framework builds invoice exchange around suppliers, buyers and their respective ASPs, with tax data also reported to the FTA.
The core flow can be summarised as:
Supplier → Supplier ASP → Buyer ASP → Buyer
with required tax information also reported to:
FTA / Corner 5
The supplier sends invoice data to its ASP in the agreed format. The ASP validates the data and, where necessary, converts it into the UAE-standard XML format before sending it onward to the buyer’s ASP.
The buyer’s ASP then validates and delivers the Electronic Invoice to the buyer. In parallel with the commercial exchange, the required Tax Data is reported through the framework to the FTA, and electronic confirmations flow back through the relevant providers.
This is why e-invoicing implementation affects more than accounts receivable. Incoming supplier invoices and AP workflows also need to be part of the project.
Using an ASP does not transfer the underlying compliance responsibility away from the business.
The Guidelines expressly note that ASPs perform many of the practical exchange activities while the compliance obligation remains with the supplier, or with the buyer where self-billing applies.
This is an important control point. A business cannot assume that choosing an accredited provider makes incorrect customer data, tax treatment or invoice amounts the provider’s responsibility.
The timing rule needs more care than a simple statement that “all e-invoices have 14 days.”
Under Ministerial Decision No. 243 of 2025, where the issuer is a VAT Registrant, the Electronic Invoice or Electronic Credit Note must be issued and transmitted within the timeline prescribed by the VAT Law.
Subject to that rule, other relevant Electronic Invoices and Electronic Credit Notes must be issued and transmitted through the Electronic Invoicing System within:
14 days from the Date of Business Transaction
The Decision defines the Date of Business Transaction as the earlier of the date the transaction occurred or the date payment was received.
VAT-registered businesses should therefore continue to apply the applicable VAT timing rules rather than replacing them with a blanket 14-day assumption.
Implementation dates are not the only deadlines finance teams need to control.
The system-failure rule is especially important because it applies to both issuers and recipients. Internal procedures therefore need to define what qualifies as a reportable system failure, who identifies it and who is responsible for ensuring the FTA notification is made within the required window.
These obligations also connect directly to the administrative-penalty regime. HAL’s UAE E-Invoicing Penalties guide explains the current fine structure separately.
The V1.1 Guidelines provide more detailed retention guidance than a simple “store invoices in the UAE” statement suggests.
The general periods described in the Guidelines include:
Longer periods can apply where there is a dispute, tax audit, FTA audit notification or certain voluntary-disclosure circumstances.
Ministerial Decision 243 says Electronic Invoices, Electronic Credit Notes and associated data must be stored “within the State.” However, V1.1 clarifies the policy intent: the records must remain secure, intact, retrievable and capable of being provided to the FTA in complete and readable form.
The Guidelines specifically explain that compliant infrastructure may be located inside or outside the UAE if those requirements are satisfied. Storage can also be delegated contractually to the ASP, but the business remains legally responsible for meeting the retention obligation.
The current Guidelines also address scenarios that do not fit a simple one-invoice/one-payment model.
For advance payments, a tax invoice must be issued when VAT becomes due on the advance. When the final invoice is later issued, it covers the remaining balance rather than repeating the full amount, with the earlier advance invoice referenced where appropriate.
For retentions, the Guidelines recognise established commercial and accounting practices provided the VAT and e-invoicing requirements are met. A later Electronic Invoice can be issued for the retained amount when the buyer becomes liable to release it.
VAT Groups also receive a specific transitional measure. Business Transactions between members of the same VAT Group have a 24-month grace period beginning January 1, 2027 before the Electronic Invoicing obligations are required for those intra-group transactions.
The Guidelines cover additional scenarios including Free Zones, deemed supplies, the margin scheme, continuous supplies, summary invoices, disclosed agents, exports and e-commerce. Businesses with these transaction types should map the relevant scenario before designing the ERP-to-ASP flow.
The current legal timeline is:
The pilot and voluntary implementation period began on July 1, 2026. Voluntary participants must follow the applicable technical requirements, but the dedicated e-invoicing administrative penalties do not apply until that Person becomes mandatorily subject to the system.
For a detailed explanation of the phases and Revenue threshold, see HAL’s verified UAE E-Invoicing Deadline guide.
The Guidelines themselves include implementation-readiness steps. The following checklist translates those into a finance and systems workflow.
The goal is not simply to prove that one sample invoice can pass through the network. The business needs a repeatable operating process covering normal transactions, incoming invoices, exceptions, failures, corrections and record retention.
The dedicated penalty framework is set out under Cabinet Decision No. 106 of 2025.
Current penalties cover failures such as not implementing the Electronic Invoicing System or appointing an ASP on time, failing to issue or transmit required Electronic Invoices and Electronic Credit Notes, late system-failure notifications, and failing to notify the appointed ASP about relevant registered-data changes within the required period.
The fines are separate from other VAT and Tax Procedures penalties that may apply to the underlying tax obligation. A business should therefore evaluate the specific requirement that has been breached rather than treating e-invoicing as replacing the existing tax framework.
The Ministry publishes the current legislation and updates through its official eInvoicing portal.
The official implementation checklist specifically tells businesses to assess whether their accounting, ERP and invoicing applications can generate and extract the required Electronic Invoice data.
That includes practical source information such as customers, suppliers, invoice lines, credit notes, tax information, receivables, payables and transaction records. Businesses also need a way to receive statuses and incoming invoice information back into the finance process.
HAL Invoicing can support underlying invoice and credit-note workflows and related transaction records. It should not, however, be treated as a UAE Accredited Service Provider, PINT-AE connectivity service or direct FTA reporting solution unless those specific capabilities are documented separately.
The ASP remains the accredited exchange layer; the ERP or accounting environment remains responsible for supplying reliable business data into that process.
The UAE e-invoicing rules should not be treated as one static guideline document. A reliable compliance view comes from reading the MoF Guidelines, Ministerial Decisions, later amendments, PINT-AE requirements, mandatory-field material and ASP rules together.
For implementation teams, that translates into a practical sequence:
Confirm scope → determine the correct deadline → prepare identifiers and data → appoint an ASP → map ERP fields → integrate AR and AP → test normal and exception flows → go live → maintain records and controls
The underlying finance system remains an important part of that process because the structured invoice is only as reliable as the transaction and master data feeding it.
HAL Invoicing can support the invoice and transaction workflows behind an e-invoicing implementation, while the business works with its selected UAE Accredited Service Provider for the exchange layer.
Book a HAL demo to review how your current invoicing and finance workflows can be prepared for the UAE e-invoicing transition.
The principal programme guidance is published through the Ministry of Finance. The FTA itself directs businesses to the MoF portal as the official source for information regarding the introduction of UAE e-invoicing.
The current document available through the Ministry of Finance is UAE Electronic Invoicing Guidelines V1.1, dated June 1, 2026.
No. The current Guidelines state that Persons making Business Transactions in the UAE can fall within scope regardless of VAT-registration status, unless specifically excluded.
No. The official UAE framework requires structured invoice data. PDFs, Word documents, images, scans and ordinary emailed invoices do not qualify as Electronic Invoices by themselves.
No. V1.1 states that Electronic Invoices are issued, transmitted and received in XML format and will not feature a QR code or barcode.
The framework uses structured XML with the applicable PINT-AE billing requirements.
The current deadline is October 30, 2026 for businesses with Revenue of AED 50 million or more. The July 31 date still printed in V1.1 was superseded by the later 2026 amendment.
Yes. The current framework requires in-scope Persons to work with an Accredited Service Provider for the applicable sending, receiving, exchange and reporting processes.
