Business Process Consultant, UAE

Owner-led approvals and a delegation of authority

In many UAE businesses, especially family groups and founder-run companies, the owner still approves a large share of decisions personally. That works while the company is small. As it grows, purchase requests, supplier payments and customer discounts start to queue behind one person, and managers learn to work around the queue with phone calls and verbal approvals that leave no record.

A delegation of authority is the process answer. I start by listing every decision type that actually reaches the owner or the general manager, then agree with leadership which of those can move down a level, under what conditions and with what evidence. The result is a written matrix that covers, for example:

• purchase approvals by category and value band, described without hard-coding figures into the narrative;
• credit limit changes and customer discounts;
• supplier payments, including who releases a check or a bank transfer;
• hiring, salary changes and visa sponsorship decisions;
• contracts and quotations above a normal size.

Where the group has free zone and mainland companies, the matrix often differs by entity, because authorized signatories and bank mandates differ. I record those differences rather than forcing one rule. The owner keeps the decisions that truly need them, and everything else moves with a clear trail. Later, the same matrix becomes the basis for approval workflows in whatever system you choose.

PRO work, visas and renewals as a real process

Trade license renewals, establishment cards, employee visas, labor contracts and medical insurance are a constant stream of work in any UAE company with staff. In many firms this sits with a PRO, an outside typing center or one administrator, and the process exists mainly in their head and their email.

Mapping it as a process changes the conversation. A typical hire-to-pay map in the UAE does not start with payroll. It starts with an offer, moves through visa and permit steps, onboarding, bank account setup and the first salary, and returns to the PRO desk at every renewal and at exit. When it is drawn out, the weak points become obvious: documents requested from employees several times, expiry dates tracked in a personal spreadsheet, fines caused by renewals that nobody owned, and a final settlement that depends on someone remembering the steps.

In the redesign I agree who owns each step, which documents are collected once and stored in one place, what triggers a renewal and who checks it is complete. The rules themselves come from the authorities and your PRO, and I do not interpret them. My part is making sure the work is visible, owned and handed over properly. The same map also shows where salary data must be ready for the WPS file, so payroll and the PRO desk stop working from different versions of the employee list.

Order to cash with post-dated checks and VAT steps

Order to cash in the UAE often has steps that generic templates leave out. Customers may pay by post-dated check, by bank transfer against a statement, or by a mix of both. Sales teams sometimes collect checks themselves. Credit decisions are made on relationships rather than on a written policy. Each of these is workable, but only if the process says who does what.

When I map the flow, I follow a real order from quotation to cash in the bank and mark every step where information changes hands. Common findings include:

• checks received by sales staff and handed to accounts days later, with no register in between;
• no agreed step for a returned check, so follow-up depends on the salesperson;
• credit holds lifted by phone without a record;
• tax invoices raised before delivery is confirmed, then credited and reissued.

The future design places each control at the natural point: a check register at receipt, a deposit schedule owned by finance, a defined path for returns, and a clear rule for when the tax invoice is issued. Your tax advisor confirms the VAT treatment and timing; I make sure the process supports whatever they advise and that the steps are the same in every branch. That design is then ready to be tested against an ERP, which is where the ERP business analyst work takes over.

Procurement, contracts and retention in project businesses

Contractors, fit-out firms and MEP specialists in the UAE run a procure-to-pay process that is really a project process. Material requests come from site, purchase orders are raised against a budget that may not be visible to the buyer, deliveries arrive with notes that do not match the order, and subcontractor certificates move between site, the commercial team and accounts before anyone pays.

Retention is where these gaps show most. Amounts retained from subcontractors and retained by your own client need to be tracked against the contract terms until release, and in many firms that tracking lives in a commercial manager's spreadsheet. When the person changes roles, the history goes with them.

I map procure to pay and the project delivery flow together, from tender handover to final account, with the contract as the reference point. The future design typically defines:

• who can raise a request against which budget line;
• how goods receipts are confirmed at site and matched before payment;
• how subcontractor certificates are reviewed, approved and recorded;
• who tracks retention and what triggers a release request.

I describe the commercial process and leave contract interpretation to your legal and commercial advisors. For sector context, the UAE construction ERP page covers the system side once the process is agreed.

Bilingual documents, remote workshops and what comes next

Many UAE processes produce documents in English and Arabic: tax invoices, delivery notes, employment paperwork and letters to authorities. The engagement runs in English, and any Arabic wording in procedures, forms or templates is drafted or reviewed by your own staff or a local partner. I mark on each map which documents need a bilingual version, so that requirement is not discovered late in a software project.

The work is remote. Each session is a video call with the people who do the job, not only their managers, and I draw the maps live so mistakes are corrected on the spot. Visits are possible only by arrangement. Maps, the delay log and the delegation matrix sit in shared documents your team keeps after the engagement.

Software comes after the process is agreed. When the design is settled, there are usually three possible next steps:

• use your existing systems better, with no new purchase;
• remove manual steps with targeted automation, which my UAE business automation page explains;
• move to a new ERP or CRM, using the maps as the basis for requirements and selection, as described on the UAE ERP consultant page.

I take no commissions from software vendors, so the recommendation can honestly be to change nothing but the process. The global business process consulting page describes the method in more detail.