Contracting ERP Consultant, Qatar

When your contract sits beneath someone else's

On larger Qatar projects, the employer usually contracts with a main contractor on FIDIC-based conditions, and the work is then split into packages: civil and structural works, blockwork and plaster, waterproofing, joinery, facades, landscaping and roads. A contracting business that wins one of these packages signs a subcontract which mirrors the main contract in many respects. Retention, defects liability, program obligations and the payment cycle are often copied down, sometimes with tighter terms than the main contractor itself accepted.

That position creates an ERP requirement many generic systems miss. You need to record not only your own subcontract with the main contractor, but also the relevant conditions inherited from the employer's contract, because they decide when you will be paid and what can be deducted. If you in turn sublet parts of the package, the same logic runs one more level down.

I start by reading through a live subcontract with your commercial manager and listing the terms that drive money: payment period, retention basis, advance terms, set-off rights, back-charge provisions and any pay-when-paid wording. Each becomes a field, a rule or a report in the requirements. Interpreting those clauses is a matter for your legal advisor; my part is making sure the system can hold what they mean.

Advance guarantees, retention bonds and facility headroom

Contracting in Qatar ties up a lot of bank capacity. An advance payment usually needs a guarantee that reduces as the advance is recovered through certificates, a performance bond sits in place until completion or beyond, and some contracts allow retention to be released early against a retention bond. Each instrument consumes part of a facility with your bank, and each one has an expiry date that someone must watch.

Most firms track this in a spreadsheet kept by one person in finance. When that person is away, an extension request can be missed, or a reduction the contract allows is never claimed, leaving facility headroom locked up that the business could use for the next tender.

In the ERP design I link each guarantee to its contract, its bank and facility line, and to the event that should change it: advance recovered, practical completion, end of defects liability. The same register then answers practical questions. How much facility is free today? Which bonds can be reduced once the latest certificate is paid? Which subcontractors still owe you replacement bonds? It is not a complex module, but vendor demonstrations rarely show it, so I make it part of the evaluation scenario.

Site instructions, variations and a paper trail in two languages

Variations on Qatar projects normally begin with a written instruction from the engineer or the main contractor, followed by a priced proposal, review and eventual approval. Between instruction and approval, the work often goes ahead, materials are ordered and subcontractors are mobilized. If the ERP only learns about a change once it is approved, every cost incurred in the meantime looks like overspend on the original scope.

I design a variation record that exists from the first instruction, with its own cost code so spending can be charged to it immediately. The record carries the instruction reference, the submitted value, any revised value and the approved amount, and it links to the matching change issued to each affected subcontractor. Claims for time and additional cost follow a separate notice route, so I keep them in their own register rather than mixing them with agreed variations.

Correspondence with public employers and their consultants is frequently in Arabic, English or both. The ERP does not need to replace your document control system, but it should hold the reference numbers and dates that tie each variation to its letters. I agree that boundary early: the document system keeps the files, the ERP keeps the money, and a clean reference joins them.

Approved vendor lists, local value and a tax position to confirm

Employers and main contractors in Qatar often control who may work on a project. Subcontractors and suppliers may need to be prequalified, appear on an approved list or be accepted through a submittal before they start. In the energy sector, buyers run localization programs that ask about local spending, local suppliers and the national workforce. The questions vary by buyer and change over time, so I describe them in the requirements as outputs the ERP should produce from clean master data, rather than as fixed formats.

That means supplier records need more than a name and bank account: trade license details, insurance cover, approval status per employer and expiry dates for each document. When those fields are kept current, prequalification packs and local value questionnaires stop being a scramble at tender time.

On tax, my understanding is that Qatar has no general VAT in force, so contracting invoices do not show it today. Please have your tax advisor confirm today's position before the design is frozen, and ask them about any withholding or income tax points that apply to payments to foreign parties. I keep tax codes available in the configuration so that a future change can be handled through settings rather than a redesign.

Starting points and where an independent consultant fits

Smaller Qatar contracting firms tend to run on an accounting package, with subcontract registers, variation logs and guarantee lists held in workbooks on shared drives. Larger ones may have a contracting system bought years ago that handles costs well but keeps weak commercial records. Either way, the hardest part of migration is agreeing, contract by contract, the applied, approved, paid and retained figures on both the upstream and downstream side, plus the open value of every guarantee.

I prepare that position with your commercial and finance teams before cutover, using my ERP data migration approach, and I write the requirements through requirements gathering so each vendor responds to the same document. Because I do not resell software or take commission, I can recommend a lighter setup where it is enough.

For the general view of the industry, see ERP for contracting. Firms that act as the main contractor will find more on certificates and site workforce costs on the Qatar construction ERP page, and building services firms can read the MEP ERP page for Qatar. For topics that apply across the country, start from the Qatar hub or my Qatar ERP consulting page.