Approval Matrix Template
One table that says who may approve what, up to which limit, who steps in when they can't, and what record each approval leaves. Copy it, then replace the example limits and roles with your own.
Workflow Authority Editorial Desk · Updated
An approval matrix (also called an approval authority matrix or a delegation of authority matrix) is a table that lists the decisions your company makes, the limit or condition that applies to each, and the role allowed to approve it. Finance teams use it for spend, payments and contracts. It is also where you decide what an AI agent may prepare and which person must say yes before anything changes.
The template below has one row per decision. The example rows show how a filled-in matrix reads; the limits are written as bands (Band 1, Band 2, Band 3) because the real amounts must come from your own delegation of authority policy, not from a template.
The template
Each column, and what goes in it:
- Decision or action: What is being approved, as one specific action: “pay a supplier invoice”, not “finance”.
- Limit or condition: The amount band, risk tier or condition that puts an item in this row.
- Prepared by: The role (or AI agent) that drafts the request. It can never also approve it.
- Approver: The role that says yes or no. Always a person’s role, never a system.
- Second approver or escalation: Who else must approve, or who decides when the approver rejects or is unsure.
- Backup approver: The named delegate who approves when the approver is away.
- Evidence kept: What the approval leaves behind, so an auditor can see what was approved and why.
- Expected response time: How long an item may wait before it escalates.
Approval Matrix Template: example rows
Example rows. Bands 1–3 stand for the limits in your own delegation of authority policy; replace every role, limit and response time with yours.
| Decision or action | Limit or condition | Prepared by | Approver | Second approver or escalation | Backup approver | Evidence kept | Expected response time |
|---|---|---|---|---|---|---|---|
| Raise a purchase order with an approved supplier | Within Band 1 | Requester (an AI agent may draft it) | Budget owner | None | Budget owner’s named delegate | Purchase order, quote, budget line checked | 1 business day |
| Raise a purchase order with an approved supplier | Band 2 | Requester | Budget owner | Financial controller | Deputy controller | As above, plus competing quotes where your policy asks for them | 2 business days |
| Add a new supplier or change a supplier’s bank details | Any amount | Procurement or accounts payable clerk | Accounts payable manager (not the person who entered it) | Treasury, for bank detail changes | Named accounts payable lead | Supplier documents, call-back to a known contact on file | Before the first payment |
| Pay an invoice that matches its purchase order and receipt | Up to the purchase order amount | Accounts payable clerk or AI agent (prepares the payment only) | Accounts payable manager | None | Named accounts payable lead | Match result, exceptions list, payment run record | Next payment run |
| Pay an invoice above its purchase order, or with no purchase order | Any amount; Band 2 and above escalates | Accounts payable clerk or AI agent (flags it) | Budget owner | Financial controller | Budget owner’s named delegate | Reason for the difference, contract terms | 2 business days |
| Sign or renew a contract | Band set by total contract value | Contract owner | Department head | Legal review; CFO at Band 3 | Named deputy department head | Final terms, legal review notes, renewal price against the previous term | Before the notice date |
| Post a manual journal entry | Any amount | Accountant | Financial controller (never the preparer) | CFO above Band 3 | Named senior accountant | Supporting documents, reason for the entry | Before period close |
| Let an AI agent change a record in a system of record | Per the workflow’s risk tier | AI agent (prepares the change) | Named workflow owner | Second reviewer for high-risk workflows | Named backup workflow owner | Original proposal, approver’s edits, approver, time, model and workflow version, result | Set per workflow |
| Turn on a new AI workflow, or widen what one can do | Per the workflow’s risk tier | Workflow owner | Department head (medium risk); senior leader (high risk) | Security and risk review | Named deputy | Intake record: owner, systems, data, write access, whether actions can be undone | Before go-live |
How to fill in the approval matrix
- Start from your delegation of authority. Your company’s delegation of authority policy, usually approved by the board or leadership, says who may commit the company to what. Copy its limits into the bands. The matrix applies those limits; it should never set new ones. If no such policy exists, that is the first gap to close.
- List decisions, not departments. Write one row for each action that commits money, data or the company: raising a purchase order, adding a supplier, changing bank details, paying an invoice, signing a contract, posting a journal, changing a customer record, turning on an AI workflow.
- Give each row its limit or condition. Use an amount band where money moves, a risk tier where data or systems change, and “any amount” for actions that are risky whatever the value, such as changing a supplier’s bank details.
- Keep the preparer and the approver apart. Whoever prepares an item (a person or an AI agent) must not approve it. Then read across rows for combinations one person should not hold, such as creating a supplier and approving that supplier’s payments.
- Name roles in the matrix and people in a register. The matrix says “Financial controller”. A separate register says who holds that role today and who their delegate is. When someone changes jobs, you update the register, not the matrix.
- Give every row a backup and an escalation. Without a named backup, approvals either stall or get signed by whoever happens to be around, which is how controls quietly stop working.
- Say what evidence each approval leaves. For each row, write down what must be kept: the request, the documents checked, who approved, when, and what they changed. An approval no one can show later is hard to defend in an audit.
- Make the systems match the matrix. A spreadsheet only works if your ERP, procurement and workflow tools enforce the same limits. Check every row against the approval rules set up in those systems, and fix whichever one is wrong.
- Date it, version it and review it. Put an owner, a version number and an effective date on the matrix. Review it on a schedule you set, and again after a reorganization, a new system or a new AI workflow.
Adding AI-assisted work to the matrix
AI agents change who prepares work, not who is accountable for it. A few extra rules keep the matrix meaningful once agents draft purchase orders, match invoices or update records.
- An agent prepares; a person approves. List agents in the “Prepared by” column only. The approver column always names a person’s role. See how to add human approval to agentic workflows.
- Approving a proposal is not permission to carry it out. Write separate rows for “approve the recommendation” and “let the agent make the change”, so a yes to one does not quietly grant the other.
- Add limits that add up. An agent can make many small purchases that each sit under the Band 1 limit but add up to a large amount. Set a combined limit per agent, per supplier and per period. More on this in enforcing spend authority limits in AI-assisted procurement.
- Use the workflow’s risk tier as the condition. Classify each AI workflow by what it can change, what data it touches and whether its actions can be undone, then let the tier decide the approver. How to decide what AI agents can access and change walks through it.
- Keep the agent’s version in the evidence. For AI rows, record the original proposal, the approver’s edits, and the model and workflow version that produced it, so the approval can be traced later.
- Say who can pause it. Each AI row needs a named role that can stop the workflow, and a rule for when they must.
Approval matrix, delegation of authority, RACI: what’s the difference?
These documents are often confused, and a company usually needs more than one of them.
| Document | What it answers | What it doesn’t do |
|---|---|---|
| Delegation of authority policy | Who may commit the company, and up to which limits | Say how each action is prepared, checked or recorded |
| Approval matrix | For each action: the limit, the preparer, the approver, the backup and the evidence | Set the limits itself; it applies the policy |
| RACI chart | Who is Responsible, Accountable, Consulted and Informed on a task or project | Set money limits or say who may sign |
| Segregation of duties matrix | Which duties one person (or agent) must not combine | Name approvers; it is the check you run on the approval matrix |
Common approval matrix mistakes
- Names instead of roles. The matrix goes out of date the first time someone leaves.
- No backup approver. Work waits, or someone without authority signs to keep it moving.
- Limits checked one transaction at a time. Splitting a purchase into several smaller ones gets around them.
- A matrix the systems don’t follow. If your ERP lets a Band 2 payment through on a Band 1 approval, the system is the real policy.
- Approvers who can’t see the evidence. An approver who only sees a summary is signing off on trust, not on the documents.
- “Human review required” with no role named. Every approval needs an owner who can be asked about it later.
- Never reviewed. Limits, people and systems change; an old matrix gives a false sense of control.
Where to check your own limits and rules
This template gives structure, not numbers. The values in your matrix should come from your own sources:
- Your delegation of authority policy and the board or leadership decisions that approved it, for the limits.
- Your ERP and procurement tools’ approval settings for the rules actually enforced today.
- Your internal audit team or external auditor for which approvals they test and what evidence they expect. US public companies assess these controls as part of internal control over financial reporting under SOX section 404; see approval gate requirements under SOX 404 for AI-assisted reporting.
- Your regulator’s guidance if you work in a regulated industry, for any approvals it requires by name.
Frequently asked questions
What is an approval matrix?
A table that lists each decision a company makes, the limit or condition that applies, who prepares it, who approves it, who covers when they are away, and what evidence is kept.
What should an approval matrix include?
At minimum: the decision, its limit or condition, the preparer, the approver, a second approver or escalation, a backup approver and the evidence kept. A response time per row helps stop items waiting forever.
How many approval levels should it have?
As many as your delegation of authority policy has limits, and no more. There is no standard number; fewer, clearer bands are easier to follow and to set up in your systems.
Who should own the approval matrix?
Give it one named owner who keeps it versioned and reviewed, often in finance, and give each row an owner in the team that runs that action.
Can an AI agent be an approver?
In this template, no. An agent can prepare a request, a payment or a record change, but the approver is always a person’s role, and their decision is recorded with the agent’s original proposal.
How often should we review it?
On a fixed schedule you set with your auditors, and whenever the organization, your systems or your AI workflows change.
Read next
- How to Keep a Record of Who Can Approve What in AI Workflows
A workable approval record names owners, limits agent actions, and proves it.
- Role-Based Approval Thresholds for AI Finance Decisions
Clear approval limits keep finance AI from acting beyond its authority.
- How to Stop Automated Finance Pipelines Skipping Approval Gates
Build approvals into agent permissions, not just the pipeline.
- How Procurement Approval Gates Work (And How to Sequence Them)
Learn how to sequence approval gates by risk, spend, and authority.
- When Should AI Escalate to a Human? A Plain Guide
Confidence scores mislead, so risk tiers should decide when humans step in.
Some workflow tools enforce this split between preparing and approving. Nodes, for example, starts read-only, treats reading and changing as separate permissions, and holds every change until a named person approves it. Workflow Authority is commissioned by Nodes; this template was prepared by its editorial desk with AI assistance.