Payables teams are frequently given goals that measure somebody else's decision, and the resulting frustration is entirely predictable. A goal is useful when the team can move it by working differently, and misleading when it moves because finance changed payment terms or purchasing changed its behaviour. Three goals meet that test and one popular target does not.
Goals the team controls
The age of the oldest item in each queue, which is about chasing and routing. The share of invoices processed without an exception, given the ones that arrive matchable, which is about tolerance and handling. And the elapsed time from receipt to approval, which is about routing, cover and escalation. All three respond to how the team works.
A goal to share rather than own
The proportion of invoices arriving with a purchase order and a goods receipt behind them. Payables cannot move this alone, and giving it to them as a target produces reporting rather than change. Shared with purchasing, and reported by department, it becomes the number that actually improves the whole cycle.
The target to avoid
Days payable outstanding as a payables performance measure. It blends deliberate payment policy with process failure: an organisation paying to long terms and one that is late on short terms can score identically. It is a legitimate cash metric for finance and a misleading operational goal for the team processing invoices.
Questions people ask about accounts payable goals
What about cost per invoice?
Useful if measured internally and tracked over time. It varies with the exception mix, so it should be read alongside that rather than alone.
Should we set a touchless target?
Only relative to your own purchase-order coverage, which caps it. A target above the ceiling is unreachable by construction.
How many goals is right?
Three or four. More and nobody remembers them, which means nobody acts on them.