ERP Rescue Consultant, Qatar

Why a Qatar ERP rescue centers on live contracts

Most ERP recoveries can be planned from the finance office. For the contracting, fit-out, MEP and facility services firms this page is written for, the real exposure sits in contracts that are running right now. A troubled rollout tends to hurt them in specific ways:

• Opening contract positions were migrated incompletely, so cost to date, billing and retention no longer match the project files.
• Site requests and goods receipts stopped flowing because site staff were not trained or lack access.
• Subcontractor balances are disputed because deductions and retention were not carried over correctly.
• Payroll was moved over at the same time, and labor cost has not reached the right contracts since.
• The implementer has delivered the accounting core but not the project module the business actually bought the system for.

Each of these makes the next payment application or the next cash forecast harder to prepare, which is why leadership often notices the problem through cash before anyone calls the ERP a failure. The rescue has to deal with that business exposure first and the software second. The general approach is set out on the ERP recovery page; what follows is how it applies to a Qatar business with work in progress.

First steps: payments in, payments out and payroll

The opening days of a rescue are about protecting cash and people. I sit down remotely with finance and the project managers to list what must happen in the coming weeks regardless of the state of the ERP, and to decide for each item whether the new system can handle it now, needs a controlled workaround, or should temporarily stay in the old tool.

Typical items on that list:

• Payment applications: each live contract's next application, with the values agreed against the project file, even if the ERP is not yet the source.
• Subcontractor and supplier payments: a clear basis for what is due, so payments are neither delayed nor duplicated.
• Salary run: confirmation that the next WPS file can be produced and checked, with a fallback if it cannot.
• Purchasing on site: a simple route for urgent requests that still records them against the right contract.

Every workaround gets an owner, a record and a planned end, so it can be reversed into the ERP later. Once these basics are secure, pressure drops and the diagnosis can proceed calmly. Anything with a legal or tax dimension, such as disputed subcontract amounts or withholding on foreign suppliers, goes to your lawyer or tax advisor.

Repairing job cost and retention data

Contract data is usually the hardest part of a Qatar recovery, because it combines finance, procurement and site records that were often held in different places before the ERP. Repair work starts from the project files, not the system, and works contract by contract.

For each live contract I help your team rebuild a reference position: approved budget by cost code, committed orders, cost to date, amounts billed and approved, variations, advance recovered, retention held and retention owed to subcontractors. That position is then compared with what the ERP shows, and each difference is classified as a migration error, a posting error, a configuration gap or a timing difference.

The fixes follow the classification:

• Migration errors are corrected with documented adjustments approved by finance.
• Posting errors are reversed and re-entered with the right contract and cost code.
• Configuration gaps go to the implementer with the evidence and a priority.
• Timing differences are noted and checked again at the next month-end.

Closed or nearly finished contracts may not be worth migrating in detail at all; a summary balance can be enough. Deciding where detail matters is part of the repair plan, and it keeps recovery effort away from history nobody will consult.

Working with an implementer who is partly remote or has moved on

Some ERP implementers serving Qatar run delivery from teams in other countries, with a smaller group in Doha. That model can work well, but when a project goes wrong, the distance makes it easy for issues to drift between people. Part of the rescue is restoring a single line of accountability.

If the implementer remains engaged, I organize a reset with them. Open items are sorted into those essential to run contracts and payroll, those that can follow later, those no longer needed and those in dispute. The implementer names who will do the work and when, and acceptance is defined by tests your staff can run. Disputes are judged against the signed documents and the effect on the business.

If the implementer has withdrawn or the relationship cannot continue, the focus shifts to securing what you own: administrator access, hosting or subscription control, configuration and custom code, migration files and the issue history. A replacement partner will want to assess the system before committing, and a clean handover pack makes that faster and cheaper.

Notice periods, retentions held against the implementer and payment disputes are matters for your lawyer. I provide a factual summary of scope against delivery to support their advice, and I stay neutral in how the facts are described.

Continue, re-scope or re-platform for a Qatar business

With operations secured and contract data repaired, owners can decide what happens next. I prepare a short options paper rather than a recommendation alone, so the reasoning is visible.

Continuing suits a platform that handles your core contract, procurement and payroll needs once specific gaps are closed. Re-scoping suits a project that tried to go live with every module at once; a stable core of finance, procurement and contract billing can go first, with plant, HR or service management following in later phases. Re-platforming suits only a product that cannot carry the costing depth or the labor volumes your business needs without fragile custom work.

For a project-based business, timing also matters. Switching systems mid-way through major contracts means migrating live positions twice, which raises the risk of errors in exactly the data owners care most about. Sometimes the right answer is to stabilize the current system now and plan a change around natural breaks in the contract cycle.

If your system is live but simply not trusted, an ERP audit in Qatar is a lighter starting point. For ongoing client-side oversight after recovery, see the Qatar implementation consultant page, the contracting industry page or the Qatar overview.