Finance controls

How to design an approval matrix (delegation of authority) that works

A practical method to write a delegation-of-authority matrix that people follow and systems can enforce.

8 min read · Updated 1 November 2026

On this page

What an approval matrix is

A delegation-of-authority (DoA) matrix sets out who can approve which commitments, up to which amount. It is approved by the board or management, and every approval system should mirror it exactly.

Build it in five steps

  1. List the decision types: purchase orders, vendor bills without PO, expenses, journals, payments, contracts, hiring, capex, credit notes, write-offs.
  2. Set amount bands that match your business — few enough to remember, usually three or four.
  3. Assign roles, not names — "department head", "controller", "CFO", "CEO" — so the matrix survives people changes.
  4. Add the separation rules: the requester never approves their own request; whoever approves a vendor's bank details doesn't approve that vendor's payments.
  5. Define delegation: who covers whom during absence, for how long, and up to which limit.

A simple example structure

DecisionBand 1Band 2Band 3
Purchase orderDepartment head+ Controller+ CFO
Bill without POBudget owner+ Controller+ CFO
Manual journalControllerController+ CFO

Fill in your own amounts.

Putting it into NetSuite

  • Employee-level limits for native routing.
  • SuiteFlow or SuiteApprovals rules for levels, departments and parallel approvers.
  • An amount above which decisions must be made inside NetSuite, not from chat.

Test every band in sandbox with a record just below and just above each limit.

Keep it alive

Review the matrix every year and whenever the organisation changes. Compare a sample of real approvals with the matrix each quarter — that is exactly what your auditor will do.

See Axiera Approvals on your own NetSuite records