What a delegation of authority matrix defines
Each row of the matrix answers one complete question: for this kind of spend, in this part of the organization, up to this amount — who decides? The columns that make the answer usable are the amount band (a contiguous, non-overlapping range in a stated currency), the spend category (travel, meals, software, professional services), the entity and department (authority is granted within a legal entity, and often within a budget line), the primary approver by role (name roles, not people — “Finance manager, entity X” survives a resignation), and the backup approver (who decides when the primary is on leave or is the submitter).
Internal-control frameworks treat this as core design material: COSO’s Internal Control — Integrated Framework organizes effective internal control into interdependent components, and the GAO’s Green Book emphasizes prioritizing preventive control activities. An authority matrix is precisely that: a preventive control, deciding who may commit the company before the money moves.
Build the table
The builder collects rows with the six fields above and renders the matrix as a finance-readable table you can check by eye before exporting.
Two properties make the output survive contact with reality. Completeness: every plausible claim should land in exactly one row — including the very large one, which needs an explicit top band routed to executive or board authority. Readability: if a row needs explaining, it needs rewriting. A matrix that only its author can interpret will not survive an audit walkthrough or a new manager’s first week.
| Field | What to enter | What to avoid |
|---|---|---|
| Amount band | A contiguous range in one stated currency, e.g. 0–500, 500–5,000 | Overlapping bands; bands in mixed currencies; an open top band with no escalation row |
| Category | The spend categories your policy already uses | Inventing categories for the matrix that the expense system does not have |
| Entity / department | The legal entity, and the department when authority is budget-line specific | “Group” as an entity — someone specific pays every claim |
| Primary approver | A role: manager, department head, finance manager, CFO | Named individuals; roles no one currently holds |
| Backup approver | The role that decides in the primary’s absence or conflict | Leaving it blank; naming the submitter’s peer |
| Notes | Escalation conditions, exception owners, effective date | Policy prose — the matrix is a table, not a document |
The matrix is authority; the workflow is execution
A delegation matrix and an approval workflow answer different questions, and conflating them breaks both. The matrix says who has the authority to commit the company — a policy artifact, owned by finance leadership, reviewed on a cadence, shown to auditors. The workflow says how a specific claim moves — who is notified, in what order, what evidence is collected, what happens on timeout — and it is a system configuration that should be derived from the matrix, never the other way around.
The distinction shows up in practice as layered review: the line manager approves the business purpose of a claim, while finance reviews the tax evidence or the currency conversion before reimbursement. One claim, two decisions, each by the person with authority over that dimension.
Set amount bands from your own data
There are no universal thresholds, and this page deliberately does not suggest any. A band that routes most claims to senior approvers in one company is a rounding error in another — copying a template’s numbers imports someone else’s spend distribution along with them.
Pull your last two quarters of claims and look at the distribution by amount, per entity. The bands should follow the distribution’s natural breaks, not round numbers chosen in a meeting. Put the routine bulk in the lowest band. Size the top of each band by attention, not prestige. Denominate per entity — the same numeric threshold means different things in different markets. Record the effective date: bands are calibrated to a spend distribution that will drift.
Backups, conflicts, and exceptions
The rows cover the normal case. Three abnormal cases decide whether the matrix works under pressure.
Absence: the backup column exists so that a claim never waits on one person’s vacation; the backup inherits the same band and category scope. Conflict: when the approver is the submitter, the claim must route around them, upward or sideways to finance, never downward. Exception: someone will eventually need to approve outside the matrix; the matrix should name who may grant exceptions and require that each one is recorded with its reason — an exception without a record is indistinguishable from a control failure.
Review the matrix when the company changes
A matrix is calibrated to an org structure and a spend distribution, and both drift. Review it quarterly, and immediately when any of these occur: a new entity or market opens; reporting lines change; budgets reset; an audit finding names an approval gap; or the exception log grows.
The quarterly pass itself is short if the matrix is a table: check that every role still exists, every band still matches the distribution, every backup is still valid, and the exception log has nothing recurring. Date the review — an undated matrix is presumed stale by exactly the people it is meant to convince.
About this guide
The builder assembles rows from user input and renders them as a table; the CSV export contains exactly the rendered rows, in the same order, with no additions. No thresholds, roles, or bands are suggested by the tool — every number and name comes from the user.
Operational tool and guidance for finance teams. Not legal, audit, or accounting advice. Appropriate approval authorities, thresholds, and review cadences depend on company size, sector, regulatory regime, and auditor expectations.