ERP Implementation Consultant, Qatar

Why ERP implementations stall in Qatar

Most Qatar ERP projects that run into trouble do so for reasons that were visible early. The common ones are tied to how project-based businesses operate:

• Cost structure designed in a hurry. Cost codes, project phases and budget lines are set up quickly to get configuration moving, then turn out not to match how quantity surveyors and project managers actually report.
• Live contracts ignored until cutover. The plan assumes a clean start, but dozens of contracts are mid-way through, with retention, advances and subcontractor certificates that must carry over.
• Payroll volume underestimated. A workforce spread across sites, with different allowances and overtime rules, takes far more testing than an office payroll.
• Site users left out. Training and testing focus on the head office, so material requests and receipts on site fail in the first week.
• Owner approvals informal. Decisions are made in conversations and never written down, so the partner builds to the last instruction it heard.

None of these are platform problems. They are ownership problems, and they are fixed by someone on the business side who tracks them from the first workshop. That is the role I take. If a project is already well off course, the ERP recovery service is a better fit than ongoing oversight.

Moving live contracts into the new system

For a contractor, the hardest part of data migration is not customers or items. It is the position of every open contract at the cutover point. If those balances arrive wrong, project reports lose credibility from day one and managers go back to their own spreadsheets.

I build a contract migration plan with your finance team and project managers. For each open contract, it lists what has to move:

• Contract value, approved variations and the current budget by cost code.
• Costs to date and committed purchase orders or subcontracts not yet invoiced.
• Amounts billed to the client, retention held by the client and advance payment still to be recovered.
• Subcontractor certificates to date, retention withheld from them and balances due.
• Bank guarantees and their expiry dates.

The extraction from Tally, QuickBooks, Sage, a local package or job cost workbooks is handled by the partner or your IT team. My part is the checking. After each trial load, every project manager confirms their contract position in the new system against their own records, and finance reconciles the totals to the ledger. Only then is the contract signed off for the final load. The ERP data migration page describes the wider method, and ERP for project costing explains the structure those balances need to fit.

Overseeing an implementer who is partly remote

Many Qatar implementations involve a partner whose team is split: a project manager or functional lead in Doha and configuration or development work done elsewhere in the region or abroad. That model can work well, but it makes clear governance even more important, because misunderstandings take longer to surface.

At the start I agree a working rhythm with the partner: a weekly progress meeting, a short steering session with your owners at regular intervals, and a shared space where design documents, the decision log, the risk log and the change register live. Every design decision is written down with the person who approved it, which matters in family-owned businesses where several people can give instructions.

During the build I review the partner's design documents against your requirements and contracts. I ask why something is customized rather than configured, how a workflow behaves when the approver is on site with poor connectivity, and which report a project manager will use each month to review margin. Change requests are logged, estimated and approved by a named owner before work begins.

This does not replace the partner's expertise. It gives your owners a clear, independent view of progress and scope. How I approach implementations in general is set out under ERP implementation, and the Qatar ERP selection page covers how partners are compared before signing.

Payroll, timesheets and WPS at cutover

Payroll is where an implementation touches every employee, and in Qatar the workforce can be large and varied: office staff, site supervisors, skilled trades and general labor, often with different allowances, overtime rules and accommodation arrangements. Salaries are paid through the Wage Protection System, so the salary file must be right first time.

HR, finance, the partner and I treat payroll as a separate track with these checkpoints:

• Employee master data cleaned and checked, including bank details, grades, allowances and project assignments.
• Timesheet capture agreed, whether from site supervisors, a time system or spreadsheets, and tested at real volume.
• Gratuity and leave provisions moved and tied back to the general ledger, with opening amounts agreed by your accountant.
• At least one parallel payroll, compared line by line with the old system before the new one goes live.
• The WPS salary file generated by the new system and validated against the format your bank requires.
• Labor cost allocated to projects correctly, so job costing includes it from the first live month.

The cutover point is chosen between pay periods to avoid splitting a payroll run across two systems. Your HR advisor has the final word on labor law and gratuity rules; my job is to make sure the system follows that guidance and is proven before the first live run.

Testing with site teams and the first live cycle

UAT in a Qatar contracting or service business has to include the people outside head office. I schedule sessions with site engineers, storekeepers, quantity surveyors and approvers, on the phones or tablets they will actually use, working through scripts such as a material request from site, a partial delivery received at the store, a subcontractor certificate approved by the project manager and a progress claim prepared by the quantity surveyor. Results and defects go into one shared log.

Training follows the same pattern. Key users are trained first and then train their colleagues, in whatever languages the workforce needs. Bilingual print templates and any Arabic material are prepared and checked by your team or the partner.

The go/no-go decision rests on agreed evidence: contracts reconciled, payroll parallel run accepted, site UAT passed and support arrangements in place. I help you choose a cutover point that sits at the start of a billing cycle, so the first progress claims are prepared entirely in the new system. Hypercare then runs until those claims, the first subcontractor payments, the first live payroll and the month-end close have all completed.

All of this is delivered remotely, with the engagement in English; on-site days are possible only by arrangement. For the switch-over itself, read about ERP go-live support, or return to the Qatar overview.