Thresholds that reflect reality
By amount, department, entity, vendor, GL account, and document type — including the combinations, because most real matrices are combinations rather than a single ladder.
Platform · operations
Most companies have an approval matrix in a document and a different one in practice, because the documented version was too slow and people routed around it. Encoding it properly is less about automation than about deciding what the matrix actually is — and then having one rather than two.
Post a coded vendor bill automatically when all of these hold:
What it does
By amount, department, entity, vendor, GL account, and document type — including the combinations, because most real matrices are combinations rather than a single ladder.
A named delegate with a date range, so an approver on holiday does not become the reason a close slips a day. This is the most common single cause of workflow stalling.
After a threshold you set, with the item and its ageing visible to whoever needs to unblock it rather than sitting silently in somebody’s queue.
An agent operating at Level 3 routes to whoever your matrix names for that amount and department. We do not introduce a parallel approval hierarchy.
Who, when, on what basis, on the item as it stood at that moment, under which policy version. An approval you cannot reconstruct is not evidence.
What is unusual about this item relative to the last forty like it, shown before the detail — so approving is a decision rather than a scroll.
Nearly every company we assess has a documented approval matrix and an operating one, and the gap between them is where the control has already failed. The documented version usually requires more approvals than the business can tolerate, so people found workarounds — a verbal sign-off, a blanket pre-approval, an email chain that substitutes for the process.
Encoding a matrix into software makes that gap unsustainable, which is uncomfortable and useful. The right first step is not configuration; it is deciding which matrix is real and adjusting the documented one to something the business will actually follow.
The single most common reason a close slips a day is an item sitting in the queue of somebody who is away. Every company knows this and most handle it by asking someone to share credentials, which destroys the audit trail and creates the segregation problem the matrix existed to prevent.
Proper delegation — a named delegate with a date range, recorded as a delegation rather than as the original approver acting — solves it without that cost. It is unglamorous and it removes a recurring failure.
An approval on an item nobody read is worse than no approval, because it manufactures evidence of oversight that did not occur. That is why items arrive with the difference shown first, why rejection is exactly as fast as approval, and why there is no bulk approve at any authority level.
We also report approval rate and time per item per approver. Not to police anyone — because somebody approving ninety-nine percent of items in three seconds each is telling you the routing threshold is wrong, not that they are careless.
Limits
This is approval and exception routing for financial documents. Modelling arbitrary business processes across departments is a different product category.
If nobody can state who approves what above $25,000, no software supplies the answer. That decision has to be made before configuration, and it is usually the slow part.
A matrix requiring four approvals on a $400 expense will be routed around whatever system enforces it. Encoding it faithfully just relocates the frustration.
Questions
Send your documented thresholds and we will tell you where they differ from what happens in practice.