The accounts payable workflow process is usually drawn as a flowchart and experienced as a series of questions: where is that invoice, who has it, why has it not been approved, and is it going to land in this month or next. Those are questions about STATE, not about steps, and it is a useful distinction because most teams try to fix a state problem by redrawing the steps. A workflow that makes state visible answers all four questions without anyone asking, and it does so before any automation is involved. This page is about getting the visibility first, what it changes, and why automating a route nobody has written down tends to make the confusion arrive faster.
State, not steps: the four questions a workflow should answer
Where is this invoice, who is holding it, what is blocking it, and which period will it land in. A team that can answer those from a screen rather than from memory has already recovered most of the time a workflow tool promises, and has done it without changing how anybody works.
Why visibility comes before automation
Automation encodes a route. If the route is partly undocumented and partly folklore, what gets encoded is the folklore, executed faster and with less opportunity to notice. Write the route down, run it visibly for a month, and the parts worth automating become obvious rather than assumed.
What the visible version costs to run
Nothing structural: the same people doing the same work, recorded. On the worked example on this site, 400 invoices touched three times at six minutes, with 12% going wrong and taking eighteen minutes more, is 134.4 hours a month: $4,300.80 at a $32 loaded rate, $10.75 an invoice. Knowing that figure is what turns a workflow discussion from a preference into a decision.
Questions people ask about accounts payable workflow process
Do we need workflow software to get visibility?
Not to start. A shared list with a state against each invoice gets most of the benefit, and it also tells you whether the states you chose are the right ones before you pay somebody to encode them.
How many states should an invoice have?
Few enough that two people classify the same invoice the same way. Received, coded, matched, awaiting approval, approved, posted is usually enough. A fixed set is what makes one month comparable with another.
What about invoices that skip steps?
They are the ones worth watching, because a skipped step is either a step you do not need or a control that is not operating. Either answer is useful; not knowing is not.