How Do You Set Up a Payment Approval Matrix?

Separate three decisions: whether the business needs the expense, whether the bill is ready to pay, and whether funds may leave the bank. One person may perform several tasks in a small shop, but each decision should still have a clear owner.

• Requester: explains the purpose and supplies the bill, order or other support.
• Approver: checks business need, receipt of goods or services, and authority to spend.
• Payment preparer: checks the payee, amount, supporting records and payment instructions.
• Releaser: checks that approval covers the payment being released and authorises the transfer.

Write roles first, then assign a named person and backup to each. An accounts employee preparing a transfer should not have to guess whether a manager can approve it.

Start with recent payments. Group them into routine purchases, recurring commitments, stock purchases, staff claims, advances and unusual spending. Give each group an approver who understands the expense and is responsible for its budget.

Choose limits from your cash position and the responsibility you are comfortable delegating. State whether the limit applies to the full bill, including taxes and charges. Apply it to the whole purchase or commitment, so splitting an invoice or transfer cannot avoid approval.

Add a backup approver and releaser to your working version. A person with technical access to the bank should still need the business authority assigned in the matrix.

Use risk rules alongside amount limits. Even a small payment should leave the routine route when the payee, purpose or supporting evidence changes.

• ✓New supplier or changed bank details: verify the account through an independently held contact before approval and release.
• ✓Advance before delivery: record the reason, expected delivery and person responsible for following up.
• ✓Missing receipt or disputed delivery: hold payment until the issue is resolved or an authorised exception is recorded.
• ✓Payment benefiting the requester personally: route it to another authorised person.
• ✓Unexpected urgency or payment outside the usual run: use the exception route without dropping the checks.

A familiar supplier name is not enough to clear changed payment instructions. Record who verified the change and how, alongside the approval.

Make the normal rule simple: nobody approves their own request or reimbursement. Where two people are available, one prepares the payment and the other checks the evidence and releases it. Record unavoidable overlaps.

If the owner is the only person available, full separation is not possible. Use documented checks before release and arrange a later review by a suitable independent person. Describe this honestly as a staffing limitation; a later review does not establish independent approval before payment.

Record delegation before the absence. Specify the delegate, covered expenses, maximum authority, effective period and exclusions. Confirm that the delegate can carry out the required bank action using their own authorised access.

• Keep routine payments within the written delegation.
• Name an alternate when the delegate is also the requester.
• Hold excluded payments until the owner or another properly authorised person approves.
• Give the returning owner a list of payments, exceptions and unresolved items.

Use a short exception record for an urgent repair, unsupported claim or other departure from policy. Include the reason, amount, payee, missing evidence, approving authority and follow-up owner. An exception needs approval before release too.

For an illustrative example, a workshop needs an urgent repair costing Rs 18,000. Its operations lead has a routine limit of Rs 10,000. The lead records the breakdown and quotation; the owner approves the specific payment before release. The completed repair record is attached afterwards. Urgency explains the exception; it does not expand the lead's limit.

Keep one payment record that connects the request, supporting documents, approval and bank reference. An approval should identify the payee, amount, purpose and bill or request reference. A general message saying 'go ahead' is too ambiguous.

• ✓Save the approver's identity, decision and timestamp before release.
• ✓Keep the approved version of the bill or payment schedule with that decision.
• ✓Record the releaser, release timestamp and bank transaction reference separately.
• ✓Get fresh approval if the payee, bank account, amount or approved scope changes.
• ✓For batch approval, preserve the exact list of payments approved.

Use the supplier payment run weekly routine guide to organise approved bills for release. Use the bank reconciliation monthly routine guide afterwards to match released payments to bank entries. Reconciliation checks the outcome; it does not replace prior approval.

• Approving after release and describing it as prior approval.
• Using amount limits while ignoring advances, changed payees or missing evidence.
• Letting a backup approve their own request.
• Treating an old recurring approval as permission for changed amounts or terms.
• Leaving authority unchanged after someone changes role or leaves.

Each month, sample payments across expense types and check both authority and timing. Review exceptions, overdue advances and recurring commitments. Update the matrix when responsibilities change. The finance operations guides hub can help place this review within your wider monthly routine.