FTA e-invoicing compliance: the ongoing obligations every UAE business must meet
What does FTA e-invoicing compliance require?
UAE businesses that have appointed an Accredited Service Provider often assume the hard part is over, but e-invoicing compliance continues with every invoice, every credit note, and every system change. Missing the 14-day issuance window, failing to notify the Federal Tax Authority of a system failure within two business days, or leaving a registered-data change unreported to your provider can each trigger a separate administrative penalty.
FTA e-invoicing compliance means meeting a short list of recurring obligations set out in Ministerial Decisions 243 and 244 of 2025, and it works best when each obligation has a named owner and a monthly control. This guide turns those decisions into an obligation register, an ownership map, a 14-day clock explainer, a control calendar, and an evidence file, and shows how Wafeq supports each step.
[Wafeq UI: An invoice’s e-invoicing section showing the FTA reporting status and the Peppol delivery status. To be captured from the UAE e-invoicing pilot; no public image is available.]
[Wafeq UI: An invoice’s e-invoicing section showing the FTA reporting status and the Peppol delivery status. To be captured from the UAE e-invoicing pilot; no public image is available.]
Who is in scope of the UAE e-invoicing system?
Any person conducting business in the UAE is in scope for every business transaction, unless the person or the transaction is excluded by ministerial decision. Free zone companies are not excluded as a category, and business-to-consumer transactions are not subject to the system until a later decision sets a date.
The exclusions in Ministerial Decision 243 cover sovereign activities of government entities, certain airline documents, and financial services that are VAT-exempt or zero-rated. Whether your own business or a specific transaction is excluded is a factual question.
The guide on: which businesses are exempt from e-invoicing walks through the common cases. Any person can also join voluntarily from 1 July 2026.
Which obligations apply continuously?
Ten obligations recur after go-live: appoint a provider, issue and receive e-documents, include every data field, report, store, and make two time-limited notifications. The register below maps each obligation to the article of the Ministerial Decision that creates it. The text of Decision 243 is published by the Ministry of Finance, and the phasing is in Decision 244.
No. | UAE E-invoicing Obligation | Source | Typical owner | Obligation Timing |
|---|---|---|---|---|
1 | Appoint an Accredited Service Provider (issuer and recipient, as applicable) | Decision 243, Art. 5(1) | Finance lead | By 30 October 2026 (revenue AED 50 million or more) or 31 March 2027 (below AED 50 million) |
2 | Implement the e-invoicing system | Decision 244 | Finance and IT | By 1 January 2027 or 1 July 2027 |
3 | Issue and transmit an e-invoice for each business transaction | Decision 243, Art. 6(1), 6(4), 6(5) | Billing | Within 14 days of the date of the business transaction (registrants follow the VAT Law timeline) |
4 | Issue and transmit an e-credit note in the four prescribed cases | Decision 243, Art. 6(2) | Billing and receivables | Same timing as invoices |
5 | Process received e-invoices and e-credit notes through the system | Decision 243, Art. 6(3) | Payables | On receipt |
6 | Include every data field the Ministry prescribes | Decision 243, Art. 7 | Master data owner | Every document |
7 | Report documents to the FTA through your provider | Decision 243, Art. 6(6), 6(7) | Provider, supervised by finance | Within the timeline set by the Minister |
8 | Store e-invoices, e-credit notes, and associated data within the UAE | Decision 243, Art. 11 | IT and finance | For the retention period in the Tax Procedures Law |
9 | Notify the FTA of a system failure | Decision 243, Art. 12 | IT and compliance | Within 2 business days of the failure |
10 | Notify your provider in writing of changes to data registered with the FTA | Decision 243, Art. 5(3) | Compliance | Within 5 business days of the FTA’s confirmation of the change |
The dates above match the FTA’s reminder of late October 2026, which also set out the order of steps: select a provider, contract and integrate, then complete the procedures on EmaraTax. The obligations themselves come from Ministerial Decision 243, and the phasing from Ministerial Decision 244.
The dates above match the FTA’s reminder of late October 2026, which also set out the order of steps: select a provider, contract and integrate, then complete the procedures on EmaraTax. The obligations themselves come from Ministerial Decision 243, and the phasing from Ministerial Decision 244.
Read also: UAE FTA e-invoicing: what your accounting system must support before the deadline
Who should own each compliance obligation?
Give each obligation one named owner in finance, IT, or tax, and agree in writing what your Accredited Service Provider does on your behalf. Compliance fails most often in the gaps between teams, for example when IT knows about an outage but nobody tells the tax team that a notice is due. A simple ownership map removes those gaps.
Activity | Primary owner | Backup | What the provider does |
|---|---|---|---|
Creating invoices and credit notes on time | Billing manager | Finance lead | Validates, converts, and transmits each document |
Customer and supplier master data (TRNs, addresses, codes) | Master data owner | Billing manager | Rejects documents that fail validation |
Processing received e-invoices | Payables manager | Finance lead | Delivers received documents into your system, if the product supports inbound |
System failure and incident notices | IT lead | Tax manager | Reports its own incidents; you still notify the FTA of yours |
Changes to registered business data | Tax manager | Finance lead | Updates records when you notify it in writing |
Retention and evidence file | Finance lead | IT lead | Stores data according to the contract; confirm where |
Annual review of scope and contract | Finance lead | Tax manager | Supplies service reports and contract terms |
What does your provider do, and what stays with you?
Get up to 30% Off Wafeq yearly packages
Enter your email to receive your exclusive discount code. New users only!
Your provider validates, converts, transmits, and reports documents, but the obligations remain those of the issuer and recipient, who fulfil them through the provider. Decision 243 says the issuer and recipient fulfil their exchange and reporting duties through the appointment of an Accredited Service Provider. That phrasing places the duty on you, with the provider as the channel.
In practice, this means you should read the service levels, ask how failures are escalated, and confirm who tells the FTA about what. If you are still deciding on a provider, the questions in how to choose an FTA Accredited Service Provider apply here as well.
Do recipients have compliance duties too?
Yes, recipients must also appoint a provider as applicable and process received e-invoices and credit notes through the system, so payables teams are in scope. Businesses that mostly buy still need a provider, and in-scope businesses generally use one provider for both sending and receiving.
That changes the daily work of accounts payable. Supplier documents should arrive as structured data, be reviewed, and be posted, instead of being keyed in from a PDF. Agree on the review and approval steps before the volume arrives.
Read also: E-invoicing readiness checklist for SMEs in the UAE: 10 things to do before October 2026
How does the 14-day rule work in practice?
E-invoices and credit notes must be issued and transmitted within 14 days of the business transaction date, the earlier of supply or payment. The clock is counted in calendar days from the Date of Business Transaction, which Decision 243 defines as the earlier of the date the transaction occurred or the date payment was received.
Registered businesses follow the timeline in the VAT Law, which in the usual case also allows 14 days, and Decision 243 applies the 14-day window to issuers more generally. In either case, the practical advice is the same: do not let documents wait for a month-end batch. The table shows how the date is set in four common cases.
Scenario | Date of business transaction | Latest issue date | Comment |
|---|---|---|---|
Goods delivered on 3 January, payment received on 20 January | 3 January | 17 January | Supply came first |
Advance payment received on 5 March, supply on 25 March | 5 March | 19 March | Payment came first, so it sets the date |
Service completed on 28 February 2027, invoice raised on 20 March | 28 February | 14 March | The 20 March invoice is late |
Goods returned and refund paid on 10 April | 10 April | 24 April | An e-credit note is required |
When must you issue an e-credit note?
An e-credit note is required when a transaction is cancelled, the price is reduced, consideration is returned, or an administrative or numerical error occurred. These are the four cases in Decision 243, and each must be issued and transmitted through the system on the same timeline as an invoice.
This is why a reported e-invoice cannot simply be edited: the correction route is a credit note followed by a new invoice. The mandatory fields for tax invoices and credit notes are summarized in VAT invoice requirements in the UAE, and the full data field list is prescribed by the Ministry.
What about agents and self-billing?
An agent can issue e-invoices on behalf of a principal, and a recipient can self-bill on behalf of an issuer when both are VAT registrants. Both options are in Decision 243, and both still run through the e-invoicing system and a provider.
If your business uses agents or self-billing arrangements, document who issues, who approves, and who is responsible for the 14-day clock, because the obligation does not disappear when someone else presses the button.
Read also: UAE e-invoicing penalties: what businesses need to know before 2027
What can the FTA see once you are live?
The FTA can access and use any data processed, received, and stored in the e-invoicing system, and invoice data reaches it through your provider. That changes how you should think about accuracy: the authority will hold your invoice-level data, so differences between what you invoiced and what you declare can be visible.
Providers sit between your accounting system and the FTA. They validate each document against the technical specification, convert it to the required format, send it over Peppol, and report the tax data.
The role is explained in:what an Accredited Service Provider does in UAE e-invoicing.
Why should your invoice data match your VAT return?
Reconcile your e-invoice data to your VAT return every period, because the same invoices feed both, and the FTA can see both. Credit notes, late documents, and rejected invoices are the usual causes of differences.
A short monthly reconciliation catches most issues. Compare total output tax on transmitted invoices and credit notes with the output tax in your ledger, and investigate any difference before the VAT return is prepared.
Where must e-invoicing data be stored?
Decision 243 requires e-invoices, e-credit notes, and associated data to be stored within the UAE for the period set in the Tax Procedures Law. Ask your provider and your accounting vendor where your data is hosted, and get the answer in writing.
VAT records must generally be kept for five years and corporate tax records for seven. If you export data to another system, make sure the copy you keep also meets the in-country storage requirement.
Can the FTA share e-invoicing data?
Yes, Decision 243 lets the FTA share e-invoicing data with other government entities or foreign bodies under international agreements. The sharing is subject to the Tax Procedures Law. This is another reason to treat the quality of your invoice data as a governance matter, not only a technical one.
Read also: How to implement e-invoicing in the UAE: finalized framework, integration, validation and reporting
What must you notify, and how fast?
Two duties are time-limited: notify the FTA of a system failure within two business days, and notify your ASP of data changes within five. Both clocks run in business days, which Decision 243 defines as any day except weekends and official federal holidays.
What counts as a system failure?
A system failure is any technical malfunction, disruption, or unavailability of the e-invoicing system that stops the issuer or recipient from meeting its obligations. The duty applies whether the failure started in your own systems or at your provider.
If you cannot transmit invoices because your integration is down, your provider’s platform is unavailable, or the network is disrupted, treat it as a potential notification event, and decide quickly. The notification follows the mechanism and procedures that the FTA sets.
How should you run an incident?
Run every disruption through the same five steps: log it, assess the impact, notify, fix, and record the outcome. Agree the steps with your provider so nothing depends on one person’s memory.
- Log the time. Record when the failure started, who detected it, and which documents were affected.
- Assess the impact. Identify documents that are close to their 14-day limit.
- Notify the FTA. Send the notice through the FTA’s prescribed mechanism within two business days of the failure.
- Fix and retransmit. Work with your provider to restore service and transmit pending documents.
- Record the outcome. File the notice, confirmation, and lessons in your evidence file.
Which penalties attach to compliance failures?
Cabinet Decision 106 of 2025 attaches separate penalties to late implementation, missing documents, and missed notifications, and they can stack. The table summarizes the amounts as described in Wafeq’s penalties guide. Confirm them against the decision text before relying on them.
Failure | Penalty | Notes |
|---|---|---|
Delay in implementing the system, including failure to appoint a provider on time | AED 5,000 for each month or part of a month | Confirmed in the FTA’s reminder of late October 2026 |
Failure to issue and transmit an invoice or credit note | AED 100 per document, capped at AED 5,000 per month | As summarized in Wafeq’s guide |
Failure to notify the FTA of a system failure within two business days | AED 1,000 per day, with no monthly cap | As summarized in Wafeq’s guide |
Failure to notify your provider of data changes within five business days | AED 1,000 per day | As summarized in Wafeq’s guide |
Most of these failures start with preventable mistakes, such as invalid TRNs, wrong dates, and missing fields. The common ones are covered in: 3 costly mistakes UAE businesses make when preparing for e-invoicing.
Read also: UAE e-invoicing deadlines and rules: your questions answered
Which compliance controls should you run each day, week, and month?
Run a small set of recurring controls: daily exception checks, weekly 14-day aging, monthly reconciliation to your VAT ledger, and quarterly failure drills. Controls turn the obligation register into habits. Each control below has an owner and leaves evidence.
Rhythm | Control | Owner | Evidence |
|---|---|---|---|
Daily | Review rejected, unsent, and failed documents, and clear or escalate each one | Billing manager | Exception report with notes |
Weekly | Age every document not yet transmitted against the 14-day limit, and confirm credit notes exist for returns and cancellations | Billing manager | Aging report |
Weekly | Clear the inbox of received e-invoices and credit notes | Payables manager | Inbox status screen |
Monthly | Reconcile transmitted invoices and credit notes to the VAT ledger | Finance lead | Signed reconciliation |
Monthly | Validate new customer and supplier TRNs and update records | Master data owner | Validation log |
Quarterly | Run a failure drill: simulate an outage, notify internally, and test the escalation path with your provider | IT lead | Drill report |
Annually | Re-check the revenue band, scope, provider contract, and registered data | Tax manager | Review memo |
Invalid registration numbers are the quickest way to have documents rejected, so the monthly TRN control pays for itself. The steps for checking numbers are in Wafeq’s guide to TRN verification in the UAE.
Read also: UAE e-invoicing timeline: don’t miss your ASP deadline or go-live date
What should an e-invoicing compliance evidence file contain?
Keep one evidence file that shows who you appointed, what you issued and received, what went wrong, and what you did about it. A tidy file shortens any FTA query. It also shows your provider, auditors, and lenders that compliance is managed.
Evidence | What it proves | Owner |
|---|---|---|
Provider contract and the appointment confirmation completed on EmaraTax | You appointed a provider before the deadline | Finance lead |
List of in-scope entities, TINs, and revenue band | You applied the right deadline to each entity | Tax manager |
Record of your Peppol participant ID and onboarding status | Your entity can exchange documents on the network | IT lead |
E-invoice and e-credit note data stored in the UAE, with hosting confirmation | You meet the storage duty | IT lead |
Incident log and copies of FTA notices | You notified within two business days | IT lead and tax manager |
Written notices to your provider about data changes | You met the five-business-day duty | Tax manager |
Monthly reconciliation sign-offs and control reports | Your controls ran | Finance lead |
Training records for billing and payables staff | Your people know the rules | Finance lead |
The participant ID record matters more than it looks, because your trading partners and your provider will ask for it when you onboard. The process is explained in how to obtain your UAE Peppol participant ID.
Read also: Understanding UAE e-invoicing: a practical guide for companies
How does Wafeq support FTA e-invoicing compliance?
Wafeq is both your accounting software and your Accredited Service Provider, so issuing, validating, transmitting, and reporting happen in one platform. Wafeq’s UAE page states accreditation number 129932 and says e-invoicing is included in the plan. Confirm the entry on the Ministry of Finance list, and check that the status matches what you are told.
On the Ministry of Finance side, you can check the published list of Accredited Service Providers.
On the product side, Wafeq describes how invoices are validated, converted to PINT AE, sent over Peppol, and reported to the FTA.
On the product side, Wafeq describes how invoices are validated, converted to PINT AE, sent over Peppol, and reported to the FTA.
Which obligations does the platform help with?
The platform covers issuing and transmitting documents, locking reported invoices, correcting through credit notes, and showing a status for each document. It does not replace your owners and controls. Use the platform to produce the evidence the earlier tables ask for.
- Issuing and transmitting: each finalized invoice is validated, converted, sent, and reported through your plan’s e-invoicing.
- Corrections: once an invoice has been reported, its reported fields can no longer be edited. You void it, which creates a credit note, and issue a new one.
- Status and receiving: each document shows its reporting and delivery status, and received e-invoices can be reviewed and posted without re-keying.
- Counterparty checks: when you create a customer, you can look up its TIN or VAT number, verify the number with the FTA, and see whether it is on the Peppol network.
What the platform can't do decides who owns the obligations, runs the drills, or files the notices. Those stay with the business, and the register, calendar, and evidence file in this guide are designed to make them routine.
What the platform can't do decides who owns the obligations, runs the drills, or files the notices. Those stay with the business, and the register, calendar, and evidence file in this guide are designed to make them routine.
Read also: E-invoice management software in the UAE: what businesses need to know
FTA e-invoicing compliance is a set of habits more than a project. Appoint your provider on time, and then give each continuing obligation an owner: the 14-day clock for invoices and credit notes, the data fields, the in-country storage, and the two notifications.
Run a short set of controls every day, week, and month, keep an evidence file, and reconcile your e-invoice data to your VAT ledger so the FTA sees the same story in both. Most penalties come from skipped basics rather than complex positions, and a clear register and calendar make the basics routine. Wafeq’s platform produces the documents and statuses that your controls need, and your team supplies the ownership.
FAQs about FTA e-invoicing compliance
Is FTA e-invoicing compliance only about appointing a provider?
No, appointing a provider is the first obligation, and the rest are continuing duties: timely issuing, data fields, reporting, storage, and two notifications. Treat go-live as the start of compliance, not the end of the project.
Do businesses that only sell to consumers need to comply?
Business-to-consumer transactions are not subject to the system for now, and a business engaged only in them is not subject until a later ministerial decision. If you also sell to businesses or government entities, those transactions are in scope.
Does a free zone company need to comply?
Yes, free zone companies are not excluded as a category, and Decision 243 applies to any person conducting business in the UAE. Check each transaction against the exclusions, and apply the deadline for your revenue band.
What happens if I appoint my provider late?
The FTA says an administrative penalty of AED 5,000 applies for each month or part of a month of delay in implementing the system. That includes failing to appoint a provider within the prescribed deadline.
Can I edit an e-invoice after it has been sent?
No, a reported e-invoice is corrected with an e-credit note and, where needed, a new invoice, not by editing the original. Decision 243 lists the cases that require a credit note, including cancellations, price reductions, returns, and errors.
Where should my e-invoicing data be stored?
Within the UAE, for the retention period in the Tax Procedures Law, according to Decision 243. Ask your provider and accounting vendor to confirm the hosting location in writing.
Does voluntary adoption carry penalties?
Voluntary adopters are not subject to the penalty decisions, but businesses already in a mandatory phase are. Decision 244 allows any person to adopt e-invoicing voluntarily from 1 July 2026, and Decision 243 says the penalty decisions do not apply to those who issue voluntarily. Confirm how this applies to your own situation.
See how e-invoicing works inside Wafeq.
See how e-invoicing works inside Wafeq.
Check how your invoices are validated, sent over Peppol, and reported to the FTA from the same platform as your books, with e-invoicing included in your plan.
