Invoice processing workflows all look alike on paper because the spine is the same everywhere: arrive, capture, match, approve, pay. What differs, and what determines whether a team is comfortable or drowning, is the design of the branches. A workflow with four well-owned branches feels manageable; the same spine with an undifferentiated exception queue feels like a pile.
Give each branch a reason
No purchase order, price variance, quantity variance, no goods receipt, unrecognised supplier, suspected duplicate, disputed. The reason is what determines who can resolve it, and recording it converts a queue of stuck invoices into a set of specific short tasks. It also lets you count reasons monthly and see which upstream problem is generating the most work.
Give each branch an owner
Price to purchasing, quantity and receipts to whoever takes deliveries, supplier problems to whoever maintains supplier records, disputes to a named person with the supplier contact. Ownership outside payables is what makes exceptions clear quickly, because the person who can resolve it is the person who has the information.
Give each branch an age and a target
Elapsed time in the branch, with a target that somebody looks at weekly. Without ageing, an exception queue has no shape and nothing distinguishes an item stuck for a day from one stuck for a quarter. With it, the weekly management task is short: look at the oldest three in each branch and make three phone calls.
Questions people ask about invoice processing workflow
How many branches should there be?
Enough that each has a distinct owner and a distinct action. Six or seven covers nearly every situation, and more than that usually means two reasons that nobody actually distinguishes.
Can invoices move between branches?
Yes, and the workflow must permit it. An invoice that turns out to be a duplicate after being matched has to be able to move, and forbidding it pushes the handling into email.
What should be reported upward?
Counts by branch and the oldest age in each. Two small tables that fit on a page and tell a manager everything they need.