Nabeel Al Nassir
November 3, 2026
9 Min read
UAE e-invoicing is the Ministry of Finance and Federal Tax Authority requirement for businesses to issue, exchange and report invoices as structured PINT AE files through an Accredited Service Provider on the Peppol network. It goes live from 1 January 2027 for businesses with revenue of AED 50 million or more, from 1 July 2027 for everyone else, and from 1 October 2027 for government entities, with ASP appointment deadlines before each go-live date.
This guide is the starting point for the whole topic. It explains who is in scope, how the phases and deadlines work, what the technical model looks like, what penalties apply, and what an ERP or billing system has to do before its go-live date. Each section links to a deeper Pixbit guide where the detail is longer than an overview should carry.
An e-invoice in the UAE is not a PDF sent by email. It is a structured, machine-readable invoice built to the PINT AE specification, which is the UAE version of the Peppol International invoice model and is based on UBL 2.1 XML. The invoice is generated in the supplier's system, passed to the supplier's Accredited Service Provider, validated and signed, sent to the buyer's Accredited Service Provider, and reported to the Federal Tax Authority. The buyer receives data their own system can read directly, and the tax authority receives the same data close to real time.
The rules sit in a set of Ministerial Decisions issued in 2025 and 2026 and in Cabinet Decision No. 106 of 2025, which sets the penalties. The scope covers business-to-business and business-to-government transactions. Business-to-consumer invoices are outside the initial mandate, although a business that sells to both other businesses and consumers will still need its system to tell the two apart and route each one correctly.
For most companies the change is less about tax and more about software. Invoice data that used to be loosely formatted now has to meet a fixed schema with mandatory fields, code lists and validation rules, and every invoice has to travel through an external provider before it counts as issued.
The mandate is phased by size and by sector, and each phase has two dates: the date by which a business must appoint an Accredited Service Provider, and the date from which e-invoicing becomes mandatory.
Businesses with annual revenue of AED 50 million or more are in the first phase. Under Ministerial Decision No. 66 of 2026 they must appoint an Accredited Service Provider by 30 October 2026, and e-invoicing is mandatory for them from 1 January 2027. Pixbit's ASP appointment guide covers how to choose and contract a provider for this deadline.
Businesses with revenue below AED 50 million are in the second phase. They must appoint an Accredited Service Provider by 31 March 2027 and go live from 1 July 2027.
Government entities follow their own track, with ASP appointment by 31 March 2027 and mandatory e-invoicing from 1 October 2027. Suppliers to government need to watch both their own phase and the date their government buyers start receiving e-invoices.
A voluntary pilot has been open since 1 July 2026 for businesses that want to test their integration before their mandatory date. Using the pilot window is the most practical way to find data quality problems while there is still no penalty attached to them.
The UAE uses a five-corner model built on the Peppol network. The first corner is the supplier's system, usually an ERP, accounting package or billing platform. The second corner is the supplier's Accredited Service Provider, which validates the invoice against PINT AE rules, applies the required signature and sends it over Peppol. The third corner is the buyer's Accredited Service Provider, which receives the invoice. The fourth corner is the buyer's own system. The fifth corner is the Federal Tax Authority, which receives the tax data reported by the service providers.
The important point for developers is where responsibility sits. The business does not connect directly to the tax authority. It connects to its Accredited Service Provider, usually through an API, and the provider handles the Peppol exchange and the reporting. That means the business owns the quality of the invoice data and the integration with its provider, while the provider owns the network transport and the signature.
PINT AE defines the fields, the code lists and the business rules each invoice must pass. Seller and buyer identifiers, tax registration numbers, line-level tax categories, currency and exchange rate handling, credit note references and payment terms all have specific requirements. An invoice that fails validation is rejected by the provider, and a rejected invoice has not been issued. The developer-level detail of the format and the provider API is in Pixbit's guide to PINT AE and Peppol API integration.
Cabinet Decision No. 106 of 2025 sets out the administrative penalties. A business that fails to implement e-invoicing or fails to appoint an Accredited Service Provider by its deadline faces a penalty of AED 5,000 for each month of non-compliance. Failing to issue an e-invoice when one is required carries a penalty of AED 100 per invoice, capped at AED 5,000 per month. Failing to notify the authority of a system failure that prevents e-invoicing carries a penalty of AED 1,000 for each day of delay.
The per-invoice penalty is the one that most affects system design. A business that issues thousands of invoices a month can reach the monthly cap quickly if its integration silently fails, so monitoring rejected and unsent invoices is a compliance control rather than a reporting extra.
Most of the work sits in the invoicing system rather than at the provider. The system has to produce every mandatory PINT AE field from its own data, which often means cleaning customer master records, adding missing tax registration numbers, mapping internal product and tax codes to the official code lists, and handling edge cases such as discounts, prepayments, mixed-rate invoices and credit notes that reference an original invoice.
It also has to manage the invoice lifecycle. An invoice is created, sent to the provider, validated, accepted or rejected, delivered and reported. The system needs to store the status at each step, retry failed submissions, show rejected invoices to the finance team with the reason, and keep the signed version for audit. Pixbit's guide to UAE e-invoicing requirements for ERP systems works through these requirements in detail.
Businesses on mainstream ERP platforms will usually rely on a connector or add-on from the vendor or the provider, but configuration and data mapping still fall on the business. Businesses running custom billing software, industry platforms or several systems across group companies typically need a custom integration layer that collects invoice data from each source, maps it to PINT AE, sends it to one provider and returns the status to each source system.
E-invoicing also touches corporate tax. The same invoice data feeds revenue recognition and audit trails, so the integration is a good moment to check that the accounting system can support the records the Federal Tax Authority expects under corporate tax, which is covered in Pixbit's guide to corporate tax software in the UAE.
The order of work matters more than the speed. The first step is confirming the phase and both deadlines that apply, including for each legal entity in a group. The second is appointing an Accredited Service Provider, because the provider's API and onboarding process shape everything after it. The third is a data gap analysis that compares current invoice data against PINT AE mandatory fields and lists every missing or badly formatted value. The fourth is building or configuring the integration and the status handling. The fifth is testing with real invoice samples, ideally in the voluntary pilot, before the mandatory date arrives.
For businesses in the first phase, the ASP appointment deadline falls on 30 October 2026, so the remaining work now sits between appointment and the 1 January 2027 go-live. For businesses in the second phase, there is still time to run the full sequence calmly, and starting early leaves room to fix master data properly instead of patching it at the last minute.
E-invoicing is one of several government connections a UAE business system may need. Property platforms connect to Dubai Land Department services, healthcare platforms connect to health information exchanges, and many customer-facing apps use UAE PASS for identity. Pixbit's UAE government API integration guide maps these together, and the government API integration services page explains how Pixbit builds and maintains them as one integration layer.
E-invoicing in the UAE is the requirement to issue business-to-business and business-to-government invoices as structured PINT AE files, sent through an Accredited Service Provider on the Peppol network and reported to the Federal Tax Authority, instead of as paper or PDF invoices.
It becomes mandatory from 1 January 2027 for businesses with revenue of AED 50 million or more, from 1 July 2027 for businesses below that threshold, and from 1 October 2027 for government entities.
An Accredited Service Provider is a company approved by the UAE authorities to validate, sign and exchange e-invoices on the Peppol network on behalf of businesses and to report invoice data to the Federal Tax Authority. Every business in scope must appoint one.
Under Cabinet Decision No. 106 of 2025, failing to implement e-invoicing or appoint an Accredited Service Provider costs AED 5,000 per month, failing to issue an e-invoice costs AED 100 per invoice up to AED 5,000 per month, and failing to report a system failure costs AED 1,000 per day.
In most cases yes. The ERP must produce every mandatory PINT AE field, map internal codes to official code lists, connect to the Accredited Service Provider and track each invoice's status, which usually needs configuration, data cleanup or a custom integration layer.
Pixbit builds e-invoicing integrations for UAE businesses running custom billing platforms, industry software and multi-entity ERP setups, covering data mapping, provider API connection, status tracking and audit storage. Costs sit in a broad AED band that depends on the number of source systems and invoice volume, and Pixbit scopes e-invoicing integration in a single discovery session.
Digital Marketer
Share on
Have an idea that needs to go mobile? Launch it with us!
Let's Talk
Explore insightful articles and tips from our experts on the latest trends in web development and marketing.
Tell us your business aspirations, and let's craft a custom solution that drives business growth, ensuring satisfaction and exceeding your goals with precision.
Let's Talk
