When You Have Hundreds of Vendors:
Vendor Management Is a Systems Problem

I know an AP lead at a service company who used to know her vendors. Their kids' names. Their billing quirks. Which ones email instead of mail, which ones bill the wrong way every quarter. For years that was the job. Then the company grew. The vendor count went from forty to four hundred. And one day she said something that stuck with me: "I don't manage vendors anymore. I manage the spreadsheet."

That's the moment vendor management stops being a relationship problem and starts being a systems problem. Most companies don't notice the line until they're well past it.

What "Vendor Management" Actually Looks Like

When a company says "we manage our vendors," they usually mean a few things stitched together that nobody owns end-to-end:

• The vendor file in the accounting system — names, addresses, tax IDs, payment methods.
• The contact list someone keeps in Outlook or a CRM — the people you actually email and call.
• The contracts folder — sometimes SharePoint, sometimes a filing cabinet, sometimes both.
• The performance scorecard — usually nonexistent, sometimes a quarterly review meeting that gets postponed.
• The W-9 collection process — a recurring fire drill at year-end.

Each lives in a different system, maintained by a different person, updated on a different schedule. The vendor isn't fragmented — your record of them is.

Why It Quietly Breaks Things

The damage from a fragmented vendor system rarely shows up as a single dramatic failure. It shows up as a steady tax on everything around it.

You pay a duplicate vendor twice because the same company got entered three different ways: ACME LLC, Acme Inc, Acme L.L.C. You miss a 1099 because the W-9 is in someone's email, not in the system. You sign a renewal at the old rate because nobody flagged that the contract was up. You spend a Friday afternoon trying to figure out why a vendor stopped getting paid — and the answer is that their bank info changed three months ago and the email went to a coworker who was on vacation.

None of those are dramatic. All of them happen.

The Thing That Has to Change

Past a certain size — somewhere around two or three hundred active vendors, in my experience — vendor management has to stop being a relationship managed by a person and start being a system managed by software, with the person doing the judgment work the system can't.

That sounds obvious until you try to do it. Most accounting platforms treat the vendor record as a payment destination, not a relationship. They'll happily store a name and a routing number and stay quiet about everything else.

What an actual vendor system needs to track:

• A single canonical record per vendor — same vendor, same record, regardless of how the AP clerk types the name on a given day.
• Payment method, schedule, and changes to either, with a date stamp on every change.
• Contract status — current term, expiration, renewal trigger, who owns the relationship.
• W-9 status — collected, valid, when it expires.
• Performance signals — late deliveries, billing errors, rejected invoices. The data is already there in your operational system. Most companies just never connect it to the vendor record.

When those things live in one place, vendor management becomes something a controller can actually do. Without them, vendor management is the AP clerk's heroics.

What I See When I Walk Into This

The fix is rarely a software purchase. The systems you already have can usually do most of this — your accounting platform, your operational system, the contracts folder. The work is connecting them, deduplicating the records, and building the small set of automations that keep the connection from rotting over time. A weekly job that flags vendors with no current W-9. A nightly sync that prevents duplicate vendor entries. A simple report that shows which vendors haven't been paid in 90 days but are still marked active.

None of that is glamorous. It's not a SaaS pitch. It's just plumbing. But it's the difference between AP being a job two people can do and AP being a job that depends on the one person who knows everybody.

If you're past three hundred vendors and you're not sure what would happen if your AP lead took a two-week vacation, that's the question worth answering — not "should we buy a vendor management tool."

← Back to all posts