Best practice in accounts payable invoice processing is four habits, and none of them requires software to begin. Everything arrives at one monitored address with its date recorded. Everything carries a status, an owner and an age. Cheap validation runs before anything expensive. And every exception carries the reason it failed and goes to whoever can resolve it.
One arrival point, with the date
Every invoice enters through a channel somebody monitors, and the date it reached the organisation is recorded because payment terms run from it. Invoices sent to individuals are invisible until forwarded, and consolidating channels is a quarter of polite persistence that permanently closes the largest leak most organisations have.
Validation before matching
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 that cost nothing, run in milliseconds and catch a large share of both errors and fraud before any expensive step is reached.
Exceptions with reasons and owners
Price variance to purchasing, quantity variance or missing receipt to whoever takes deliveries, supplier problems to whoever maintains records, disputes to a named person. Each exception carrying its reason and the two numbers that disagree turns a research task into a short specific conversation.
Close everything explicitly
Paid, credited, cancelled or written off with a reason recorded. Invoices that simply stop being discussed accumulate in the open list, and once the list is untrusted people go back to asking each other, which is exactly the state the process was built to replace.
Questions people ask about accounts payable invoice processing best practices
Which habit returns most?
Consolidating arrival channels, because it costs nothing and stops invoices being invisible until a supplier telephones about one.
How many statuses should there be?
Five or six from a fixed list. Free text drifts within days into variants that cannot be counted, and a queue that cannot be counted cannot be managed.
Do we need software for any of this?
Not to start. Statuses, owners and ages work on a spreadsheet at modest volume. Software matters when several people edit the record or the history must be trusted a year later.