Skip to content

Insights E-Invoicing

E-Invoicing Software UAE: Is Your Accounting System Ready for the Mandate?

E-invoicing software in the UAE: what your accounting or invoicing system must do under the Ministry of Finance rules, and how to test it before go-live.

E-Invoicing Software UAE: Is Your Accounting System Ready for the Mandate?
E-Invoicing Software UAE: Is Your Accounting System Ready for the Mandate? Photo: Velmont Crest Editorial

Key takeaways

  1. The mandate names no approved accounting package; it requires one Accredited Service Provider and a system that can supply the data
  2. Your system must generate and extract all required data points, and send them to the provider in a format you agree with it
  3. Electronic Invoices are XML with no QR code, so a buyer who is not yet onboarded may still need a separate tax invoice
  4. Inbound invoices and confirmation messages are in scope, so accounts payable needs the integration as much as sales does
  5. Large businesses go live on 1 January 2027; businesses below AED 50 million appoint a provider by 31 March 2027 and go live on 1 July 2027
  6. Test six paths end to end before go-live, then agree an error-resolution model with the provider

If you are shopping for e-invoicing software in the UAE, the first thing to know is that the rules do not hand you a list of approved packages. What the Ministry of Finance accredits is a service provider, and your own accounting, ERP or invoicing system has to work with that provider. This guide sets out what that system must be able to do, what the Ministry’s own documents say about integration and testing, and how to decide whether you need new software at all.

The short answer. UAE e-invoicing is mandatory for any person doing business in the UAE unless excluded. You appoint one Accredited Service Provider, and your system must produce every required invoice data point and exchange it with that provider in an agreed format. The provider converts it to the UAE XML standard and reports tax data to the Federal Tax Authority.

The facts below come from the Ministry of Finance documents listed at the end, which we read directly for this article. Where a point is our own practical view rather than a rule, we say so.

What the mandate actually requires of your software

The legal duty sits on the business, not on the software. Article 6(1) of Ministerial Decision No. 243 of 2025 requires the issuer to issue and transmit an Electronic Invoice for any Business Transaction, and Article 6(7) says issuers and recipients fulfil their obligations through the appointment of an Accredited Service Provider. Nothing in the decision names a mandatory accounting package, and the Guidelines frame compliance as “working with an ASP”.

The Guidelines then put the system question into one sentence in Appendix 1. Every person in scope should carry out a gap analysis of the requirements against its activities and must ensure that its “accounting/ERP/invoicing systems can generate and extract all the data points that are required for Electronic Invoices”, and should plan any data migration that may be needed.

That sentence gives you a four-part test for any system, whether it is cloud accounting software, an ERP, a billing tool or a spreadsheet process:

TestWhat it means in practice
GenerateThe system holds or can calculate every data point the Electronic Invoice requires
ExtractThose data points can leave the system in a structured form, by file, API or connector, not only as a printed or PDF document
Send in an agreed formatYou and your provider settle how invoice data is shared, and the provider converts it to the UAE XML standard if it arrives in another format
ReceiveInbound invoices, confirmation messages and status updates can come back and be matched to your records

Notice what is absent. Nothing says your software must natively write the final XML file. The framework in the Guidelines has the supplier submit invoice data to the provider in an agreed format, and the provider validates it and converts it into the UAE standard XML if it arrived in a different format. That is why the right software question is rarely “is my package e-invoicing compliant?” and usually “can my package give a provider clean, complete data, and can it take the answers back?”.

How the five-corner model shapes the integration

The UAE uses a decentralised model with five corners. The Guidelines describe it this way:

CornerWhoRole in the flow
1Supplier (you, when you sell)Submits invoice data in the agreed format to its provider
2Supplier’s Accredited Service ProviderValidates, converts to UAE XML if needed, sends to the buyer’s provider and reports tax data to the FTA
3Buyer’s Accredited Service ProviderValidates, sends electronic confirmation to Corner 2, passes the invoice to the buyer and reports tax data to the FTA
4Buyer (you, when you purchase)Receives the invoice in a format agreed with its provider
5Federal Tax AuthorityReceives tax data reported by the providers

Two things follow for software. First, you never connect your system to the FTA directly. Your integration point is your provider. Second, you are Corner 1 on sales and Corner 4 on purchases, so the same system, or two different ones, has to handle both directions. Many businesses run billing in one tool and payables in another, and both ends need a defined path to the provider.

For the network side of how a document physically travels, our Peppol e-invoicing explainer covers the exchange layer, and the UAE e-invoicing guide covers scope, exclusions and the rollout in full.

What your invoice data has to look like

The content of an Electronic Invoice is set by the Peppol PINT-AE billing specifications, which the Guidelines point to, and the Ministry has published a separate document listing the mandatory fields. You do not need to memorise the specification to judge a system, but you do need to know which parts of it catch finance teams out. The Guidelines add several specific points.

Point from the GuidelinesWhy it matters for your system
Electronic Invoices are XML with no QR code or barcodeA template that prints a QR code is no longer the compliance artefact
Tax category is a mandatory field for each transactionFree-text or missing VAT treatment in your item or line setup will fail validation
You may not add your own optional fields to PINT-AECustom fields on your invoice that you assumed would travel with it may not; discuss industry-specific needs with the provider
Multiple payment dates go in the “Invoice Terms” fieldInstalment terms need a place to be captured as text in a structured field
A different date of supply goes in the “VAT Point Date” fieldYour system needs a date of supply separate from the issue date
HSN codes are currently optionalNo rush, but the Guidelines say the timeline for making them mandatory will be announced
For exports where the buyer has no Peppol ID, the predefined endpoint 0235:9900000099 must be includedYour export invoices need that endpoint populated automatically

The specification itself is published by Peppol and the Ministry updates its Guidelines, so treat any field list in an article, including this one, as a pointer and check the current Ministry documents before you build.

Identifiers: seller and buyer

Appendix 6 of the Guidelines clears up how businesses are identified, and it is where many customer masters fall short.

PartyRule in the Guidelines
Seller registered for VATThe 15-digit VAT Tax Registration Number goes in IBT-031
Seller not registered for VATThe 10-digit Tax Identification Number (TIN) goes in IBT-032; a Corporate Tax TRN must not be put in IBT-031
Either wayOne of IBT-031 or IBT-032 must be provided, under PINT-AE rule IBR-177-AE
Buyer Identifier (IBT-046)Optional by default, but mandatory where rule IBR-135-AE conditions are met, whether or not the buyer is VAT registered
Buyer Legal Registration Identifier (IBT-047)Conditional; mandatory where the Invoice Type Code is 480 (out of scope of VAT) or 81 (credit note related to goods or services), under rule IBR-136-AE

The TIN itself is a unique 10-digit identifier and, for businesses already registered with the FTA, the first 10 digits of the 15-digit TRN. Your system needs a place to store both, and the buyer-side identifiers need to be captured when you create the customer, not when you raise the invoice. A customer record with no tax identifier is a likely gap, and no provider can fill it for you.

If you are reviewing how your chart of accounts and item master feed those fields, our walkthrough of PINT-AE field mapping to a UAE chart of accounts goes through the accounting side line by line.

The document types your software must handle

The Guidelines set out four document types, each with a standard and, for tax documents, a self-billed 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

The Guidelines also state that there is no Electronic Invoice category for provisional invoices. Every provisional invoice issued should be an Electronic Invoice, and adjustments are made by issuing an Electronic Credit Note or an additional Electronic Invoice. If your billing tool lets staff print a “pro-forma” or “provisional” document that you never book as an invoice, that habit has to change. Our guides to pro-forma invoices and self-billing rules set out where the lines fall.

Credit notes deserve their own test. Article 6(2) of MD 243 of 2025 requires an Electronic Credit Note where a 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 matters because routine billing corrections now become structured documents sent through the system, and a system that lets users overwrite or delete an issued invoice is working against the process.

Do you need new software? Three realistic positions

Your answer depends on what your current system can already do. This section is our practical view, not a rule, and it rests on the Guidelines’ requirement that your system can generate and extract the data and, where needed, integrate with the provider.

PositionSigns you are hereLikely route
Structured system, data is cleanCustomer tax identifiers complete, tax codes are set per item, invoices come out of the system rather than a word processorAgree format and connector with the provider, then test
Structured system, data is dirtyThe software is capable but customer records, tax categories and credit-note habits are inconsistentFix master data first; the software may need only configuration
Documents made by handInvoices built in spreadsheets or documents, numbered by hand, no structured data behind themMove invoicing into a system that holds structured data, or accept that the provider must be fed from something

The middle row is the most common. Remediation is cheaper than replacement and it has to happen under every option, because a new system loaded with the old data inherits the same errors. The Guidelines say as much in Appendix 1, where data migration is called out as something to plan for.

If you are choosing or replacing an accounting package for reasons beyond e-invoicing, our overview of accounting software for UAE small businesses covers the wider selection criteria. For e-invoicing, add the questions below.

Questions to put to any software vendor

These are questions to ask, not answers we are asserting about any product. A vendor’s reply is a claim, so ask for the reply in writing and for a live demonstration against your own invoices.

QuestionWhat a good answer shows
Can it generate every mandatory data point, including tax category, seller and buyer identifiers and date of supply?Field-by-field coverage against the current Ministry list
Which providers does it already connect to, and by what method (API, file, connector)?Named providers, a method, and who maintains the connection
Can it receive inbound Electronic Invoices and confirmation messages?A defined inbound path, not sales-side only
How does it handle an invoice the provider rejects?A visible error queue, a correction route and an audit trail
Does it block editing or deleting an issued invoice and force a credit note?Credit-note-only correction after issue
How are specification updates delivered?Who updates it when PINT-AE changes, and how quickly
Where is invoice data stored, and can you export it?An export route that supports your retention duty

On specification updates, the Guidelines say providers must stay informed of updates and use the latest version when exchanging invoices, and that the person should work with the provider to address changes in legislation, technology and technical specifications. If your own software lags the provider’s version, the gap is yours to close.

Choosing the provider and the software together

The Ministry’s separate document, Considerations for Selecting an Accredited Service Provider (version 1.1, dated 28 October 2026), puts integration at the top of the integration-and-data-management section. It asks whether the provider has “the necessary functionalities to seamlessly integrate with your current ERP/accounting/invoicing systems”, and tells businesses to inquire about APIs, data formats and integration support.

That makes the provider the other half of the software decision. A provider with a ready connector for your system removes most of the integration work. A provider that offers only file upload or its own portal leaves you with a manual step that has to be built into the close. For the full set of provider questions the Ministry raises, see our e-invoicing guide to selecting a provider, which sets out the accreditation model under Ministerial Decision No. 168 of 2026, effective from 1 October 2026.

Three constraints shape the choice:

  • One provider. The Guidelines say a person must appoint only one provider for both sending and receiving. Your sales and purchase flows cannot be split across two.
  • Accreditation status is checkable. The Ministry publishes the register of accredited providers on its e-invoicing pages. Check it on the day you sign, not from a list in an article.
  • Tax Groups onboard member by member. Each member has its own TIN and its own Peppol participant identifier, and members may use different providers. A group on one shared system may therefore need one integration feeding several onboarded entities. Our guide to e-invoicing for VAT groups covers the flow, and Ministerial Decision No. 197 of 2026 excludes transactions between members of the same Tax Group for 24 months starting from 1 January 2027.

The timeline your software project works back from

Dates come from Ministerial Decision No. 244 of 2025, as amended by Ministerial Resolution No. 66 of 2026.

GroupAppoint provider byImplement by
Revenue equal to or exceeding AED 50,000,00030 October 20261 January 2027
Revenue below AED 50,000,00031 March 20271 July 2027
Government entity31 March 20271 October 2027

Voluntary and pilot use has been open since 1 July 2026, and the Guidelines encourage early onboarding so that you can test without the risk of penalties. Business-to-consumer transactions are not subject to the system, and a person engaged exclusively in such transactions is not subject to it, until a date determined by a ministerial decision. A newly established business has no phase-in at all and must be onboarded before its first invoice.

If your business is at or above AED 50 million and has not appointed a provider, the date for appointment has passed and the go-live is about six weeks away, so the software work is now a compressed project. Our phase 2 readiness plan for businesses below AED 50 million shows how to lay the same work out over the longer runway.

A practical way to use the dates: work back from go-live. The provider needs onboarding via EmaraTax, a participant identifier and test cycles, and your system needs configuration and integration before those tests can start. The Guidelines say onboarding is started by you, not the provider, from the E-INVOICING tile in EmaraTax.

The readiness steps, mapped to your system

Appendix 1 of the Guidelines gives four steps. Here is what each means for the software side.

Guidelines stepSoftware tasks
1. Understand requirementsGap analysis of data points against what your system can extract; list invoice categories per revenue stream; plan data migration
2. Select an ASPConfirm integration method; contract and commercial terms; onboarding via EmaraTax; obtain Peppol participant identifier
3. Test exchange and reportingAgree how invoice data is shared, how confirmations arrive and how inbound invoices are received; integrate; reconfigure approval workflows
4. Go liveGovernance model with the provider for error resolution; monitor exchange and reporting

After go-live there is an ongoing duty. If your circumstances change, for example you register for VAT, join or leave a Tax Group, deregister or close down, the Guidelines say you should promptly update your provider via EmaraTax. Row 4 of the Cabinet Decision No. 173 of 2026 penalty table covers failing to notify the provider of changes to data registered with the Authority, so your software’s customer and entity master should have an owner who watches for those changes.

The Ministry’s readiness checklist, items that touch software

Appendix 2 of the Guidelines lists 17 readiness questions, which the Guidelines do not number. Counting them in the order they appear, five bear directly on your system:

Position in listQuestion in the Guidelines
4Have you identified the data points required on an Electronic Invoice and ensured your accounting or ERP systems can extract them?
10Have you agreed how invoice data will be transmitted to and from your provider?
11Have you agreed how you will receive confirmation messages on exchange and reporting?
13Have you completed the changes to your ERP or accounting applications to generate the necessary data points?
14Have you completed any necessary integrations between your ERP or accounting applications and your provider’s systems to send and receive invoice data?

The thirteenth and fourteenth items depend on the fourth, tenth and eleventh being settled. Settling the data-flow agreements before the configuration work is our suggested order, not the Ministry’s, because the integration method can change how the configuration should be done.

Testing: six paths, not two

The Guidelines list what testing must cover, and the list shows how much of the project is not about sending invoices.

#Path to testDirection
1Transmitting invoice data to the providerOutbound
2The provider issuing the invoice to the buyerOutbound
3Receiving confirmation of success or failure of the exchangeOutbound
4Receiving an Electronic Invoice that a supplier issued to you through the providerInbound
5The provider reporting the required Tax Data to the FTAReporting
6Receiving confirmation of success or failure of the Tax Data reportingReporting

Build a test set from your own history rather than from clean examples. Include a zero-rated export, a tax-exempt supply, a credit note, an advance-payment invoice, a multi-currency invoice and a customer with no tax identifier, because those are the cases where data points go missing. Our guides to export and zero-rated formats and multi-currency invoices cover the treatment of those cases.

Retail and point-of-sale businesses should read our POS integration guide before deciding where the connection sits, because business-to-consumer sales sit outside the system for now while any business-to-business sale at the same till does not.

Who owns what

The Guidelines divide the responsibilities in Appendix 3, and the division clarifies which part of the software work is yours.

PartyResponsibility that touches your systems
You (Person)Verify company details in EmaraTax, complete contract and onboarding, decide how invoice data is sent, complete customisations to in-house systems, test transmission, ensure confirmations are received for all tax data reported
ProviderOnboard you to the Peppol network, work with you on integrations and customisations, provide the participant identifier, exchange documents, report tax data to the FTA, use the latest specification
FTARegistration, TINs and TRNs, onboarding via EmaraTax, analysis of invoice data for audits and fraud detection
Ministry of FinanceFramework, standards, accreditation of providers, monitoring compliance

The line to notice: the provider works with you on integrations, but the customisation of in-house systems and the receipt of confirmations are yours. A provider contract that treats integration as “customer responsibility” has not moved the work off your desk, it has told you whose desk it is on.

Records, storage and the data your system must keep

Article 11 of Ministerial Decision No. 243 of 2025, as replaced from 1 October 2026, requires you to retain all Electronic Invoices, Electronic Credit Notes and associated data for the period prescribed under the Tax Procedures Law and to keep them capable of being produced to the Authority on request. The requirement to store the data within the State was removed in that replacement.

Appendix 4 of the Guidelines adds four clarifications that affect where your archive sits.

PointWhat the Guidelines say
DelegationA provider may store invoices for you if agreed contractually, but this does not transfer the Article 11 obligation; you remain responsible
Storage layerNo requirement to store at a particular layer, provided retention period, integrity, security and availability to the FTA are preserved
Provider logsProviders keep transactional logs with unique identifiers for the end-to-end cycle; those logs are not the business-document data you must retain
ConfirmationsProviders must tell you, on an event basis and without undue delay, when invoices or tax data have been successfully transmitted to the Authority

The retention period for VAT and accounting records is five years under Article 3(1)(a) of the Tax Procedures Executive Regulation, and corporate tax records are kept for seven years under Article 56 of the Corporate Tax Law. FTA Decision No. 4 of 2026 separately requires that records are complete, legible and accessible to the Authority on request, including access to the system in which they are saved, and says a third party may maintain records but you remain legally responsible. Our guide to financial record keeping in the UAE sets out how those rules interact.

For software, that means two checks. Can your system export issued invoices, credit notes and their data in a form you can produce on request? And if the provider stores them, does your contract let you retrieve them for the full retention period, including after you leave the provider?

Timing, penalties and why software choice affects them

Article 6(5) of MD 243, as replaced from 1 October 2026 by MD 197 of 2026, requires issue and transmission within 14 Business Days of the Date of Business Transaction. That is subject to Article 6(4), which makes a VAT registrant issue and transmit within the timeline prescribed by the VAT Law, so for a registered business the VAT deadline governs and the 14 Business Days is the outer limit.

A system that batches invoices overnight, or that depends on a person to click “send” at month end, can fail that test without anyone noticing. Our guides to tax invoice requirements and the 2026 tax invoice format cover the VAT timing side.

The penalty schedule is annexed to Cabinet Decision No. 173 of 2026, which repealed Cabinet Decision No. 106 of 2025.

#ViolationPenalty
1Issuer or recipient fails to implement the system under MD 244 of 2025, including failure to appoint a provider; or a recipient that implemented fails to keep complying with its recipient obligationsAED 5,000 for the first instance, then AED 5,000 per month or part month while it continues, total capped at AED 50,000 in any 12 consecutive months
2Issuer fails to issue and transmit an Electronic Invoice through the systemAED 100 per invoice, capped at AED 5,000 per calendar month
3Issuer fails to issue and transmit an Electronic Credit Note through the systemAED 100 per credit note, capped at AED 5,000 per calendar month
4Issuer or recipient fails to notify the provider of changes to data registered with the AuthorityAED 250 per day or part day, capped at AED 5,000 per calendar month

The decision does not apply to a person who issues, transmits, shares, exchanges or reports on a voluntary basis, and where the same person is issuer, recipient or both for the same violation, only one penalty is imposed. The system link is plain: rows 2 and 3 are triggered by invoices your software did not get through, and row 1(b) by a recipient process that fell over after go-live. These penalties sit alongside the ordinary VAT and tax procedure penalties and do not replace them.

Where software projects go wrong

These are patterns we expect to see based on the Ministry’s own checklist and test list, offered as practical risks, not statistics.

  1. Fixing the invoice template and nothing else. The mandate is about structured data, so a better-looking PDF is not progress.
  2. Leaving customer master data for last. Missing or mistyped tax identifiers stall every later step.
  3. Building the sales path and forgetting the purchase path. Inbound invoices, confirmations and approval workflows are named in the Guidelines.
  4. Allowing edits to issued invoices. Corrections have to travel as credit notes and replacement invoices.
  5. No named owner for the provider relationship. The Guidelines expect a governance model for error resolution before go-live.
  6. Trusting a vendor’s “compliant” label. Ask which providers it connects to, by what method, and who maintains it when the specification changes.
  7. Ignoring the separate-invoice problem. A buyer not yet onboarded may still need a non-XML tax invoice, which the process has to accommodate for a time.

How Velmont Crest can help

Velmont Crest is a UAE accounting and advisory firm for small and medium businesses. On e-invoicing we work on the accounting side of the project: the data-point gap list, customer and item master clean-up, tax category mapping, test cases drawn from your own invoices and the month-end reconciliation between your ledger and the provider’s confirmations. We are an advisory firm and not a government body, and we do not select or accredit providers. Provider accreditation and the register are the Ministry’s.

Our e-invoicing setup advisory page sets out the scope, and the related VAT services, bookkeeping and accounting and accounts receivable and payable management pages cover the processes that feed and receive the invoices. If you want a view on whether your current system is enough, get a free quote.

Sources

The rules in this article come from the Ministry of Finance and the Federal Tax Authority. Check the current versions before acting, since the Guidelines and specifications are updated.

Frequently asked questions

Do I need new accounting software for UAE e-invoicing?
Not necessarily. The Ministry of Finance rules require you to appoint one Accredited Service Provider, and the Guidelines say your system submits invoice data to that provider in an agreed format, which the provider converts to the UAE XML standard if needed. What your current system must do is generate and extract every required data point. If it cannot, you either change its configuration, add an integration or replace it.
Which accounting software is approved for UAE e-invoicing?
The rules do not approve accounting software. What the Ministry accredits is the service provider, and it publishes the register of Accredited Service Providers on its e-invoicing pages. Any statement that a specific accounting package is government approved should be checked against the Ministry's own pages and the provider's accreditation status, not taken from a software vendor's marketing.
Can I keep using Excel or Word to invoice?
The rules do not name a tool, but every Electronic Invoice has to carry the prescribed data fields and reach the Ministry's system through your provider. Whether a spreadsheet can do that depends on whether you can supply the required data points in a format your provider accepts. Ask your shortlisted providers directly, in writing, which input formats they take.
Does the e-invoicing mandate apply if I am not VAT registered?
Yes. The Ministry of Finance Guidelines say all Persons who make a Business Transaction in the UAE are within scope notwithstanding their VAT registration status, unless a transaction or person is specifically excluded. A business not registered for VAT identifies itself with its 10-digit Tax Identification Number.
Does my software need to produce a QR code?
No. The Guidelines state that Electronic Invoices are issued, transmitted and received in XML format and will not feature a QR code or barcode. A buyer that has not yet implemented e-invoicing may still ask for a separate tax invoice or commercial invoice to support input tax recovery, so your process may need to produce both for a period.
Can I use more than one e-invoicing provider?
No. The Guidelines say a Person within scope must appoint only one Accredited Service Provider for both sending and receiving invoices, and should onboard with only one provider for all its e-invoicing requirements. Members of a Tax Group are the exception in one sense: each member is onboarded individually with its own TIN and may choose a different provider.
Does accounts payable have to be connected too?
Yes. Article 6(3) of Ministerial Decision No. 243 of 2025 requires the recipient to process Electronic Invoices and Electronic Credit Notes through the system, and the Guidelines list receiving a supplier's invoice from your provider among the paths to test. Row 1(b) of the Cabinet Decision No. 173 of 2026 penalty table reaches a recipient that implemented and then failed to keep complying.
Who stores the e-invoices, my software or the provider?
Either can, but the legal duty stays with you. Appendix 4 of the Guidelines says a provider may store invoices on your behalf where contractually agreed, that delegating does not transfer the Article 11 obligation, and that there is no required storage layer provided retention, integrity, security and availability to the FTA are preserved.
How long must I keep e-invoices?
Article 11 of Ministerial Decision No. 243 of 2025, as replaced, points to the period prescribed under the Tax Procedures Law. For VAT and accounting records that is five years under Article 3(1)(a) of the Tax Procedures Executive Regulation, and corporate tax records are seven years under Article 56 of the Corporate Tax Law. Confirm the period that applies to your own records.
What happens if my system cannot issue an invoice in time?
Article 6(5) of Ministerial Decision No. 243 of 2025, as replaced from 1 October 2026, requires issue and transmission within 14 Business Days of the Date of Business Transaction, but a VAT registrant is held to the timeline in the VAT Law under Article 6(4). Cabinet Decision No. 173 of 2026 sets AED 100 per missed invoice, capped at AED 5,000 per calendar month.
When must my business be ready?
Under Ministerial Decision No. 244 of 2025 as amended by Ministerial Resolution No. 66 of 2026, a business with revenue of AED 50 million or more implements by 1 January 2027. A business below AED 50 million appoints a provider by 31 March 2027 and implements by 1 July 2027. Government entities implement by 1 October 2027. Voluntary use has been open since 1 July 2026.
Is a newly formed company exempt from the phase-in?
No. The Guidelines say a newly established Person within scope must appoint an Accredited Service Provider and complete onboarding before issuing its first invoice, irrespective of its date of establishment. Any invoice it issues must be an Electronic Invoice, so the invoicing tool has to be chosen with that in mind from day one.

Filed under: e-invoicing software, invoicing software UAE, PINT-AE, Accredited Service Provider, accounting system, ERP integration, Peppol, UAE compliance

Published · Updated