Payables systems produce dozens of reports and most organisations use four. The others get printed at month end and filed. Knowing which four are worth building properly, and what each is actually for, saves a great deal of reporting effort and produces a management routine that fits on one page.
The queue by state, and ageing with status
How many invoices sit at each stage, and how much is overdue broken down by whether it is deliberate or stuck. The first is the operational picture; the second turns an aging report from a number nobody can act on into the specific figure payables can move. Together they are the weekly management routine.
Goods received, not invoiced
Deliveries recorded against orders that have not been billed. This is the accrual in operational form, it is finance's most-wanted report from the payables system, and it exists only if receipts are being recorded at line level. Where it cannot be produced, somebody rebuilds it by hand every month, usually under time pressure.
The exception reason mix
What proportion of exceptions were caused by no order, missing receipt, price variance, quantity variance and everything else, month by month. This is the improvement report: it says which upstream problem is generating the most work, and it is the one report that changes what other departments do rather than just describing payables.
Questions people ask about accounts payable reports
What about supplier spend analysis?
Useful to purchasing for negotiation, less so to payables operationally. Build it if somebody will act on it.
How often should each be looked at?
Queue and ageing weekly, goods received not invoiced at month end, exception mix monthly.
Why do most reports go unused?
Because they describe rather than prompt an action. A report nobody would act on differently is not worth the effort of producing.