How do I set up purchase request approval routing by department, amount, and category?

The budget owner is the one non-negotiable approver: they're accountable for the money. Add the manager only when they bring information the budget owner lacks (is this person's request legitimate?). Add finance selectively - above thresholds, for new vendors, or where coding and budget questions need expert eyes - not on every request. Three-plus approvers on routine purchases is how approval becomes theater.

A typical mid-market pattern: requester's manager or budget owner up to a low threshold (e.g., $1K - $5K); department head or director to a mid threshold (e.g., $10K - $25K); VP/finance leadership above that; CFO for the largest commitments (e.g., $50K+). Calibrate so 80% of requests clear in one or two steps, and set thresholds at natural risk breaks in your spend distribution rather than round numbers borrowed from a template.

Rubber-stamping is usually a context problem: approvers see a name and an amount, so a click is all they can contribute. Give them the decision context in the approval itself - what's being bought and why, remaining budget including pending requests, the quote, prior purchases from the vendor. Then reduce the volume: raise thresholds so approvers only see requests worth their judgment. An approver who sees five well-contextualized requests a week reads them; one who sees fifty reads none.

The defined path a request travels for sign-off - who must approve, in what order, under what conditions - enforced automatically rather than decided ad hoc per request.

Trigger them by category or form answers: selecting "software" inserts IT review, a contract attachment inserts legal. Conditional steps keep specialist review where it's relevant without taxing every purchase.

Sequential when later approvers should benefit from earlier decisions (manager validates need before finance reviews budget); parallel when reviews are independent (IT security and budget owner) and you want to compress cycle time.

Use delegation with an audit trail (delegate acts, record shows both names), mobile/email approval so travel doesn't block decisions, and escalation rules that reroute after a defined wait.

Automated reminders first, then escalation to an alternate or the approver's manager after your SLA lapses - with the escalation logged. The existence of escalation usually fixes behavior before it ever fires.

More than two for routine spend, more than three or four for anything. Each layer should add a distinct decision; layers that exist "for visibility" should be notifications instead.

Block self-approval in the system: requests route to the next level up (or a peer reviewer) whenever requester and approver would be the same person. This is a standard audit finding waiting to happen - close it structurally.

They should be able to - approval friction is the top cause of cycle-time complaints. Look for actionable notifications with enough context to decide, not just a link to a login page.

Set change rules: increases beyond a tolerance (percentage or dollar) re-route through the chain, with the delta highlighted; trivial changes proceed with a logged note. Silent post-approval edits are the loophole auditors look for.

Keep them philosophically aligned (same thresholds, same accountability logic) but recognize the procurement approval is the real spend decision - invoice approval then becomes largely a confirmation that what arrived matches what was authorized.

Maintain the matrix as a controlled document and demonstrate the system enforces it: auditors will sample transactions and trace each to a timestamped approval consistent with the matrix. System-enforced routing turns this from an interview into a report.

Correct the rule, document the exception (what happened, why, whether the spend was ratified by the right approver), and keep both in the trail. One-off exceptions with documentation are normal; silent corrections are findings.

Split the request across budget lines and route to both owners - each approves their share. Avoid the "one owner approves, we'll true it up at allocation" pattern; that's how shared costs become disputed costs.

Stampli routes procurement documents - purchase requests, POs, service tickets - through predefined, configurable approval workflows based on document characteristics like amount, type, and department, so the right approvers are notified automatically without manual triage. Approvers see budget context (allocated, committed, spent, remaining) while reviewing, workflows can be edited in draft without disrupting live operations, and every decision lands in an immutable audit trail. Task steps (gather quotes, verify vendor) can be embedded in the workflow so pre-approval work happens on the record.