ERP Rescue Consultant, UAE

Recognizing a UAE ERP project that needs rescue

Projects in trouble send signals long before anyone uses the word failure. The difficulty is that each signal on its own looks manageable, and the people closest to the work have every reason to stay optimistic. A rescue starts when someone adds the signals up.

Warning signs worth taking seriously in a UAE rollout:

• Go-live has been postponed repeatedly, with each fresh date announced before anyone fixed what caused the previous slip.
• The VAT return is still prepared in the old package or in spreadsheets, even though the new ERP is meant to be live.
• Arabic invoice layouts, tax invoice fields or the WPS salary file are listed as still in progress.
• The partner raises change requests for work your staff assumed was already paid for.
• The free zone or second entity was postponed to a later phase that has no date.
• Users keep the previous system open in another window because they do not trust the new one.

None of these proves the project cannot succeed. Together they mean the current plan no longer describes reality, and leadership needs an outside view before spending more. That view is what an independent ERP second opinion provides, and it is always the opening step of my rescue method.

Building a factual picture both sides can accept

When I arrive on a troubled project, every party already has its own account of what went wrong. The partner says requirements kept changing; finance says the system was never configured properly; operations says nobody asked them. All of these can be partly true, and none of them helps decide what to do next.

I build a factual picture instead, working remotely and talking to each group separately so people can talk freely:

• What was agreed: the proposal, statement of work, requirement documents and approved change requests.
• What was built: the configuration, custom work, integrations and data loaded, checked directly in the system.
• What works: a short set of end-to-end tests covering a sale, a purchase, a stock movement, a salary run and a VAT report.
• What is needed: the processes the business must run on day one, confirmed with the people who run them.

The gaps between those four views are the real scope of the rescue. I present them neutrally, in the same session, to both your leadership and the partner. Where the commercial position is disputed, I prepare a factual record of scope against delivery for your lawyer to review; legal conclusions about the contract are theirs to draw, not mine.

Stabilizing month-end and the VAT return first

A troubled ERP becomes a business crisis when it threatens a filing or a payment. Before any redesign, the immediate goal is that the business can still invoice, pay staff, close the month and submit its VAT return on time. That is done with your accountant and tax advisor, who remain responsible for what is filed.

Depending on how far the project got, stabilization can take several forms:

• A short, controlled parallel run, where the old package remains the book of record until the new one reconciles.
• Documented manual procedures for specific gaps, such as reverse charge entries on imports, each with an owner and a sign-off.
• Corrections to tax codes or posting rules that are producing wrong figures in the return report, confirmed by your advisor before they change.
• A reconciliation of opening balances, receivables and payables, so the ledger can be trusted again.

Corporate tax adds a second reason for care. Records produced during a messy transition still need to support your tax position, so I keep a clear trail of every adjustment made during stabilization. Your accountant decides how those adjustments are treated. Only once the close is predictable does it make sense to discuss the longer recovery.

Working with the current partner, or moving to a new one

Most rescues are completed with the existing implementation partner. They know the configuration, they have context and switching costs time. What usually needs to change is the baseline: a revised scope both sides accept, clear acceptance criteria, named decision-makers on the client side and a plan that reflects real capacity.

I facilitate that reset as a neutral party. Open items are grouped into must-have for stable operation, can follow later, no longer needed and disputed. Disputed items are resolved from the signed documents and the effect on operations rather than from the loudest voice.

Sometimes the relationship cannot continue. The partner may have lost the people who knew your project, or trust may have gone on both sides. The UAE has no shortage of implementers for each major platform, but any new partner will want its own assessment before committing. A clean handover protects you in that conversation:

• Administrator credentials and ownership of the subscription or hosting account.
• Configuration notes, custom code and integration details.
• Data migration files and mapping documents.
• The open issue list with status and evidence.

Any notice, termination or payment question goes to your lawyer before it goes to the partner.

Choosing between continuing, shrinking scope and switching platform

Once the facts are clear and daily operations are protected, leadership faces a real decision. I lay out the options in a form that makes the trade-offs visible:

Re-platforming is the most expensive answer and the least often justified, so I treat it as a conclusion to be proven rather than a reaction to frustration. The general method is set out on the ERP recovery page. If the system is already live and the concern is performance rather than delivery, an ERP audit for UAE companies is the better starting point. For projects that recover and need steady client-side oversight, see the UAE implementation consultant page or the UAE overview.