ERP Audit Consultant, Qatar

An ERP audit for a market without VAT

In VAT countries, a system review often starts from the tax return because it forces every invoice through a known structure. Qatar has not introduced VAT, so there is no quarterly return quietly testing your data. Errors in coding, approvals and project allocation can sit unnoticed for a long time, until a contract closes with a loss nobody saw coming.

That changes the focus of an ERP audit here. The central question is whether the system tells the truth about contracts, cash and people. Tax still matters: depending on who owns an entity, corporate income tax may apply, and some payments to non-resident suppliers can attract withholding. I do not assess either. Where the ledger structure or supplier data might affect them, I record the observation for your tax advisor.

It is also worth being clear that this review sits apart from your statutory audit. Your auditor forms an opinion on the financial statements; I look at configuration, data and controls inside the ERP and give no opinion on the accounts. The two can support each other, because a cleaner system means fewer audit queries, but neither replaces the other. The general method is set out on the ERP health check page; the sections below describe what it looks like for a Qatar business.

Testing whether contract figures hold up

I choose a small set of contracts with your finance lead, ideally one profitable, one marginal and one recently closed, and trace them through the ERP from award to the latest payment. The aim is to see whether the system's view of each contract matches the paperwork and the project manager's understanding.

The trace covers:

• Budget and cost codes: whether the contract budget is loaded at the level costs are recorded, so variances mean something.
• Commitments: whether open purchase and subcontract orders appear against the contract before invoices arrive.
• Billing: whether each payment application, approved amount, variation and advance recovery is recorded against the right contract.
• Retention: whether retention receivable and payable are tracked per contract in the ERP, or reconstructed in a spreadsheet at the end.
• Guarantees: whether performance and advance payment guarantees, and their expiry, are visible to finance.

Where the ERP and the spreadsheet disagree, I establish which is right and why the other drifted. The findings show which contract controls work and which exist only on paper. If the platform itself cannot support the costing depth you need, the job costing solution page explains the options.

Labor cost, timesheets and the WPS file

For many Qatar businesses, labor is the largest and least visible cost. Site workers, drivers and technicians may be employed by one entity, accommodated in shared camps and deployed across several contracts in a month. If the ERP cannot follow that movement, labor cost is either spread evenly or left in overheads, and contract margins become guesses.

The labor review checks how hours are captured, whether the same timesheet feeds both payroll and job cost, and how indirect costs such as accommodation, transport and visas are allocated. I compare a sample month across the timesheet source, the payroll register and the job cost reports to see whether they tell the same story.

Then I look at payroll output. Qatar requires wages to go through the Wage Protection System, and the ERP or payroll tool should produce the salary file your bank accepts. I check whether the file is generated directly, whether anyone edits it by hand before upload, and who can change employee bank details, basic pay or allowances. Manual editing of a salary file is both an error risk and a control weakness, and it can often be removed by correcting a few configuration details. Rules on pay and end-of-service remain with your HR and legal advisors.

Approvals, procurement and user access

Project businesses spend money in many places at once. A site engineer raises a request, a buyer issues an order, a storekeeper receives goods and finance pays the supplier. Each handoff is a control point, and in a busy Qatar contractor some of them are quietly skipped to keep the site moving.

The access and procurement review asks practical questions:

• Can a single user create a supplier, raise an order and approve the payment?
• Are approval limits set by value and by contract, and can they be bypassed by splitting an order?
• Is goods receipt recorded at site before invoices are matched, or entered later by finance from delivery notes?
• How is site petty cash issued, spent and cleared, and does it reach the right contract?
• Are there generic logins for sites or stores, or active accounts for staff who have left?
• Who can reopen a closed period or change cost codes on posted transactions?

I test these against the configuration and against real documents, not just against policy. Where perfect segregation is unrealistic for a lean team, the report suggests compensating checks, such as a monthly exception report reviewed by the owner or finance manager, so control improves without slowing the site.

Spreadsheets, licenses and a ranked set of findings

Every spreadsheet that sits beside the ERP tells you something. A retention tracker, a labor allocation sheet or a cash flow file built from exports exists because someone needed information the system did not give them. I list these files, find out who maintains them and why, and decide with you whether each one points to a configuration gap, a training issue or a genuine platform limit.

I also review what the business pays for. User licenses are compared with active users, unused modules are noted, and links to banks, attendance devices or an outside payroll tool are tested for errors nobody is told about.

The final report ranks every finding by business risk and effort to fix. Each one shows the evidence, why it matters, the likely cause and the recommended action. Items your own staff can fix, items for your implementation partner and decisions for the owner are separated, and tax-related observations are listed for your advisor. I present the findings in a remote session. Where the report calls for improvement work, ERP optimization is the next step; if a rollout is still unfinished, the Qatar ERP rescue page fits better. For the wider market view, see the Qatar overview and Qatar ERP consultant page.