To keep supplier records clean, hold one record per supplier, name the roles allowed to add or change a record, require every change to arrive as a request that leaves evidence, merge duplicates to a single record of use without discarding anything, and review the list on a stated cadence. The discipline is entirely about the record, not about the relationship.
This article is general information about process and recordkeeping. It is not accounting, tax, legal or investment advice. How any transaction is recorded, classified or reported is a judgment for a qualified accountant who knows the business. Any cadence or limit mentioned here is for the organization to set with its qualified advisors and write into its own documents.
One record per supplier, and what that means in practice
One record per supplier sounds obvious until you look at a list that has been running for a while. The same supplier appears under a trade name, a legal name, an abbreviation, and a misspelling, and each version has collected its own history.
The rule is that each supplier the organization deals with has exactly one record, and that record is the only place its details are held. Everything else points at it. Where a supplier genuinely operates as separate entities the organization contracts with separately, those are separate suppliers, and the record should say plainly why they are distinct.
Decide what the record holds and keep the list short. The supplier's name as it appears on its own paperwork, the names it is also known by, a contact point, the details needed to pay it, the reference the organization uses internally, and a note of the arrangement in force. Resist adding fields nobody maintains, because an unmaintained field makes the whole record look unreliable.
The return on this work is clarity and retrieval. When someone needs to know who a supplier is, what was agreed, and where to find the paperwork, a clean record answers it in one place.
How to keep supplier records clean step by step
- Pull the full list. Every supplier record, including the ones nobody has used for a long time. Work from the complete list rather than the active portion, because the duplicates hide in the inactive part.
- Sort by name and read it. Most duplicates are visible to a human reading a sorted list, which is faster than any clever matching.
- Group the obvious duplicates. Same supplier under different spellings, abbreviations, or a trade name alongside a legal name. Group them without changing anything yet.
- Pick the record of use for each group. Usually the one with the most complete and most recently confirmed details. Write down why you picked it.
- Merge to the record of use. Carry the history across, point the superseded records at the one you kept, and mark them as superseded rather than removing them. Nothing gets discarded.
- Fill the gaps on the records you kept. Missing contact points and unconfirmed details, taken from the supplier's own paperwork rather than from memory.
- Write down who may add or change a record from now on. Without this step the list drifts back quickly.
- Set the review cadence and record it in the organization's own documents, along with the name of the role that owns the list.
Starting from a list that is already a mess
Do the pass in one sitting rather than in fragments. A half-finished cleanup leaves the list in a worse state than before, because now some records are current and some are not and nothing says which.
If the list is too long for a single sitting, split it by first letter and finish each slice completely before starting the next. Keep a note of where you stopped, so an interruption does not cost you the pass.
Who may add or change a supplier record
Name the roles, not the people, and keep the group small. Someone needs to be able to add a supplier without a bottleneck, and the set of people who may change payment details should be smaller than the set who may add a supplier at all.
Separate the request from the change. The person who asks for a record to be created or amended should not be the person who makes the amendment. Where the organization is too small for that, record a review of changes by someone outside the process, and say in the document that this is the arrangement. Which changes the organization treats this way is its own decision, taken with its qualified advisors.
Write the route down in one place: who requests, who may make the change, what the request has to contain, and where the request is filed. A route that lives only in habit produces changes nobody can trace back to a request.
How a change request is evidenced
A change with no evidence behind it is a change nobody can explain later. The evidence does not need to be elaborate; it needs to exist and be attached to the specific change.
| A complete change request | What leaves a gap | |
|---|---|---|
| Who asked | A named requester | "Came from the supplier" |
| What changed | The field, the old value and the new value | "Details updated" |
| Why | The reason, in the requester's words | Nothing recorded |
| Source | The supplier document or confirmed contact the new detail came from | Recollection of a conversation |
| Who made the change | A named person, dated | A system entry with no attribution |
Keep the request itself, not just a note that one existed. The request is the record; a summary of it is a second-hand account.
Changes to the details used to pay a supplier deserve their own line in the organization's documents, with a defined confirmation route back to the supplier through a contact point the organization already held rather than one supplied with the request. Record the confirmation alongside the change.
Merging duplicates without losing anything
Merging is the part people get wrong, usually by trying to tidy the list rather than preserve it.
Pick the record of use, move the history onto it, and leave the superseded records in place marked as superseded with a pointer to the record you kept. Nothing is removed. A superseded record that still points somewhere is useful; a gap where a record used to be is not, because old paperwork and old correspondence still refer to it.
Write a short merge note for each group: which records were involved, which one you kept, and why. The note takes a moment and answers the question that comes up later when someone finds a reference to a record that no longer appears to be active.
Where the duplicates are not actually duplicates, say so on both records. Suppliers with similar names, or related entities the organization deals with separately, will be grouped again by the next person unless a line on each record explains the distinction.
The review cadence: how to keep supplier records clean over time
Give the list an owner by role and a review cadence the organization sets and records in its own documents. Log the date of each review and what changed, including reviews where nothing changed.
A review is short if the list is maintained. Read the records added since the last pass, check that payment details on records changed since the last pass have a filed request behind them, look for new duplicates, and mark as dormant anything with no activity for a period the organization defines.
A handful of events should prompt a look outside the cadence: a supplier tells you its details have changed, a request arrives to change payment details, a record is added by someone outside the named roles, or a payment goes somewhere unexpected and the record is part of the explanation.
Clean supplier records are not an achievement anyone notices. They are what makes every later question answerable in one place instead of several. For a starting template for the record fields and the change request, the Free Resources page on this site is where to look.