ERP Business Analyst in Riyadh

Turning Riyadh approval habits into an authority matrix

Ask a Riyadh finance manager how a large purchase gets approved and the answer usually starts with a rule and ends with exceptions. Above a certain level it goes to the general manager; certain categories always go to the owner; a committee meets for major contracts; when the approver is traveling, someone else signs. None of that is unusual, but an ERP cannot route approvals on goodwill and memory.

A good first deliverable for many Riyadh organizations is a delegation of authority matrix. It lists each type of decision, such as purchase requests, supplier contracts, customer discounts, credit limits, payment releases and write-offs, and shows who requests, who reviews, who approves and who stands in when that person is unavailable. Limits are recorded by your finance team in your own terms.

Building the matrix surfaces disagreements early. Two department heads may each believe they own the same approval, or a committee may exist on paper but never meet. Settling those questions before configuration is far cheaper than discovering them when purchase orders sit unapproved after go-live. Once agreed, the matrix becomes a direct input to workflow design, and it is useful to your auditors whatever platform you choose.

Mapping processes across a city of long distances

Riyadh businesses are rarely in one place. A distributor may run its sales and finance teams from Olaya or King Fahd Road, its main warehouse in one of the industrial areas toward the south or east, and delivery vans crossing the city all day. A contractor may be managed from one district while its active sites sit in the new northern neighborhoods. A clinic or retail group may have branches spread across districts that are an hour apart in traffic.

Processes break at the points where these places meet: a delivery note that comes back from site days later, a stock transfer recorded in the warehouse but not at the branch, a site purchase made in cash and reported at month end. Those handoffs are what my process maps focus on.

Because I work remotely, I ask your staff to record short walk-throughs on location: a storekeeper explaining how goods are received, a site engineer showing how materials are requested, a branch supervisor demonstrating the end-of-day routine. Combined with photos of the actual forms, these give a truer picture than a meeting-room description. The ERP process mapping service explains the mapping notation I use.

Interviewing everyone, not only the managers

Riyadh teams are often a mix of Saudi managers, Arabic-speaking supervisors from across the region and staff from South Asia and elsewhere who work mainly in English. If requirement sessions include only senior managers, the BRD records how management believes the work happens, which is rarely how it actually happens on the warehouse floor or at the branch counter.

I plan interviews at three levels: leadership for goals and policy, supervisors for exceptions and approvals, and clerks or storekeepers for the daily routine. The engagement runs in English. Where an interviewee is more comfortable in Arabic, a bilingual colleague from your team joins to interpret, and any Arabic wording that ends up in the requirements comes from, or is checked by, native speakers on your side.

I keep sessions short and focused, record the main points in a shared document during the call, and send a summary the same day so people can correct it while the detail is fresh. That habit matters more in a busy capital office, where the same people are juggling several priorities and may not have time for a long review later. The ERP requirements gathering page describes the interview method in general terms.

Stamps, signatures and documents that still travel on paper

Many Riyadh businesses still run part of their work on stamped and signed paper. Customers may expect a company stamp on a quotation or delivery note, suppliers may send signed invoices, and government-facing correspondence often follows formal letter conventions. A requirements document that ignores this produces a system that people work around.

For each key document, I record what it is, who issues it, who signs or stamps it, where the original is kept and whether the other party will accept a digital version. Some documents can move into the ERP as digital approvals with the scanned original attached. Others must still be printed, stamped and filed, and the requirement is then about producing them correctly from the system and tracking their return.

Where a question touches legal validity, for instance whether an electronic approval replaces a wet signature for a particular contract type, I note it as an open item for your legal advisor rather than answer it myself. The BRD then records the decision once it is made. This part of the analysis tends to be quick, but skipping it is one of the more common reasons a new system ends up running alongside a filing cabinet.

Separating group rules, Saudi obligations and local habit

A requirements register for a Riyadh organization usually mixes three kinds of item. Some come from a parent group or head office policy. Some come from Saudi obligations such as tax, e-invoicing or labor reporting. Others are simply how the business has always worked. All three look the same on a list, but they deserve very different treatment.

I tag each requirement with its source and, where relevant, who confirmed it. A Saudi obligation is noted as confirmed by your tax or legal advisor, not by me. A group policy points to the policy owner. A local habit is marked as such, which lets the steering group ask a useful question: is this a requirement, or something we should change now that the system is being replaced?

This tagging changes vendor conversations. Bidders can see which items are fixed and which are open to their standard approach, and it narrows the customization they propose. The national e-invoicing scenarios themselves are detailed on my Saudi Arabia ERP business analyst page. For the wider Riyadh context, including regional headquarters reporting, see the Riyadh ERP consultant page, or contact me to plan the workshops.