Skip to main content
KreupAI Logo
GLOSSARY GUIDEApplies to: UAERetailOS
KB-093

What Is EmaraTax? The FTA Portal, Its Scope and What SMBs File There

A clear definition of what is emaratax, including scope, purpose, components, obligations, common misunderstandings and operational system implications.

Author:Bosco Sabu John
11 min read

What Is EmaraTax? The FTA Portal, Its Scope and What SMBs File There

What Is EmaraTax? In practical terms, what is emaratax is a concept, institution, standard or platform that organisations must translate into owned data, controlled workflows and retrievable evidence. Its exact scope can vary by jurisdiction, activity and effective date. Verify current requirements with EmaraTax, FTA, distinguish the formal definition from common shorthand, and record the operational consequences in the relevant business system.

Definition at a glance

QuestionWorking answer
What is it?What Is EmaraTax? In practical terms, what is emaratax is a concept, institution, standard or platform that organisations must translate into owned data, controlled workflows and retrievable evidence. Its exact scope can vary by jurisdiction, activity and effective date. Verify current requirements with EmaraTax, FTA, distinguish the formal definition from common shorthand, and record the operational consequences in the relevant business system.
Who owns it internally?Assign the operational or compliance owner responsible for the underlying process and evidence.
What should the system hold?Authoritative master data, dated requirements, workflow status, approvals, exceptions and retrievable evidence.
What is the main mistake?Treating a general definition as a substitute for the current rule, standard, contract or operating context.

Use this definition as orientation. Verify current primary sources before making a regulated, financial, safety or certification decision.

Written for the owner or finance manager of a UAE SMB who has been told there is an e-invoicing deadline and cannot tell whether it applies this year or next. After reading it you should know which date binds you, what an Accredited Service Provider does, and which parts of your customer and item master will stop the onboarding. Every date, threshold and penalty below comes from the Ministry of Finance's own decisions, linked at the end; anything unconfirmed is flagged. Note that the Federal Tax Authority states on its own e-invoicing page that "the only official source of information related to the introduction of e-Invoicing in the UAE is the Ministry of Finance portal".

The model: five corners, and no portal to log into

The UAE has adopted what the Ministry of Finance calls a Decentralised Continuous Transaction Control and Exchange model, built on OpenPeppol. The Electronic Invoicing Guidelines set out the corners plainly: "Corner 1: Supplier; Corner 2: Supplier's ASP; Corner 3: Recipient's (buyer's) ASP; Corner 4: Recipient (buyer); Corner 5: Federal Tax Authority."

That is the whole architecture. You never talk to the FTA. Your accounting system talks to your service provider, which validates the data, converts it to XML, delivers it to the buyer's provider, and reports the tax data to the FTA in parallel. There is no portal where you key in an invoice, and no clearance step holding up the sale.

MoF defines an eInvoice as "a structured form of an invoice data that is issued and exchanged electronically between a supplier and a buyer and reported electronically to the UAE Federal Tax Authority", and states that PDF, Word documents, images, scanned copies and emails do not qualify. Documents are "issued, transmitted and received in XML format and will not feature a Quick Response Code ('QR code') or barcode", so if you have been through the Saudi rollout, unlearn the QR habit. Recipients must also process invoices through the system, so sitting on the buying side is not a way out.

What an Accredited Service Provider is, and why you cannot avoid one

An ASP is a company accredited by the Ministry of Finance under Ministerial Decision No. 64 of 2025 to operate corners 2 and 3 for you. Its obligations include the "exchange and reporting of Electronic Invoices including receiving confirmation messages" and "secure transmission of Electronic Invoices using encryption". It also generates "a UUID for every Electronic Invoice", so the document identity is created outside your ERP and has to be stored back into it.

Appointing one is a legal obligation with its own deadline, separate from go-live, and that distinction is the most common planning error. The appointment date sits months earlier on purpose: the ASP needs that window to onboard you, and every business in your revenue band is queuing for the same providers. MoF's ASP page currently lists 38 fully accredited providers and 12 more in final production assessment. Check it on the day you sign, not the day you shortlist.

Two lines from MoF's selection guidance are worth quoting into your procurement. On data residency: "Where is the Electronic Invoicing data stored? Locally within the UAE or overseas?" On commercial terms: "Ensure that the provision of 100 free Electronic Invoices per annum is included in the contractual terms." A proposal without that allowance came from someone who has not read the same guidance you have. Ministerial Resolution No. 56 of 2026 also let local companies partner with international providers for the underlying technology, so the entity on the contract and the entity running the access point may differ. Ask which is which.

The timeline, and the amendment that moved it

Ministerial Decision No. 244 of 2025 set the schedule. Ministerial Resolution No. 66 of 2026 replaced Article 5, paragraph (a), clause (1) of it, and only that clause.

CategoryAppoint ASP byImplement by
Pilot Programme participants (written agreement)n/aProgramme commences 1 July 2026
Person with Revenue ≥ AED 50,000,00030 October 2026 (was 31 July 2026)1 January 2027
Person with Revenue < AED 50,000,00031 March 20271 July 2027
Government Entity31 March 20271 October 2027

Most SMBs sit in the third row, which is less time than it looks, because providers will be absorbing the large-business wave until January 2027. Note how Revenue is defined: "the gross income earned by a Person during the most recent Accounting Period, based on the financial statements prepared in accordance with applicable legislation". Gross income, not taxable turnover, so a thin-margin trading business can clear AED 50 million while feeling nothing like a large enterprise.

[NEEDS SOURCE: whether the AED 50 million Revenue test in Ministerial Decision No. 244 of 2025 is applied per legal person or aggregated across a VAT group or commonly controlled entities.]

One live inconsistency: MoF's Guidelines V1.1, dated 1 June 2026, still print 31 July 2026 as the large-business ASP deadline, while Resolution No. 66 of 2026, issued 14 May 2026, sets 30 October 2026. The Resolution binds; the Guidelines explain.

What is in scope, and the exclusions that matter

Ministerial Decision No. 243 of 2025 applies the system to "any Person conducting Business in the State in respect of every Business Transaction" except where excluded, and this holds "regardless of whether they are established in the UAE". In scope: B2B, B2G, G2B and G2G. Out of scope for now: consumer transactions, exempted "until such time determined by a decision issued by the Minister". A pure B2C retailer is outside the mandate today and should assume that is temporary.

Article 4(1) excludes four things: transactions "conducted by Government Entities in a sovereign capacity, and which are not in competition with the private sector"; international passenger transport by an airline "where an Electronic Ticket is issued", plus ancillary services provided directly to passengers; international transport of goods by an airline "where an Airway Bill is issued", for 24 months; and "financial services that are exempt from VAT or subject to VAT at the zero rate", tied to Article 42 of the VAT Executive Regulation. A category of Excluded Persons will be set later. One grace period to diarise: intra-group transactions get "twenty-four (24) months commencing on 01 January 2027".

Six document categories exist: Electronic Tax Invoice, Electronic Tax Credit Note, Commercial Invoice, Electronic Credit Note, self-billed electronic Tax Invoice and self-billed electronic Tax Credit Note. Plus a line that catches project teams late: "There is no Electronic Invoice category for 'provisional invoices'. Every provisional invoice issued should be an Electronic Invoice." If your sales process runs pro-forma documents, decide now which are legally invoices.

Identifiers and the data dictionary

This is where SMB readiness projects live or die, because it is all master data.

The Tax Identification Number (TIN) is "a unique 10-digit identifier and the first 10 digits of the 15-digit TRN issued to all entities registered with FTA". Your Participant Identifier on the Peppol network is "0235 followed by the 10-digit TIN", where 0235 is the UAE scheme identifier and a fixed value in the seller block. Reserved endpoints cover the cases with no ordinary buyer to address: 0235: 9900000097 for deemed supply buyers, 0235: 9900000098 for buyers not onboarded, and 0235: 9900000099 for exports.

The mandatory field requirements document, version 1.0 dated 23 February 2026, groups fields into invoice details (invoice type code, transaction type code, business process type, specification identifier, payment means type code), seller details, buyer details, document totals, tax breakdown and line items. Two seller fields catch people out. The registration identifier needs a registration identifier type from a fixed list (TL, EID, PAS, CD), so "trade licence" has to be coded rather than free text. And every line needs a unit of measure code, which most SMB item masters hold as an uncontrolled string such as "pcs", "PC" or "each".

Retention is yours regardless of who stores it: "5 years following the Tax Period" for Taxable Persons, "5 years from the end of the calendar year" for others. An ASP "may store Electronic Invoices, Electronic Credit Notes and associated data on behalf of the Person", but the Person "remains ultimately responsible".

UAE, Saudi and Oman are three different machines

A GCC SMB selling across all three will hear "e-invoicing mandate" three times and be tempted to buy one answer. The models differ architecturally, not just in the fields.

UAESaudi Arabia (ZATCA)Oman (Fawtara)
ModelDecentralised CTC and Exchange, five corners, OpenPeppolCentralised: clearance for standard invoices, reporting within 24 hours for simplifiedFive corners, Oman Tax Authority as corner 5
What you must appoint or installA MoF Accredited Service Provider, mandatory, integrated to your systemNo intermediary. Onboard each invoicing unit (EGS) directly and obtain a Cryptographic Stamp IdentifierA "certified service provider or compatible ERP solution"
Format and QRPINT AE XML, no QR codeUBL 2.1 XML (or PDF/A-3 with XML embedded), QR mandatory, nine TLV tags in Phase 2[NEEDS SOURCE: format and QR requirement. The OTA portal says "approved formats" without naming a specification]
Mandate stagePilot 1 July 2026; ≥AED 50M live 1 January 2027; <AED 50M live 1 July 2027. B2C exempt for nowPhase 2 waves running. Wave 25 covers VAT-subject revenues above SAR 187,500, integration by 1 February 2027. B2C in scope, as simplified invoicesPhase 1 August 2026 (100 large VAT-registered companies); Phase 2 February 2027 (all large); Phase 3 August 2027 (all remaining VAT-registered)

The OTA states phase 4, for government entities, commences in February, without giving a year. [NEEDS SOURCE: the year of Fawtara phase 4, and B2C treatment under Fawtara.]

Your Saudi entity holds cryptographic keys and a counter chain that must survive restarts and restores; your UAE entity holds a contract and a clean customer master. Different problems, different failure modes, and a single "GCC compliance module" that treats them as one configuration is a claim to interrogate.

What a small business actually does first

None of this requires the mandate to have started, and all of it is work you will otherwise do under deadline pressure while your ASP waits.

  1. Establish which deadline binds you, on gross income from the most recent Accounting Period per your financial statements, not the VAT return. Record the calculation and the period used.
  2. Confirm your TRN and derive your TIN, the first 10 digits of it. Check against the FTA certificate, not a sales template carrying a typo from 2018.
  3. Validate every customer TRN for length, checksum and validity against the FTA's verification service. A B2B customer with a blank TRN cannot be addressed by participant identifier and falls to the non-onboarded endpoint.
  4. Split customers into B2B, B2G and B2C properly. Most SMB masters have one flag nobody has audited. B2C is out of scope today and in scope later, so the classification has to be real, not inferred from whether an address was captured.
  5. Fix the seller registration data. Hold the registration identifier and its type as a coded value from TL, EID, PAS or CD, and address line 1, city, country subdivision and country code AE as structured fields rather than one blob.
  6. Map every tax code to the tax category codes and rates the specification expects, including zero-rated, exempt and out-of-scope. Unmapped codes are the commonest cause of a failed first test transmission.
  7. Clean the item master and assign unit of measure codes, converting "pcs", "PC", "each" and "no." to the coded list. Start before the ASP asks: the deduplication argument inside your own business takes longer than the mapping.
  8. Inventory your documents. List everything you issue that behaves like an invoice, including pro-forma, provisional, delivery-linked billing, self-billed supplier arrangements and credit notes, and map each to one of the six categories.
  9. Shortlist and appoint an ASP on MoF's questions: data location, owned or resold platform, support, per-transaction pricing, and the 100 free electronic invoices per annum. Verify accreditation on the signing date.
  10. Onboard via EmaraTax, integrate, and test across your real document inventory rather than a sample of clean invoices. Agree in writing who notifies the Authority of a System Failure, and who holds the records.

What it costs to get this wrong

Cabinet Decision No. 106 of 2025 sets the administrative penalties.

ViolationPenalty
Failure by the Issuer to implement the Electronic Invoicing SystemAED 5,000 per month or part thereof
Failure to transmit an Electronic Invoice, or an Electronic Credit Note, on timeAED 100 each, capped at AED 5,000 per calendar month
Failure by the Issuer, or the Recipient, to notify the Authority of a System FailureAED 1,000 per day or part thereof
Failure by Issuer or Recipient to notify the Service Provider of data changesAED 1,000 per day or part thereof

Transmission failures are capped; notification failures are not. A change of trade licence details that never reaches the ASP accrues daily.

Where teams get this wrong

Treating the ASP appointment date as the project deadline. It is the date by which a contract must exist. Integration, master data cleanup and testing sit between it and go-live, and the ASP cannot start until you have signed.

Assuming the Saudi playbook transfers. Teams that ran a ZATCA project arrive expecting certificates, QR codes and a counter chain, and build capacity for the wrong problem. The UAE puts the cryptography and the UUID at the ASP; your work is data quality.

Leaving the customer master until the ASP asks. TRN validation surfaces duplicates, dissolved entities and free zone companies recorded under the wrong name. Each is a small commercial conversation, and the hours do not compress.

Forgetting the buying side. A Recipient who fails to notify a System Failure attracts the same AED 1,000 per day as an Issuer. Accounts payable has a project too.

What to automate, and what not to

Automate the mechanical parts: producing structured data from your sales documents, mapping tax codes and units of measure, validating TRNs on save rather than at month end, storing the ASP's UUID and confirmation against the invoice, and alerting when a confirmation does not arrive. A missing acknowledgement is invisible in the sales figures and is exactly what the per-invoice penalty is written for.

Do not automate the classification decisions. Whether a supply is a zero-rated financial service, whether a government counterparty acts in a sovereign capacity, and whether a document is a provisional invoice or an invoice are judgements with tax consequences, and a system that guesses produces documents that transmit cleanly and are still wrong. Notifying the Authority of a System Failure should be a person's decision with a timestamp, not a retry loop.

Where a system helps

The mandate does not ask your ERP to talk to a regulator. It asks your ERP to produce complete, correctly coded, structurally valid invoice data for every business transaction, and to keep the acknowledgement. That is where SMB systems are weakest: uncontrolled units of measure, tax codes accumulated over years, customers with no validated TRN, and no way to see that six invoices last Tuesday never came back confirmed. An ERP that validates TRNs and coded values at the point of entry, integrates once to your chosen ASP and reconciles confirmations against the sales ledger daily removes most of the work above. See RetailOS for SMB ERP.

FAQ

Do I need to appoint an ASP if I only sell to consumers? Not for those sales today. Decision 244 exempts business-to-consumer transactions "until such time determined by a decision issued by the Minister". If you issue any B2B or B2G invoice, that transaction is in scope and you need an ASP.

Can I connect my ERP directly to the FTA and skip the ASP? No. Everything routes through corners 2 and 3, which are accredited providers. The FTA is corner 5 and receives tax data from providers, not taxpayers.

My revenue is just under AED 50 million. Which deadline applies? On the face of Decision 244, appointment by 31 March 2027 and implementation by 1 July 2027, on gross income from the most recent Accounting Period. If you are close to the line or sit in a group structure, get the position confirmed rather than assumed.

What happens if my ASP has an outage? Notify the Authority of the System Failure. Cabinet Decision No. 106 of 2025 penalises failure to notify at AED 1,000 per day or part thereof, for Issuer and Recipient alike, with no cap. [NEEDS SOURCE: the prescribed method and time limit for notifying the FTA of a System Failure, and whether transmission deadlines are suspended during one.]

Related reading: KB-093 and KB-094.

Sources