The UAE's Electronic Invoicing System is a Peppol five-corner model: your ERP or POS never talks to the Federal Tax Authority. It sends invoice data to your one Accredited Service Provider, which converts it to PINT-AE XML, exchanges it with the buyer's provider and reports the tax data to the FTA. Consumer sales are outside the system until the Minister decides otherwise, so a shop's till receipts do not change; every business-to-business and business-to-government invoice and credit note does, whether or not you are VAT-registered. Businesses at AED 50 million revenue or more must appoint a provider by 30 October 2026 and go live by 1 January 2027; everyone else by 1 July 2027. Every sentence above is quoted below from the Ministry of Finance's decisions and its June 2026 guideline.
According to BengalTech's 2026 price list, a custom ERP built in Dhaka for a UAE business with the e-invoicing integration scoped in runs $7,500 – $14,000 for a small business, and a custom POS starts at $2,200, one-time with the source code yours.
This guide is for finance and operations leads in the UAE deciding whether their current ERP, POS or billing system can meet the 2027 mandate, and for anyone commissioning a custom one. It is not tax advice: we implement the standard, your tax adviser confirms compliance, and the Ministry's documents outrank anything here.
Who Is In Scope, and Why Your Till Receipts Are Not (Yet)
The guideline's scope chapter is blunt: e-invoicing is mandatory "for any Person conducting Business in the UAE, in respect of every Business Transaction, regardless of whether they are established in the UAE", and "notwithstanding their VAT registration status". Its transaction table ticks B2B, B2G, G2B and G2G and leaves every consumer cell blank, because "any supplies to or from natural persons who are not in Business are not within the scope". Ministerial Decision 244 puts a date on that: consumer transactions are excluded "until such time determined by a decision issued by the Minister".
For a retailer, restaurant or clinic that means the POS keeps printing ordinary receipts to walk-in customers. What changes is everything else the same business does: invoicing a corporate client, a hotel, a government department or a franchisee; and receiving invoices from suppliers, landlords and agencies. The guideline also removes the usual excuse: "a customer's Electronic Invoicing onboarding status or tax registration status does not affect the Electronic Invoicing obligations". If the buyer is not on the network yet, you send to a predefined endpoint and give them a PDF as well.
The exclusions in Article 4 of Decision 243 are narrow: sovereign government activity, airline passenger tickets and ancillary services, airline cargo for the first 24 months, and VAT-exempt or zero-rated financial services. Voluntary adopters may join from 1 July 2026 and are held to the full technical standard but, per the guideline, not to the e-invoicing penalties until their mandatory date.
The Deadlines, Including the One That Moved
Decision 244 set a pilot from 1 July 2026 with an invited working group, voluntary adoption from the same day for anyone, then three mandatory phases by revenue. On 10 May 2026 the Ministry announced a targeted amendment: the provider-appointment deadline for the largest businesses moved to 30 October 2026 so they could choose from a wider provider market, while the go-live date "remains fixed". Many vendor summaries still print the old July date.
| Who | Appoint a provider by | Implement by | Source |
|---|---|---|---|
| Business with revenue of AED 50 million or more | 30 October 2026 (moved from 31 July 2026 by MD 66 of 2026) | 1 January 2027 | MD 66 of 2026, amending MD 244 Art. 5(1)(a) |
| Business with revenue below AED 50 million | 31 March 2027 | 1 July 2027 | MD 244 of 2025, Art. 5(1)(b) |
| Government entity | 31 March 2027 | 1 October 2027 | MD 244 of 2025, Art. 5(1)(c) |
"Revenue" is gross income in the most recent accounting period per the financial statements (Decision 244, Article 1). The Ministry's accredited provider list showed 49 accredited and 8 pre-approved providers when this guide was written in September 2026; onboarding with the one you pick is done by your own account admin in EmaraTax, not by the provider and not by us.
The Eight Things Your ERP or POS Must Do
Each row quotes the Ministry's document, says what it means for the system, and says how we build it. Guideline page numbers refer to version 1.1 of 1 June 2026. The guideline itself tells businesses to "ensure that their accounting/ERP/invoicing systems can generate and extract all the data points that are required" and to carry out a gap analysis; the rows below are that gap analysis in advance.
Send invoice data to one Accredited Service Provider, for both sales and purchases
- Guideline, pp. 10, 14
- A Person within the scope of Electronic Invoicing "must appoint only one ASP in respect of both sending (e.g. accounts receivable) and receiving (e.g. accounts payable) Electronic Invoices." The supplier "submits Electronic Invoice data in an agreed format with its ASP", which "converts it into the UAE standard Electronic Invoice in an XML format".
- In the system
- Your ERP or POS integrates with your provider's API, not with the FTA. The provider does the XML, the Peppol transport and the tax-data report. Your system's job is to hand over complete, correct data and to take invoices back in.
- How BengalTech builds it
- One integration module with a provider adapter behind it. The invoice, credit note and inbound-document contracts are fixed; the adapter for the provider you choose from the Ministry's list is the only part that changes if you ever switch.
Carry all 41 mandatory fields of an electronic tax invoice, and no home-made ones
- Mandatory fields, §4.1; Guideline, p. 37
- The Ministry's mandatory-fields document lists 41 fields for an electronic tax invoice, from invoice number, date and type code through seller and buyer electronic addresses to line identifier, quantity and unit-of-measure code. The guideline adds that businesses "will not be allowed to add additional optional fields of their own into PINT-AE."
- In the system
- Most legacy invoice tables are missing several of these: the buyer's Peppol electronic address, the invoice type code, tax category codes per line, unit-of-measure codes. Anything your own template needs beyond PINT-AE has to be negotiated with the provider, not bolted on.
- How BengalTech builds it
- The invoice model is designed from the field list outward. Every mandatory field is a non-nullable column or a validated lookup, and the "issue" action refuses to run until all of them are present, so an incomplete invoice cannot leave the system.
Identify every party by TIN-based Peppol identifier
- Guideline, pp. 6, 23
- The participant identifier is "0235 followed by the 10-digit TIN of the" business. When a buyer "has not yet implemented Electronic Invoicing and does not have a Participant Identifier, the predefined endpoint (0235:9900000098) should be mandatorily included by the supplier", and a regular PDF tax invoice is still required for that buyer.
- In the system
- Your customer master needs a TIN and a Peppol endpoint for every business customer, plus a flag for the ones not yet onboarded so the system sends both the electronic invoice and the PDF.
- How BengalTech builds it
- The customer record stores TIN, endpoint and onboarding status; the endpoint is looked up through the provider at invoice time; a not-onboarded buyer automatically gets the predefined endpoint and a PDF tax invoice in the same run.
Issue and transmit within 14 days, and produce the right document type
- MD 243, Art. 6(5); Guideline, p. 22
- The electronic invoice or credit note "must be issued and transmitted by the Issuer through the Electronic Invoicing System within 14 days from the Date of Business Transaction", the earlier of the transaction date and the payment date. Six categories exist: electronic tax invoice, tax credit note, commercial invoice, credit note, and self-billed versions of the first two.
- In the system
- A VAT-registered business issues tax invoices; an unregistered one still issues electronic commercial invoices. Paper and PDF commercial invoices "must be replaced". The clock starts at delivery or payment, whichever is first.
- How BengalTech builds it
- The document type is derived from your VAT status and the supply, never chosen by hand. An ageing view shows every business transaction not yet transmitted against its 14-day deadline, and unsent documents older than a configurable threshold page the finance lead.
Correct with credit notes, never by editing
- MD 243, Art. 6(2)
- The Issuer "shall issue and transmit an Electronic Credit Note" where the transaction is cancelled, the consideration is reduced, the consideration is returned in full or in part, or "an administrative or numerical error has occurred in relation to the Business Transaction."
- In the system
- Once transmitted, an invoice is immutable. A typo in a quantity is fixed with a credit note and a new invoice, both of which are themselves exchanged and reported.
- How BengalTech builds it
- Transmitted documents are append-only. The UI offers "credit note" and "reissue" instead of "edit" or "delete", pre-filled from the original, and links the three documents so an auditor can follow the chain.
Track confirmations and rejections for every document
- Guideline, pp. 10–11, 48
- The buyer's provider "sends electronic confirmation" on validation, the FTA "sends electronic confirmation ... once the Tax Data has been successfully reported", and if validation fails there is "no reporting of Tax Data". Providers must inform businesses "on an event-driven basis and without undue delay" that documents reached the Authority.
- In the system
- An invoice has a lifecycle: drafted, sent to provider, accepted by the buyer's provider, reported to the FTA, or rejected at any of those steps. A rejected invoice has not been issued in law.
- How BengalTech builds it
- A status per document driven by the provider's callbacks, a rejection queue with the validation message in plain language, and a rule that a rejected invoice re-enters the 14-day clock rather than silently sitting in "sent".
Receive inbound invoices through the same system
- MD 243, Arts. 5(3), 6(3)
- "The Recipient shall process Electronic Invoices and Electronic Credit Notes through the Electronic Invoicing System." Businesses must also "notify the appointed Accredited Service Provider in writing of any change to the data registered with the Authority ... within five (5) Business Days".
- In the system
- Supplier invoices arrive as XML from your provider. Keying them in by hand from a PDF is the old world; the ERP should ingest them into accounts payable and match them to purchase orders.
- How BengalTech builds it
- An inbound queue that maps PINT-AE documents to supplier bills, three-way matches against purchase orders and goods receipts, and flags mismatches. A registered-data change screen reminds you of the five-day notice to your provider.
Store for five years, and report a failure within two business days
- Guideline, p. 12; MD 243, Arts. 11–12
- Data "must be retained for a period of: 5 years following the Tax Period to which they relate" (7 years for real estate records), in a system where records "can be retrieved and reproduced by the FTA in a complete and readable form". "Every Issuer and Recipient shall notify the Authority of a System Failure within 2 Business Days".
- In the system
- The XML and its confirmations are the legal record, not your printed PDF. The guideline says servers may sit outside the UAE as long as records are promptly retrievable, and delegating storage to a provider does not transfer the obligation.
- How BengalTech builds it
- Every transmitted document, response and confirmation is archived immutably with an export-for-audit function. A provider or connectivity outage past a configurable threshold raises an alert with the notification text and the two-business-day deadline.
Why Master Data, Not the XML, Is the Whole Game
In Saudi Arabia's ZATCA model the hard engineering sits on the till: per-device certificates, hash chains, QR codes, 24-hour reporting. The UAE moved all of that into the provider layer. The guideline says the provider "converts" your data into the standard XML, generates the UUID, encrypts the transmission and reports to the FTA. There is no QR code, no cryptographic stamp on your side, and 14 days instead of 24 hours. What is left for your system is deceptively unglamorous: every business customer with a TIN and endpoint, every item with a tax category code and unit of measure, every invoice with a type code, and the discipline to correct by credit note. That is a data-model and workflow problem, and it is exactly where a legacy ERP with free-text customer fields and hand-typed VAT lines fails.
We build ERP and POS in Dhaka for businesses in the Gulf, and the same engine that keeps a Saudi till compliant through an internet outage keeps a Dubai trading company's invoices complete before they reach the provider. See how we scope the ERP build and the POS tiers, and if you also trade in Saudi Arabia, the ZATCA Phase 2 guide covers the other half. The same engine also carries the Bangladesh NBR rules, which ask for the invoice fields and the books in a system rather than clearance.
What Non-Compliance Costs
Cabinet Decision 106 of 2025, announced by the Ministry on 8 December 2025, sets the e-invoicing-specific fines. Ordinary VAT invoicing penalties under Cabinet Decision 40 of 2017 still apply on top.
| Violation | Fine |
|---|---|
| Failing to implement the system or to appoint an Accredited Service Provider | AED 5,000 per month |
| Electronic invoice not issued or sent within the timeframe | AED 100 per invoice, capped at AED 5,000 per month |
| Electronic credit note not issued or sent within the timeframe | AED 100 per credit note, capped at AED 5,000 per month |
| Failing to notify the FTA of a malfunction in the system | AED 1,000 per day or part of a day |
| Failing to notify the appointed provider of a change to registered data | AED 1,000 per day or part of a day |
Ten Questions to Ask Any ERP or POS Vendor Before 2027
- Which Accredited Service Providers from the Ministry's list have you integrated with, and can I see an invoice go end to end in their test environment?
- Show me the customer record. Where do the TIN, the Peppol endpoint and the onboarding status live?
- Can the system issue an invoice with a mandatory field missing? (It must not.)
- How does it choose between an electronic tax invoice and a commercial invoice, and who can override that?
- What happens when a buyer is not on the network yet? Does it send to the predefined endpoint and produce the PDF tax invoice automatically?
- Can a user edit or delete an invoice after transmission? (No. Credit note and reissue only.)
- Show me the screen that lists everything unsent against the 14-day deadline, and the rejection queue.
- How do supplier invoices come in, and do they match to purchase orders?
- Where are the XML documents and the provider confirmations stored, for how long, and can I export them for the FTA in a readable form?
- If the provider is down for a day, who is alerted, and where is the two-business-day notification text?
What an E-Invoicing-Ready Custom Build Costs
BengalTech's 2026 tiers: a custom ERP for a small business $7,500 – $14,000, for a mid-sized one $14,000 – $28,000; a custom POS for a single counter Starts at $2,200, multi-staff outlet Starts at $3,400, multi-branch with cloud sync Starts at $5,900. One-time, source code yours, no per-user or per-terminal fee. The e-invoicing integration is scoped into the build at the free scoping session: the PINT-AE data model, the adapter for your chosen provider, inbound processing, status tracking and the archive. Your provider's own fees are separate and paid to the provider; we do not resell one.
For what an ERP costs without the UAE layer, see the ERP buyer's checklist, the custom POS cost guide, the ERP price guide and the four-way ERP cost comparison. UAE businesses evaluating a Dhaka team should also read the UAE outsourcing guide.
Sources
External references behind the figures and claims on this page. Rate bands and vendor pricing move — check the source before quoting a number.
- Ministerial Decision No. 243 of 2025 on the Electronic Invoicing System
UAE Ministry of Finance
Scope and exclusions (Art. 3–4), appointment of one Accredited Service Provider and the five-business-day data-change notice (Art. 5), issuance within 14 days of the business transaction and the four credit-note cases (Art. 6), storage within the State (Art. 11) and notification of a system failure within two business days (Art. 12).
- Ministerial Decision No. 244 of 2025 on the Implementation of the Electronic Invoicing System
UAE Ministry of Finance
Pilot and voluntary phase from 1 July 2026; the AED 50 million revenue threshold and the 1 January 2027, 1 July 2027 and 1 October 2027 implementation dates; business-to-consumer transactions excluded until a further decision of the Minister (Art. 5).
- Ministerial Decision No. 66 of 2026 amending Ministerial Decision No. 244 of 2025
UAE Ministry of Finance
The provider-appointment deadline for businesses at or above AED 50 million revenue moved from 31 July 2026 to 30 October 2026, with the 1 January 2027 implementation date unchanged.
- UAE Electronic Invoicing Guidelines, version 1.1 (1 June 2026)
UAE Ministry of Finance
The five-corner exchange flow and confirmations (pp. 10–11), XML format with no QR code and the five- and seven-year retention periods (p. 12), scope by transaction type and the single-ASP rule (p. 14), the six invoice categories and the predefined endpoint for buyers not yet onboarded (pp. 22–23), the ban on home-made optional fields (p. 37), onboarding through EmaraTax (pp. 21, 38–39) and event-driven transmission confirmation by providers (p. 48).
- UAE Electronic Invoice Mandatory Fields, version 1.0 (23 February 2026)
UAE Ministry of Finance
The 41 mandatory fields of an electronic tax invoice (section 4.1) and the TIN-based participant identifier with the 0235 scheme prefix.
- Ministry of Finance announces the issuance of Cabinet Resolution on administrative fines related to the Electronic Invoicing System (8 December 2025)
UAE Ministry of Finance
Cabinet Decision No. 106 of 2025: AED 5,000 per month for not implementing the system or not appointing a provider; AED 100 per late invoice or credit note capped at AED 5,000 per month; AED 1,000 per day for failing to notify the FTA of a malfunction or the provider of a data change.
- Ministry of Finance announces targeted amendments to eInvoicing system decisions (10 May 2026)
UAE Ministry of Finance
The reasoning for moving the appointment deadline to 30 October 2026 (a wider, more competitive provider market) and the statement that the 1 January 2027 implementation date remains fixed.
- eInvoicing Accredited Service Providers (ASPs)
UAE Ministry of Finance
The Ministry's published list of accredited providers under Article 16 of Ministerial Decision No. 64 of 2025: 49 accredited and 8 pre-approved when checked on 4 September 2026.
Frequently Asked Questions
Not yet. Ministerial Decision 244 of 2025 says business-to-consumer transactions "shall not be subject to the Electronic Invoicing System ... until such time determined by a decision issued by the Minister", and the guideline confirms supplies to natural persons not in business are out of scope. A retailer's till receipts do not change. Its sales to other businesses and to government entities do, and so do its supplier invoices coming in.
No. The UAE uses a five-corner Peppol model. Your system sends invoice data to your single Accredited Service Provider, which converts it to PINT-AE XML, exchanges it with the buyer's provider and reports the tax data to the FTA. The integration you build is to the provider's API, and you onboard with that provider yourself through EmaraTax.
The pilot and voluntary phase opened on 1 July 2026. Businesses with revenue of AED 50 million or more must appoint a provider by 30 October 2026 (Ministerial Decision 66 of 2026 moved this from 31 July) and implement by 1 January 2027. Businesses below AED 50 million must appoint by 31 March 2027 and implement by 1 July 2027. Government entities implement by 1 October 2027.
No. The guideline states that electronic invoices "are issued, transmitted and received in XML format and will not feature a Quick Response Code (QR code) or barcode." There is also no per-device cryptographic stamp; integrity comes from the provider network and the FTA's confirmations. A POS built for ZATCA in Saudi Arabia needs a different, and in some ways simpler, integration for the UAE.
Cabinet Decision 106 of 2025, announced by the Ministry of Finance on 8 December 2025, sets AED 5,000 per month for not implementing the system or not appointing a provider, AED 100 per late invoice or credit note capped at AED 5,000 per month, and AED 1,000 per day for failing to notify the FTA of a malfunction or the provider of a data change. Penalties do not apply during voluntary adoption before your mandatory date.
According to BengalTech's 2026 price list, a custom ERP for a small business runs $7,500 – $14,000 and for a mid-sized one $14,000 – $28,000; a custom POS starts at $2,200 for a single counter and starts at $5,900 for a multi-branch chain. One-time, source code yours. The UAE e-invoicing integration (PINT-AE data model, provider adapter, inbound processing, archive) is scoped into the build at the free scoping session. Your provider's own fees are separate and paid to the provider.
Go-live is 1 January or 1 July 2027. Which is yours?
A free scoping session runs the eight requirements against your current system and gives you a fixed quote for the gap. NDA before technical detail if you want one.