Multi-Level Purchase Approvals by Amount, Supplier & Branch

Short answer: A multi-level purchase approval system routes each purchase order to the correct approver automatically, based on configurable rules — amount, supplier type, department, or branch. No one needs to decide who should see the PO; the system already knows.

Why Single-Level Approval Breaks Down

Many businesses start with one approver for all purchases. As the business grows, that person becomes a bottleneck. Alternatively, they delegate informally, and suddenly no one is sure who has authority over what.

The typical symptoms:

• The MD approves a RM 300 stationery order and a RM 300,000 raw material order using the same process
• A department head approves a purchase that should have gone to finance first
• A branch in Johor waits three days for KL to approve an urgent local purchase
• No one knows what the actual approval authority limits are — they exist only in someone's head

None of these are unusual. They are the natural result of a business that grew faster than its approval structure.

How a Multi-Level Matrix Works

The approval matrix is a set of rules that the system applies automatically when a PO is submitted. Each rule specifies:

• Trigger condition — amount, supplier category, department, branch, or item type
• First approver — who reviews the PO first
• Second approver — who reviews after the first, if required
• Escalation — what happens if no one responds within a set time

Example matrix for a trading company:

This matrix is configured once. After that, every PO routes itself.

Branch and Entity Separation

For businesses with multiple branches or operating companies, the approval matrix can be scoped per entity. A Penang branch PO goes to the Penang GM first. A Kuala Lumpur branch PO goes to the KL operations head. Cross-branch consolidation is still visible to group finance — but operational approvals stay local.

This is particularly useful for groups running separate AutoCount companies under one holding entity.

Delegation and Absence Handling

An approval system that stops working when the approver is on leave is not a working system. Multi-level approval handles this through:

• Manual delegation — an approver sets a delegate for a defined period
• Auto-escalation — if no response within X hours, the PO moves to the next approver in the chain
• Out-of-office rules — configured in advance, not scrambled at the last minute

What This Removes From Your Day

For the MD or director: you stop seeing every RM 200 purchase. Your inbox shows only what genuinely needs your attention.

For finance: every PO that reaches the payment stage has a documented approval chain. Audits become straightforward.

For operations: purchase requests do not sit in a queue waiting for someone to decide who should approve them.

This fits within a broader workflow automation approach and is part of the full procurement and PO automation system.

FAQ

Can approval rules be changed after go-live?

Yes. The approval matrix is configurable by an admin user. Changes take effect on new POs immediately — existing in-progress POs follow the rules that were in place when they were submitted.

What if a PO needs to be split across two departments?

If a PO contains items from different cost centres, the system can split the approval routing so each department head approves their portion before the PO is finalised.

Can we have different approval currencies — e.g., USD purchases need separate approval?

Yes. Currency can be used as an additional routing condition. A USD purchase above a set equivalent value in MYR can be routed to a different approver than a regular MYR purchase.

Want to stop being the bottleneck for every purchase? WhatsApp us to design your approval matrix.