
ByAhsan Nadeem@ashtech52Lead Full-Stack Engineer
For businesses with revenue of AED 50 million or more, UAE e-invoicing integration has to work by 1 January 2027. They had to appoint an Accredited Service Provider (ASP) by 30 October 2026. If you missed that date, appoint one now: the penalty is capped and modest for a business that size.
What decides your exposure from here is whether your ERP can pass a real invoice, a credit note and a rejection through your ASP before go-live.
Updated 4 November 2026. This is general information, not legal or tax advice. Confirm your position with a tax adviser and on the Ministry of Finance e-invoicing portal, the official source for timelines.
Appointing an ASP gets you a contract, and a contract doesn't send an invoice. The work that remains is data mapping and testing, and connecting a finance system to an outside API is the kind of API and integration work we offer. The choice of ASP and your tax treatment stay with you and your adviser.
The ASP deadline has passed and UAE e-invoicing integration go-live hasn't moved
- The appointment date has passed. No later decision moving it is listed on the Ministry's portal as of today, and its Guidelines V2.0, dated 26 October, still give 30 October.
- Go-live hasn't moved. It remains 1 January 2027 for the AED 50m group.
- The penalties are new. Cabinet Decision 173 of 2026 repeals Decision 106 of 2025.
- The rules changed in October too. Decisions 197 and 168 took effect on 1 October, and the mandatory field list was reissued on 28 October.
- The specification is live. Peppol publishes PINT AE Billing version 1.0.4 for invoices and credit notes.
One warning on sources. Many pages still cite the old numbers, and that includes the FTA's own e-invoicing page, updated 2 November, which still refers to Decision 106 for penalties. The Ministry's October programme deck marks 106 as repealed, and Decision 173 says so itself. Go by the decisions.
Dates by phase, and what Decision 66 of 2026 changed
Your phase depends on Revenue, defined as gross income in your most recent accounting period.
Who | Appoint an ASP by | Implement by |
|---|---|---|
Revenue of AED 50m or more | 30 October 2026 | 1 January 2027 |
Revenue under AED 50m | 31 March 2027 | 1 July 2027 |
Government entities | 31 March 2027 | 1 October 2027 |
Decision 66 of 2026 changed only the first appointment date, from 31 July to 30 October. It left the go-live date alone, so the extension shortened the gap between signing an ASP and going live.
Three changes from Decision 197, in force since 1 October, matter to system design:
- Timing: the limit for issuing an e-invoice or credit note moved from 14 days to 14 Business Days from the transaction. VAT registrants still follow the VAT Law timeline.
- Storage: the earlier wording requiring storage "within the State" is gone. You must keep records for the Tax Procedures Law period and be able to produce them on request.
- System failure: the duty to tell the FTA about a system failure has been removed, along with its AED 1,000 a day penalty.
Cabinet Decision 173 penalties: AED 5,000 a month for not implementing, capped at AED 50,000
Violation | Penalty | Cap |
|---|---|---|
Not implementing, including not appointing an ASP, or a recipient not staying compliant | AED 5,000 for the first instance, then AED 5,000 per month or part month | AED 50,000 in any 12 consecutive months |
Not issuing and sending an e-invoice | AED 100 each | AED 5,000 per calendar month |
Not issuing and sending an e-credit note | AED 100 each | AED 5,000 per calendar month |
Not telling your ASP about changes to data registered with the FTA | AED 250 per day or part day | AED 5,000 per calendar month |
Decision 106 charged AED 5,000 per month with no cap, and named only the issuer on that line. Recipients are now named too, so a business that mainly buys isn't outside it.
A worked penalty table
Here is the first line applied to a business that missed 30 October. This is our reading of the text, not an FTA calculation. It assumes the failure began on 31 October, that Decision 173 was already in force, and that months count from that date. We found no published method, and the English copy of the decision leaves its issue date blank, so confirm the Gazette date. A different count could move these figures by AED 5,000.
ASP appointed on | First instance | Months or part months | Total |
|---|---|---|---|
20 November 2026 | AED 5,000 | 1 | AED 10,000 |
15 December 2026 | AED 5,000 | 2 | AED 15,000 |
15 January 2027, not yet live | AED 5,000 | 3 | AED 20,000, plus invoice penalties |
About 1 July 2027 | AED 5,000 | 9 | AED 50,000 (cap) |
The AED 50,000 cap isn't the whole exposure
The cap applies to the first line only. The other three have their own monthly limits, and 50 missed invoices in a month reach the invoice limit. If all four lines ran at their limits for a year, the arithmetic is AED 50,000 plus three lots of AED 60,000, or AED 230,000. That is our sum and a theoretical ceiling. The decision only rules out a second penalty when the same person is issuer and recipient for the same violation.
Ordinary VAT and tax procedure penalties under Cabinet Decision 40 of 2017 can also apply, according to the Guidelines. Ask your adviser what a non-compliant tax invoice would mean for your customer's VAT recovery, because that conversation may matter more to you than the fine.
If you missed the 30 October ASP deadline
Don't wait for clarity on the penalty. Each further month or part month adds AED 5,000 on the reading above.
- Confirm your phase. Check Revenue against your latest financial statements. If you're under AED 50m, you have until 31 March 2027.
- Check your exclusions. Exempt financial services, sovereign government activity and some airline supplies are carved out. Consumer-only sellers are covered in the last section.
- Pick from the live list. The Ministry's provider list had 84 names when we read it. Its October deck says 65 accredited and 5 pre-approved, and the list is updated periodically, so trust the list. Pre-approved providers had 30 days from 1 October to complete accreditation.
- Choose one provider for both directions. The Guidelines require one ASP for sending and receiving, so finance teams on the payables and receivables sides need to decide together.
- Contract, then onboard. The contract comes first. Your EmaraTax account admin then starts onboarding from the E-INVOICING tile, and your Peppol participant identifier comes through the ASP.
- Keep a dated record. Note when you appointed and why it was late, and take it to your adviser.
An eight-week plan to 1 January
This is our suggested order, not an official one. Adjust the weeks to your volumes.
- Week 1: sign the ASP, start onboarding, agree the data format and how confirmation messages come back.
- Weeks 2 and 3: map your ERP data to the mandatory fields and fix master data, buyer identifiers first.
- Weeks 4 to 6: build the connection and run the test pack below.
- Week 7: agree with the ASP who fixes what when an invoice fails. The Guidelines ask for this governance model before go-live.
- Week 8: dry-run a day of real invoices, then freeze changes before 1 January.
Three ways to connect your ERP: connector, middleware or direct API
The rules don't prescribe a method. The Guidelines say the supplier submits data to its ASP "in an agreed format", and the ASP validates it and converts it to the UAE XML if needed. So you may not have to generate PINT AE XML yourself, which is a question worth asking first.
The routes below are as described by Cygnet, a vendor that sells UAE e-invoicing. The final column is our view.
Route | Suits | Watch for | Ask before choosing |
|---|---|---|---|
Direct API from ERP to ASP | Modern ERP, high volumes | More upfront work, and you carry the updates when rules change | Who updates the mapping when PINT AE changes? |
Connector or middleware | Several or older ERPs | One more system and licence to run | Is your exact ERP version supported, in production today? |
File or SFTP batch | Low volumes, older systems | Limited real-time validation, so errors surface late | How do failures get back into the ERP? |
With about eight weeks left, a supported connector for your exact ERP version is usually the shortest path, and custom API work makes sense where none exists or invoices start in several systems. That's our judgement, not a rule.
ERP makers and ASPs make differing claims about native UAE support and its dates, and we couldn't confirm them from the makers' own documents. Get it in writing: version, PINT AE release and how responses come back. The Ministry's ASP selection questions also cover product ownership, who provides support, uptime SLAs, retention and hidden fees. ASPs must give each end user 100 free exchange and reporting services a year, which won't go far at this size but is useful to smaller firms. A clear project scope will also help you compare quotes.
The test pack: invoices, credit notes, rejections, archiving
A sandbox invoice with perfect data proves very little, so test your awkward cases. We selected these from the rules, and your ASP may add more.
Test | What to prove | Rule |
|---|---|---|
Standard tax invoice | All 51 mandatory fields fill from ERP data | Mandatory Fields V1.1 |
Commercial invoice for exempt or out-of-scope sales | 49 fields, with the right treatment of TRN | Mandatory Fields V1.1 |
Foreign currency invoice | Tax Accounting Currency filled, AED totals at the Central Bank rate | Guidelines 12.2 |
Full credit note | Links to the original, buyer legal ID present for type code 81 | Decision 243; Guidelines 18.2.1 |
Partial credit note, and one note for several invoices | Both post correctly in your ledger | Guidelines 12.2 |
Technical rejection | A deliberately bad invoice returns from the ASP, shows in the ERP and reaches a named person | FTA FAQ; Guidelines 5.1 |
Buyer dispute | Handled outside the network and corrected by credit note, as there's no cancellation | FTA FAQ |
Incoming supplier invoice | Reaches payables and passes your approval flow | Guidelines 13.3 |
Buyer not onboarded yet | Predefined endpoint 0235:9900000098 on the e-invoice, plus a regular tax invoice sent as well | Guidelines 10.2.2 |
Export to a foreign buyer | Dummy endpoint, tax data reported, invoice delivered outside the network | FTA FAQ |
Reporting confirmation | Success and failure messages for tax data both reach you | Guidelines 13.3 |
Archive retrieval | Pull an old invoice complete and readable, on request | Guidelines 5.4 |
Three of these need a closer look:
- Rejections. The FTA says rejections by ASPs and the reporting platform rest only on technical Schematron validation, and the ASP returns a problem invoice to you. Build the return path before go-live, and ask your ASP whether a corrected invoice can reuse its number.
- Buyers who aren't live. Your AED 50m obligation doesn't depend on your customer's status, and smaller buyers have until 1 July 2027. Guidelines 10.2.2 covers that gap for tax invoices: until the buyer implements, you issue a regular tax invoice, such as a PDF, as well as the electronic one, and put the predefined endpoint 0235:9900000098 on the e-invoice. Ask your ASP how it handles this.
- Archiving. Records generally stay for 5 years after the tax period, and for longer in cases such as audits, disputes and real estate. An ASP can hold them by contract, but the legal duty stays with you.
Where we would look first for missing data
These are likely gaps in our judgement, because older billing systems rarely held these fields for a PDF invoice:
- Buyer electronic address and identifier: the buyer's TIN, the first 10 digits of the TRN, with scheme 0235.
- Seller legal registration type: TL, EID, PAS or CD.
- Eight transaction flags: free zone, deemed supply, margin scheme, summary invoice, continuous supply, disclosed agent, e-commerce and exports.
- Line amounts in AED: VAT and total payable on each line.
- Payment due date: required even when payment is on the spot.
- Unit of measure: a code on every line.
You can't add your own optional fields to PINT AE. HSN codes are optional for now, with any mandatory date still to be announced. If your invoices start at a shop counter, our notes on offline-first billing software cover invoice numbering, where tax rules shape the database.
After go-live, tell your ASP about changes to data registered with the FTA within 5 Business Days of its confirmation. That's the fourth penalty line.
If you are under AED 50m: what to do before 31 March 2027
You have five months to appoint and eight to go live, and that time is best spent on data rather than software. The Ministry says 82% of UAE businesses are micro businesses under AED 3m turnover, so many in this group will have simple needs.
- Start with customer data. Collect TINs and legal registration details now. If you don't have a TIN, you generate one through EmaraTax.
- Ask your accounting software supplier which ASP it works with, and whether it's on the list.
- Consider going early. Voluntary implementation has been open since 1 July 2026, and penalties only apply from your mandatory date.
If you only sell to consumers, the sources need care. Decision 244 says a person engaged only in B2C isn't subject to the system for now. The FTA's FAQ says a B2C-only business must appoint an ASP if it receives B2B supplies. Ask your adviser. New businesses in scope must onboard before issuing their first invoice.
Frequently asked questions
Has the 30 October deadline been extended again?
Not as far as the official record shows on 4 November 2026. The Ministry of Finance portal lists no later decision, and its Guidelines dated 26 October still give 30 October 2026 for appointing an ASP and 1 January 2027 for go-live. Check the portal for any newer notice.
What is the penalty for not appointing an ASP?
Under Cabinet Decision 173 of 2026, the first instance costs AED 5,000 and each further month or part month adds AED 5,000, up to AED 50,000 in any 12 consecutive months. Separate limits apply to missed invoices and credit notes. The decision takes effect the day after Gazette publication, so confirm that date with your adviser.
Who is exempt or out of scope, and are B2C invoices covered?
B2C transactions are not covered for now. Exclusions include sovereign government activity, airline passenger tickets and related services, airway bill cargo for a limited period, and exempt financial services. Imports are not subject to it. Transactions inside a VAT tax group are excluded for 24 months from 1 January 2027, though each member must still onboard.
Do I need to replace my ERP?
No rule we read requires it. The Guidelines require your systems to generate and extract the mandatory data, and they let you agree a data format with your ASP, which converts it to the UAE XML if needed. The usual work is mapping data, adding fields and connecting through a connector, middleware or API.
How do I check whether a provider is accredited?
Use the provider list on the Ministry of Finance website, which shows an accreditation number for each entry and is updated periodically. Onboarding also runs through EmaraTax, where you select your provider from the E-INVOICING tile. Don't rely on a seller's own claim.
What happens when an invoice is rejected?
If validation fails, your ASP returns the invoice to you, and these rejections are technical only. A buyer can dispute an invoice for commercial reasons, but that happens outside the e-invoicing process. Invoices can't be cancelled, so errors in an issued invoice are corrected with a credit note.
Run the rejection test first, because it shows the most in the least time. If the bad invoice never reaches a named person, book a free consultation with one of our engineers. We'll go through the mapping and the connection with you and say what the work involves, whether on a fixed price or time and materials basis.
Sources
- Ministry of Finance, UAE e-invoicing portal (updated 4 November 2026)
- Cabinet Decision 173 of 2026, violations and administrative penalties
- Cabinet Decision 106 of 2025, now repealed
- Ministerial Decision 66 of 2026, amending Decision 244
- Ministerial Decision 244 of 2025, implementation
- Ministerial Decision 243 of 2025, the e-invoicing system
- Ministerial Decision 197 of 2026, amending Decision 243
- Ministerial Decision 168 of 2026, accreditation of service providers
- UAE Electronic Invoicing Guidelines V2.0 (26 October 2026)
- UAE Electronic Invoice Mandatory Fields V1.1 (28 October 2026)
- Considerations for Selecting an Accredited Service Provider V1.1 (28 October 2026)
- UAE eInvoicing Programme deck (October 2026)
- Ministry of Finance, list of service providers
- Federal Tax Authority, e-invoicing page and FAQ (updated 2 November 2026)
- Peppol, PINT AE Billing specification
- Cygnet.One, integrating your ERP with the UAE five-corner model (vendor, 7 January 2026)



