Finance Index
What are typical invoice approval thresholds, and how should I set them?
Reference guide to invoice approval thresholds, including control design, audit evidence, risk points, finance procedures, and compliance review.
Approval thresholds are the dollar bands that determine how much review an invoice receives. Set them from your own invoice distribution, not a generic table: pick the level where the bulk of routine invoices clear with one approver, add a second approver where amounts justify dual review, and reserve executive levels for genuinely material spend.
At a Glance
| Aspect | Short Answer | Why It Matters |
|---|---|---|
| Typical invoice approval thresholds | Approval thresholds are the dollar bands that determine how much review an invoice receives. | Keeps work moving without losing accountability. |
| Set thresholds so executives aren't | Pull twelve months of invoice data and look at the distribution. | Helps finance decide what to do next. |
| Approval path | Splitting shows up in data before anyone admits it: multiple invoices from the same vendor, same requester, within days of each other, individually just under a threshold. | Reduces payment errors, timing issues, and reconciliation cleanup. |
| Set approval thresholds | Both. | Keeps work moving without losing accountability. |
| Amount-based approval routing | Routing logic that selects the approver path from the invoice amount - e.g., one approver under $5K, two from $5K - $50K, executive sign-off above. | Keeps vendor records and payment decisions reliable. |
How do I set thresholds so executives aren't approving $50 invoices but nothing big slips through?
Pull twelve months of invoice data and look at the distribution. Typically a large majority of invoice volume sits in a small share of dollars - set the single-approver band to absorb that volume, and place the executive band where dollars (not counts) concentrate. Then enforce the bands in-system with amount-based routing so the policy can't be skipped, and re-baseline annually: thresholds set at one company size quietly become either rubber stamps or bottlenecks as volume grows.
Employees are splitting invoices to stay under their approval limit - how do we detect and stop it?
Splitting shows up in data before anyone admits it: multiple invoices from the same vendor, same requester, within days of each other, individually just under a threshold. Detect it with vendor-level velocity and amounts-near-limit reports; deter it by making cumulative vendor spend visible to approvers, applying thresholds to related groups of invoices where feasible, and treating detected splits as a policy violation rather than a workflow quirk. The structural fix is upstream: require purchase requests before commitment so the full intended spend is approved once, at its real size.
What are typical invoice approval thresholds by company size?
Patterns vary widely, but as a rough shape: smaller companies often run a single threshold (everything above a few thousand dollars gets a second look); mid-market companies run two or three bands with manager/director/executive tiers; enterprises tie bands tightly to a formal DOA with per-entity calibration. Your own spend distribution should drive the numbers.
How do I set approval thresholds - should they be based on dollar amount, risk, or both?
Both. Dollar bands are the backbone, but risk modifiers matter: new vendors, off-contract spend, sensitive categories (legal, consulting, donations), and unusual coding warrant review regardless of amount. Amount-only thresholds systematically under-review small-but-risky spend.
What is amount-based approval routing?
Routing logic that selects the approver path from the invoice amount - e.g., one approver under $5K, two from $5K - $50K, executive sign-off above. It is how a DOA becomes an operating control instead of a policy document.
Should thresholds apply to invoice total, line amount, or cumulative vendor spend?
Invoice total is the standard enforcement point. Line-level thresholds add complexity that rarely pays off; cumulative vendor spend is better handled as a monitoring control (vendor spend reports, contract-level approval) than as a routing rule, but it must exist somewhere - otherwise splitting defeats the total-based control.
Should approval thresholds differ for capex vs opex invoices?
Often yes. Capex usually carries its own authorization process (project or AFE approval), so the invoice-level control verifies the spend maps to an approved project; opex thresholds do the primary control work. Misclassifying capex as opex to dodge project approval is itself a pattern worth monitoring.
How should thresholds work for credit memos and negative invoices - do they need approval too?
Yes - credits adjust liabilities and can mask errors or fraud (a fake credit can offset a fake invoice). Route them through approval like invoices, generally to whoever approved the original spend, with attention to large or round-number credits.
How do I handle invoices that exceed the highest individual authority - board approval workflow for large invoices?
The commitment, not the invoice, should get board-level approval - contract or purchase authorization before the spend occurs. The invoice workflow then verifies the invoice maps to that approved commitment, with CFO-level sign-off documented against the board action.
A vendor sends one large annual invoice that always breaches thresholds and stalls - how should we handle expected large invoices?
Pre-approve the arrangement: approve the contract or renewal at the right authority level before the invoice arrives, then let the invoice route as a match against that known commitment. Predictable large invoices stalling every year is a process design failure, not a control success.
How often should approval thresholds be re-baselined as the company grows?
Review annually against the current invoice distribution, and any time volume, headcount, or entity structure changes materially. A threshold that routed 10% of invoices to executives three years ago may route 30% today.
Flat thresholds vs percentage-of-budget thresholds - which works better for approval limits?
Flat dollar thresholds win for invoice approval: they're unambiguous, enforceable in-system, and auditable. Percentage-of-budget logic belongs upstream in budget-vs-actual monitoring and purchase request controls, where budget context actually exists at decision time.
Stampli perspective
Stampli supports amount-based routing as a first-class workflow condition - different approver paths by amount band, combined with vendor, department, GL, subsidiary, or location conditions - plus approval authority controls that block completion when no approver with sufficient authority has acted. Approvers see the invoice in full context (image, coding, history, PO data), which makes near-threshold and repeat-vendor patterns visible at the point of decision.