Every purchase, expense, travel or contract request routed to the right approver and recorded with a timestamp, in Arabic and English.

In many Saudi companies an approval is a WhatsApp voice note from the owner, which cannot be found when the auditor, the bank or ZATCA asks who authorised a payment. Odoo Approvals gives each request type its own form, approver chain and required fields, logs every decision with a comment and timestamp, and hands approved purchase requests to Purchase, which is why Naqlah, an Odoo Gold Partner in Saudi Arabia, maps your delegation of authority matrix into it during a governance push.
Request forms and notifications render in Arabic and English, so a branch supervisor submits in Arabic and finance reviews in English on the same record. Approver chains mirror how Saudi companies actually sign off: supervisor, department head, finance, then the owner or GM above a threshold, matching the delegation of authority matrix a family group or a PIF portfolio company already holds. Each decision keeps its timestamp and comment, ready for internal audit, a ZATCA query on a Zakat or VAT return, or a board review, and Naqlah links HR request types to Time Off so leave and contract changes are approved before anyone touches Qiwa or Mudad.
Delegation of authority
Thresholds, sequences and minimum approvals follow your DoA matrix line by line. Changes to the matrix are documented in configuration rather than remembered.
Mobile approvals
Owners and GMs approve from the Odoo app while travelling, with the attachments in hand. Reminders escalate requests that sit too long.
Audit trail
Full history exports to PDF or Excel for auditors. Requester and approver are separated by design, which supports segregation of duties for Zakat and VAT audits.
1. Request submitted
The branch manager submits a purchase request from the mobile app with the amount, the vendor, the product and a quote attached.
2. Chain runs
Operations approves first, then finance when the amount is above the threshold, with the requester's manager added automatically.
3. Purchase order created
The approved request is converted into a purchase order in Odoo Purchase, with the approval reference carried on the order.
4. History kept
The request, comments, timestamps and attachments remain linked for internal audit, and the vendor bill later reconciles against the approved amount in Accounting.
Timelines depend on scope, and Naqlah gives you a clear roadmap in the first consultation.
| Area | Before | With Odoo via Naqlah |
|---|---|---|
| Request channel | WhatsApp message, voice note or email | Typed form with required fields and attachments |
| Approver | Whoever replies first | Defined chain with sequence and minimum count |
| Evidence | Screenshots searched when the auditor asks | Timestamped log with comments on the request |
| Thresholds | Remembered by the finance team | Amount based routing per request type |
| Follow through | Purchase order typed again by hand | Purchase order created from the approved request |
| Reporting | None | Cycle time and bottlenecks per approver |
Everything else, we cover in a free 30-minute consultation.
Free consultation. Meet the team and get a clear roadmap in one call.