What this automation does
New vendors go from “we need to pay these people” to an active, verified vendor without a dozen emails back and forth.
- Request. An employee fills in a short internal form with the vendor’s name, contact, what they supply, expected annual spend and the budget owner. The request is checked against existing vendors to catch duplicates and near-matches.
- Approve the relationship. The budget owner or procurement approves the new vendor. High-spend or high-risk categories add a second approver.
- Invite the vendor. The vendor receives one secure intake link to upload a W-9 (or W-8 for foreign vendors), a certificate of insurance if required, and enter remittance details.
- Read and cross-check. A vision model extracts fields from the W-9 and insurance certificate. Code compares them with the typed answers and with your requirements, such as coverage limits and certificate holder name.
- Screen. The legal and business names are screened against OFAC’s SDN and Consolidated sanctions lists and your own blocked-vendor list.
- Verify and create. A person calls the vendor at an independently sourced number to confirm bank details. Then the workflow creates the vendor in QuickBooks Online or BILL with the 1099 flag, terms and documents attached, and notifies the requester.
When it is worth building
It pays off when onboarding is slow, inconsistent or risky. Typical signs are vendors waiting weeks for their first payment, W-9s missing at year end, contractors on site with expired insurance, and bank details accepted from an email reply.
If you add a few vendors a year, a checklist and a shared folder are enough. If your AP platform already includes vendor self-onboarding with tax form collection, use it. Some do this well. The custom version is worth it when you need insurance tracking for subcontractors, approval routing by category, or one process across several entities and payment tools. Construction, property management and staffing companies feel the insurance side most.
Architecture
| Layer | What we use | Why |
|---|---|---|
| Internal request | A Jotform or Microsoft Forms request linked to the vendor list | Duplicates are caught before anyone emails the vendor |
| Vendor intake | A Jotform form with file uploads, sent as a unique link per vendor | Vendors upload once, and answers arrive structured |
| Document reading | OpenAI’s GPT models or Claude through the API, with vision input | Reads W-9s and insurance certificates of any layout |
| Checks | A code step with requirements by vendor type, plus sanctions list screening | Pass and fail decisions must be exact and explainable |
| Document storage | Google Drive or SharePoint with restricted folders | Tax forms and certificates stay in one controlled place |
| Vendor creation | QuickBooks Online through n8n’s built-in node, or BILL through its API using n8n’s HTTP Request node | The vendor appears only when everything has passed |
| Notifications | Slack and Gmail | Requesters see status without asking AP |
How to build it
- Define vendor types. For each type, such as subcontractor, professional services, supplies and software, list required documents, insurance minimums and approvers.
- Clean the vendor list first. Merge duplicates and inactive vendors before launch, or the duplicate check will flag everything.
- Build the two forms. Keep the internal request short. Make the vendor form conditional, so foreign vendors see W-8 instead of W-9 and subcontractors see insurance uploads.
- Build extraction and cross-checks. Extract W-9 fields and compare the legal name and tax classification with the typed answers. Check certificates for limits, dates and certificate holder wording against the vendor type.
- Add screening. Download OFAC’s SDN and Consolidated lists from its Sanctions List Service on a schedule and screen with fuzzy name matching. Possible matches go to a person, since common names produce false positives.
- Separate bank verification. Route bank details to a verification task that requires a call-back note and the name of the person who called before the vendor record is created.
- Schedule renewals. Store insurance expiry dates and request new certificates 30 days ahead. Optionally flag the vendor for payment hold if coverage lapses.
What breaks in production
- Bank changes by email. A convincing email asks to update remittance details. The workflow must never accept bank changes through any channel without the call-back step, and it should alert finance when someone tries.
- Legal name versus trade name. The vendor types their trade name but the W-9 shows the legal name, which causes TIN mismatches later. Store both and use the legal name for tax reporting.
- Old W-9 revisions and missing signatures. Vendors upload whatever is on their desktop. Check the revision and request a fresh form when needed. IRS instructions do not require most vendors to sign the certification unless they were previously notified of an incorrect TIN, so treat a missing signature as a policy check, not a legal one.
- Certificate holder errors. The certificate names a different entity than yours. This is easy for a model to read and easy for a person to miss.
- Process bypass. Someone pays a new vendor by card to skip onboarding. Compare card merchants against the vendor list monthly.
- Abandoned intakes. Vendors start the form and never finish. Send two reminders, then notify the requester.
Timeline and cost
A setup with two or three vendor types, W-9 and insurance checks, and vendor creation in one accounting system typically takes two to three weeks. Lumeor builds it for $3,500 to $9,000, depending on the number of vendor types, insurance requirements, entities and whether you need ongoing certificate tracking. Model costs are small, a few document reads per vendor. Tax IDs and bank details make this a good case for keeping the workflow on infrastructure you control. See n8n Cloud vs self-hosted for the trade-offs. For keeping certificates, licenses and other documents current after onboarding, see AI compliance document monitoring. New vendors then flow into AP approvals for their first bills.
How to measure success
- Business days from request to active vendor
- Vendors created with a complete, current W-9 (target is all of them)
- TIN mismatches and missing forms found during 1099 preparation
- Active subcontractors with expired insurance on any given day
- Duplicate vendors created per quarter
- Bank detail changes verified by call-back (target is all of them)