ERP Business Analyst in Qatar

Scoping requirements when tax is not the main driver

There is, as far as I know, no broad VAT regime operating in Qatar at present, even though the wider Gulf has debated one at length. Tax positions can move, so confirm today's rules with Qatar's tax authority and your own advisor before the design is frozen. For requirements work, this changes the emphasis rather than removing tax from the picture.

Corporate income tax can apply to some entities depending on ownership and activity, and certain payments to non-residents may carry withholding obligations. Neither is something I advise on. What I do is ask your advisor the questions that shape the system, then record the answers as requirements:

• Which legal entities need separate books, and which activities sit in each one.
• How costs shared between entities or joint arrangements are allocated and evidenced.
• Which supplier payments need to be flagged for review by your tax team.
• What audit trail your external auditors expect on journals, approvals and changes to master data.

I also add a short set of flexibility requirements: tax fields on customers, suppliers and items that can be activated later, and invoice layouts that can take extra lines without a redesign. That keeps the system ready if the position changes. How those settings are then built is something I handle as your ERP consultant in Qatar.

Tenders, guarantees and payment applications as requirements

Many Qatar contractors and suppliers work for government ministries, semi-government companies or main contractors delivering public projects. Those clients ask for a lot of paperwork, and much of it lives outside any system today. When I map the contract lifecycle, I separate the documentation requirements from the accounting ones so neither gets lost.

Typical requirements I write for this kind of business include:

• A register of bid, advance payment and performance guarantees with issuing bank, value, expiry date, renewal alerts and the contract each one secures.
• Prequalification and compliance documents held against the company and each project, with owners and review dates.
• Interim payment applications prepared from measured progress, submitted to the client, revised after the engineer's review and then invoiced at the approved value.
• Retention tracked on client contracts and subcontracts separately, with release conditions recorded.
• Variation orders logged from instruction to approval, so unapproved work is visible as a risk.

These requirements usually decide which platform fits far more than the general ledger does. My ERP process mapping page explains how I draw these flows, and the ERP for construction article gives wider background.

Workforce, camps and WPS: requirements on the labor side

For many Qatar businesses, labor is the largest cost and the most fragile data set. Contracting, MEP, facility management and manpower supply firms may have most of their people on sites or in shared accommodation, paid through the Wage Protection System. If employee records are inconsistent, salary files get rejected and project labor cost ends up allocated by hand.

In the requirements, I cover where each piece of data is created and who owns it: employee master data and document expiry dates, allowances and deductions, attendance captured on site, overtime approval, and the transfer of approved hours to both payroll and job costing. I also ask how accommodation, transport and visa costs are recovered against projects, because owners often want them in project margins but rarely see them there today.

Whether payroll will sit in the ERP, a separate HR system or with a provider is a decision I record explicitly, with the integration it implies. The current WPS file format should be confirmed with your bank. The resulting requirement set feeds straight into ERP requirements gathering and later into test scripts.

Remote discovery with Qatar owners and teams

Requirements work in Qatar starts with the owner or managing partner, because they usually hold the commercial rules that never made it into a procedure. I then interview finance, commercial and operations leads separately, followed by the people who handle documents every day: storekeepers, timekeepers, document controllers and accounts staff.

Sessions are booked online inside Qatar working hours, Sunday through Thursday, avoiding month-end valuation dates and adjusting for Ramadan hours. Some staff are more comfortable in Arabic, Hindi, Urdu or another language, so I keep questions short, work from real documents such as payment certificates and delivery notes, and use colleagues to interpret where needed. Arabic output requirements, such as bilingual invoices or letters to government clients, are flagged on each document in the BRD.

I do not have a presence in Qatar and do not travel there by default; an on-site visit is possible only by prior arrangement. After every workshop you receive a written summary, and each unresolved point carries the name of whoever will close it. For the structure of the final document, see ERP BRD consulting, and for my wider work in the country, the Qatar overview.