Best practice lists in payables are usually written at a level of abstraction nobody can act on. Written as instructions, the list is short and most of it costs nothing. Four practices cover the processing side, each preventing a specific and recognisable failure, and none of them requires software before it can be started this week.
One arrival address, with the date recorded
Every invoice enters through a channel somebody monitors, and the date it reached the organisation is recorded because terms run from it. Invoices sent to individuals are invisible until forwarded, and that gap is usually the largest hidden delay in a payables process because nobody is measuring the part before payables sees anything.
Validate before you match
Supplier exists, invoice number is new for them, lines sum to the net, net plus tax equals the total, date is plausible, bank details agree with what you hold. Six checks costing milliseconds that catch a large share of duplicates and the commonest fraud shape before any expensive step is reached.
Route exceptions by their reason
Price variance to purchasing, quantity variance or missing receipt to whoever takes deliveries, unrecognised supplier to whoever maintains records. Each exception carrying its reason and the two numbers that disagree turns a research task into a short conversation with the person who already knows the answer.
Close every invoice explicitly
Paid, credited, cancelled or written off with a reason. Invoices that stop being discussed accumulate in the open list, and an untrusted list sends everybody back to asking each other, which is the state the process existed to replace. Explicit closure is what keeps the queue credible.
Questions people ask about accounts payable processing best practices
Which practice returns most?
Consolidating arrival channels. It costs a quarter of polite persistence with suppliers and colleagues and it permanently closes the biggest leak most organisations have.
How many statuses should we use?
Five or six from a fixed list. Free text drifts into variants that cannot be counted, and a queue that cannot be counted cannot be managed.
Do we need software first?
No. All four work on a shared mailbox, a spreadsheet and a written procedure, and doing them first makes any later purchase considerably more effective.