Invoice Approval Workflow Checklist

An invoice approval workflow checklist covers six stages: receive the invoice at a single point, verify it is for goods or services received, match it against the purchase order or delivery note, route it to the right approver within their authority, pay only after documented approval, and record who approved and when. The goal is simple: no payment leaves the bank without a verified, documented approval — and no invoice sits unapproved past its due date. The workflow prevents the two most expensive AP failures: duplicate payments and payments for goods never received.

An invoice approval workflow is the process that stands between an arriving invoice and a leaving payment. In a small business without a defined workflow, that process is ad-hoc: invoices sit in inboxes, get paid by whoever has banking access, and no one can say with confidence who approved what. The result is duplicate payments, invoices paid twice after a reissue, and — most damagingly — payments to fraudsters who exploited the gap between arrival and approval. This checklist defines a workflow short enough to actually run in a small business, where every step prevents a specific, measurable loss.

Receive & log

Route every supplier invoice to a single dedicated inbox or intake point
A single intake point is what makes the workflow possible. Invoices scattered across personal emails, WhatsApp, and a paper tray cannot be tracked, prioritised, or audited. A dedicated inbox means every invoice is seen, logged, and enters the workflow — instead of being discovered weeks later or lost entirely.
Log the invoice on arrival: supplier, date received, amount, due date
Logging an invoice the day it arrives is what turns "we will deal with it" into a trackable workflow. The due date is what drives prioritisation — an invoice due in three days is handled before one due in thirty. Without a log, due dates are missed and early-payment discounts are forfeited silently.

Verify & match

Confirm the invoice is for goods or services actually received
This is the most important check in the workflow. An invoice for something never delivered is the most common source of wrongful payment — and it is almost always caused by approving without confirming receipt. Match the invoice to a delivery note, a signed-off service, or a confirmation from the person who requested the purchase.
Match the invoice against the purchase order: amount, quantity, items
Suppliers occasionally change prices, add line items, or bill for quantities different from what was ordered. A three-way match — purchase order, delivery note, invoice — catches discrepancies before payment, when they are still easy to resolve. After payment, the supplier has no incentive to correct them.
Check for duplicate invoice numbers from the same supplier
A supplier who reissues an invoice after a correction often sends it with the same number. Without a duplicate check at the verification stage, the workflow processes and pays it twice. Recovering an overpayment is far harder than preventing one — and most duplicate payments are never recovered.

Approve & pay

Route the invoice to an approver who has authority for the amount
Approval authority exists to prevent a single person from authorising payments beyond their responsibility. An approval from someone without authority is not an approval — it is a signature that creates a process violation discoverable during an audit. The workflow must route the invoice to the right approver based on the amount.
Record the approval: who, when, and on what basis
An approval without a record did not happen. If a payment is later questioned — by an auditor, a partner, or the tax office — the approval trail is what proves the payment was authorised and verified. A timestamped record turns "we approved that" from a claim into evidence.
Pay only after documented approval, and link the payment to the invoice
Paying before approval is the failure the entire workflow exists to prevent. Linking the payment to the invoice — by reference number or transaction ID — is what closes the loop. Without that link, the same invoice can re-enter the workflow and be paid again, or be questioned again at year-end.

How Nika helps

Nika handles the verification half of this workflow automatically. She watches the intake inbox, enters every invoice, matches it against existing records, and flags duplicates and unusual details before it reaches an approver. From {price} per processed invoice, an approver sees an invoice that is already entered, verified, and flagged — not a raw PDF. The approval decision stays with a human; the verification work that makes the decision informed is Nika's.

Questions

What is a three-way match?

A three-way match compares three documents before payment: the purchase order (what was ordered), the delivery note (what was received), and the invoice (what was billed). When all three agree, the invoice is paid. When they differ — in quantity, price, or items — the discrepancy is resolved before payment. Three-way matching prevents the most common overpayments but is only practical when the verification is automated or the volume is low.

Who should approve invoices in a small business?

In a small business, the owner or a designated manager typically approves invoices above a threshold. The key principle is separation of duties: the person who enters the invoice should not be the person who approves the payment. In a very small team, even a second pair of eyes — a co-founder, a spouse, an external accountant — is better than a single-person chain. Nika handles the entry and verification; the approval stays with a person who can be accountable.

Automate this with Nika