.svg)
Most finance teams have an invoice approval process. Very few have one that works well under pressure.
When invoice volumes are low and the team is small, email approvals feel manageable. Someone forwards an invoice, the manager approves it, the AP team processes it. Simple enough. But as the business grows, the same process that worked at 50 invoices a month starts to crack at 300. Approvers become bottlenecks. Invoices sit in inboxes for days. Suppliers follow up. Late payment fees accumulate. And the AP team spends more time chasing approvals than processing them.
According to Ardent Partners' 2025 State of ePayables report, 49% of AP leaders say invoice approvals take too long, and 48% report high levels of invoice exceptions and manual interventions. These are not isolated problems. They are the predictable result of approval processes that were designed for a smaller, simpler operation and never rebuilt as the business scaled.
This guide covers how to design an invoice approval workflow that holds up at scale, what to look for when automating it, and the mistakes that most businesses make along the way.
Email-based invoice approval is the default in most mid-market businesses. An invoice arrives, someone forwards it to the relevant manager, the manager replies to confirm approval, and the AP team processes it. On the surface, this works.
The problems are structural. Email provides no visibility into where an invoice is in the approval process at any given moment. There is no automatic escalation when an approver does not respond. There is no audit trail that a compliance team or auditor can rely on. And there is no way to enforce approval thresholds consistently, because the process depends on individuals following an informal convention rather than a system enforcing a rule.
According to Tipalti's 2025 Global Finance Outlook research, 28% of finance professionals say communication gaps between departments are the primary cause of AP process delays. In email-based workflows, those gaps are structural. The invoice leaves the AP team's hands and enters a system, the approver's inbox, that the AP team has no visibility into and no control over.
This is the scenario that most exposes the fragility of manual approval workflows. A department head is on annual leave. Their inbox is unmonitored, or monitored intermittently. Invoices accumulate. Some have payment terms that are already running. By the time the approver returns, several invoices are overdue, a supplier has sent a reminder, and the AP team has been manually chasing an update for a week.
In a well-designed automated workflow, an unavailable approver triggers an automatic escalation to a defined substitute or the approver's manager. The invoice keeps moving. The payment terms are respected. Nobody has to chase anything manually.
ApprovalMax's Q1 2026 platform benchmarks found that with intelligent approval routing, 25% of all invoices are fully authorised in under two hours, and 50% are completed within 24 hours. For businesses chasing early payment discounts, that speed is directly linked to margin improvement.
The direct cost of slow approval is the late payment. A supplier invoice that should have been paid in 30 days takes 45 because it sat in an approver's inbox for two weeks. The supplier charges a late payment fee. Or simply notes the pattern and, over time, adjusts how they prioritise this customer's orders.
The indirect cost is harder to measure but equally real. Artsyltech's 2026 research found that manual invoice processing workflows experience an average approval delay of 12 to 18 days, with 23% of invoices requiring rework due to data entry errors or missing information. Every rework cycle adds days to the approval timeline and absorbs team capacity that should be directed elsewhere.
There is also the discount capture cost. Early payment discounts, typically 1 to 2% of invoice value, require payment within a compressed window, often 10 days. A business with a 12 to 18 day average approval delay cannot capture those discounts reliably. At scale, that is a meaningful margin leak.
A well-designed approval workflow answers three questions for every invoice: who needs to approve it, under what conditions does that change, and what happens if they do not respond in time?
The answers should be documented and enforced by the system, not left to individual judgement. A typical threshold structure for a mid-market business looks like this:
Escalation rules sit on top of this. If an invoice has not been actioned within three business days, it automatically escalates to the approver's manager. If the approver is marked as unavailable, it routes to a defined substitute from the moment it is assigned.
A checklist is a list of things someone needs to do. A workflow is a system that ensures those things happen in the right order, by the right person, within the right timeframe, with a documented trail of what occurred.
Most email-based approval processes are checklists. They rely on people following the agreed steps consistently. The problem is that consistency is hard to maintain at scale, under pressure, and across a team where different people have different habits and different interpretations of the rules.
A workflow enforces the process. It routes the invoice automatically. It tracks status in real time. It escalates when action is needed. And it records every step, so the audit trail exists without anyone having to compile it manually.
The finance teams with the most effective accounts payable workflows share several characteristics:
Approval happens at the purchase order stage, not the invoice stage. When a purchase order is raised and authorised, the business commitment has already been approved. The invoice that matches it should flow through quickly, because the decision to spend that money was made upstream. Only invoices with discrepancies should require significant approval effort.
GL coding is separated from approval. Combining the decision about whether to pay an invoice with the decision about how to code it creates bottlenecks and errors. In well-designed workflows, finance codes the GL account and the department manager approves the business validity. These are different questions for different people.
Mobile approval is the default, not an afterthought. Approvers are not always at a desk. An approval workflow that requires logging into a desktop system to action invoices will have slower cycle times than one that supports mobile or email-based approval with a full audit trail.
Automating a broken or poorly designed workflow produces a faster broken workflow. Before selecting a platform, it is worth spending time mapping the current state accurately.
Start by following a single invoice through your current process from the moment it arrives to the moment it is paid. Document every step:
Do this for three or four different invoice types: a routine purchase from a regular supplier, an invoice from a new supplier, a high-value invoice that requires senior approval, and an invoice with a discrepancy. Each one will likely reveal different process gaps.
When talking to the people who currently touch invoice approvals, four questions tend to surface the most useful information:
The answers to these questions shape the design of the automated workflow. An approver who says they delay approval because they cannot see the corresponding purchase order needs a system that surfaces that document automatically at the point of approval. An approver who says they are interrupted constantly by email requests needs a mobile-friendly interface with batched notifications.
Too many approval levels. Every additional approval step adds time and creates a potential bottleneck. Approval hierarchies should reflect genuine control requirements, not organisational politics. If an invoice under £200 requires three levels of approval, the workflow is not controlling risk. It is adding friction.
Thresholds that do not match actual delegation authority. If the documented policy says invoices above £10,000 require CFO approval, but in practice the Finance Manager approves them, the documented policy is the wrong policy. Design the workflow around how decisions are actually made, then formalise the right version of that.
No auto-approval for matched invoices. If an invoice arrives that perfectly matches an approved purchase order in price, quantity, and supplier, it should not require a human to manually approve it. Auto-approval for matched invoices, with a clear audit trail, removes the most routine step in the process and lets the team focus on exceptions.
Most approval workflow platforms use rules-based routing: if the invoice meets condition A, route it to approver B. This works for straightforward cases, but it requires someone to anticipate every possible condition and write a rule for it. When a new scenario arises that was not anticipated, either the invoice routes incorrectly or someone has to intervene manually.
AI-driven routing interprets context rather than matching conditions. It can recognise that an invoice from a supplier who has previously submitted invoices with errors should receive additional scrutiny, even if the amount is below the standard threshold. Or that an invoice from a long-standing, reliable supplier with a clean match record can move through the approval step quickly.
This is part of what makes AI-native platforms meaningfully different from rules-based systems, not just in speed, but in the quality of the routing decisions over time.
The practical test of an approval platform is whether your busiest, most senior approvers will actually use it. If the system requires logging into a dedicated portal every time an invoice needs approval, the reality is that many approvals will happen via email instead, outside the system, and the audit trail will be incomplete.
The best platforms provide approval capability through email or mobile with a single click, while capturing that action within the system. The approver does not need to change how they work. The audit trail is complete regardless.
An approval workflow that is not connected to your ERP creates a data reconciliation problem. Approvals happen in one system. Payment happens in another. Someone needs to manually reconcile the two, or run the risk that a payment goes out for an invoice that was not properly approved in the system of record.
Real ERP integration means that when an invoice is approved in the workflow platform, that approval is reflected in the ERP immediately. GL coding, supplier records, and payment terms are pulled from the ERP into the approval workflow, so the approver is working with accurate, current data. And the approved invoice feeds back into the ERP without any manual re-entry.
Dost's approval workflow module is configurable by the finance team without developer involvement. Approval thresholds, escalation rules, routing logic, and substitute approvers are all set up through a straightforward interface that does not require technical expertise to maintain.
Approvals can be actioned via email or mobile with a full audit trail captured automatically. Every step from invoice receipt to payment authorisation is logged, timestamped, and available for audit without anyone having to compile it.
The workflow is integrated with Dost's 3-way matching and data extraction modules, so by the time an invoice reaches the approver, it has already been matched against the purchase order and delivery note. The approver sees the invoice, the match status, and any discrepancies, all in one view, without having to consult a separate system.
Want to see what this means for your team's processing time and cost? Use Dost's savings calculator to run the numbers.
The right answer depends on the business, but as a general principle, fewer levels with clearer thresholds produce better outcomes than more levels with overlapping responsibilities. Most mid-market businesses operate effectively with two to three approval tiers based on invoice value, with additional controls for new suppliers or high-risk categories. The American Payroll Association's 2025 benchmark study found that organisations average 8.2 days to process invoices manually and 2.1 days with automation. Each additional approval level that is not strictly necessary adds to that 8.2 day baseline.
With modern platforms, yes. The configuration question is one of the most important to ask during vendor evaluation. Some platforms require developer involvement or vendor support to modify routing rules, thresholds, or escalation paths. Others provide a self-service configuration interface that a finance operations manager can use directly. The latter is significantly more practical for a growing business where processes change regularly.
A well-designed automated workflow handles urgency in two ways. First, escalation rules can be configured to accelerate the timeline for invoices flagged as urgent, routing them to a senior approver immediately rather than following the standard sequence. Second, suppliers with time-sensitive invoices, those with early payment discount windows, for example, can be configured to trigger priority routing automatically based on the payment terms captured from the invoice. The key is that urgency is handled by the system, not by someone manually intervening and bypassing the normal controls.
An invoice approval workflow that cannot scale is not a workflow problem. It is a business risk. Every day that invoices sit unapproved is a day that payment terms erode, supplier relationships strain, and the AP team absorbs work that should not require human attention.
The fix is not more people. It is a better-designed process, enforced by a system that routes automatically, escalates without prompting, and records every step without anyone having to maintain the audit trail manually.
The starting point is mapping what you have today, honestly, before selecting any technology. The design decisions that follow from that mapping will determine whether the automated workflow holds up under the pressure that the manual one could not.
See how Dost's approval workflows work for your team.
