Purchase request approval matrix for Cambodia teams
How Cambodia teams can design purchase request approval rules using amount thresholds, roles, budget checks, quotations, and receiving evidence.
A good approval matrix balances speed and control
If every purchase needs five approvals, operations slow down. If purchases skip evidence and budget review, finance and auditors carry the risk. The approval matrix should route only the right decisions to the right people.
Approval rules to define
- Amount thresholds by department, project, or budget owner
- Quotation requirement by category or value
- Finance review for budget availability and coding
- Goods received confirmation before closing the purchase
- Exception path for urgent purchases with post-review
What to keep in the audit trail
The purchase record should keep the requester, approval path, quotation files, selected vendor, budget review, PO reference, and receiving evidence together. That single thread is what makes procurement easier to defend.
How you build the matrix, step by step
An approval matrix is something you configure, not something a vendor decides for you. These are the pieces, in the order you set them up — and each one answers a different question.
- 1Administrator
Define the workflow, then its steps in order
A workflow is an ordered list of steps. Steps run in sequence, and the request sits at exactly one of them at a time — which is what makes "where is it?" a question with an answer.
- 2Administrator
Name a kind of approver, never a person
A step says line manager, department head, budget owner, finance team, or a role — and the actual person is resolved against whoever raised this request. Configure it once and it is correct for every department; name individuals instead and you rebuild it every time somebody is promoted.
- 3Administrator
Attach conditions to decide what happens at that step
A condition on a step evaluates the request — amount, category, procurement method — and resolves to proceed, skip, route to a different step, or reject. This is where the amount bands actually live: as conditions, so a $50 order does not visit the director.
- 4Administrator
Set the sourcing bands separately
How many people approve and how many suppliers must quote are two different questions, so they are configured separately: an amount band sets the minimum number of quotes and whether a formal tender applies. Deliberately independent — a small purchase can need three quotes without needing three signatures.
- 5Administrator
Decide what a step demands before it will accept an approval
A step can require a written comment. The organisation can require every approver to confirm no conflict of interest. Where a probationary manager approves, the step can stay open for their own manager to co-sign rather than closing on one signature.
- 6Administrator
Plan for the exception before you need it
Urgent and sole-source purchases need a route, or people will find one outside the system. Give them a waiver step reached by a procurement-method condition — the approval still happens, it is just recorded as a waiver granted by a named person rather than disappearing into an ordinary approval.
- 7Humaneti
What the auditor gets, without asking anyone
Each decision writes its own record: which step, which approver, the outcome, the comment, the time, and the conflict-of-interest confirmation where one was required. The trail is a by-product of approving, not a report someone assembles afterwards.
A workflow step that names a role nobody currently holds will stop a request rather than skip silently — the system says which step and which role, so the gap is fixed in configuration instead of being worked around.