A person signing paperwork beside a calculator
Step by step · Governance

Approval limits set for a smaller company

The thresholds were set when revenue was a third of what it is now, and the finance director still approves every invoice above a figure that was material then.

Key Takeaways
  • Delegation of authority tables are set at a point in time and rarely scale with the business.
  • Limits that are too low create bottlenecks and approval without review, which is worse than no approval.
  • Limits that are too high leave material spend committed without a second pair of eyes.
  • The right test is what proportion of value each level approves, not what the thresholds are in isolation.
  • Reviewing the table against actual spend distribution takes an afternoon and is rarely done.

Every company has a delegation of authority table. It was written at a specific moment, usually in response to a growth stage, an audit finding or a governance review.

The business then grows, inflation compounds and transaction volumes rise, and the table stays where it was, because changing it requires a decision nobody is prompted to make.

The symptom is familiar: senior people approving large volumes of small transactions, and doing so quickly because the volume makes genuine review impossible.

That is not a stronger control than a higher limit. It is a weaker one wearing the appearance of rigour. It is also expensive in a way that never appears in any budget, since the cost is senior time spent on items that a rule could handle and a sample could verify. Quantifying that cost is usually enough to move the conversation, and it uses the same arithmetic as any other comparison of effort against value, in the way total cost comparisons do, provided the underlying figures trace back to transactions as any defensible subtotal must.

Delegation of AuthorityApprovalsControlsGovernanceProcess
01

What happens when limits do not scale

Volume rises at each approval level. The person at the top of the table receives more items, each taking the same time to review properly.

Since the time is not available, review becomes approval, and the control degrades without any change in documentation. The table still says what it always said.

Meanwhile the queue becomes a delay for the business, which creates pressure to bypass it entirely, which is where retrospective orders come from, as retrospective purchase orders describes.

Both effects come from the same cause and both are invisible in any metric the company currently reports.

Two colleagues working with a laptop and calculator in an office
Volume rises at every level while the thresholds stay where they were.

Thresholds age with revenue

A limit set when revenue was a third of today's size now routes routine spend to the finance director.

The AgentCFO podcast talked about removing complexity and compliance load where it no longer earns its place, which is what a stale approval table adds.

Pull the last quarter of approvals, find where one person signs most of the volume, and reset that threshold first.

02

Four symptoms of a stale table

Each is measurable from approval data, which is why this review is quicker than it sounds.

High volume at the top level: A senior approver handling hundreds of items a month, which makes substantive review arithmetically impossible.
Very fast approval times: Median approval time measured in seconds indicates a queue being cleared rather than reviewed.
Approval concentration: A large share of items approved by one person, which is both a control risk and a single point of delay.
Bypass activity: Retrospective orders, card usage or split transactions, which are responses to friction rather than to policy, as unmanaged spend shows.
03

The right test

The question is not whether a threshold looks sensible. It is what proportion of total spend value each approval level actually sees.

A well designed table has senior levels seeing a small number of items representing a large share of value, and junior levels seeing high volumes of low value.

Where a senior level sees high volume and a modest share of value, the threshold is too low for the current business and should rise.

That analysis takes an afternoon using approval data, and it converts a governance discussion into an arithmetic one, which is where it belongs, in the same way materiality thresholds should be revisited.


Judge the table by the distribution it produces. Not by whether the numbers look prudent.
04

What a healthy distribution looks like

The shape matters more than the specific thresholds, which differ by company.

LevelVolumeValue share
ExecutiveA small number of items per month, reviewable in detail.A meaningful share of total value.
DepartmentalModerate volume within a defined budget.The bulk of operational spend.
Automated or delegatedHigh volume, low value, controlled by rules and sampling.A small share of value, where individual review is uneconomic.

Delegation of authority sits within your governance framework and may be constrained by board policy, banking mandates or regulatory requirements. Change it through the appropriate route.

"

Approving four hundred items a month is not reviewing four hundred items a month.

ChatFin
05

Reviewing the table

Five steps, using approval data you already hold, producing a recommendation rather than an opinion.

Pull the spend distribution

Transaction counts and values by band over twelve months, which shows where value actually sits.

Map current limits onto it

So the volume and value seen by each level is visible rather than assumed.

Measure approval time by level

Median seconds per approval, which indicates whether review is happening at all.

Propose thresholds that produce the right shape

Fewer, more substantial items at senior levels, with sampling below.

Set a review trigger

Revenue growth or volume growth beyond a threshold prompts the next review, rather than waiting for an audit finding.

Two accountants working at a shared office table
The distribution the table produces is the test, not the numbers themselves.
06

Two objections to raising limits

Both are reasonable and both are addressed by what replaces the approval rather than by keeping it.

Objection

It weakens the control

Approval that takes four seconds is not a control. Raising the limit and introducing sampling with genuine review of the sample is usually stronger, and it should be presented that way.

Objection

The board set these limits

Then the board should see the distribution analysis, since it shows what the limits produce in practice, which is different from what they were designed to produce.

07

How ChatFin supports approval design

The analysis is arithmetic over approval and transaction data, and the design decision is entirely yours.

Distribution analysis prepared: Spend by value band and approval level with volumes and value shares, from your ERP data.
Approval behaviour surfaced: Volumes and median times per approver, which is what shows whether review is substantive.
Prepared work at each level: Items reaching an approver arrive with the supporting evidence assembled, which is what makes a smaller number of substantive reviews possible, alongside limits applied per action.

Delegation of authority, thresholds and governance decisions remain matters for your board and your leadership.

Free tool

AI Cost Estimator for the CFO Office

Four inputs. A first year range, a timeline, and three delivery models compared. No login required.

Frequently Asked Questions

How often should approval limits be reviewed?

On a trigger rather than a calendar: material revenue or volume growth, a significant acquisition, or a sustained rise in approval volumes at any level. Most companies review only after an audit finding, by which point the distribution has been wrong for years.

Does raising limits weaken control?

Not necessarily. An approval performed in seconds because of volume is not providing review. Raising the limit and introducing genuine sampling below it frequently produces more actual scrutiny, provided the sampling is real and its results are acted on.

What is the best measure of whether limits are right?

The proportion of total spend value seen at each approval level, alongside the volume of items. Senior levels should see few items representing significant value. Where they see high volume and modest value, the threshold is too low for the business.

What should replace individual approval at low values?

Rules based controls with sampling, supported by budget ownership and periodic review of the population. The key is that the sample is genuinely reviewed and exceptions acted on, otherwise the control has been removed rather than redesigned.

Test the distribution

Approval in four seconds is not review.

Pulling the spend distribution, mapping current limits onto it and measuring approval times converts a governance debate into an arithmetic one.

If you want a first year range for prepared approvals with evidence assembled, the estimator will produce one before any scoping.

Open the estimator
Book a Demo
Put it on your own numbers

See what this looks like in your ERP.

We will walk through the workflow behind this article on the system you already run, using your own data, and show what a first phase would actually cover.

✓Runs on the ERP you already have, on the version you already run
✓Every action prepared as a draft that a person approves before it posts
✓A first phase scoped against your real workflows, not a generic package
Schedule a Demo
Confidential & private

This article is general information for finance and accounting teams. It is not legal, tax, accounting or investment advice. Dates and thresholds are given as published at the time of writing and several of these timelines have moved before, so confirm the current position with your advisers and with the relevant authority before acting.

Photos by Mikhail Nilov and Pavel Danilyuk, free to use under the Pexels License (commercial use, no attribution required).