Browse Business Software Categories

A
B
C
D
E
F
H
I
M
N
P
R
S
W
Close  

Accounting

Financial Management

Invoice Approval Workflows: Routing AP Invoices for Sign-Off

Sherman Hsieh
Share This Post!
Published
Invoice Approval Workflows: Routing AP Invoices for Sign-Off

Last updated: October 8, 2026 · Independent guide · We do not sell rankings or coverage.

An invoice approval workflow is the set of rules that decides who must sign off on a vendor invoice before your company pays it, in what order, and what record is kept of each decision. In a well-run AP department, the workflow routes each invoice automatically by amount, department, GL account or vendor, gives every approver a backup, and locks the approved record so nobody can change it before payment. Below are the stages, owners and controls, and how ERP and AP automation tools handle routing.

  1. Receive and capture the invoice in one place.
  2. Validate and match it against the vendor master, the purchase order and the receipt.
  3. Code it to GL account, department, location and project.
  4. Route it to approvers using your approval matrix.
  5. Approve, reject or delegate within the approver’s authority limit.
  6. Escalate invoices that stall or fail a rule.
  7. Release for payment and lock the approved record.
  8. Retain the audit trail and review the rules on a schedule.

Stage roles at a glance

The table below is an illustration of how ownership often splits in a mid-sized company. Whatever your structure, the person who enters an invoice should not give final approval or release the payment.

Stage Responsible Accountable Consulted / informed
Capture and validate AP specialist AP manager Purchasing, receiving
Coding AP specialist or requester Budget owner Controller (new GL accounts)
Routing rules System administrator Controller Internal audit, CFO
Approval and delegation Budget owners Department heads, CFO above limits AP manager (informed)
Escalation AP manager Controller Approver’s manager
Payment release Treasury or designated payer Controller or CFO AP manager
Audit trail and rule review AP manager Controller External auditors

Stage 1: Receive and capture the invoice

Owner: AP specialist. Input: PDF, paper, portal or EDI invoice. Output: a draft bill in the system with an image or file attached.

Every invoice should arrive through one channel: a dedicated AP inbox, a supplier portal or EDI. Our guide to the EDI 810 invoice covers electronic invoices. The control here is completeness, because an invoice in a budget owner’s personal inbox is invisible to AP and to your accrual.

What goes wrong: vendors email the person who ordered the goods, and AP learns about the bill when the vendor chases payment. Tell vendors in writing where to send invoices.

Stage 2: Validate and match

Owner: AP specialist. Input: draft bill, vendor master record, PO and receipt. Output: a validated bill, or an exception.

Check that the vendor is active, the invoice number is not a duplicate and the remit-to details match the vendor master. For PO invoices, a two-way or three-way match compares the invoice to the PO and receipt. Many companies treat a clean match as the approval, because the budget owner approved the spend on the PO.

Controls: duplicate checks, match tolerances set by the controller, and separate verification of bank detail changes. What goes wrong: loose tolerances, or matched invoices sent for a second “courtesy” approval that adds days without adding control. APQC’s open benchmark puts the median time to resolve an invoice error at 4.0 days across 2,861 organizations (APQC, no date shown), so every exception you prevent here saves time later.

Stage 3: Code to GL, department and project

Owner: AP specialist or the requester. Input: validated bill. Output: bill lines with GL account, department, location, class or project.

Coding drives routing, so the department and GL account must be correct before the bill enters the workflow. PO invoices inherit coding from the PO. For non-PO invoices, store default coding on the vendor record.

What goes wrong: invoices split across departments. Sage Intacct’s department-based value approval, for example, requires all lines on a bill to carry a single department unless the vendor has its own assigned bill approver, in which case the department rule is bypassed (Sage Intacct Help, October 1, 2026). Test split invoices before you go live.

Stage 4: Route by approval rules

Owner: system administrator configures; the controller owns the rules. Input: coded bill. Output: an approval request in the right person’s queue.

Your approval matrix is the written policy behind the routing. Most companies combine four dimensions:

  • Amount: higher totals go to more senior approvers or add approval levels.
  • Department or cost center: the budget owner for the coded department approves first.
  • GL account: sensitive accounts such as legal fees or capital assets add a specialist approver.
  • Vendor: a named owner approves recurring vendors such as software subscriptions.

The matrix below is an illustration for a company with about $100 million in revenue. Take your thresholds from your board-approved delegation of authority.

Invoice type Amount (illustration) Approvers Notes
PO invoice, matched within tolerance Any None beyond the match PO approval covered the spend
Non-PO invoice Up to $5,000 Department budget owner One approver
Non-PO invoice $5,000 to $50,000 Budget owner, then department head Sequential
Non-PO invoice Over $50,000 Budget owner, department head, CFO Sequential
Legal fees GL account Any General counsel, plus amount rule Specialist added by GL
Capital asset GL accounts Any Controller, plus amount rule Confirms capitalization

What goes wrong: rules that live only in people’s heads, and rules that drift after a manager leaves or a department is renamed. Sage Intacct notes that if an approver is later restricted by department or entity, that approver stops receiving notifications and bills can stay stuck in submitted status (Sage Intacct Help, October 1, 2026).

Stage 5: Approve, reject or delegate

Owner: budget owners and executives. Input: approval request with the invoice image, coding and PO or contract. Output: an approved or rejected bill with a timestamped decision. A rejection needs a reason and should return the bill to AP or the requester.

Delegation is the control most often handled badly. Every approver needs a named substitute set up in the system before an absence, not a forwarded email. Check two points:

  • Whose limit applies. NetSuite’s SuiteApprovals documentation states that when you delegate approval, your approval limits still apply (Oracle NetSuite Help, no date shown). Your policy should say whether a delegate may exceed their own limit.
  • Who the fallback is. In Business Central, a delegated request goes to the designated substitute, then the direct approver, then the approval administrator, in that order (Microsoft Learn, October 16, 2025).

What goes wrong: self-approval, and delegation chains that end with a junior employee approving a large invoice. Block self-approval in the system and review active delegations monthly.

Stage 6: Escalate stalled and failed invoices

Owner: AP manager. Input: overdue approvals and rule exceptions. Output: a resolved bill or a documented hold.

Set a service level for each approval step, such as two business days, with an automatic reminder and then escalation to the approver’s manager. Business Central’s overdue approval notification, for example, alerts the approver, the approver’s own approver and the requester (Microsoft Learn, October 16, 2025).

What goes wrong: AP approving on the manager’s behalf to hit a payment run, which breaks segregation of duties. If an urgent invoice cannot wait, record a documented override signed by the controller.

Stage 7: Release for payment and lock the record

Owner: treasury or a designated payer. Input: fully approved bill. Output: a payment in the next run, with the bill locked.

Invoice approval and payment authorization are separate controls. Ramp offers a payment release step in which a designated payer reviews an approved bill before funds move, on its Plus plan (Ramp Help Center, no date shown). Pair payment release with bank-side controls such as positive pay.

The approved record must not change silently. Ramp states that changing the vendor, total amount, payment details or payment schedule always restarts the approval chain (Ramp Help Center, no date shown). Test whether an edited approved bill returns to the queue in your system.

What goes wrong: admin roles that bypass approval. BILL’s developer documentation states that administrators can pay a bill regardless of policy or approval status (BILL Developer Docs, no date shown). Keep admin roles few and review their payments.

Stage 8: Retain the audit trail and review the rules

Owner: AP manager, with the controller accountable. Input: approval history. Output: evidence for auditors and an updated matrix.

For each invoice, your system should show who approved, when and under which rule, including delegated and bypassed steps. Sage Intacct records bypassed approval rules as Approved in the audit trail (Sage Intacct Help, October 1, 2026), so be ready to explain steps that show as approved without a named person.

For public companies, the auditing standard for internal control over financial reporting describes expenditures being made “only in accordance with authorizations of management and directors” (PCAOB AS 2201, paragraph .A5, no date shown). Private company auditors ask the same questions. The IRS says to keep income tax records for 3 years in general, and 7 years if you claim a bad debt deduction or a loss from worthless securities (IRS, June 30, 2026). Many companies keep AP approval records for 7 years.

Review the matrix yearly and after every reorganization. Our guide to ERP security and internal controls covers the related user access reviews.

Metrics to track

Review these monthly by approver and department. Our article on AP and AR KPIs and dashboards covers the wider payables picture.

  • Approval cycle time: days from submission to final approval, by approver. APQC’s open benchmark shows a median of 15.0 days from receipt of invoice until payment is transmitted, across 2,226 organizations (APQC, no date shown).
  • Invoices past the approval service level: shows where escalation or delegation is failing.
  • Touchless rate: share of PO invoices that match and pass without manual approval.
  • Rejection rate and reasons: coding rejections point back to Stage 3.
  • Overrides and admin payments: count and value of invoices paid outside the normal workflow. The target is close to zero.
  • Late payment fees and missed early-payment discounts: the cost of slow approvals in dollars.

How software supports each stage

Each vendor below sells the product described, and the documentation cited is its own.

Oracle NetSuite. The SuiteApprovals SuiteApp covers vendor bills with hierarchical or custom routing, employee and general amount limits, delegation and approval history (Oracle NetSuite Help, no date shown). Employee records carry a Vendor Bill Approver, Vendor Bill Approval Limit and Vendor Bill Entry Limit (Oracle NetSuite Help, no date shown). Delegation is limited to employees in the same subsidiary (Oracle NetSuite Help, no date shown).

Microsoft Dynamics 365 Business Central. Approval User Setup assigns each user an approver, a Purchase Amount Approval Limit in local currency, a substitute and one approval administrator (Microsoft Learn, June 17, 2026). That page sets limits by user and amount and does not describe department routing, so ask your partner how they would build it.

Sage Intacct. AP bill approval policies combine four rule types: vendor-based, value approval by bill total, value approval by transaction department, and user level (Sage Intacct Help, October 1, 2026).

AP automation tools. BILL includes custom approval policies on its Corporate plan at $89 per user per month and on Enterprise (custom pricing), but not on Essentials ($49) or Team ($65) (BILL pricing, no date shown, checked October 8, 2026). Ramp routes by amount on all plans and by department, location, vendor, entity and GL fields on Ramp Plus, listed at $15 per user per month plus a platform fee (Ramp Help Center, no date shown; Ramp pricing, no date shown, checked October 8, 2026). A separate tool adds a sync point, so confirm that approval status and coding flow back to your ERP.

How we researched this

We read the pages ranking for “invoice approval workflow” in October 2026, which were mostly vendor glossaries and blogs from AP software sellers (Zone & Co, Yooz, Peakflo, Hyperbots). They rarely cite sources, and none compares how named systems handle delegation, split coding or edits after approval. We then read the vendor documentation for NetSuite, Business Central, Sage Intacct, BILL and Ramp, APQC’s open benchmarks, PCAOB AS 2201 and IRS record retention guidance. Features can change with new releases.

Related guides

Frequently asked questions

Do PO-backed invoices need a separate approval?

Often they do not. If the PO was approved and the invoice matches the PO and receipt within tolerance, many companies treat the match as the approval. Invoices that fail the match, or non-PO invoices, go through the approval matrix.

How many approval levels should an AP invoice have?

Most mid-sized companies use one approver for small non-PO invoices and add a level at each major threshold, ending with the CFO. Each level adds time, so add one only where the amount or risk justifies it.

What should happen when an approver is on vacation?

The approver should set a named delegate in the system before leaving, with start and end dates. Avoid forwarding invoices by email, because the system then records the wrong approver.

How long should we keep invoice approval records?

The IRS says to keep tax records for 3 years in general and longer in some cases, such as 7 years for bad debt deductions. Many companies keep AP approval history for 7 years; confirm the period with your auditors.

Sources

Sherman Hsieh

CEO & Editor-in-Chief, Business-Software.com
Independent analysis of enterprise software — ERP, CRM and more
Sherman Hsieh is the founder, CEO, and editor-in-chief of Business-Software.com. He leads the site's independent, buyer-focused coverage of ERP, CRM, and other business systems, including vendor-neutral comparisons, pricing analysis, and implementation guidance. Before founding Business-Software.com, Sherman was an executive at Siebel ...

Users Who Read This Article Also Read