Vendor Consolidation: Why Construction Companies Have 3,000 Vendors They Shouldn't, and How to Fix It
Ask a construction CFO how many vendors their company has, and they'll usually say "a few hundred." Check the vendor master file, and the count is 3,000+. The gap between the perception and the reality is where operational problems compound: duplicate vendors receiving separate payments, spend analysis distorted by splits across versions of the same vendor, AI matching systems confused by similar records, and 1099 reporting that accidentally produces multiple forms for the same payee.
The accumulation happens because adding a vendor is easy and removing one is hard. Every new invoice from a one-time vendor creates a new record. Every typo in a vendor name creates a duplicate. Every corporate reorganization creates new entity versions. Over a decade of operations, thousands of vendors pile up, most never used again, many duplicates, many with bad data. Periodic consolidation is the fix — and it produces real operational improvements.
Understanding how duplicates accumulate helps prevent them going forward:
Common duplicate sources
- Typos — "ACME Concrete Inc" and "ACME Concret Inc" created as separate vendors
- Spacing and punctuation — "ACME Concrete, Inc." vs "ACME Concrete Inc" vs "ACME Concrete INC"
- Multiple locations — parent company and various branches all as separate vendors
- DBA/legal name confusion — legal entity and trade name as separate vendors
- Entity type changes — vendor changed from LLC to Inc, both versions persist
- Invoice source variations — vendor sometimes submits as "ACME" sometimes as "ACME Construction"
- Different remit-to addresses — assumed to be different vendors when actually same entity
- Onboarding by different people — each creates their own record without checking existing
Each cause is preventable but hard to prevent through training alone. Automated duplicate detection at vendor creation time is a far more reliable prevention than procedure documents.
The first step in consolidation is finding the duplicates that exist. Detection techniques:
Duplicate detection techniques
- Exact name match (after normalization — trim whitespace, standardize case, remove punctuation)
- Fuzzy name match — edit distance algorithms that detect typos and variations
- Tax ID match — same EIN means same legal entity
- Bank account match — same routing/account means same payee
- Address match — same address is strong signal; flag for review
- Phone/email match — same contact data often means same vendor
- Payment pattern match — similar payment amounts and frequencies to similar addresses
Combining techniques reduces false positives. Two vendors with similar names and the same EIN are almost certainly the same. Two vendors with similar names but different EINs and addresses might be legitimately separate entities (franchisees, unrelated companies with similar names).
Merging two vendor records into one requires specific data handling:
Vendor merge procedure
- Identify the "master" vendor record to keep — usually the one with most history or best data
- Identify "duplicate" records to merge
- Move all historical transactions from duplicates to master — invoices, payments, POs
- Move all historical compliance data — COIs, W-9s, vendor questionnaires
- Update any active records referencing the duplicate vendor to reference the master
- Deactivate (not delete) the duplicate records with note explaining the merge
- Preserve an audit trail showing what was merged, when, and by whom
Never actually delete vendor records — soft-delete / deactivate only. Historical accounting records may reference the vendor ID, and deletion breaks those references. Deactivation preserves the history while preventing new use.
Different merge approaches for different duplicate situations:
Duplicate merge approach by situation
- Both active duplicates — merge with care; both may have recent transactions and open items
- One active, one inactive — merge inactive into active; easier case
- Both inactive — consolidate histories; won't be used again but preserves clean data
- Open AP on duplicate — resolve the open items first, then merge
- Open PO on duplicate — reassign PO to master record before merge
- Payment in flight to duplicate — wait until payment clears before merge
Mid-flight transactions are the gotcha. A merge during an open payment cycle can stall payments or create duplicates. Scheduling merges during low-activity windows reduces risk.
A large portion of most vendor masters are one-time vendors — companies paid once and never again. These shouldn't be in the active master at all:
One-time vendor handling
- Identify vendors with only one or two historical transactions and no activity in 2+ years
- Review the transactions to confirm one-time nature
- Deactivate the vendor record — preserves history but prevents casual reuse
- Use a "one-time vendor" pattern for legitimate one-off purchases — dedicated code that doesn't create a full record
- Establish a threshold below which one-time payments don't warrant a vendor record (e.g., $500)
The one-time vendor pattern matters because it prevents the master from growing uncontrollably. A company that creates a new vendor for every one-off purchase has no chance of maintaining a clean master; a company that uses a dedicated pattern for one-time purchases keeps the master focused on recurring relationships.
The 80/20 rule applies heavily to vendor masters. Typically 80% of spending runs through 20% of vendors — often even more concentrated. Identifying and curating that top 20% delivers most of the value; the long tail can be managed with lighter touch.
Get AP insights in your inbox
A short monthly roundup of construction AP + accounting posts. No spam, ever.
No spam. Unsubscribe anytime.
Consolidation is an opportunity to enrich the vendor records kept:
Vendor data enrichment during consolidation
- EIN verified against IRS records
- Address verified against USPS or equivalent
- Bank account information verified through ACH validation
- W-9 on file and current
- COI current (for subs) with all required endorsements
- Vendor classification accurate — materials supplier, specialty sub, services, etc.
- Default cost coding accurate for the vendor's typical work
- 1099 classification correct based on current tax status
Consolidated, enriched vendor data enables better automation. AI classification works better on clean data. Three-way matching is more reliable. 1099 reporting is less error-prone. The downstream benefits compound.
A successful consolidation can backslide quickly without governance. Ongoing practices:
Ongoing vendor master governance
- Duplicate detection at vendor creation time — fuzzy match against existing records before creating new
- Vendor creation approval workflow — someone reviews new vendor requests
- Minimum information required for vendor creation — no partial records
- Periodic master review — monthly or quarterly scan for emerging duplicates
- Annual consolidation cycle — built-in cleanup as part of year-end
- Clear ownership — someone responsible for master quality as a specific duty
Ownership matters. Masters degrade when nobody is responsible for their quality. A designated vendor master owner — whether a dedicated role or a responsibility within AP — keeps the master clean through routine practice rather than periodic crisis cleanups.
Clean vendor masters enable real spend analysis:
Spend analysis enabled by consolidation
- Total spend by vendor accurately reflects reality — no splits across duplicates
- Vendor concentration analysis — who are the top N vendors and what's the concentration risk
- Category spend analysis — consolidated view of concrete spending, electrical work, etc.
- Negotiation leverage — accurate spend data supports rebate negotiations
- Contract consolidation opportunities — same vendor with multiple uncoordinated POs can be consolidated
- Price variance detection — same vendor charging different rates to different project teams surfaces
Most companies underestimate their spend with their top vendors because the spend is split across duplicate records. Consolidating reveals the true concentration and opens negotiation opportunities that weren't visible before.
Clean vendor masters also reduce fraud risk:
Fraud risk factors reduced by consolidation
- Duplicate payment risk — invoice paid against two vendor records for same vendor
- Ghost vendor risk — fake vendor lost in large master becomes easier to spot in clean master
- Vendor impersonation — duplicate records with different remit addresses can enable fraud
- Bank change fraud — clear single record with bank history makes fraudulent change requests easier to detect
- Audit gaps — auditors examining clean master more likely to catch anomalies
Fraud thrives in complexity. Clean vendor data makes fraudulent patterns more visible and reduces opportunities for exploitation.
Vendor master consolidation is unglamorous but high-value AP work. The typical construction company has thousands of vendor records where hundreds would serve, with duplicates, outdated data, and one-time vendors cluttering the master. Systematic consolidation — identifying duplicates, merging carefully, deactivating one-time vendors, enriching the records kept — produces a clean master that enables better spend analysis, more reliable automation, reduced duplicate payment risk, lower fraud exposure, and easier 1099 processing. Going-forward governance prevents backsliding. The consolidation project itself is typically a 3-6 month effort for mid-sized companies, with ongoing maintenance taking a fraction of that. The return on the investment shows up across many downstream processes — which is exactly why master data quality is worth the attention it rarely gets.
Written by
Sarah Blake
Head of Product
Former AP Manager at a $200M construction firm, now leads product at Covinly. Writes about what AP teams actually need from automation — beyond the marketing promises.
View all posts