---
title: "Approval workflows in accounting: controls that stop errors early"
description: "An approval workflow only controls risk if the approver sees the real issue. Here is how to design routing, limits and evidence so approvals catch errors before they post."
author: "Maren Calloway"
category: "Accounting Operations"
date: 2026-10-27T07:55:02.157Z
canonical: "https://tasksheriff.com/blog/accounting-approval-workflow-controls"
---

# Approval workflows in accounting: controls that stop errors early

![Computer screen showing a dashboard with application trend graphs and key metric panels.](https://images.unsplash.com/photo-1763718528755-4bca23f82ac3?crop=entropy&cs=tinysrgb&fit=max&fm=jpg&ixid=M3w4OTQwNjJ8MHwxfHNlYXJjaHwxfHxBcHByb3ZhbCUyMHdvcmtmbG93cyUyMGluJTIwYWNjb3VudGluZyUyMGFwcHJvdmFsJTIwd29ya2Zsb3clMjBjb250cm9sc3xlbnwxfDB8fHwxNzkyNTE4NjQzfDA&ixlib=rb-4.1.0&q=75&w=1200&auto=format)

> An approval workflow only controls risk if the approver sees the real issue. Here is how to design routing, limits and evidence so approvals catch errors before they post.

Say a controller reviews a sample of approved invoices and finds one paid twice. The approver on both was careful. Each copy looked normal in isolation.

This is the usual failure of approval workflows. The step exists, the name is on the record, and nothing was actually checked. Design decides whether a control works.

## What an approval is for

An approval does one of three jobs. It confirms that the spending was authorized, that the goods or services arrived, or that the accounting is right. Mixing the jobs makes the step weak. An approver asked to confirm all three, for every item, will confirm none.

Write down which job each approval does. Then give that approver only the information needed for that job.

## Types of approval workflow

  ![](https://hsppuvezyxmkpzkgfkho.supabase.co/storage/v1/object/public/media/enrichment/39b6f926-5a52-4bf1-99e0-a3cf4d8c6ff8/9009bbf8-c0d5-464e-afe1-1025b837f295/00749de0-0218-4a33-923d-a45e98635ed8.jpg)

- **Single approver.** Fast and cheap. Suits low-value, low-risk items.

- **Sequential.** A chain, such as manager then finance. Slow, and later approvers often rely on earlier ones.

- **Parallel.** Several approvers at once, each for a different job, such as budget owner and receiving.

- **Conditional.** The route depends on amount, vendor, account or exception type. This is the form that scales.

Most teams do best with conditional routing. Low-risk items take the short path, and unusual items take the long one.

## Four design rules

### Route by risk, not by habit

Set thresholds by amount, but add triggers for conditions: a new vendor, a changed bank account, an account that rarely gets postings, an invoice with no purchase order, a date near period end. These conditions matter more than the amount for fraud and error.

### Show the anomaly

The approval screen should lead with what is different. "Price is 14 percent above the last six invoices from this vendor" is a reason to look. A table of fields is not. This is where an automated system helps most: it compares the item to history and states the difference in a sentence.

### Keep the separation of duties

The person who enters should not approve, and the person who approves should not release payment. The idea is standard in internal control practice and is described in general terms under [separation of duties](https://en.wikipedia.org/wiki/Separation_of_duties). Software agents need the same treatment: give the agent its own identity, and do not let it approve its own work.

### Make delegation explicit

Approvers go on leave. If delegation is informal, people share credentials. Build a delegation feature with a start date, an end date and a log entry, so a stand-in is visible.

## Where automated controls fit

Automation can take over the checks that do not need judgment, and leave the judgment to people. Examples:

- Duplicate detection across vendor, number, amount and date, including near-matches.

- Three-way matching with tolerances set by finance.

- Blocking a posting into a closed period.

- Holding a payment when the bank details differ from the vendor master.

These are preventive controls. They act before the entry posts, which is cheaper than finding the error in close. The [COSO](https://www.coso.org/) internal control framework distinguishes preventive from detective controls and is a common reference for how to balance them.

## Test the control, not the form

Once a quarter, test whether the approvals work. Pick a sample and ask three questions:

- How long did the approver spend on the item?

- Did the approver ever reject or query an item of this type?

- Could the approver see the reason the item was routed to them?

An approver who has never rejected anything in a year is not a sign of clean data. It is a sign of a rubber stamp. Seed the sample with a known error and see whether it gets caught.

## A sketch of a workable policy

ConditionRoute

Matches PO and receipt, within tolerance, known vendorPosts automatically; sampled monthly
Price or quantity variance beyond toleranceBudget owner reviews variance
No POManager approval, then finance review
New vendor or changed bank detailsFinance verifies by callback; second approver releases
Above the payment limitNamed senior approver

Treat the table as a starting point, and set the actual limits with your own risk owners. We do not give audit or legal advice here, so check your design with your auditors.

## What to do next

Pull the last month of approvals and sort them by the time each approver took. The fastest ten percent are where your design is weakest. Ask what the approver saw on screen, and change that first.

If you'd like to see how these ideas translate into an actual system, this walkthrough covers managing the approval workflow section of an accounting platform, where routing and approval settings are configured in practice. It's a useful reference for seeing how approver assignments and review steps are set up, which makes the design choices above easier to apply to your own process. Even if you use different software, the setup logic carries over.

If you'd like to see how routing and approver settings are actually configured, this walkthrough from SMECore Africa shows the approval workflow section of an accounting management system in practice. Watching the setup makes it easier to picture how the design choices discussed here, such as who approves what and at which stage, translate into software. Even if your own system differs, the structure is a useful reference when mapping your controls.

---
Source: https://tasksheriff.com/blog/accounting-approval-workflow-controls