Skip to content

Insights E-Invoicing

UAE E-Invoicing Go-Live on 1 January 2027: The Checklist for Businesses at AED 50M and Above

The UAE e-invoicing go-live on 1 January 2027 for businesses at or above AED 50m revenue — the official readiness checklist, the ASP steps and what changed.

UAE E-Invoicing Go-Live on 1 January 2027: The Checklist for Businesses at AED 50M and Above
UAE E-Invoicing Go-Live on 1 January 2027: The Checklist for Businesses at AED 50M and Above Photo: Velmont Crest Editorial

Key takeaways

  1. Go-live is 1 January 2027 for any Person whose Revenue is equal to or exceeds AED 50,000,000
  2. Revenue means gross income in the most recent Accounting Period, taken from the financial statements
  3. The ASP appointment deadline was 30 October 2026 in the amending decision; the MoF Guidelines table prints 31 October 2026
  4. Onboarding is initiated by the business through EmaraTax, not by the service provider
  5. Each Tax Group member onboards separately on its own TIN, even though intra-group transactions are excluded for 24 months from 1 January 2027
  6. Newly established companies get no phase-in — an ASP must be in place before the first invoice

The UAE e-invoicing go-live on 1 January 2027 is the point at which the mandate stops being a planning exercise. Businesses at or above AED 50 million of revenue were required to have an Accredited Service Provider appointed by the end of October 2026, and from 1 January 2027 every invoice those businesses issue in scope has to be a structured Electronic Invoice moving through the Peppol-based network — not a PDF, and not a print from the accounting system.

This guide is written for that first cohort and for their finance teams. Every date, amount and article reference below comes from the Ministerial and Cabinet Decisions themselves, or from the Ministry of Finance’s own October 2026 guidance, and each is cited so you can check it.

The direct answer: businesses whose Revenue is equal to or exceeds AED 50,000,000 must implement the UAE Electronic Invoicing System by 1 January 2027, under Article 5(1)(a) of Ministerial Decision No. 244 of 2025 as replaced by Ministerial Decision No. 66 of 2026. Revenue means gross income in the most recent Accounting Period per the financial statements. The service-provider appointment deadline has already passed.

Who the 1 January 2027 go-live actually catches

Scope and timing are set by two different instruments, and conflating them is the most common planning error we see.

Scope sits in Ministerial Decision No. 243 of 2025. Article 3 applies the Decision to “any Person conducting Business in the State in respect of every Business Transaction”, except where the Person or the transaction is excluded under Article 4. The Ministry of Finance’s UAE Electronic Invoicing Guidelines put the consequence bluntly in their own highlights: Electronic Invoicing is mandatory for any Person conducting Business in the UAE regardless of their VAT registration status, unless specifically excluded.

Timing sits in Ministerial Decision No. 244 of 2025. Article 5(1) phases implementation by Revenue, and paragraph (a) — the one that governs this cohort — was replaced in full by Ministerial Decision No. 66 of 2026.

So a business can be squarely in scope under MD 243 and still have months of runway under MD 244 — or, in this cohort’s case, days.

InstrumentWhat it decidesWhat it does not decide
Ministerial Decision No. 243 of 2025 (as amended by MD 197 of 2026)Who is in scope, what is excluded, the issue-and-transmit obligations, data fields, storageWhen you go live
Ministerial Decision No. 244 of 2025 (as amended by MD 66 of 2026)The pilot, the voluntary window, and the phased mandatory dates by RevenueWhat an invoice must contain
Ministerial Decision No. 168 of 2026Accreditation of service providersYour own compliance deadline
Cabinet Decision No. 173 of 2026Violations and administrative penaltiesScope or timing

How the AED 50 million test is measured

This is where businesses with a borderline position most often get the answer wrong, because “revenue” in ordinary speech and “Revenue” in the Decision are not the same thing.

Article 1 of MD 244 of 2025 defines Revenue as “the gross income earned by a Person during the most recent Accounting Period, based on the financial statements prepared in accordance with applicable legislation in the State or, if such financial statements are not available, based on other documentation acceptable to the Authority”. The same article defines Accounting Period as “the period for which the Person is required to prepare financial statements, in accordance with the applicable legislation in the State”.

Three practical consequences follow.

QuestionWhat the definition gives you
Which figure?Gross income from the financial statements — not taxable supplies, not VAT-return turnover, not management accounts
Which period?The most recent Accounting Period, i.e. your last statutory financial-statement period
No statements?Other documentation acceptable to the Federal Tax Authority — so the fallback is discretionary, not a free pass
Does the B2C carve-out reduce the figure?No. Article 5(2) removes Business-to-Consumer transactions from the system’s scope; it does not carve them out of the Revenue test

If your last financial statements show gross income at or above AED 50,000,000, you are in the first wave, even if a large share of that income comes from consumer sales that are not themselves in scope. That asymmetry catches retail and hospitality groups in particular, and it is a good reason to have the figure agreed with whoever prepares your financial statements for corporate tax purposes rather than estimated by the finance team in a meeting.

The phased timeline, and a one-day discrepancy worth knowing about

Here is the full phasing from Article 5(1) of MD 244 of 2025, with paragraph (a) in its replaced form.

PhaseWhoAppoint an ASP byImplement by
(a)Person with Revenue at or above AED 50,000,00030 October 20261 January 2027
(b)Person with Revenue below AED 50,000,00031 March 20271 July 2027
(c)Government Entity31 March 20271 October 2027
(d)Any remaining Person or Government Entity in scope, once (a) to (c) are completeOn appointment being requiredOn implementation being required

One point of honesty about the official paperwork. The binding wording in Article One of MD 66 of 2026 is “shall appoint an Accredited Service Provider by 30 October 2026”. The Ministry of Finance’s own UAE Electronic Invoicing Guidelines, version 2.0 dated 26 October 2026, print a table in chapter 8.3 giving the last date to appoint a provider for this cohort as 31 October 2026. The two documents differ by a day.

We did not find that discrepancy flagged in any of the published commentary we checked, and we are not going to resolve it for you: the Ministerial Decision is the legal instrument and 30 October 2026 is the date we would work from, while noting that the Ministry’s guidance says otherwise. Both dates are now in the past, so nothing turns on it for the appointment itself — but if you are reconstructing a compliance timeline for an auditor or a board paper, cite the Decision and footnote the Guidelines rather than picking one silently.

Two earlier dates matter for context. Article 3(4) of MD 244 of 2025 commenced the Pilot Programme on 1 July 2026, with participation only by written agreement under Article 3(2). Article 4 opened voluntary implementation to any Person from the same date. The wider UAE e-invoicing mandate covers how those phases fit together; businesses below the threshold should read the Phase 2 readiness plan instead of this one.

If you missed the ASP appointment deadline

Appoint a provider now, document the date, and treat the remaining time as a testing problem rather than a procurement problem.

Row 1 of the table annexed to Cabinet Decision No. 173 of 2026 covers failure by the issuer or the recipient to implement the system in accordance with MD 244 of 2025, “including the failure to appoint an Accredited Service Provider”. The charge is AED 5,000 for the first instance, plus AED 5,000 for each month or part of a month during which the non-compliance continues, with total fines capped at AED 50,000 in any period of 12 consecutive months.

The fine is the smaller problem. The sequence that has to happen before 1 January — contract, EmaraTax onboarding, participant identifier, system integration, end-to-end testing, governance for error handling — is the real constraint, and the last two steps are the ones that cannot be rushed without consequences in your January billing run.

The Ministry’s own readiness checklist

Appendix 2 of the UAE Electronic Invoicing Guidelines sets out what the Ministry describes as a high-level indicative readiness checklist. It is the closest thing to an official go-live gate, and it is worth running as a formal sign-off rather than a reading exercise. Restated:

#Checklist item (per MoF Guidelines, Appendix 2)
1Understood MD 243 of 2025 and its amendments, plus the related changes in the VAT Decree-Law, VAT Executive Regulation and Tax Procedures Law
2Identified your own go-live date under the phased plan in MD 244 of 2025 and its amendments
3Reviewed the administrative penalties in CD 173 of 2026
4Identified the data points required on an Electronic Invoice and confirmed your accounting/ERP system can extract them
5Selected a provider and completed all contractual and commercial obligations
6Created a profile on the provider’s system
7Registered with the FTA and created your TIN if you do not already have one
8Completed onboarding with your provider via EmaraTax
9Obtained a Peppol participant identifier via your provider
10Agreed how invoice data will be transmitted to and from your provider
11Agreed how you will receive confirmation messages on exchange and reporting
12Agreed data hosting and data security requirements
13Completed the changes to your ERP/accounting applications to generate the required data points
14Completed the integrations between those applications and your provider’s systems
15Completed testing of Electronic Invoice exchange and reporting with your provider
16Established a governance model with the provider for resolving errors
17Confirmed you are ready to go live per the roll-out plan

Items 4, 13 and 14 are where most of the elapsed time goes, and all three are accounting-data problems dressed as IT problems. If your customer master has no TIN for a third of your UAE business customers, items 13 to 15 will stall regardless of how good the provider is.

What changed in the rules on 1 October 2026

Anyone who built a 2027 plan from the 2025 decisions is working from superseded text. Two instruments took effect on 1 October 2026 — MD 168 of 2026 on accreditation, and the amending decision that matters most here. Ministerial Decision No. 197 of 2026 rewrote parts of the core obligation set.

ProvisionPosition under MD 243 of 2025 as issuedPosition from 1 October 2026
Art. 6(5) transmission deadlineWithin 14 days from the Date of Business TransactionWithin fourteen (14) Business Days from the Date of Business Transaction
Art. 4(1) exclusionsNo Tax Group exclusionNew paragraph (f): transactions between members of the same Tax Group excluded for 24 months starting 1 January 2027; the old (f) becomes (g)
Art. 11 storageStore all data within the State per the Tax Procedures Law timelineRetain the data for the period prescribed under the Tax Procedures Law and ensure it can be produced to the FTA on request — the in-State requirement is gone
Art. 12 system failureIssuer and recipient to notify the FTA within 2 Business DaysRepealed outright by Article Three of MD 197 of 2026
Definition of “System Failure”Defined in Art. 1Deleted
Accredited Service Provider definitionTied to MD 64 of 2025A provider granted Accreditation under the legislation regulating the system — MD 64 of 2025 having been repealed by MD 168 of 2026

The shift from 14 days to 14 Business Days reads like a relaxation and in isolation it is. It is not one in practice for VAT-registered issuers, for the reason set out further below.

Step 1: understand the rules, then size the gap

Appendix 1 of the Guidelines frames the first step as understanding the changes across the Tax Procedures Law, the VAT Decree-Law and the VAT Executive Regulation, then carrying out a gap analysis “of the requirements against its activities” to work out which categories of Electronic Invoice each transaction type needs and which data points those invoices require.

In practice that means producing three documents before anyone touches a system:

  • A transaction inventory — every revenue stream, each tagged to an invoice category and a tax treatment.
  • A field-level gap list — the required data points against what your ERP can actually extract today.
  • A master-data remediation list — missing buyer TINs, duplicate customer records, inconsistent trade-licence details.

The field requirements themselves sit in the Peppol PINT-AE billing specifications, and the Ministry has published a separate mandatory-field document alongside the Guidelines. Our walkthrough of mapping a UAE chart of accounts to the PINT-AE fields covers the accounting side of that exercise, and the Peppol network explainer covers how a document physically moves once it leaves your system.

Two field-level points from the Guidelines are worth flagging now because they surprise people in testing. HSN codes are currently optional, with the timeline for making them mandatory to be announced. And the name of the trade-licence issuing authority has to be populated manually by the issuer in the “Authority Name” field, with no code list provided.

Step 2: appoint a provider and onboard through EmaraTax

The Guidelines are specific that the onboarding process “should be initiated by the Person or Government Entity (not the ASP) via EmaraTax”. The sequence they describe:

  1. Finalise the contract and commercial obligations with the chosen provider.
  2. The account admin of the Taxable Person initiates onboarding in EmaraTax.
  3. Open the E-INVOICING tile to view the list of providers, select yours, and proceed to that provider’s portal.
  4. Obtain a Peppol participant identifier via the provider.
  5. If the business is not registered and not required to register with the FTA for tax purposes, generate a TIN through EmaraTax first.

Two constraints sit inside that list. The Guidelines state that each Person or Government Entity should onboard with only one provider for all of their Electronic Invoicing requirements. And the identifier is not something you choose: it is your TIN, which the Guidelines describe as the first 10 digits of your 15-digit TRN.

Under the five-corner model the Guidelines set out, you are corner 1 as supplier, your provider is corner 2, your customer’s provider is corner 3, your customer is corner 4, and the Federal Tax Authority is corner 5. You never connect to the FTA directly — Article 6(7) of MD 243 of 2025 says the issuer and recipient fulfil their obligations through the appointment of an Accredited Service Provider.

What to ask a provider before you sign

The Ministry published a separate document, Considerations for Selecting an Accredited Service Provider, version 1.1 dated 28 October 2026. It is a question set rather than a ranking, and it is the right basis for a procurement scorecard.

AreaQuestions the MoF document raises
ExperienceHow long providing e-invoicing services; how long as a Peppol Service Provider; how long operating in the UAE; the accreditation date
Geographical reachWhich countries the provider serves; which Emirate it is based in
Product ownershipWhether the platform is its own product or a third party’s; whether support is in-house or sub-contracted; what value-added services come with it
IntegrationWhether it integrates with your current ERP, accounting or invoicing systems — APIs, data formats, integration support
RetentionWhat arrangements exist for retaining invoice and credit-note data for the Tax Procedures Law period and producing it to the FTA on request
Compliance and securityWhich certifications it holds; encryption, access controls and incident response
Support and SLAsSupport response times; defined SLAs for uptime and availability
PricingSubscription versus per-transaction; hidden or additional costs
ScalabilityHow the system scales; the roadmap for future enhancements

One commercial fact from that document is worth knowing before you negotiate. It states that under Ministerial Decision No. 168 of 2026, Accredited Service Providers are required to provide 100 free e-invoice exchange and reporting services per annum to each end-user, commencing from the date of signature of each end-user agreement. Reading MD 168 of 2026 itself, that sits in the self-declaration a provider submits as an eligibility condition: it declares that it “is committed to providing (100) one hundred free eInvoice exchange and reporting services per annum to each End-User, commencing from the date of the signature of each End-User agreement”. For a high-volume business it is immaterial; for a small entity inside a larger group it is not.

Also check accreditation status rather than reputation. MD 168 of 2026 repealed MD 64 of 2025 and its amendments and replaced pre-approval with direct accreditation, and the Ministry publishes the register — Article 5(2) of MD 243 of 2025 makes the list of Accredited Service Providers something the Ministry publishes, so verify your shortlist on the Ministry’s e-invoicing pages on the day you sign rather than relying on a list reproduced in any article, this one included.

Step 3: test exchange and reporting end to end

Appendix 1 of the Guidelines lists six paths that need testing, and they are not symmetrical — half of them are inbound, which is the half most projects under-test because the finance team thinks of e-invoicing as something it does to customers.

#Path to test
1Transmitting invoice data to the provider
2The provider issuing the invoice to the buyer
3Receiving the confirmation message from the provider on success or failure of the exchange
4Receiving an Electronic Invoice from the provider that a supplier has issued to you
5The provider reporting the required Tax Data to the FTA
6Receiving the confirmation message from the provider on success or failure of the Tax Data reporting

Paths 4 and 6 deserve particular attention. Article 6(3) of MD 243 of 2025 requires the recipient to process Electronic Invoices and Electronic Credit Notes through the system — a standing obligation on the buying side, enforceable in its own right. Row 1(b) of the table annexed to CD 173 of 2026 reaches a recipient that implemented the system and then failed to maintain compliance with its recipient obligations. Accounts payable is therefore in scope for go-live testing, not just accounts receivable. Businesses running outsourced accounts payable and receivable processes should confirm who owns the inbound confirmation checks before January.

Testing should also cover credit notes rather than invoices alone. Article 6(2) requires an Electronic Credit Note where the transaction is cancelled, where the agreed consideration is reduced for any reason, where consideration is returned in full or in part, and where an administrative or numerical error has occurred. That last case means routine billing corrections now generate structured documents.

Step 4: go live, with a governance model attached

The Guidelines ask for a governance model agreed with the provider before go-live on how errors arising during and after go-live will be resolved, then for the business to commence exchange and reporting per the roll-out plan and monitor for issues, working with the provider on timely resolution.

Our view of what that governance model has to contain to be useful, in accounting terms:

  • A named owner for transmission failures, with an agreed response window.
  • A daily exception report in the first month, dropping to weekly once the error rate stabilises.
  • A monthly reconciliation of invoices issued in the ledger against invoices confirmed as transmitted and reported.
  • A documented procedure for the case where an invoice is rejected after the customer has already received the goods.

That last item is where January revenue gets stuck. Appendix 4 of the Guidelines requires providers to ensure that Persons are informed, on an event-driven basis and without undue delay, that Electronic Invoices or Tax Data Documents have been successfully transmitted to the Authority. Those confirmations are the evidence base for your monthly control, so make sure they land somewhere a person actually reviews rather than in an unmonitored mailbox.

There is also a standing obligation that outlives go-live. Article 5(3) of MD 243 of 2025 requires the issuer and recipient to notify the appointed provider in writing of any change to the data registered with the FTA under Article 6(4) of Cabinet Decision No. 74 of 2023, within five Business Days of receiving the FTA’s confirmation of the amendment. The Guidelines add that changes of circumstance — registering for VAT, joining or leaving a Tax Group, deregistering, closing the business — should be put through EmaraTax using the reverification or offboarding processes. Row 4 of the CD 173 of 2026 table charges AED 250 for each day of delay, capped at AED 5,000 per calendar month, for failing to notify the provider of changes to registered data.

The 14-Business-Day clock, and the VAT deadline that can override it

Article 6(5) of MD 243 of 2025, in its replaced form, requires the Electronic Invoice or Electronic Credit Note to be issued and transmitted through the system within fourteen Business Days from the Date of Business Transaction. That is a genuine easing from the original fourteen calendar days.

The clause is expressly “subject to Clause 4 of this Article”, and Article 6(4) provides that where the issuer is a Registrant, it shall issue and transmit the Electronic Invoice and the Electronic Credit Note within the timeline prescribed by the VAT Law. For a VAT-registered business, therefore, the VAT Law’s own tax-invoice timeline continues to govern, and the fourteen Business Days is the outer boundary rather than the working deadline. If your current practice is to issue tax invoices right at the VAT deadline, e-invoicing removes the informal slack you may have been relying on, because transmission now has to complete inside the same window. Our guide to tax invoice requirements in the UAE sets out the invoice-level rules those deadlines attach to, and the 2026 tax invoice format guide covers the content side.

Tax groups: excluded invoices, individual onboarding

The new Article 4(1)(f) exclusion is one of the most useful changes of October 2026 for groups, and one of the easiest to over-read. What it excludes is “Business Transactions carried out between Persons who are members of the same Tax Group, for a period of twenty-four (24) months starting from 1 January 2027”.

What it does not do:

AssumptionPosition under the Guidelines and MD 197 of 2026
”Our group only needs one onboarding”No. Each member of a Tax Group needs to be onboarded, each with its own TIN generating its own participant identifier
”The group representative’s TRN is our identifier”No. Your TIN is the first 10 digits of your own TRN, not the representative’s
”All members must use the same provider”No. The Guidelines state group members may each onboard with a different provider
”Intra-group invoicing is excluded permanently”No. The exclusion runs 24 months from 1 January 2027
”Third-party invoices by group members are excluded too”No. The exclusion covers transactions between members of the same Tax Group only

Groups that read the exclusion as a two-year reprieve from the whole mandate will discover otherwise in January, because their external invoicing is unaffected by it. Our note on VAT group invoicing under e-invoicing goes through the document flow in more detail.

Newly established companies get no phase-in

This provision deserves its own section because it inverts the phasing logic people have internalised. Chapter 8.4 of the Guidelines states that Persons newly established and within the scope of Electronic Invoicing are required to appoint a provider and complete the onboarding process before issuing their first invoice, irrespective of their date of establishment, and that any invoice issued must be a compliant Electronic Invoice.

A company incorporated in the UAE in 2027 therefore cannot invoice on PDFs while it waits to cross a revenue threshold — the threshold phasing is not available to it. For anyone planning a new UAE entity — a new group company, a free-zone subsidiary, a restructuring vehicle — provider selection now belongs on the incorporation checklist next to the trade licence, the TRN and the bank account, and the first invoice cannot be raised until onboarding is finished.

Invoice categories to map before go-live

Chapter 10 of the Guidelines sets out six categories of Electronic Invoice. Mapping each revenue stream to one of them is step 4 of the readiness checklist in concrete form.

Document typeStandard billingSelf-billing
Tax InvoiceElectronic Tax InvoiceSelf-billed electronic Tax Invoice
Tax Credit NoteElectronic Tax Credit NoteSelf-billed electronic Tax Credit Note
InvoiceCommercial InvoiceNot applicable
Credit noteElectronic Credit NoteNot applicable

A Commercial Invoice is the term for an invoice issued for sales that do not require a Tax Invoice under the VAT Decree-Law. Self-billing is permitted under Article 9 of MD 243 of 2025 where both recipient and issuer are Registrants, subject to the conditions in the VAT Executive Regulation — the five self-billing conditions are worth checking before you assume your existing arrangement carries over. Article 8 separately allows an agent acting on behalf of a principal to issue and transmit through the system on the principal’s behalf.

One clarification in the Guidelines closes a gap that many businesses have been relying on: there is no Electronic Invoice category for provisional invoices. Every provisional invoice issued should be an Electronic Invoice, with adjustments handled by issuing either an Electronic Credit Note or an additional Electronic Invoice. If your billing process leans on pro-forma or provisional documents, that process needs rewriting before January. Summary invoices have their own treatment.

Advance payments and retentions

Appendix 5 of the Guidelines addresses a scenario that affects construction, contracting and any business billing against milestones.

Where an advance payment is received, a tax invoice must be issued at the time of receipt. The final invoice should then cover only the remaining balance amount, not the full contract value, because a tax invoice has already been issued for the advance. A reference to the original invoice may be included under IBT-25 and IBT-26, or a note provided in IBT-022, and the Guidelines state that the cbc:PrepaidAmount field may be left blank since the later invoice already reflects only the outstanding amount.

The worked example in the Guidelines uses a contract of AED 10,000 plus 5% VAT with an advance of AED 1,000 plus 5% VAT: the advance invoice carries AED 1,000 net and AED 50 of VAT, and the final invoice carries AED 9,000 net and AED 450 of VAT, referencing the advance invoice.

Where an advance relates to specific invoice lines, the Guidelines require it to be allocated to those lines; where it relates to the transaction as a whole, buyer and seller may agree the allocation across lines, provided the allocation is reasonable, consistently applied, supported by the commercial arrangement, and does not alter the VAT treatment of the underlying supply. That is an accounting-policy decision to settle before go-live, not an invoice-by-invoice judgement call.

Storage and retention after go-live

Article 11 of MD 243 of 2025, in its replaced form, requires any Person subject to the system to retain all Electronic Invoices, Electronic Credit Notes and any associated data for the period prescribed under the Tax Procedures Law, and to ensure such records are capable of being produced to the Authority on request.

Appendix 4 of the Guidelines then clarifies four points that matter for how you contract with your provider.

PointWhat the Guidelines say
DelegationUsing a provider for storage is permissible where contractually agreed, but does not transfer the legal obligation under Article 11; the Person remains ultimately responsible
Storage layerNo requirement that storage occur at a specific system layer, including C1/C4, provided retention period, integrity, security and availability to the FTA are preserved
Provider logsProviders retain transactional logs with unique transaction identifiers covering the end-to-end exchange and reporting cycle; these are the provider’s obligation and are not the business-document data you must retain
ConfirmationsProviders must inform Persons, on an event-driven basis and without undue delay, of successful transmission to the Authority

On the retention period itself, the obligation points to the Tax Procedures Law rather than naming a number. The underlying periods are the ones you already run to — five years for VAT and accounting records under Article 3(1)(a) of the Tax Procedures Executive Regulation, Cabinet Decision No. 74 of 2023 as amended by Cabinet Decision No. 17 of 2026, and seven years for corporate tax records under Article 56 of Federal Decree-Law No. 47 of 2022. Our guide to financial record keeping in the UAE sets out how those windows interact; confirm the applicable period for your own position before you configure an archive policy around it.

What the penalties are, and what they are not

The schedule is annexed to Cabinet Decision No. 173 of 2026, which repealed Cabinet Decision No. 106 of 2025 in full under its Article 4. Four rows, read from the Decision’s own table:

#ViolationPenalty
1(a) Failure by the issuer or the recipient to implement the system per MD 244 of 2025 and its amendments, including failure to appoint an ASP; (b) failure by a recipient that implemented under (a) to then maintain compliance with its recipient obligations under MD 243 of 2025 and its amendmentsAED 5,000 for the first instance of (a) or (b) or both, plus AED 5,000 for each month or part thereof that the non-compliance continues, total fines not to exceed AED 50,000 in any period of 12 consecutive months
2Failure by the issuer to issue and transmit an Electronic Invoice to the recipient through the systemAED 100 per Electronic Invoice, maximum AED 5,000 per calendar month
3Failure by the issuer to issue and transmit an Electronic Credit Note to the recipient through the systemAED 100 per Electronic Credit Note, maximum AED 5,000 per calendar month
4Failure by the issuer or the recipient to notify the appointed provider of changes to the data registered with the AuthorityAED 250 for each day of delay or part thereof, maximum AED 5,000 per calendar month

Three readings to correct, because we have seen all three in circulation.

The per-document penalties are capped. Rows 2 and 3 each stop at AED 5,000 per calendar month. A claim that a repeated error across hundreds of invoices produces hundreds of uncapped fines does not match the table. The caps are separate from each other, so a bad month can reach AED 10,000 across both rows — but it does not scale with volume beyond that.

The voluntary phase is penalty-free. Article 2(2) states the Decision does not apply to a Person who issues, transmits, shares, exchanges or reports on a voluntary basis, and the Guidelines confirm that penalties apply only from the date mandatory implementation is required.

Acting as both issuer and recipient does not double the charge. Article 3(2) provides that where the same Person acts as issuer, recipient, or both in respect of the same violation, only one administrative penalty is imposed for that violation under the Decision.

Worth noting what left the schedule. The two rows under CD 106 of 2025 that charged AED 1,000 per day for failing to notify the FTA of a system failure are gone, consistent with Article 12 of MD 243 of 2025 having been repealed. The provider data-change rate fell from AED 1,000 to AED 250 per day and gained a monthly cap it did not previously have.

Separately, these e-invoicing penalties do not displace the ordinary tax penalty regime. The Guidelines point to Cabinet Decision No. 40 of 2017 and its amendments for administrative penalties relating to the VAT Decree-Law and the Tax Procedures Law, which is where failures to issue or maintain compliant tax invoices are dealt with. The wider UAE tax penalties position for 2026 and the VAT return filing deadlines and penalties both sit alongside this schedule rather than inside it.

What go-live changes in the monthly close

For the finance function, 1 January 2027 changes three routines permanently.

Revenue cut-off becomes evidenced externally. Until now, the invoice date in your ledger was effectively self-declared. From go-live, each in-scope invoice carries a transmission and reporting trail through your provider to the FTA, so the cut-off in your books is corroborated by data the FTA holds. Period-end revenue adjustments that previously lived quietly in a journal will now need to match a structured document.

A new reconciliation joins the close. Invoices raised, invoices transmitted, and invoices confirmed as reported should agree every month, with differences explained. That is a control to add to your close checklist, and it is the single most useful thing a finance team can put in place in the first quarter of live running. Our monthly bookkeeping service is where we build that reconciliation into the close.

VAT and corporate tax become harder to tell different stories about. The FTA is given power under Article 10 of MD 243 of 2025 to access and use any data processed, received and stored under the system, and Appendix 3 of the Guidelines lists data analysis for tax audits and fraud detection among the Authority’s roles. Structured invoice data that does not reconcile to your VAT returns or your corporate tax filing is now visible without an audit being opened.

Where businesses are getting this wrong

The recurring failures we see in UAE e-invoicing projects, in rough order of how much January pain they cause:

  • Treating the mandate as an IT project. The binding constraints are master data, tax codes and invoice categories — all accounting deliverables.
  • Testing outbound only. Recipient obligations under Article 6(3) and row 1(b) of the penalty table are real, and accounts payable is usually the least prepared function.
  • Assuming the Tax Group exclusion covers everything. It covers intra-group transactions for 24 months from 1 January 2027, and nothing else.
  • Reading 14 Business Days as the operative deadline while VAT-registered, when Article 6(4) points back to the VAT Law timeline.
  • Relying on provisional or pro-forma documents that no longer have a category.
  • Assuming the provider carries the compliance obligation. Appendix 4 of the Guidelines says delegation does not transfer it.
  • Letting transmission confirmations land in an unmonitored mailbox, so a failed invoice is discovered by a customer rather than by finance.
  • Working from the 2025 decisions without the October 2026 amendments.

How Velmont Crest helps

We are not an Accredited Service Provider and we will not become one. Our role on an e-invoicing programme sits on your side of the table: reading the decisions as they change, sizing the gap between what the rules require and what your accounting system can produce, cleaning the master data that determines whether your invoices pass validation, shortlisting providers against the Ministry’s own selection criteria, and building the monthly reconciliation that keeps the position defensible after go-live.

For businesses in the 1 January 2027 cohort, the useful work left is testing, master data and governance. For everyone below the AED 50 million line, the 1 July 2027 date arrives with its own appointment deadline in March 2027, and the preparation is the same work on a longer runway. Our e-invoicing setup advisory service covers both, and sits alongside the audit support your auditor will want once a full year of structured invoice data exists.

If you want a view on where your own books stand against the mandate, get a free quote.

Sources

Primary instruments and official guidance used for this article, all read in November 2026:

Rules and official guidance in this area have changed repeatedly through 2026. Confirm the current position on the Ministry of Finance e-invoicing pages before acting on any date or amount in this article.

Frequently asked questions

When does UAE e-invoicing become mandatory for large businesses?
On 1 January 2027. Article 5(1)(a) of Ministerial Decision No. 244 of 2025, as replaced by Article One of Ministerial Decision No. 66 of 2026, reads that a Person subject to the Electronic Invoicing System whose Revenue is equal to or exceeds AED 50,000,000 "shall appoint an Accredited Service Provider by 30 October 2026 and shall implement the Electronic Invoicing System by 1 January 2027". The go-live date has not moved since the original decision was issued in 2025, even though the service-provider appointment deadline was extended once.
How is the AED 50 million threshold measured?
On gross income, not on taxable supplies. Article 1 of Ministerial Decision No. 244 of 2025 defines Revenue as "the gross income earned by a Person during the most recent Accounting Period, based on the financial statements prepared in accordance with applicable legislation in the State or, if such financial statements are not available, based on other documentation acceptable to the Authority". Accounting Period is defined in the same article as the period for which the Person is required to prepare financial statements. So the test runs off your last set of financial statements, and it is not limited to the transactions that are themselves in scope for e-invoicing.
I missed the 30 October 2026 ASP deadline. What now?
Appoint one immediately and keep the evidence of when you did it. Failing to implement the system in accordance with Ministerial Decision No. 244 of 2025, including failure to appoint an Accredited Service Provider, is the first row of the table annexed to Cabinet Decision No. 173 of 2026. It carries AED 5,000 for the first instance and AED 5,000 for each month or part of a month that the non-compliance continues, with total fines capped at AED 50,000 in any period of 12 consecutive months. The separate and larger risk is that onboarding, integration and testing cannot be compressed into the days before 1 January 2027.
Does e-invoicing apply if my business is not registered for VAT?
Yes. The Ministry of Finance's UAE Electronic Invoicing Guidelines state that Electronic Invoicing is mandatory for any Person conducting Business in the UAE regardless of their VAT registration status, unless specifically excluded under Article 4 of Ministerial Decision No. 243 of 2025 and its amendments. A business in scope that is not required to register with the Federal Tax Authority for any tax type still has to register in order to obtain a Tax Identification Number, because the TIN becomes its Peppol participant identifier.
What is my participant identifier for UAE e-invoicing?
Your Tax Identification Number. The Ministry of Finance Guidelines state that the TIN is the first 10 digits of the 15-digit Tax Registration Number already issued to entities registered with the Federal Tax Authority, and that this TIN is used to generate your Peppol participant identifier. One trap is called out in the Guidelines specifically: if you are part of a Tax Group, your TIN is the first 10 digits of your own TRN, not the first 10 digits of the Tax Group representative's TRN.
Are transactions between Tax Group members in scope?
Not for the next two years. Ministerial Decision No. 197 of 2026 added a new paragraph (f) to Article 4(1) of Ministerial Decision No. 243 of 2025, excluding "Business Transactions carried out between Persons who are members of the same Tax Group, for a period of twenty-four (24) months starting from 1 January 2027". The exclusion covers the invoices, not the onboarding. The Guidelines are explicit that each member of a Tax Group still needs to be onboarded, each on its own TIN and its own participant identifier, and that group members may onboard with different service providers.
How long do I have to transmit an electronic invoice?
Fourteen Business Days, and possibly less. Article 6(5) of Ministerial Decision No. 243 of 2025, as replaced by Ministerial Decision No. 197 of 2026 with effect from 1 October 2026, requires the Electronic Invoice or Electronic Credit Note to be issued and transmitted through the system "within fourteen (14) Business Days from the Date of Business Transaction". That clause is expressly subject to Article 6(4), which requires a VAT-registered issuer to issue and transmit within the timeline prescribed by the VAT Law. Where the VAT deadline is shorter, the VAT deadline governs.
Do I still have to store invoice data inside the UAE?
No, not since 1 October 2026. The original Article 11 of Ministerial Decision No. 243 of 2025 required storage "within the State". Ministerial Decision No. 197 of 2026 replaced it with an obligation to retain all Electronic Invoices, Electronic Credit Notes and associated data for the period prescribed under the Tax Procedures Law and to ensure the records are capable of being produced to the Authority on request. The Ministry's Guidelines add that there is no requirement for storage to occur at a specific system layer, and that delegating storage to a service provider does not transfer the legal obligation.
Can my service provider take over the compliance obligation?
No. Appendix 4 of the UAE Electronic Invoicing Guidelines states that use of an Accredited Service Provider for storage purposes is permissible where agreed contractually, but that such delegation does not transfer the legal obligation under Article 11, and that the Person remains ultimately responsible for compliance with retention requirements. The same logic runs through the rest of the framework — Article 6(7) of Ministerial Decision No. 243 of 2025 says you fulfil your obligations through the appointment of a provider, which is a delivery mechanism, not a transfer of liability.
Is an invoice penalty charged per invoice without limit?
No, and this is a common misreading. Rows 2 and 3 of the table annexed to Cabinet Decision No. 173 of 2026 charge AED 100 for each Electronic Invoice, and AED 100 for each Electronic Credit Note, that the issuer fails to issue and transmit through the system — but each row is capped at AED 5,000 per calendar month. The two caps are separate, so a month with both failures can reach AED 10,000. Claims that a single error replicated across hundreds of invoices produces hundreds of uncapped penalties do not match the Decision's own table.
Do penalties apply during the voluntary phase?
No. Article 2(2) of Cabinet Decision No. 173 of 2026 states that the Decision does not apply to a Person who issues, transmits, shares, exchanges or reports on a voluntary basis. The Ministry's Guidelines say the same thing in plainer terms, noting that administrative penalties apply only from the date a Person is required to implement Electronic Invoicing on a mandatory basis. For the AED 50 million cohort, that date is 1 January 2027.
What happens to a newly incorporated company in 2027?
It gets no phase-in. The UAE Electronic Invoicing Guidelines state that Persons newly established and within the scope of Electronic Invoicing are required to appoint an Accredited Service Provider and complete the onboarding process before issuing their first invoice, irrespective of their date of establishment, and that any invoice issued must be a compliant Electronic Invoice. For a new UAE entity, provider selection belongs in the incorporation plan alongside the trade licence and the bank account.
How do I onboard with an Accredited Service Provider?
Through EmaraTax, and you start it. The Guidelines state that the onboarding process should be initiated by the Person or Government Entity, not the provider, via the Federal Tax Authority's EmaraTax system by the account admin of the Taxable Person, using the E-INVOICING tile to view the list of providers and then proceeding to the chosen provider's portal. The Guidelines also state that each Person should onboard with only one provider for all of their Electronic Invoicing requirements, and that the contract and commercial obligations should be finalised first.
Does the system failure notification still exist?
No. Article 12 of Ministerial Decision No. 243 of 2025 originally required every issuer and recipient to notify the Federal Tax Authority of a System Failure within two Business Days. Article Three of Ministerial Decision No. 197 of 2026 repealed that article outright, and the definition of System Failure was deleted from Article 1. Consistently with that, the two rows in the old penalty schedule that charged AED 1,000 per day for failing to notify a system failure do not appear in the table annexed to Cabinet Decision No. 173 of 2026.
Should credit notes be treated as an afterthought before go-live?
No, and they are where testing most often falls short. Article 6(2) of Ministerial Decision No. 243 of 2025 requires an Electronic Credit Note where the Business Transaction is cancelled, where the agreed consideration is reduced for any reason, where consideration is returned in full or in part, and where an administrative or numerical error has occurred. That last limb turns ordinary billing corrections into a structured document that has to be issued and transmitted through the system, with its own penalty row and its own monthly cap.

Filed under: e-invoicing, UAE e-invoicing, PINT-AE, Peppol, Accredited Service Provider, EmaraTax, VAT, compliance

Published · Updated