Purchase invoice approvals: stop decisions getting stuck in inboxes

Purchase invoice approval workflows help finance teams establish what is owed, who can authorise it and what is preventing payment. A dependable workflow makes those decisions visible before an invoice becomes overdue. It also gives staff a workable route when the usual approver is away or a delivery does not match the bill.

The starting problem is often familiar: invoices arrive in different inboxes, managers approve them in messages, and finance reconstructs the history later. Adding a reminder bot can reduce some chasing, but it cannot decide whether the goods were received or whether the approver had the right authority.

This guide focuses on the operating process around purchase invoices. The examples and proposed thresholds are illustrative; your finance lead should set the actual authorisation rules, accounting treatment and payment controls for your organisation and jurisdiction.

Follow an invoice from arrival to release

Choose several recent invoices and trace each one without relying on people's memories. Find the original document, the supplier record, the delivery or service evidence, the approval decision and the eventual payment record. Include an invoice that caused difficulty as well as straightforward purchases.

Record where time passed without action. An invoice can spend ten minutes being checked and several days waiting in a manager's mailbox. Those are different problems. Faster document capture will not solve an authorisation delay caused by an unclear budget owner or a missing service acceptance decision.

Check how the team identifies the same invoice when it arrives twice. A supplier might send a PDF, a statement and a reminder containing the original attachment. A matching method needs to consider supplier identity and invoice details rather than treating every incoming email as a new liability.

Agree the start and end of the process. Approval to record an invoice, approval of the expenditure and release of a payment may be separate decisions. Keep those distinctions visible, especially where different people hold those responsibilities. A single ambiguous “approved” label invites misunderstanding during a busy payment run.

Create an intake record that supports a decision

Use a monitored intake route with coverage when the usual finance colleague is absent. Ask suppliers to use the agreed address where practical, while allowing staff to forward invoices received elsewhere without losing the original arrival date. The route should make documents easier to find, not create another unattended mailbox.

The working record should capture a stable supplier identifier, invoice number, issue date, stated due date, currency, total and the related purchase or service reference. Include the original document and any later correction. Preserve the supplier's values separately from internal classifications so reviewers can see what changed.

Automated extraction can suggest fields, but missing or conflicting information needs review. A PDF with two totals, an unreadable currency symbol or a credit note should not pass simply because the software produced a value. Require the reviewer to compare important fields with the source when the checks indicate uncertainty.

For UK organisations, GOV.UK describes the information an invoice must include. Build a locally appropriate completeness check with your finance adviser. A missing field should lead to a clear query and owner; it should not disappear into a generic rejected-documents folder.

Match the request, delivery and invoice

Where purchase orders are used, connect the invoice to the authorised order and the evidence that goods or services were received. These records answer different questions. An order establishes what was requested; a delivery record supports what arrived; an invoice states what the supplier is asking to be paid.

For a service, the evidence may be a signed timesheet, a completed milestone or an acceptance record. Decide who can confirm that evidence. Finance staff should not have to infer completion from a supplier's description if the operational manager is the person who knows whether the work was delivered.

Some legitimate purchases will not have a purchase order. Define a controlled route for them rather than forcing staff to invent a reference. Capture why the route applies, who confirms the purchase and whether a separate policy issue needs attention. Frequent exceptions may indicate a purchasing process that needs redesign.

Avoid universal matching tolerances. A small rounding difference and a change in contracted unit price carry different implications. Your organisation should decide which discrepancies can be accepted, by whom and with what record. A useful automation presents the difference and the evidence instead of hiding the judgement behind a green tick.

Write the approval rules in everyday language

Set out approval requirements by the factors that actually change responsibility: entity, department, amount, purchase type and any special risk. Keep the rules accessible to the people applying them. A matrix understood only by the system administrator is difficult to maintain when the organisation changes.

• Identify who owns the relevant budget and who can cover their absence.
• State which purchases need a second decision or specialist review.
• Separate confirmation of delivery from permission to spend where appropriate.
• Explain how an approver records a refusal, a question or a request for correction.
• Set a review route for purchases outside the ordinary rules.

These are design questions, not recommended monetary thresholds. An illustrative £2,000 approval boundary might be appropriate for one organisation and entirely unsuitable for another. Decide thresholds against your actual governance, contract commitments and financial controls, then document the approved version and effective date.

Do not let a change in a person's role silently leave old permissions active. Connect the approval directory to a maintained staff and delegation record. Periodic checks should confirm that current roles match the rules, particularly after restructuring, staff departures or the opening of a new branch.

Handle absence without losing accountability

An approval system should know what happens when a manager is on leave. Delegation needs a start date, end date, scope and an accountable replacement. Simply forwarding everything to a personal email address may expose information and does not establish whether the recipient has authority to decide.

Show the delegate why the invoice reached them and what they are being asked to confirm. They need the same delivery and order evidence as the original approver. If they cannot make the decision, the system should provide an escalation route rather than encouraging an approval made only to clear the queue.

Set reminders according to working arrangements and invoice urgency. Repeated messages every few hours can teach staff to ignore the system. A consolidated list of outstanding decisions with clear due dates may be more useful. Escalation should go to a person able to resolve the blockage.

Keep a record of the person who made the actual decision, even when acting as a delegate. Reporting everything under the original manager's name makes later review unreliable. Accountability is easier to preserve when the record explains who acted, under which authority and using which version of the invoice.

Work through a partial-delivery example

Consider a hypothetical distributor ordering ten identical components. Eight arrive, two are delayed, and the supplier invoices for all ten. The document can be captured correctly while still being unsuitable for straightforward approval. The operational evidence, rather than the extraction accuracy, determines the next step.

The reviewer records the quantity difference and sends a focused query to the purchasing owner. Depending on the agreed supplier terms and company policy, the next action could involve a corrected invoice, a credit or another authorised arrangement. The workflow should capture the decision without assuming the answer in advance.

If payment is held, the reason and responsible person should be visible. A later reminder from the supplier can then be linked to the existing case instead of starting a new approval chain. The finance team can explain the position without asking the warehouse to repeat the investigation.

Now change the example: all ten arrived, but the warehouse record was never completed. That is an internal evidence gap, not necessarily a supplier error. Route it to the right owner and measure it separately. Combining both situations under “invoice problem” prevents the business from addressing their different causes.

Keep changes to bank details outside routine approval

A request to change supplier payment details deserves its own verified process. Do not allow an invoice attachment or an email reply to overwrite the trusted supplier master automatically. The team needs an independent way to check the request under its established fraud controls.

Record who requested the change, who verified it and who authorised the update. Keep duties appropriately separated for the organisation's size and risk. Small teams may need a practical alternative control, but an automation should not remove a deliberate check simply because one person usually performs several roles.

The Charity Commission's internal financial controls guidance is relevant to charities in England and Wales. Other organisations and jurisdictions need their own applicable controls. The transferable operating principle is to make verification and authority explicit before changing where money will be sent.

Payment release should use current approved supplier details and the authorised amount. If the details change after invoice approval, determine whether another review is required. Keep the invoice decision and payment decision linked while recognising that a previously approved bill does not validate a newly supplied bank account.

Build a useful exception queue

Give exceptions specific reasons: unknown supplier, duplicate candidate, missing receipt, price discrepancy, absent approver or disputed service. Each reason should have a responsible role and an expected next action. A queue with hundreds of items marked “needs attention” does not help anyone decide where to start.

Display age and value alongside the reason, but avoid treating the largest amount as automatically most urgent. An essential supplier, a disputed deadline or an operational dependency may change priority. Finance needs enough context to exercise judgement, rather than a sorting rule that silently becomes company policy.

Let reviewers record decisions in the same place as the evidence. An approval stored in chat while the document lives elsewhere forces the next colleague to search several systems. A link to the source can be sufficient if access and retention are reliable; unnecessary copying is not the objective.

Our invoice approval automation page outlines the delivery scope for this kind of improvement. A practical assessment can establish which exceptions ordinary rules can handle, where integrations are missing and which decisions should remain with finance or operations staff.

Test the process before the next payment run

Prepare an agreed set of test invoices using synthetic or appropriately controlled data. Include an ordinary approved purchase, a duplicate, a credit note, a foreign-currency invoice and a document with missing information. Add cases specific to your business, such as several deliveries against one order.

Check permissions with each role. A requester should not gain access to unrelated department invoices just because they can upload a document. An approver should see the information required for their decision, and finance should retain a complete authorised history. Test what happens when a member of staff leaves.

Simulate a connection failure after a decision has been recorded but before the accounting system confirms receipt. A retry must not create a second bill. The team needs a way to identify whether the first attempt succeeded before repeating the action, with a clear reconciliation step where necessary.

Run the old and proposed processes in a controlled comparison before relying on the new route. Agree who resolves differences and what stops the trial. The pilot rollout guide provides a broader framework for release decisions, fallback and operational ownership.

Give suppliers a clear answer to a query

Agree how finance acknowledges an invoice query and when it provides another update. The message should identify the invoice, explain what is being checked and name the appropriate reply route. Avoid making payment promises before the authorised decision is available. A specific explanation is usually more useful than repeatedly saying the invoice is being processed.

Keep that correspondence attached to the working record. If a colleague covers the supplier account, they should be able to see the last commitment and continue from it. Where a corrected document arrives, link it to the original so the team can distinguish replacement information from an additional amount to pay.

Before changing that correspondence, ask finance to check the current reply address and approval wording. A saved template should remain connected to the live process when staff roles or supplier arrangements change.

Measure waiting and rework as well as speed

Compare time awaiting approval, time investigating exceptions and the proportion requiring avoidable re-entry. Separate supplier-caused issues from internal gaps. That distinction helps decide whether the next improvement belongs in purchasing, goods receipt, staff cover or the connection to your accounting software.

Report invoices due before the next payment cycle with unresolved decisions and named owners. This is more actionable than a monthly total of invoices processed. A manager should be able to look at the report and know which question to answer, rather than commissioning another spreadsheet to explain it.

Estimate benefits using observed work. If automation saves capture time but creates a large review burden, include both. Reduced chasing may release useful capacity without immediately reducing cash expenditure. Agree what success means for finance, operational teams and suppliers before using a saving estimate to justify the project.

Begin with a purchase category whose evidence and ownership are understood. Once the route works through ordinary cases and realistic exceptions, extend it deliberately. A dependable invoice workflow should make authorisation easier to follow and payment decisions easier to explain, even when the person who normally manages the process is away.

Checked sources

• GOV.UK: information an invoice must include
• Charity Commission: internal financial controls (England and Wales)