Connect your ERP to everything else you run.

Almost certainly not. The mandate requires invoices to leave as structured data through a service provider the Ministry of Finance has accredited, which is a connection from the finance system you already own to a third party. Replacing the ERP does not remove that requirement and is not a way of meeting it, because the new system will need the same connection. Businesses with annual revenue at or above AED 50 million appoint a provider by 30 October 2026 and go live on 1 January 2027; everyone else follows later. How that deadline sits against the other dated obligations in a year is argued at AI automation in Dubai.

Check the register rather than the sales deck, and the answer is usually that you need one alongside it. Accreditation is granted under Ministerial Decision No. 64 of 2025 and the Ministry of Finance publishes who holds it. A few ERP vendors appear on it, including SAP Middle East and North Africa and Zoho Software Trading, but most systems a business here runs do not. An ERP being described as e-invoicing ready is a product claim about its output format, which is a different thing from being the accredited party that transmits it.

That is the whole service. We build against each system’s documented interface rather than its database, so the ERP is not modified and its next upgrade does not undo the work. What decides the answer is not the ERP but the system on the other side: a bank, a marketplace and a courier all publish something usable, while some warehouse and point-of-sale systems here publish nothing at all. We check every one of them in the first fortnight and name anything out of reach in the scope, in writing, rather than discovering it later, which is the scoping discipline the rest of the AI and automation programme runs on.

Yes, and it has to be designed that way from the start rather than filtered afterwards. Each entity has its own trade licence, its own tax registration and its own invoice sequence, so the separation belongs in the data rather than in a report that groups by a field. Where the two entities sit under different regimes the question goes further than invoicing, and which of your companies may hold a given customer record is argued at custom CRM development.

They are not the same purchase and the figures published on this search are for the other one. An implementation is priced against modules, users and a licence that recurs. An integration is priced against the number of systems, how well each publishes an interface, and how much data has to be migrated and reconciled. That means one connection to a bank is a small piece of work and four connections to systems that expose nothing is a large one, and the scope tells you which you are in before anything is committed. We quote per connection so a second one is a decision rather than a renegotiation.

Usually the tax codes, the invoice fields and part of the chart of accounts. A system set up for a parent company abroad carries that country’s tax treatment and rounding, and 5% VAT tends to be added on top rather than designed in. Corporate tax is a second obligation on the same ledger, at 0% up to AED 375,000 of taxable income and 9% above it, for tax periods from 1 June 2023. There is also a timing rule people miss: a tax invoice is due within 14 days of the date of supply. If you are migrating off a legacy package such as TallyPrime at the same time, that is a data question rather than a tax one, and it is counted before it moves.

It survives, if it was built and documented properly, and this is the first question worth asking any supplier. Connections built against a documented interface keep working across versions; connections written straight to database tables break at the next release, silently, and are usually noticed at a month end. We build against the interface, record the field mappings in your repository, and keep the credentials in your name, so an upgrade is an afternoon of checking rather than a second project. Where the wider brief is a platform rather than a set of connections, that is argued at enterprise software development.