Processing supplier invoices is usually organised around the invoice, which is right for the daily work and insufficient for the questions that arrive later. 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. Those need the record organised around the vendor as well.
The per-invoice view
Arrival, validation, matching, exception, approval, coding, payment. This is the daily processing queue and it is what most systems present well. It answers where an invoice is and what is stuck, which is what a payables team needs hour to hour and what a supplier chasing a specific invoice is asking about.
The per-vendor view
Every invoice for that supplier with its status, every exception with its reason, every payment with its allocation, every credit note, and the bank detail change history. This answers total exposure, makes statement reconciliation practical, and is where the pattern in a difficult relationship becomes visible rather than being felt.
Why one supplier must be one record
Duplicate supplier records split payment history, defeat duplicate detection and guarantee that statements will never reconcile. They are created under time pressure when an invoice arrives under a trading name nobody recognises, and they are painful to merge afterwards, which is why supplier creation deserves a control of its own.
Questions people ask about vendor invoice processing
How often should we reconcile statements?
Monthly for high-volume suppliers and periodically for the rest, with the rule based on spend rather than on trying to do all of them.
What should suppliers be matched on?
Tax reference and bank details rather than name, since names vary between trading and legal forms.
Who maintains supplier records?
A small named group, separate from whoever releases payment runs, with changes reviewed periodically from outside the process.
What does a difficult supplier relationship look like in the data?
A rising exception count, a growing disputed balance, or statements that never reconcile. All three appear in the per-vendor view before anybody articulates the problem, which is the main argument for having it.
How do we prevent duplicate supplier records?
Match arriving invoices on tax reference and bank details rather than on name, and route anything unrecognised to a person instead of creating a record automatically. Automatic creation is the fastest way to accumulate duplicates.