Can you keep your accounting software for UAE e-invoicing?
Compare a supported vendor route, provider portal, integration and replacement using your actual invoice data, workflows and support responsibilities.
A proposal to replace your accounting system should identify what the current system cannot do. Missing customer identifiers, inaccessible invoice lines and an unsupported connector are different problems. A migration may solve one while leaving the others intact.
Start with the UAE e-invoicing readiness map and a sample of your real billing and purchasing workflows. Then compare the smallest maintainable change that covers those workflows.
Rules checked on 30 September 2026. This article explains operational decisions and is informational, not legal advice. Your tax adviser owns scope and tax classification; software suppliers must demonstrate the route proposed for your installation.
Separate the deadline from the architecture decision
For in-scope businesses with revenue equal to or exceeding AED 50 million, ASP appointment is due by 30 October 2026 and implementation by 1 January 2027, under Decision 66 of 2026. Below AED 50 million, the dates are 31 March 2027 and 1 July 2027 under consolidated Decision 244, Article 5. Confirm your cohort through the deadline and scope worksheet.
Appointment does not establish that your accounting workflow is ready. Conversely, the requirement for an ASP does not by itself justify buying a new ledger. The MoF model allows the business to send data to its ASP in an agreed format; the ASP validates and converts it where necessary. An emailed PDF alone is not an e-invoice.
Diagnose the blocker before choosing a route
Ask finance to trace a normal invoice and a credit note from creation to approval. Where does each field live? Which values are typed into a PDF template but never saved in the underlying record? Use the invoice-data readiness sheet to identify missing data before comparing products.
Then inspect access. Record the exact product, edition, country configuration, installed version, hosting arrangement and custom modules. Ask whether a supported API or export exposes the required records, and whether statuses can return to the place finance checks each day. A product-family logo on a connector page leaves these questions unanswered.
Include purchasing. Decision 243, Article 6 addresses receiving and processing electronic invoices and credit notes as well as issuing them. A sending-only demonstration cannot settle the whole design.
Compare four routes
This matrix is a decision worksheet, not a claim that every provider offers every option. Mark each candidate as demonstrated, pending evidence or unsuitable for your business.
| Route | Consider it when | Evidence to request | Reason to reject it |
|---|---|---|---|
| Supported accounting-vendor route | Your edition has a maintained UAE workflow | Version-specific setup, named ASP, receiving and correction demo | Required scenarios or source systems are outside its supported scope |
| ASP portal or manual entry | Volume and complexity permit controlled manual work | Actual portal workflow, reconciliation method, receiving process | Re-keying creates unmanageable omissions or conflicting records |
| API or file integration | Current records are usable and a maintained interface exists | Field mapping, status writeback, recovery tests, support owner | Essential data or access is unavailable, or maintenance has no owner |
| Accounting replacement | The ledger itself cannot support required records or controls | Migration rehearsal, reconciled balances, historical access, complete acceptance plan | Replacement merely hides an unresolved mapping or ownership problem |
A portal deserves the same scrutiny as a connector. Define which system assigns the invoice number, how finance prevents conflicting versions and how each submitted document reconciles to the ledger. Treat portal feasibility as pending until the ASP and adviser confirm the actual workflow.
Check the existing vendor before commissioning middleware
There are documented and advertised routes worth inspecting first. Zoho Books’ UAE documentation describes sending invoices and credit notes and receiving bills and vendor credits, including draft review for incoming documents. Xero’s UAE page advertises sending and receiving through Invoici and appointment of Casim in EmaraTax.
These sources establish what the vendors describe. Nesaku has not tested these routes for your organisation or demonstrated their coverage of your custom billing. Ask to see your transaction types in the relevant edition. A native route that passes those checks may remove the need for a separate connector.
If invoices originate in a project, clinic or order system, inspect that handoff too. Moving the ledger does not necessarily move the billing source. Decide where an approved invoice becomes authoritative before automating its transmission.
Write a decision that survives the sales meeting
Use one sheet per route, with these fields:
| Decision field | What to write |
|---|---|
| Supported boundary | Exact installation, entities and transaction types |
| Open gap | Missing field, inaccessible record or unsupported workflow |
| Proof | Sample, document version or test identifier showing the claim |
| Delivery cost | Configuration, cleanup, integration or migration work |
| Continuing cost | Licences, ASP service, reconciliation and upgrades |
| Accountable owner | Person who approves changes and supplier who fixes failures |
| Revisit trigger | Failed test, support withdrawal or material workflow change |
The MoF provider-selection guide asks about compatibility, support and pricing. Use written quotes for your scenario, including future mapping changes. Do not compare a portal subscription with an all-in migration quote as if they cover the same work.
Before approval, attach the contract questions and acceptance tests. The broader integrate-or-replace decision guide can help with non-invoicing constraints. If the proposal still cannot identify the blocker, ask Nesaku to review the integration or migration scope before signing.
Sources and review date
Primary sources checked on 30 September 2026: MoF Decisions 244 and 66 for the amended timetable; Decision 243 for invoice and recipient obligations; the MoF programme hub for the agreed-format interface; and its provider-selection guide, version 1.0, dated 23 February 2026. Links appear beside the relevant claims. The selection guide’s URL says 2024; its cover says 2026.
Zoho Books documentation and Xero’s product page were checked on the same date as first-party capability descriptions, not executed test results. Recheck supported editions and contractual scope before purchase.