Managing supplier invoices one at a time is processing. Managing them against the supplier is where the harder questions get answered: what do we owe this vendor in total, what is in dispute, what have they billed that we never received, and does their statement agree with ours. That view is what turns payables from a queue into a relationship record.
Everything against the supplier
Every invoice, its status, its exceptions, its payments, and every credit note. Held together, this answers what is outstanding for that vendor without assembling it from three places. It is also what makes statement reconciliation practical rather than a project, and statement reconciliation is the most reliable way to find invoices you never received.
One supplier, one record
Duplicate supplier records split payment history, break duplicate detection and produce statements that will never reconcile. They are easy to create, usually when an invoice arrives under a trading name rather than the legal entity, and hard to merge later. Supplier creation deserves a control of its own for exactly this reason.
Bank details as part of the record
Payment details with a history of changes, who made each and how it was verified. This is the highest-value fraud target in payables and the record is the defence: a change with no verification recorded is a question worth asking before the next payment run rather than after it.
Questions people ask about vendor invoice management
How often should we reconcile supplier statements?
Monthly for high-volume suppliers, periodically for the rest. A rule based on spend concentrates effort where the value is.
How do we avoid duplicate supplier records?
Match on tax reference and bank details rather than name, and route unrecognised suppliers to a person rather than creating records automatically.
Who should be able to change bank details?
A small named group, with verification recorded and with that group separate from whoever releases payments.