Introduction
Most accounts payable delays aren't caused by too much bureaucracy — they're caused by a bill sitting in nobody's clearly assigned inbox until someone happens to remember it right before a due date. A workable AP approval workflow fixes this with clear ownership at each stage, not necessarily more approval steps.
Table of Contents
- The Real Cause of AP Delays
- The Three-Stage Workflow
- Stage 1: Intake and Coding
- Stage 2: Tiered Approval
- Stage 3: Payment Release
- Why Separation of Duties Matters
- Not Every Bill Needs the Same Process
- Setting Up Approval Rules in Your Accounting Software
- FAQ
- Conclusion
The Real Cause of AP Delays
The instinct when AP feels chaotic is to add more approval steps or more oversight. In practice, this usually makes the problem worse. The genuine root cause is almost always unclear ownership — a bill arrives, and it's not obvious whose specific job it is to review it right now, so it waits. A workflow that clearly assigns a named owner to each stage, even a simple two-step one, resolves this more reliably than adding complexity.
The Three-Stage Workflow
A workable structure has exactly three stages, each with a clearly assigned owner:
- Intake & Coding — the bill is logged and matched to the right budget line or purchase order
- Tiered Approval — reviewed and approved by the right person, based on dollar amount
- Payment Release — a deliberately separate step from approval
Stage 1: Intake and Coding
Every incoming vendor bill needs to be logged immediately (not batched weekly) and coded to the correct expense category or purchase order. This step should have one clearly assigned owner — typically a bookkeeper or AP clerk — whose specific job is to make sure nothing sits unlogged. Without this step done consistently, later approval-stage delays are almost guaranteed, since approvers can't act on a bill they don't know exists yet.
Stage 2: Tiered Approval
For most small and mid-sized businesses, two approval tiers are genuinely enough:
| Bill Amount | Approver |
|---|---|
| Below threshold (e.g., under $1,000) | Direct manager or department head |
| Above threshold | Finance lead or owner |
Adding more tiers than this typically slows the process down without meaningfully reducing risk, unless the business has genuinely complex, high-value purchasing patterns that justify it. The specific dollar threshold should reflect what's actually material for your business — a threshold too low creates approval-fatigue on routine bills; one too high defeats the purpose of oversight.
Stage 3: Payment Release
This is the step most small businesses skip entirely, and it's genuinely important: payment release should be a separate action from approval, ideally performed or at least confirmed by a different person than the one who approved the bill. This isn't about distrust — it's a basic control that means no single person can both approve and execute a payment without a second set of eyes anywhere in the process.
Why Separation of Duties Matters
Separation of duties is the internal-controls term for exactly this principle: splitting approval and payment-execution between different people (or requiring a second sign-off before release) closes the most common vulnerability in a small business's payment process — one person with the ability to both approve and pay an invoice, with no check in between. This is one of the simplest, highest-value controls a growing business can implement, and it costs nothing beyond a small amount of process discipline.
Not Every Bill Needs the Same Process
Applying full multi-step review to every single bill creates two problems: it slows down routine payments unnecessarily, and it can lead teams to start skipping steps on bills that genuinely need scrutiny, out of sheer approval-fatigue. A more workable approach:
- Recurring, pre-approved vendors (rent, standard SaaS subscriptions matching budget) — streamlined, lighter-touch approval if the amount matches what's already expected
- New vendors or unusual amounts — always full review, no exceptions
- One-time or unusually large purchases — always the higher approval tier, regardless of vendor history
Setting Up Approval Rules in Your Accounting Software
Zoho Books, QuickBooks, and Xero all support configurable approval rules — bills can route automatically to the correct approver based on amount or vendor, with the approval trail logged automatically for audit purposes, rather than relying on manual email chains that are easy to lose track of. Setting this up once, correctly, removes most of the "whose job is this" ambiguity that causes delays in the first place.
FAQ
For most small and mid-sized businesses, two tiers is enough: a direct manager or department head approves bills under a set threshold, and a finance lead or owner approves anything above it. More tiers than that usually slow the process down without meaningfully reducing risk, unless the business has genuinely complex, high-value purchasing.How many approval levels does an AP workflow actually need?
This is a basic internal control called separation of duties. If one person can both approve an invoice and release payment, there's no check against a fraudulent or mistaken payment going out — splitting these two steps between different people (or requiring a second sign-off before payment release) is one of the simplest, highest-value controls a small business can put in place.Why should the person who approves a bill not be the same person who pays it?
Unclear ownership, not too many approval steps. When it's not obvious whose job it is to review a specific bill, it sits in an inbox until someone happens to notice it — usually right before a payment deadline. A workflow with clearly assigned owners at each stage, even a simple one, resolves this more effectively than adding more approvers.What's the biggest cause of AP approval delays?
No — recurring, pre-approved vendors (rent, standard software subscriptions) can reasonably skip individual approval if the amount matches what's already budgeted, while new vendors or unusual amounts should always go through full review. Treating every bill identically either creates unnecessary friction on routine payments or, worse, normalizes skipping review on ones that genuinely need it.Should every vendor bill go through the same approval process?
A slow approval process is one of the most common reasons businesses miss early payment discounts entirely — if a bill sits in approval limbo for two weeks, the discount window may have already closed by the time it's approved for payment. A workflow with clear, fast turnaround times at each stage is what actually makes capturing these discounts possible in practice, not just in theory.How does an AP approval workflow affect early payment discounts?
Yes — Zoho Books, QuickBooks, and Xero all support configurable approval rules, routing bills to the right approver automatically based on amount or vendor, and logging the approval trail for audit purposes without relying on manual email chains.Can AP approval workflows be automated in accounting software?
Conclusion
A good AP approval workflow isn't defined by how many people sign off on a bill — it's defined by whether every bill has a clear, single owner at every stage, and whether approval and payment stay meaningfully separate. Get those two things right, and both the speed and the safety of the process improve together, rather than trading one off against the other.
Want your AP process set up and run without it depending on someone remembering to check an inbox? Our Finance Operations service handles exactly this. Book a free consultation to talk through your current setup.