Create an Invoice Approval Flowchart from Excel
See invoice rows become a flowchart with duplicate checks, purchase-order matching, tolerance, supplier queries and payment approval.
An invoice approval map must distinguish duplicate prevention, three-way matching and supplier correction before payment release.
The short version
- Block duplicate invoices before matching or payment.
- Separate PO/GRN matching from coding and tolerance review.
- Return supplier queries to the right recheck step.
Model the control sequence, not just the payment status
Invoice registers contain invoice number, supplier, PO and amount. A flowchart needs the checks performed on that record. In Excel, make separate rows for duplicate detection, PO reference, three-way match, tolerance review, supplier query and final payment. The duplicate outcome should stop or block the invoice rather than rejoin the payment path.
The example below uses an Accounts Payable route with exception handling. Its sheet shows a supplier correction loop and a match-within-tolerance decision; those two branches are where many invoice diagrams lose their meaning. The live chart is backed by /templates/invoice-approval-process.
The invoice approval spreadsheet and resulting flowchart
Open the sheet view to inspect the real invoice approval rows behind this editable QueryChart visualization.
Start with the trigger
The first decision blocks duplicates early, keeping an already-paid invoice out of the matching and payment path.
Add the decision routes
PO reference, three-way match and tolerance decisions create distinct routes for valid and disputed invoices.
Review the complete process
The complete chart includes supplier correction and recheck loops before the approved invoice can move toward payment.
How it works
List document and match checks
Start with invoice receipt and capture. Add duplicate, PO reference, three-way match and tolerance checks as separate rows.
Route supplier exceptions
Give unmatched and out-of-tolerance cases a query row and a supplier-correction loop. Label the successful recheck branch.
Trace to payment or block
Render the table and follow a clean invoice, a duplicate and a corrected invoice. Confirm that only an approved invoice reaches payment.
Mistakes to avoid
Paying after an unresolved query
A generic Next column can accidentally reconnect the supplier-query branch to payment. Route it back through a match or approval check.
Edit the invoice approval example
Open the source rows, replace the sample steps and verify every path in the rendered chart.
Frequently asked questions
What is the three-way match step?
It checks the invoice against the purchase order and goods receipt before payment approval.
How do I show a duplicate?
Use a decision with a Block duplicate route and a distinct Continue route.
Should supplier corrections be a loop?
Yes. The corrected or credited invoice should return to the relevant check before it can be approved.