You just hired a 1099 contractor. The signed W-9 is in your inbox. The invoice is sitting in your accounts payable queue, due Friday. Most founders pay first and discover the TIN problem ten months later when a CP2100 notice arrives. This post walks through the workflow that catches the problem in the next five minutes instead.
The whole flow runs on TinCheck's first-check-free offer through SaaSOffers, with no card required. You enter the contractor's name and TIN, you get back a match or mismatch result in real time, and you have a permanent record stamped against the W-9 before payment goes out. Total time from W-9-in-hand to verified-and-cleared: roughly four minutes once you have done it twice.
Step 1: Pull the Name and TIN Off the W-9
Open the W-9 the contractor sent you. There are exactly two fields that matter for the TIN match:
- Line 1: Name. Must be the legal name as it appears on the contractor's tax records. For individuals this is the name on their Social Security card. For single-member LLCs this is the owner's name, not the LLC name. For corporations and multi-member LLCs this is the entity's registered name.
- Part I: Taxpayer Identification Number. Either an SSN (XXX-XX-XXXX) for individuals, an EIN (XX-XXXXXXX) for entities, or an ITIN for non-resident individuals.
The most common error here is the contractor wrote their LLC's name on Line 1 and their personal SSN in Part I. The IRS treats those as two different taxpayers and will not match the pair. If you see this combination, send the W-9 back to the contractor and ask them to either use their personal name with their SSN, or get an EIN for the LLC and use both.
Take a quick screenshot of the W-9 fields. You will paste these into TinCheck verbatim in the next step. Match the formatting exactly: capitalization, punctuation, hyphens.
Step 2: Open TinCheck and Sign Up
Go to the partner link at join.sovos.com/stogo1b4hxay. The SaaSOffers partner page applies the free-first-check offer automatically. Sign up with your work email. No credit card required for the first verification.
The signup flow takes under a minute. You will land on the TinCheck dashboard with a primary action labeled "Real-Time TIN Check" or similar. Click it.
This account becomes your permanent verification log. Every check you run stays in the dashboard with a timestamp, so when an IRS auditor asks "did you verify this TIN before filing the 1099?" you have a dated record to show them. That is the secondary value of doing this in TinCheck instead of the free IRS portal. The log is automatic.
Step 3: Run the Match
Paste the contractor's legal name and TIN into the verification form. Hit submit. The check returns in under five seconds.
You will get one of four results:
Match (clean). The name and TIN you submitted match the IRS records exactly. You are safe to pay this contractor, file their 1099 at year-end, and the IRS will not issue a CP2100 for this record. Stop here, screenshot the result, attach it to the W-9 in your contractor folder, and approve the invoice.
Mismatch on TIN. The TIN you submitted does not correspond to anyone in the IRS database, or it corresponds to someone with a different name. The contractor likely wrote down their TIN wrong. Send them the result, ask them to confirm or correct the number, and re-verify. Do not pay until this clears.
Mismatch on Name. The TIN is valid but the name does not match what the IRS has on file. The most common cause is the contractor used a married name, a maiden name, or a nickname instead of their legal name. Ask for the exact name on their Social Security card or EIN confirmation letter and re-verify.
Multiple Issues. Both name and TIN are wrong. Restart the W-9 process. Do not attempt to guess corrections.
The five-second turnaround is the operational difference between TinCheck and the free IRS portal. The IRS TIN Matching service can take up to 24 hours to return a result on bulk submissions and is built for batch processing, not single ad-hoc checks during contractor onboarding.
Step 4: Handle a Sanctions Hit Before You Wire
TinCheck runs every name through OFAC, SDN, and several other sanctions lists in the same call. This is a free byproduct of the TIN check and it catches a real edge case for startups paying international service providers, design contractors, or AI labelers through global agencies.
If you get a sanctions hit, do not pay the vendor and do not send the result back to them. A sanctions match is a regulatory matter. Forward the TinCheck result to your accountant or compliance counsel. Most hits are false positives caused by common-name overlap, but the resolution path is not "ask the vendor to clarify." It is "have qualified compliance evaluate the match."
For most startup contractor onboarding, this step is a no-op. The hit rate is well under 1%. When it does fire, you are grateful the check happened before the wire went out.
Step 5: Stamp the W-9 and Log the Result
Save the TinCheck result page as a PDF or screenshot. Attach it to the contractor's W-9 in whatever folder structure you use for vendor records (Notion, Google Drive, Drata, your accounting software). That attached record earns its keep across the lifecycle of the contractor relationship:
- Year-end 1099 filing. When you or your accountant prepares 1099s in January, the attached verification proves the name and TIN pair you are about to file was IRS-matched at intake.
- Audit trail. If the IRS ever asks why a specific 1099 was filed with this exact name and TIN, the timestamped verification result is your evidence of reasonable cause.
- Onboarding handoff. When your bookkeeper changes, when you bring on an accountant, when you transition payroll to a PEO, the verification record travels with the W-9.
Mark the contractor as cleared for payment in your AP system. The invoice that was waiting can now go out.
Total elapsed time from opening the W-9 to approving the invoice: under five minutes if everything matches on first try, around fifteen minutes if you need one round of correction with the contractor.
When in the Contractor Lifecycle to Run the Check
The right time to verify is the moment the W-9 arrives, before the first invoice is paid.
The TIN error is the contractor's responsibility, but the penalty is yours. The cheapest moment to correct an error is before money has moved. Once you have paid an invoice against a bad TIN, the contractor's incentive to fix their paperwork drops sharply.
The contractor's responsiveness to a "please correct your W-9" email is highest in week one of the relationship. By month four it is much lower. By month ten when the CP2100 arrives, it is sometimes impossible to reach them at all.
The annual 1099 filing deadline is January 31. If you wait until December to verify TINs in bulk for everyone you paid that year, you will lose a non-trivial percentage to unresponsive contractors, ghosted email addresses, and people who changed their legal name without telling you.
The cleanest rule a founder can adopt: no contractor invoice gets paid without a green TIN verification logged against their W-9. Build it into your AP workflow as a hard gate, not a polite request.
How to Make This Permanent in Your Onboarding
Once you have run the workflow twice, codify it.
- 1Add a checkbox to your contractor onboarding template that reads "TIN verified via TinCheck, result attached." The checkbox sits next to the W-9 upload field. If the checkbox is empty, the contractor record is not complete and AP cannot pay invoices.
- 1Make the verification step part of your accounts payable approval flow. The simplest implementation is a custom field on the vendor record in QuickBooks, Brex, Ramp, or whatever AP tool you use. The field is required before a vendor can be approved for payment.
- 1Run a quarterly audit of your active vendor list. Filter for any vendor that does not have a TIN verification record on file and run them through TinCheck before the next invoice cycle. A 30-vendor portfolio is about an hour of work per quarter.
- 1For founders using a bookkeeper, write the requirement into the scope of work. "Verify TIN through TinCheck before adding any new 1099-eligible vendor to QuickBooks." Most bookkeepers will already be doing some version of this. If yours is not, this is a process gap worth correcting.
The point of building it into onboarding rather than treating it as a year-end task is that an annual mass verification has bad failure modes. A contractor who stopped responding in March is a problem you discover in January when you cannot file a clean 1099 for them. Verifying at intake removes that scenario.
What About the Free IRS TIN Matching Portal?
The IRS does offer a free TIN Matching service through e-Services. The product is real, it works, and for a startup with five contractors that file 1099s once a year, it is a defensible choice.
The reasons most startup founders end up paying for TinCheck anyway:
- The IRS portal requires e-Services enrollment, which is a multi-step process involving identity proofing and ID.me, often takes a week, and assumes a specific corporate role profile that does not always match a founder's setup.
- The portal does not run sanctions screening, deceased-individual checks, or USPS address validation. Those are separate products you would need to assemble.
- The portal is batch-oriented, not real-time. A single ad-hoc check during contractor onboarding is awkward to run through it.
- There is no audit trail formatted for compliance review. You get a result. The record-keeping is on you.
For a side-by-side breakdown of when the free IRS tool is enough versus when paid verification pays for itself, the TinCheck review post walks through the math. The short answer is that the free IRS option works if your contractor volume is low, your contractors are domestic-only with no sanctions exposure, and you have the operational bandwidth to maintain your own audit log. For most growing startups, the time math favors paid verification by a wide margin.
The Penalty Math, in One Paragraph
The 2026 IRS penalty for filing a 1099 with an incorrect TIN runs $60 per form if corrected within 30 days, $130 per form if corrected by August 1, $330 per form if corrected after August 1, and $660 per form for intentional disregard, capped per year based on company size. On a 30-contractor portfolio with a 5% TIN-error rate (close to the IRS's published estimate for self-reported W-9s), the unverified-at-intake scenario costs roughly $500 to $9,900 per year in expected penalties depending on when each error is caught. TinCheck's pricing for that same volume is well under $100 a year. The break-even point is one prevented mismatch.
The IRS penalty guide post breaks down the schedule in detail for the cases where you want the full numbers.
FAQ
Next Step
The fastest way to test the workflow is to run a single check against a contractor you already paid. Pull their W-9, take 90 seconds to verify the TIN, see what comes back. If it matches, your records are clean and you can move on. If it does not, you have months of lead time to fix it before the IRS notices.
Ready to unlock these deals?
Free account. No credit card required.
