Why invoice approvals stall before review

An invoice approval workflow usually does not fail at the approval button. It stalls earlier, when the invoice arrives without the evidence, authority or routing context that lets a reviewer make a clean decision. The visible symptom is a queue. The operating problem is an incomplete hand-off.

A stronger workflow treats approval as a controlled decision. The invoice, source details, reviewer, reason, timestamp and next action remain attached from preparation through sending. That design reduces ambiguity without pretending that software can resolve a missing commercial agreement.

Start with what the reviewer must decide

An approval request should answer one question: is this invoice ready to leave the business in its current form? The reviewer needs enough context to confirm the customer, amount, currency, billing trigger, supporting work and payment terms.

Completeness and approval are different controls. A document can contain every expected field and still be commercially wrong because it uses unapproved time, bills a milestone before acceptance or applies the wrong entity.

Keep the billing trigger explicit

Project progress, time entry and delivery status describe real work, but none automatically proves that the work is billable now. Name the event that authorises the charge, such as an accepted milestone, approved time period, recurring schedule or recorded usage window.

When the contract is in one system, approved time in another and the exception discussion in email, the reviewer must reconstruct the case. Connect the source reference and the reason for the amount before review begins.

Route by rule and close the return loop

A dependable path is based on role, entity, amount or exception type. Routing every invoice to the person who handled the previous case creates hidden dependencies when responsibilities change.

Returned is not a final state. The record should show what must change, who owns the correction and whether the invoice returns to the same reviewer. Otherwise the invoice leaves the queue without moving closer to sending.

Measure time by state

A single average approval time hides the source of delay. Record when the invoice became ready, how long it waited unassigned, how long it sat with a reviewer, how often it was returned and how long correction took.

Do not invent a benchmark before the population and method exist. Begin with your own invoices, define each state and review the distribution alongside volume and exception type.

Diagnose the queue before changing the workflow

Start by separating invoices that are waiting for a decision from invoices that are not yet ready for review. A ready invoice has a named customer, issuing entity, billing period, currency, line-level source and commercial trigger. If any of those facts are missing, the preparer still owns the record. Sending an incomplete record to an approver turns preparation work into review delay and makes approval-time reporting unreliable.

Next, classify the reason each review pauses. Useful categories include missing evidence, unclear authority, incorrect routing, pricing exception, entity mismatch, tax review, disputed source and correction awaiting resubmission. The category must describe the blocked decision, not the person involved. After a few cycles, finance can see whether delay comes from upstream preparation, assignment rules, reviewer capacity or repeated exceptions without inventing a generic industry benchmark.

Design the minimum review packet

The reviewer should receive one decision packet rather than a collection of links that must be reconstructed. At minimum, show the invoice version, customer and entity, amount and currency, billing trigger for each material line, the supporting record, any exception and the authority required to approve it. Keep source documents available, but put the decisive facts in the review view so the approver knows what the evidence is expected to prove.

Avoid adding every available field. More information can make the real exception harder to see. Mark what changed since the prior review, identify the lines affected and keep unchanged lines stable. If an expense lacks authority, the reviewer should be able to return that issue without losing approved milestone and time evidence. The packet is complete when another authorised reviewer can reproduce the decision from the retained record.

Build return, escalation and audit paths

A returned invoice needs a reason, correction owner and due action. Free-text comments can add context, but the state should also identify whether the preparer must attach evidence, change a value, select another entity or obtain separate authority. When the correction is complete, create a new inspectable version and return it through the affected review step. Do not silently edit an approved total or treat a chat response as the new approval record.

Escalation should address genuine inactivity or authority gaps rather than bypass a necessary control. Define who can reassign a review, when a higher authority is required and which exceptions cannot proceed until the commercial owner responds. Measure ready-to-assigned, assigned-to-decision and return-to-resubmission time separately. This creates an operating improvement loop while preserving the evidence, authority and history that make approval defensible.

Decision summary

• Keep the commercial trigger and source evidence visible for every material charge.

• Separate preparation, review, correction, sending and accounting responsibilities.

• Retain versions, reasons, owners and timestamps whenever a decision changes.

• Test the control with one difficult invoice another authorised person can reproduce.

Put the control into practice

Map one difficult invoice before redesigning the whole queue. Follow its source details, reviewers, corrections and sending decision. The places where context leaves the record are the first controls to repair.

Run the review on a real case

A services invoice contains an accepted milestone, approved time and a one-off expense. The amount is correct, but the reviewer cannot see who authorised the expense. Keep the invoice in review, attach the authority and return it through the same decision path rather than approving the total because most lines are supported.

The control succeeds when another reviewer can reproduce the decision without searching email or asking the preparer. Retain the ready time, assigned reviewer, decision, reason, correction owner and final approval time as separate facts.

Case-review checklist

• Billing trigger identified for every line

• Reviewer authority matches entity and value

• Return reason names the required correction

• Changed invoice returns to controlled review

• Approval time is measured by state

Do not optimise the queue by removing a decision that protects a genuine commercial boundary. Reduce waiting by improving evidence and routing; retain approval wherever authority, customer impact or exception risk requires it.