Invoice approval flowchart template

Invoice approval works best as a decision flow rather than a swimlane, because the hard part is which path an invoice takes, not who is holding it. We recommend following this process:

1. List every state an invoice can be in, from submitted through to paid.
2. Write down the questions that route it: does it match the purchase order, does it exceed an approval threshold?
3. Turn each question into a decision node with both exits drawn, including the exception routes.
4. Name the approver for each value band, so no branch ends without an owner.
5. Draw the diagram in the tool your audience already uses. A free template removes most of the layout work.

A three-way match checks the invoice against two other documents before payment is approved: the purchase order, which shows what was ordered, and the goods receipt, which shows what actually arrived. All three must agree on quantity and price. It exists to catch the three most common accounts payable failures: being billed for goods never ordered, goods never received, or at a price nobody agreed. It is the single most effective control in AP, which is why it sits before any approval decision on the diagram.

A two-way match compares the invoice to the purchase order only. A three-way match adds the goods receipt. The difference is whether you are confirming that something was ordered or that it actually arrived. Most organisations use three-way matching for physical goods and two-way for services, where there is no receipt to check against. If you run both, add a decision node before the match step to route by invoice type.

Each one routes the invoice down a different path:

• Match OK: the control gate. A no returns the invoice to the vendor rather than continuing.
• Over threshold: the authority gate. A yes requires manager and executive approval; a no needs the manager alone.

Add a further decision for contracted suppliers, recurring invoices, or a fast-track band under a low value; the branches stay attached as the diagram reflows.

It returns to the vendor rather than entering an approval queue. That is a deliberate choice: an invoice with a quantity or price discrepancy is the vendor's to correct, and holding it internally while someone investigates is how invoices age past their payment terms. Most AP processes leave this branch undrawn, which is exactly why mismatched invoices sit unresolved. Drawing it forces the question of who chases the vendor and by when.

An approval threshold is the value above which an invoice needs a second, more senior signature. Below it, a manager can approve alone; above it, the risk is judged high enough to warrant executive sign-off. There is no universal figure — it depends on your revenue, your risk appetite, and what your auditors expect. Set it low enough to catch material spend and high enough that executives are not approving stationery. Edit the value on the decision node to match your own policy.

The two approval steps use the manual operation shape rather than a standard rectangle. In flowchart notation that distinguishes a step a person performs from one a system performs automatically. It matters here because approval is the one step in the process that cannot be automated away without losing control. Making it visually distinct signals that to anyone reading the diagram in an audit.

Segregation of duties is the point of the process, so no single person should own the whole flow. A common split:

• Accounts payable: capture and the three-way match.
• Budget holder or manager: approval below the threshold.
• Finance director or executive: the second signature above the threshold.
• Treasury or AP: releasing the payment, but never the same person who approved it.

If the same person can approve and release, the threshold gate is doing nothing.

PowerPoint can do it with SmartArt and the Shapes gallery, but the work is manual: you place each diamond yourself, label both exits, and reattach connectors every time something moves. For a flow with two decision nodes and converging approval paths, this becomes the reason the diagram stops getting updated.

A faster route is the Lucen Flowchart tab, which snaps connectors to shape anchors and reflows the diagram with Auto layout when you add a branch. Either way, the result stays a set of native PowerPoint objects on your slide.

The download is a free .pptx made of native PowerPoint shapes, so anyone can open, read, and edit it, and you can share it as you would any deck; recipients need nothing installed.

The smart connectors, Auto Layout, and Lucen AI come from the Lucen Flowchart add-in, which adds a Lucen Flowchart tab to the ribbon and runs on Windows with PowerPoint 2016 or later and with PowerPoint for Microsoft 365. PowerPoint for the web, Mac, and mobile are not supported. Setup and troubleshooting steps are in Lucen Support.