Digital Approval Workflows for Purchases, Leave and Expenses
A digital approval workflow works when it encodes your delegation-of-authority rules: who approves what, up to which amount, in what order, who stands in when someone is away, and what happens if nobody acts. Keep chains short, route requests by amount, type and branch, let approvers act from their phones, and record every step. Make sure nobody approves their own request or pays what they approved. Start with purchases, because that is where money moves, then add expenses and leave.
Software is the easy part. The hard part, and the part most companies skip, is writing the rules down before anyone builds anything.
The short answer
- Write the delegation matrix first: request types, amount bands, approvers, and deputies.
- Every approver must add a check. If a step only forwards the request, remove it.
- Plan for absence: named deputies with date ranges, and automatic escalation when a request waits too long.
- Approve from anywhere, with a notification that links straight to the request.
- Separate duties: requester, approver and payer are different people, and every action is logged.
- Connect to accounting and HR, so an approval triggers the next step instead of a re-typed form.
“Most approval chains aren’t slow because of the people in them. They’re slow because nobody wrote down who decides when the usual person isn’t there.” — Abdulqader Wahiba, founder and CEO of ZAWAT
Start with a delegation-of-authority matrix
Before choosing any software, write a table of who may approve what. A simplified illustration for a company with three branches might look like this:
| Request | Amount | First approval | Second approval | Deputy when absent |
|---|---|---|---|---|
| Purchase request | Below OMR 500 | Branch manager | None | Assistant branch manager |
| Purchase request | OMR 500 to 5,000 | Branch manager | Finance manager | Operations manager |
| Purchase request | Above OMR 5,000 | Finance manager | General manager | Deputy general manager |
| Expense claim | Within policy | Line manager | Finance check | Department head |
| Leave | Any | Line manager | HR (balance check) | Department head |
The amounts and roles here are examples, not a recommendation; yours should reflect your business and your risk appetite. What matters is that the table exists, that it is agreed by the people who hold the authority, and that the system follows it exactly. Mapping the process before you buy software is the right way to find out how approvals really flow today.
Design rules that keep requests moving
Keep chains short
Each approver should check something specific: budget, policy, need or price. If a step adds nothing but a signature, remove it. Long chains do not add control; they spread responsibility until nobody really owns the decision.
Plan for absence
The approval that stalls when a manager travels is the most common failure in manual chains. Give every approver a named deputy, let them set their own out-of-office dates, and route requests automatically during those dates.
Escalate when nobody acts
Set a time limit for each step. When it passes, the system reminds the approver, then escalates to the deputy or the next approver up. A request should never wait silently in someone’s inbox.
Let people approve from anywhere
Most approvers will act from their phones. Send a notification with a direct link to the request, its attachments and the approve or reject buttons. If your team lives on WhatsApp, notifications can go there through the WhatsApp Business API, with the approval itself recorded in the system.
Require reasons and attachments
Purchase requests carry quotes; expense claims carry receipts; rejections carry a reason. That saves the back-and-forth that slows most approvals down.
Controls: separation of duties and an audit trail
Approvals exist to control money and risk, so the system must enforce the basics:
- Nobody approves their own request, including through a deputy arrangement.
- The approver is not the person who pays. Finance releases payment against an approved request.
- Every action is logged: who requested, who approved or rejected, when, from which device, and with what comment. Access control and audit trails covers the design.
- Changes to the matrix are themselves approved and logged, because changing a limit is a way of approving everything below it.
Connect approvals to what happens next
An approval should trigger the next step automatically, not prompt someone to re-type a form:
- Purchases: an approved request becomes a purchase order in your accounting or ERP system.
- Expenses: an approved claim goes to finance for reimbursement, with the receipts attached. Tax invoices supporting VAT claims must be kept for ten years under Article 70 of the VAT Law, fifteen for real estate, so store them properly.
- Leave: an approved request updates the leave balance and feeds payroll. HR and payroll systems in Oman covers the payroll side.
Electronic approvals and signatures also raise questions of legal validity and record-keeping. Electronic signatures and records in Oman explains what the 2025 Electronic Transactions Law means for your systems.
When the system decides automatically
Some requests can be approved by rules alone, such as leave within the balance in a quiet period, or purchases from an approved catalogue below a small limit. That speeds things up, but take care where the decision concerns people. Under Oman’s Personal Data Protection Law, as amended by Royal Decree 68/2026, a person has the right to object to decisions resulting from automated processing, and a human must be involved when reviewing them. Keep a clear route for a person to look again at any automatic rejection.
Where to start
- Purchases first. They carry the most risk and usually the most delay. Abdulqader Wahiba recommends starting there for that reason: it is where money and waiting meet.
- Then expenses, which share much of the same logic.
- Then leave, which connects to HR and payroll.
Each can be its own small first version, as scoping the first version recommends. Measure the time from request to approval before and after; it is usually the clearest sign of success.
Frequently asked questions
Do we need a full ERP system to digitise approvals? No. Approvals can be a focused system or a module connected to your existing accounting and HR tools. What matters is that approved requests flow into those systems without re-typing.
Can approvals happen over WhatsApp? Notifications can, and that helps speed. The approval itself should be recorded in the system, with the request, attachments and audit trail, rather than as a chat message that cannot be audited later.
How many levels of approval should a request have? As few as give real control. One level for small, routine requests and two for larger or riskier ones is common. Each extra level should add a specific check.
What about urgent purchases? Define an urgent route in the matrix: who can approve urgent requests, within what limit, and with what follow-up review. Without one, people will bypass the system whenever something is urgent.
Are electronic approvals legally valid in Oman? Electronic records and signatures are recognised under Oman’s electronic transactions law, with conditions. Electronic signatures and records in Oman sets out the details; take legal advice for high-value or regulated approvals.
Sources: Personal Data Protection Law, Royal Decree 6/2022, as amended by Royal Decree 68/2026, Article 14 · Value Added Tax Law, Royal Decree 121/2020, Article 70
This article states the position under the laws in force on 9 November 2026, the date of publication, and is not legal advice.
Are your approvals still running on signatures and WhatsApp? ZAWAT builds business systems that follow your delegation rules and connect to your accounting and HR. Book a call.