ERP Implementation Consultant, UAE

Where UAE ERP implementations usually slip

Few UAE implementations fail outright. More often they go live late, with a narrower scope than planned and a backlog of workarounds that finance carries for months. The causes are rarely technical. They are patterns I look for from the first week:

• Design by default. Owners and managers are too busy for workshops, so the partner configures what is typical for the platform rather than what the business does.
• Group structure left vague. The decision on how many companies, branches and cost centers to create is made quickly, then reversed after reports are built on it.
• Migration treated as a final task. Nobody cleans the customer, supplier and item lists until the last weeks, so the first trial load fails and testing shrinks.
• Payroll split off. HR and WPS are handled in a separate stream that is never tested end to end with finance postings.
• Arabic documents left to the end. Bilingual invoice and delivery note templates are built in the final days and checked by nobody who reads Arabic.

Each of these is preventable with clear ownership and early checks. My job is to make the risk visible while it is still cheap to fix. Where a project already shows most of these symptoms, the ERP recovery route may suit better than routine oversight.

Overseeing the partner from the client side

A good UAE partner welcomes an organized client counterpart, because it shortens decisions and reduces disputes. I agree that working rhythm with the partner's project manager at the start: who attends which sessions, how design decisions are recorded, how change requests are raised and approved, and what evidence closes each phase.

From then on, I review each design document against your requirements and ask the questions your team may not think to ask. Why is this a customization rather than configuration? What happens to this workflow when the approver is on leave? Which report will finance use for the VAT return, and has your accountant seen it? If a change estimate seems out of line with the work described, I request the detail behind it.

I keep a single log of decisions with its date, its reason and whoever signed it off. In a UAE family business where several owners and managers can say yes, that log prevents a lot of rework. I also keep a change register, so you can see how scope is moving against the signed statement of work.

None of this replaces the partner's expertise on the platform. It makes sure their expertise is pointed at your business. The wider method is described on my ERP implementation page, and if the partner is still undecided, the UAE selection page explains how I compare them.

Free zone, mainland and family-group setups

Many UAE businesses are not one company. A family group may hold a mainland trading business, a separate free zone company handling re-exports, a contracting arm and a property holding company, each with its own trade license, bank accounts and sometimes its own tax registration. The ERP has to reflect that structure without making daily work harder for the people who use it.

During implementation I check the decisions that are expensive to reverse:

• Which legal entities become separate companies in the system, and which are better as branches or departments.
• How intercompany sales, recharges and loans post on both sides, and how they are eliminated for group reporting.
• Which master data is shared across companies, such as items and suppliers, and which stays separate.
• How users who work across several companies are given access without seeing what they should not.
• Which currency each company reports in and how group figures are translated.

The tax position of each entity, including how free zone status interacts with VAT and corporate tax, is for your tax advisor to confirm. I make sure the setup can capture what they need. Platforms handle multi-company structures differently, and the multi-company ERP page explains the main patterns.

Migrating from Tally, QuickBooks, Sage and spreadsheets

UAE businesses arrive at a new ERP from a wide mix of systems: Tally in many owner-run traders, QuickBooks and Sage in service firms, a local accounting package in some contractors, and spreadsheets almost everywhere for stock, jobs and commissions. Each source brings its own problems.

Tally ledgers are often organized around how the accountant thinks rather than how the new chart of accounts is designed, so mapping needs care. QuickBooks files may hold years of customers that should not be migrated. Spreadsheet stock lists rarely agree with the ledger value. Older packages sometimes cannot export open documents cleanly.

I do not run the extraction scripts, which belong to the partner or your IT team. What I own from your side is the migration plan and the checks:

• A list of what moves: masters, open items, balances and how much history.
• Clean-up owners for each list, with deadlines before the first trial load.
• Reconciliation after every trial: the trial balance account by account, open customer and supplier items, stock by location and value, VAT control accounts.
• Written sign-off by the data owner before the final load.

For detail on the method, see ERP data migration. For a business moving from QuickBooks specifically, migrating from QuickBooks covers the common traps.

Testing, cutover and hypercare in a UAE go-live

The go-live decision should rest on evidence, not on the date announced to staff. I agree the criteria with your sponsor well before cutover: end-to-end UAT passed for each process, trial loads reconciled, key users trained, integrations tested and a rollback position understood.

UAT scripts for a UAE business include the cases that hurt most after go-live: an import with reverse charge, a credit note that crosses a period, an intercompany sale, a supplier payment in another currency, a salary run whose WPS output is validated against the format your bank or exchange house requires, and the reports your accountant uses to prepare the VAT return. Once the national e-invoicing program applies to your business, issuing and transmitting a test invoice through the chosen connector belongs on the same list.

Timing matters. I help you choose a cutover point with your accountant that avoids clashing with a VAT return or a payroll run, and plan the final load so opening balances and stock can be agreed quickly. Once live, a short daily call with key users and the partner reviews new issues, separating training needs from defects and change requests, and I stay with finance through the first close in the new system.

All of this is delivered remotely; any on-site day is by arrangement. More on that final stage is on the ERP go-live support page and in the UAE ERP consultant overview.