Invoice Approval Workflow: Steps, Rules and Templates

Quick answer: An invoice approval workflow is the set of steps every supplier bill follows before payment: receive and log it, check it for duplicates and errors, match it to the purchase order and receipt, code it, route it to the right approver by amount, then schedule payment. A written approval matrix and tolerance rules keep it fast and controlled.

Most late supplier payments are not caused by a lack of cash. They happen because an invoice sat in someone's inbox, went to the wrong approver, or was missing a purchase order number. Most overpayments happen for the opposite reason: invoices were approved too easily. A clear invoice approval workflow fixes both problems by deciding in advance who checks what, in which order, and what happens when something does not match.

This guide walks through the standard steps, shows how to build an approval matrix, works through a tolerance example with real numbers, and ends with a checklist and the most common mistakes. It is written for small and mid-sized businesses that pay suppliers, but suppliers can use it too: once you know how a client approves bills, you can send invoices that sail through. If you are on that side, the free invoice generator creates a clean PDF with all the fields approvers look for.

What an invoice approval workflow does

An approval workflow is a control. It exists to answer three questions before money leaves the business:

• Is the invoice real? It comes from a supplier you actually use, it is not a duplicate, and the bank details belong to that supplier.
• Is the invoice right? Quantities, prices, tax and totals agree with what was ordered and received.
• Is the spending authorized? Someone with budget authority for that cost center has agreed that the business should pay it.

Everything else, from reminders to dashboards, exists to answer those questions faster. If your process answers all three for every invoice, it is working. If it only answers the third ("my manager clicked approve"), it is not a real control.

The 8 steps of a standard invoice approval workflow

Most accounts payable teams follow some version of these steps. A very small business might combine several of them into one person's afternoon; a large one spreads them across systems and teams.

1. Receive. Invoices arrive in one place: a dedicated AP email address, a supplier portal or an e-invoicing network. Invoices sent to individual employees are forwarded there, not paid from the inbox.
2. Log and capture. Record the supplier, invoice number, invoice date, due date, amount and PO number. Many teams use OCR and data extraction software for this step; others type it into a spreadsheet or the accounting system.
3. Validate. Check that the supplier exists in your vendor master, the invoice is addressed to the correct legal entity, required tax details are present and the arithmetic is correct. Run a duplicate check on supplier plus invoice number plus amount.
4. Match. For purchase-order spend, compare the invoice with the PO (two-way match) and with the goods receipt or delivery confirmation (three-way match). Our guide to the three-way match explains each comparison in detail.
5. Code. Assign the general ledger account, cost center, project or department, and the correct tax treatment.
6. Route and approve. Send the invoice to the approver set by your approval matrix. Matched PO invoices may need only a light confirmation; non-PO invoices need the budget owner to confirm the spend.
7. Schedule payment. Approved invoices join the next payment run that lands on or just before the due date, or earlier if an early payment discount is worth taking.
8. Archive. Store the invoice, approvals and supporting documents together so you can answer an auditor, a tax inspector or a supplier query months later.

PO invoices versus non-PO invoices

The workflow splits into two paths at step 4. A PO-backed invoice was approved in advance when the order was raised, so the invoice approval mainly confirms that the bill matches what was authorized. A non-PO invoice, such as a utility bill, a subscription or an ad hoc repair, has had no prior approval, so the budget owner must approve the spending itself. Many businesses reduce risk by requiring a PO for any purchase above a set amount. If you are unsure where the line sits between the two documents, read invoice vs purchase order.

Building an approval matrix

The approval matrix is the heart of the workflow. It turns "ask whoever seems senior" into a rule anyone can follow. A simple matrix uses invoice amount and invoice type. The thresholds below are an illustration only; set your own based on your size and risk appetite.

Invoice type and amount	First approver	Second approver
PO invoice, matched within tolerance, any amount	Automatic or AP clerk	None
Non-PO invoice up to $1,000	Budget owner (department manager)	None
Non-PO invoice $1,000.01 to $10,000	Budget owner	Department head
Non-PO invoice $10,000.01 to $50,000	Department head	Finance director
Any invoice above $50,000	Finance director	CFO or owner
First invoice from a new supplier, any amount	Budget owner	AP manager (verifies vendor setup)

A few design rules make a matrix work in practice:

• Use roles, not names. Write "marketing manager", not "Sarah". Keep a separate list mapping roles to people.
• Plan for absence. Every approver needs a named delegate with the same or a lower limit, so invoices do not wait two weeks for someone on vacation.
• Stop invoice splitting. If someone can approve up to $10,000, a $14,000 bill split into two $7,000 invoices must still go to the higher level. Review approvals by supplier and period, not just one invoice at a time.
• Separate duties. The approver should not be the person who sets up the supplier or changes its bank details, and neither should release the payment alone. Segregation of duties is a core idea in internal control frameworks such as the one published by COSO.

Tolerance rules: a worked example

Tolerances decide how much an invoice may differ from the purchase order before a person has to look at it. Without them, every rounding difference becomes an exception; with loose ones, overcharges slip through. A common approach combines a percentage and a fixed cap, and applies whichever is lower.

Suppose your policy allows a variance of up to 2% of the PO value or $150, whichever is lower. A supplier sends an invoice for $10,450 against a PO for $10,000.

• Percentage tolerance: $10,000 × 2% = $200.
• Fixed cap: $150.
• Applied tolerance (the lower of the two): $150.
• Maximum invoice that passes automatically: $10,000 + $150 = $10,150.
• Actual variance: $10,450 − $10,000 = $450, which is $300 more than the tolerance allows.

Result: the invoice is held as an exception. AP asks the buyer whether a price increase was agreed. If not, the supplier is asked for a credit note or a corrected invoice for $10,000.

Now compare a second invoice for $10,120 against the same PO. The variance is $120, which is within the $150 tolerance, so it can be approved without manual review. Over a year, tolerances like this remove a large share of routine exceptions while still catching meaningful overcharges.

What slow approval actually costs

Delay has a price when suppliers offer early payment discounts. Take terms of 2/10 net 30: pay within 10 days and take 2% off, otherwise pay the full amount by day 30. On a $10,000 invoice, an approval that takes 15 days loses a $200 discount. Expressed as an annual rate, giving up that discount means paying 2% to keep $9,800 for an extra 20 days: (2 ÷ 98) × (365 ÷ 20) = 0.0204 × 18.25 = about 37.2% a year. Few businesses borrow that expensively on purpose. See our explainer on the early payment discount for when taking one makes sense.

Invoice approval workflow template

You can adapt this text into a one-page policy. Fill in the brackets for your business.

• Where invoices go: All supplier invoices are sent to [ap@yourcompany.com]. Employees forward any invoice they receive within one business day.
• Logging: AP logs each invoice within [2] business days, recording supplier, invoice number, dates, amount, currency and PO number.
• Required details: Invoices missing a PO number (where one was issued), a valid invoice number or the correct legal entity name are returned to the supplier.
• Matching: PO invoices are matched to the PO and receipt. Variances up to [2% or $150, whichever is lower] are accepted automatically.
• Approval: Non-PO and exception invoices are approved according to the approval matrix. Approvers respond within [3] business days or the invoice escalates to their delegate.
• Bank details: Any change to supplier bank details is verified by phone using contact details already on file before the invoice is approved.
• Payment: Approved invoices are paid in the [weekly] payment run that falls before the due date.
• Records: Invoices, approvals and supporting documents are retained for [7] years or the period required by law.

Manual, email-based or automated approval?

Approach	Works best for	Main weakness
Paper or PDF with signature	Very low volume, one or two approvers	Easy to lose; no reminders; hard to audit
Email plus a spreadsheet log	Dozens of invoices a month	Approvals scattered across inboxes; manual chasing
Accounting software approval feature	Small teams already on one ledger	Limited routing rules and matching
Dedicated AP automation platform	Hundreds of invoices or many approvers	Cost and setup time; still needs clean vendor data

Automation removes chasing and creates an audit trail, but it automates whatever rules you give it. Write the matrix and tolerances first, then choose a tool. Our guide to touchless invoice processing explains how far automation can realistically go, and accounts payable KPIs shows how to measure cycle time and exception rates once the workflow is running.

Setup checklist

• One intake address or portal for all supplier invoices, published to suppliers.
• A written approval matrix by role, amount and spend type, with delegates.
• A rule for when a purchase order is required.
• Matching rules (two-way or three-way) and written tolerances.
• Duplicate checks on supplier, invoice number, date and amount.
• Independent verification of new suppliers and of any bank detail change.
• Separation of duties between vendor setup, approval and payment release.
• Approval deadlines, reminders and an escalation path.
• A fixed payment run schedule tied to due dates.
• Document retention and an annual review of the whole policy.

Common mistakes

• Approving from the PDF alone. An approver who only sees the invoice cannot tell whether goods arrived. Give them the PO and receipt status alongside it.
• Too many approval levels. If every invoice needs four signatures, people stop reading and click approve. Reserve extra levels for higher risk.
• No duplicate check. The same invoice arriving by email and by post, or resent with a slightly different number, is one of the most common causes of overpayment. Our guide to duplicate invoice payments lists the checks that catch them.
• Trusting bank details on the invoice. Pay to the bank account in your verified vendor record, not to whatever the latest invoice says.
• Letting invoices age in inboxes. Approval clocks should start when the invoice arrives, not when someone opens it.
• A matrix nobody updates. People change roles. Review authorities at least yearly.

For suppliers: how to get through a client's approval workflow

If you send invoices to larger companies, their approval workflow decides when you get paid. You can help it along:

• Quote the PO number on the invoice exactly as issued, and bill against one PO per invoice unless told otherwise.
• Match quantities, units and unit prices to the PO line by line.
• Use the client's full legal entity name and billing address, and name the person who ordered the work.
• Give each invoice a unique number; the invoice number generator helps you keep a consistent sequence.
• Send it to the AP address or portal the client specified, and keep proof of submission.

A tidy layout helps too. The corporate invoice template puts the PO number, dates and totals where AP staff expect to find them. Remember that our generator only builds the PDF; you send it and follow up yourself.

For broader money-management topics, browse the business finance articles.