Key takeaways
- An authorization matrix states who may approve what, up to which amount, for which kind of spending — on one page.
- Set limits from your real transaction history, not from a round number: the limit should catch the exceptions, not everything.
- Name roles, not people, so the matrix survives someone leaving.
- Every limit needs a named deputy, or work stops whenever the approver is unavailable.
- Approval must happen before the commitment, not after the invoice arrives — otherwise it is a record, not a control.
- Review the matrix once a year and after any change in team size; a stale limit is ignored, and an ignored rule trains people to ignore the rest.
Most small businesses have approval rules. They are usually unwritten, roughly "ask me about anything big," and they fail in a predictable way: nobody agrees on what big means, so either everything gets escalated and the owner becomes a bottleneck, or nothing does and a significant commitment is made by someone who did not know it was significant.
An authorization matrix fixes this by writing the rule down: for each type of transaction, who may approve it and up to what amount. One page is enough. The value is not bureaucratic — it is that the answer to "can I commit to this?" stops depending on who is in the office and what kind of mood the week is in.
What goes in the matrix
Cover the transaction types where a decision commits money or reduces what you are owed. For most small businesses that is six rows:
| Transaction type | Up to small amount | Up to medium amount | Above that |
|---|---|---|---|
| Routine purchase (stock, supplies) | Purchasing staff | Operations lead | Owner |
| Non-routine purchase (equipment, services) | Operations lead | Owner | Owner |
| Payment release to supplier | Operations lead | Owner | Owner |
| Customer discount beyond standard terms | Sales lead | Owner | Owner |
| Write-off of a receivable or stock loss | — | Owner | Owner |
| New supplier or change of supplier bank details | Operations lead, verified separately | Owner | Owner |
Two rows deserve a note. Write-offs belong with the owner at almost any value in a small business, because a write-off is the mechanism that conceals both skimming and lapping — the reason is explained in skimming, lapping and inventory leakage. Supplier bank detail changes are on the list because they redirect every future payment, not just one.
Setting the numbers from your own history
The instinct is to pick round numbers. The better method takes twenty minutes:
- Export the last three months of purchases and payments.
- Sort by value, largest first.
- Find where the list stops being routine — where transactions become occasional and individually noticeable.
- Set the first limit just below that point.
- Check the result: if more than roughly one transaction in ten now needs escalation, the limit is too low to survive contact with a busy week.
A limit that catches everything is not a control, because it will be routed around. A limit that catches nothing is decoration. The point is to put a named person's attention on the transactions that are actually unusual for your business.
The approval has to happen before the order is placed. Approving the invoice afterwards documents a decision that has already cost you the money — useful for the record, useless as a control.
Roles, not names — and always a deputy
Write the matrix in roles: Operations lead, Sales lead, Owner. Then keep a short separate list mapping roles to current people. When someone leaves, you update one line instead of reissuing the policy — and there is no window where the rule technically names someone who no longer works there.
Every band also needs a deputy. The most common way a good matrix dies is a holiday: the approver is away, a supplier needs an answer today, someone approves it themselves, nothing bad happens, and the exception becomes the norm. Naming the deputy in advance costs one column and prevents that whole sequence.
No one approves their own expense claim or reimbursement, regardless of amount — and no one approves a payment to a supplier whose bank details they themselves entered or changed. These two are not about value; they are about the same hand being on both sides of the transaction.
Making the matrix visible
A matrix filed on a shared drive is a matrix nobody reads. Three practical habits keep it alive:
- Put it where the decision happens — pinned by the purchasing desk, attached to the supplier onboarding form, in the induction pack for new staff.
- Reference it in the payment run. Before releasing payments, the approver confirms each item was authorised at the right level. Sampling is fine for small values.
- Review it once a year, and whenever the team changes size. Inflation alone makes a three-year-old limit either meaningless or obstructive.
Reyuko does not run an approval workflow with value thresholds — the matrix itself stays a written policy. What the software does enforce is who can reach which part of the system at all: each of the seven preset roles carries its own access matrix across modules such as sales, purchasing, accounting and user management, set to full, read-only or none. So while the software will not stop a payment for exceeding a limit, it can stop someone outside the finance role from creating a payment in the first place.
That division matters when you write your matrix: enforce who may act through roles, and enforce how much through the written rule plus the review. Before relying on any software rule to hold a limit, test it the way described in verifying a feature before you rely on it.
Build your matrix in an afternoon
- List the transaction types where a decision commits money or reduces what you are owed.
- Pull three months of history and find the value where spending stops being routine.
- Write bands by role, not by name, with a deputy for each band.
- Add the two non-waivable rules: no self-approval, and no approving payments to a supplier whose bank details you entered.
- Publish it where the decisions are made, and diarise a review in twelve months.
The obvious objection is the genuine emergency — the compressor fails on a Saturday and the approver is unreachable. That case needs its own written rule rather than an unwritten exception, which is what handling emergency spending covers.
Reyuko