RoutineSmithBuild an invoice approval workflow that does not confuse routing with permission
Define invoice paths, evidence, amount thresholds and named roles before a tool sends approval requests. Keep payment release separate and send uncertain cases to a visible exception route.
RoutineSmith editorial team · Reviewed 14 September 2026 · Sources checked 14 September 2026An invoice approval workflow should first identify the invoice path, verify its required evidence, apply the current amount band and route the request to named roles. The payment-release role should remain separate from invoice preparation, review and approval. Exceptions, unavailable approvers and vendor-detail changes need explicit stop routes rather than automatic workarounds.
Use the flowchart as a control map—not as an approval policy
The one-page PDF maps capture, validation, routing, decision, payment release and exception stops. Print it for a workshop or keep it beside the editable matrix. Replace every example role and threshold with your organization’s approved policy before configuring software.
Capture → validate → route → decide → release → reconcile
Missing evidence · unavailable approver · rule gap · vendor change · rejection or expiry
Download the printable invoice approval workflow flowchart (PDF)
Start with the transactions your team actually receives
Do not begin with software screens. List the recurring paths and the evidence that proves each one is ready for an approval decision. A PO invoice is not the same control problem as a subscription renewal, a credit note or a request to change supplier banking details.
| Path | Evidence before approval | Likely owner | Hold condition |
|---|---|---|---|
| PO invoice | Purchase order, receipt and invoice | Budget or business owner | Three-way match fails or amount exceeds authority |
| Non-PO invoice | Business reason, coding and invoice | Budget owner plus finance when required | Missing purpose, evidence or permitted category |
| Subscription | Contract, owner and renewal date | Service or cost owner | Unrecognized renewal, changed terms or absent owner |
| Vendor detail change | Independent verification and change record | Vendor-control and finance owners | Request relies only on the invoice or email thread |
| Credit note | Original invoice, credit and application record | AP and finance owners | Credit cannot be linked or creates an unexplained balance |
| Urgent invoice | Normal evidence plus written urgency reason | Normal authority; no silent bypass | Urgency is used to skip verification or payment controls |
Turn approval limits into explicit amount bands
For every path, record the minimum and maximum amount and the business and finance roles that must approve it. Test the exact boundary values: immediately below, at and immediately above the threshold. If two rules overlap or leave a gap, the workflow should stop for correction rather than choose one silently.
Microsoft’s approvals documentation supports first-response, all-response and sequential approval patterns. The choice is a workflow behavior, not a substitute for a maintained authority matrix. Use sequential stages when later approval must depend on an earlier decision, and retain the response history.
Do not let one role control the full transaction
GAO internal-control guidance describes approval controls as authorized people approving transactions against management criteria. It also identifies matching the purchase order, receiving report and vendor invoice before payment approval, and describes segregation of duties as reducing the chance that one person can both cause and conceal an error or fraud.
Preparation · AP review · business approval · finance approval · payment release · reconciliation
Document the constraint · add owner review · use bank controls · review the activity independently after release
The downloadable matrix flags a rule when the payment-release role also appears as the AP reviewer, business approver or finance approver. It cannot detect two different role names assigned to the same person, so the finance owner must review the real assignments.
Write the stop routes before the happy path goes live
- MISSING APPROVER: hold the request; do not route it to the requester or workflow owner by default.
- ABSENCE: use a documented substitute with equivalent authority, a start date and an expiry date.
- THRESHOLD GAP: stop and correct the matrix before processing the invoice.
- VENDOR CHANGE: verify through a trusted channel independent of the invoice message.
- URGENT PAYMENT: preserve normal verification and authority; record the reason instead of silently bypassing controls.
Use a visible invoice exception queue for unresolved evidence and revalidation. Approval should resume only after the recorded hold condition is cleared.
Let AI propose data—not financial authority
An AI step may propose the invoice type, extract the total or summarize the evidence. It can be wrong while still producing a valid-looking answer. Route the proposed values through deterministic checks and the current approved matrix. Do not let the model add an approver, change a threshold, update supplier banking details or release payment.
NIST’s AI RMF calls for defined tasks and differentiated roles and responsibilities for human-AI oversight. In this workflow, that means documenting which fields AI may propose, which checks are deterministic and which named people remain responsible for approval and release.
Test the matrix at the boundaries and during failure
- Run one normal case for every invoice path.
- Test amounts immediately below, at and above every threshold.
- Remove an approver and confirm the request stops.
- Assign the payment releaser to a review role and confirm the conflict is visible.
- Change supplier details and confirm independent verification is required.
- Reject a request and confirm later actions do not run.
- Use an expired substitute and confirm the route stops.
- Reconcile the approval record with the payment and source evidence.
Measure missing or incorrect routes, review time, exceptions, unauthorized side effects and unreconciled payments separately. A successful notification does not prove that the financial control worked.
Write the matrix before connecting an approval tool.
The editable Excel template includes eight fictional invoice paths, amount bands, evidence fields and live checks for missing setup and incompatible payment-release roles. No account or email is required.
Download the free approval matrixInvoice approval workflow questions
What is an invoice approval matrix?
It is a maintained control that maps invoice paths and amount bands to the roles, evidence and checks required before payment may be released.
Should every invoice use the same approver?
Usually not. The route should reflect the invoice path, amount, business ownership and risk. The organization must define its own limits and substitute coverage.
Can the requester approve the invoice?
A requester may confirm that goods or services were received, but financial approval and payment release should follow the organization’s documented authority and separation rules.
How should vendor bank-detail changes be handled?
Treat them as a separate high-risk process. Verify the change through a trusted independent channel and retain the evidence before updating the approved vendor record or releasing payment.
What can AI do in this workflow?
AI can propose extracted fields, a document type or a likely route. Deterministic rules should apply the current matrix, and named humans should retain approval and payment authority.
Is this legal or accounting advice?
No. It is operational training. Approval limits, tax records, banking controls and legal duties vary by organization and jurisdiction.