Vendor Onboarding: Fixing the W-9 and COI Bottleneck
Onboarding a new vendor is a documented checklist that quietly blocks dispatch and payment. Here is every item on it, where each one stalls, and how to clear the front door in hours instead of days.
The short answer
Streamlining new vendor onboarding means collecting a W-9, a certificate of insurance naming the association as additional insured, current licenses, and payment details before a vendor can be dispatched or paid. The bottleneck is chasing missing documents and verifying the COI, work an AI agent can do automatically while staff approve exceptions.
The dispatch that dies at 'this vendor isn't set up yet'
A resident has water coming through a ceiling. A manager finds a plumber who can be there in an hour. Then accounting says the words that kill the whole thing: "That vendor isn't set up in the system yet." No W-9 on file, no verified COI, no way to cut a check. The plumber will not roll a truck without a PO, and the PO cannot be issued to a vendor who does not exist.
This is the front door of vendor management, and it is not the same problem as tracking renewals on vendors you already use. Renewal tracking keeps active vendors active. Onboarding is the cold start: a brand-new vendor, zero documents, and a clock running on a job that needs doing now.
The uncomfortable part is that none of this work requires judgment. It is a checklist. Someone emails the vendor, waits, re-emails, reads a PDF, notices the certificate holder line is wrong, emails again, waits again. Two days later the plumber is finally 'active' and the ceiling has already dried into a stain.
Key takeaways
- Vendor onboarding is a documented, deadline-driven checklist, which makes it a textbook fit for automation.
- The most common stall is not a missing document, it is an incorrect one: a COI that names the wrong entity as additional insured.
- Dispatch and payment both depend on the vendor being 'active,' so a stalled onboarding blocks two workflows at once.
- Humans should approve exceptions and edge cases; the chasing, reading, and matching is machine work.
What documents does a new vendor actually need?
Quick answer
A new vendor typically needs a completed W-9, a certificate of insurance naming the correct association or owner as additional insured, current trade and business licenses, banking or payment details, and a signed vendor agreement. Missing or incorrect versions of any one of these blocks activation, dispatch, and payment.
Checklist
0/12New vendor onboarding checklist
Twelve items, and every one is a potential stop. The list looks trivial until you multiply it by a new vendor added most weeks across a portfolio of communities, each with its own named-insured entity that the COI has to match exactly.
Where each item stalls today
The delay is almost never the document itself. It is the back-and-forth to get a correct version. Below is where the checklist actually breaks, and who is waiting when it does.
| Item | Typical stall | Who's blocked |
|---|---|---|
| W-9 | Vendor sends an old copy, wrong TIN, or unsigned | Accounting cannot pay |
| COI additional insured | Names the wrong community or omits it entirely | Manager cannot dispatch to that property |
| Certificate holder | Lists the vendor's own address, not your entity | Compliance rejects the file |
| Trade license | Expired, or a number that fails state lookup | Legal and liability exposure |
| Workers' comp | Missing with no exemption on file | Cannot approve for on-site work |
| Payment details | ACH info sent by unsecured email | Fraud risk, payment held |
According to the FBI's Internet Crime Complaint Center (IC3), business email compromise and payment-diversion schemes account for billions in reported losses annually, and vendor payment setup is a favorite entry point. That last row is why 'just email me your bank info' is a bad default. New payment details deserve a verification step, not a copy-paste.
Notice the pattern: five of six stalls are a wrong or unverified document, not a missing one. That is the real insight. You are not waiting on vendors to send things. You are waiting on someone to read what they sent, catch the error, and ask again.
How an agent chases and validates instead of your staff
The chase-and-validate loop is the part machines do well and people hate. An AI operations agent takes a new vendor from 'has nothing' to 'ready for human sign-off' by running the checklist on autopilot and only surfacing what actually needs a decision.
At One Home Agent, this is the job of Victor Vendors, the agent that tracks COIs and licenses. On the intake side, Victor sends the request, reads each document that comes back, checks it against the requirements, and re-requests the specific thing that is wrong, by name, without a person drafting the follow-up.
- 01
Request the package
The agent sends the vendor a single intake link asking for W-9, COI, licenses, and payment details, with clear instructions on the exact entity name that must appear as additional insured.
- 02
Read and validate
As documents come in, the agent parses each one: TIN and legal name on the W-9, coverage limits and named insured on the COI, license number and expiration against the correct state authority.
- 03
Chase the specific gap
If the COI names the wrong community or the license is expired, the agent re-requests only that item with a plain explanation, then follows up on a schedule until it arrives. No human writes the reminder.
- 04
Escalate the judgment calls
Anything ambiguous (an unusual exemption, a limit below policy, a license that fails lookup) goes to a staff member with the reason flagged. The person decides; the agent handles the rest.
- 05
Flip to active
Once every item validates and a human approves, the vendor is marked active and pushed to the dispatch queue, and the payee record is created in accounting.
“The mistake companies make is trying to automate the approval. You don't. You automate the 90% that is reading PDFs and sending reminders, and you keep a human on the exceptions. That is the version that survives an audit.”
Todd Paton, Partner, One Home Agent
The additional-insured trap that fails audits
The gotcha
A certificate of insurance that lists your management company as certificate holder but does not name the specific association as additional insured leaves that community unprotected. The COI can look complete and still be wrong. Verifying the exact named-insured entity per community is the single highest-value check in vendor onboarding.
A certificate holder is simply the party receiving proof of coverage. An additional insured is a party actually extended coverage under the vendor's policy. Those are not the same thing, and the difference only becomes visible when there is a claim and the wrong entity is on the paperwork.
In a multi-community portfolio this is where humans quietly drop the ball. The COI says 'ABC Management, certificate holder,' looks legitimate, and gets filed. Nobody notices that Sea Breeze Condominium Association, the community the vendor will actually work in, appears nowhere. A machine that checks the named-insured line against the specific community for every single job does not get tired at 4:45 on a Friday.
This is also where you should be honest about limits. An agent can confirm the correct entity name is present and flag when it is not. It should not be the final word on whether coverage is adequate for a given exposure. That is a conversation for your risk manager or attorney, and the agent's job is to make sure that conversation happens with a clean, verified file in front of them.
The handoff: from 'active' to a truck on site the same day
The payoff of clean onboarding is speed at the moment it matters. Once a vendor flips to active, the maintenance workflow can use them immediately. In our stack, Mason Maintenance takes the work order and dispatches to the now-active vendor without waiting on a paperwork round trip.
That is the whole point of treating onboarding as the front door rather than an afterthought. The emergency plumber from the opening scenario gets set up, verified, and dispatched in the same afternoon, because the checklist ran itself in the background while a person handled the resident.
Bottom line
Vendor onboarding is not a strategy problem, it is a follow-up problem. The documents are known, the rules are fixed, and the delay is entirely in the reading and re-requesting. Automate that loop, keep a human on the exceptions and the coverage judgment, and the front door stops blocking your dispatch queue.
Stop letting paperwork block your dispatch
We build custom AI operations agents trained on your communities, including Victor Vendors for COI and license intake and Mason Maintenance for work order dispatch. The first agent is free, and you keep it.
See how it works for PM companiesFrequently asked questions
A certificate holder is the party that receives proof of a vendor's insurance. An additional insured is a party actually granted coverage under the vendor's policy. For property management, the specific association a vendor works in should appear as additional insured, not just your management company as certificate holder.
Sources & further reading