Job search
W-9 Requested for a Tech Contract: Confirm the Payee and Submission Route
Resolve payee identity and the authorized document destination before supplying a W-9; keep worker classification, receipt and payment as separate questions.
Before sending a W-9 for a tech contract, confirm the payee, the correct tax name-number pairing and the authorized submission route. A trade name, an LLC suffix and a payment-account label can refer to different things. Resolve the mismatch before certifying tax information or sending it to an unfamiliar destination.
This guide uses current IRS pages and the published March 2024 W-9 and requester instructions checked October 23, 2026. We reviewed public documents, not a real taxpayer record, client portal or contract. Both completed cases are fictional and contain no tax numbers. LandOffer publishes this guide; recent tech roles can support a separate shortlist while you clarify this contract's onboarding request.

Identify the requester and what the W-9 is doing
The IRS W-9 overview says the form supplies a correct taxpayer identification number, or TIN, to a person required to file an information return. For a software engagement, the request commonly comes through accounts payable or vendor onboarding. Confirm which client entity is requesting it and which payee record it concerns; do not assume every person copied on a project email needs the completed form.
The form itself says to give it to the requester, not send it to the IRS. A client or authorized onboarding provider may collect the information for the payer's records. That is different from you filing a tax return or paying a fee to the IRS to activate a contract.
A W-9 request does not settle worker classification. The IRS contractor-forms page describes obtaining the form after determining that the payee is an independent contractor. Its classification guidance considers the relationship's control and independence facts. Neither a recruiter calling the work “1099” nor your signature on W-9 makes that factual inquiry disappear.
If the contracting party, scope or proposed relationship remains unclear, ask about that separately. A tax-data request cannot supply missing payment terms, an agreed project scope or an explanation of who would employ you. This guide organizes the document handoff; it does not decide your classification, tax residency or withholding obligations.
Match the tax name before copying the invoice heading
Line 1 is the required name of the individual or entity; the instructions generally connect it to the tax-return name. Line 2 is for a different business, trade, DBA or disregarded-entity name. Line 3a follows the federal tax classification of the person named on line 1. It does not follow the software role or whichever name is printed most prominently on an invoice.
The current instructions distinguish these situations:
| Stated situation | Name treatment described by IRS | What needs confirmation |
|---|---|---|
| Individual or sole proprietor | Individual tax-return name on line 1; business/DBA name on line 2 | The person and any trade name actually receiving the payments |
| Disregarded entity | Owner's name on line 1; disregarded entity on line 2 | Owner identity and the applicable federal tax treatment |
| Partnership, corporation or non-disregarded LLC | Entity's tax-return name on line 1; different trade name on line 2 | Actual classification and entity records, not the LLC suffix alone |
For a sole proprietor with an EIN, the form instructions permit either the individual's SSN or EIN. For a single-member LLC disregarded from its owner, they specify the owner's SSN or EIN, if the owner has one; an LLC taxed as a corporation or partnership uses the entity's EIN. Those are different name-number pairings. Use the TIN that belongs with the name and applicable instructions, rather than choosing an entity EIN simply because the invoice carries a business name.
If your structure, owner or tax election is uncertain, take the relevant entity and tax records to a qualified professional before certifying the form; an accounts-payable field label cannot establish those facts. Do not let a client's dropdown decide it. Similarly, having a US mailing address or a US TIN does not by itself establish that W-9 is your appropriate form. The IRS limits W-9 to US persons, including resident aliens, and directs foreign persons to the applicable W-8 or Form 8233. The applicable alternative requires its own review.
Worked payee record: Mara's trade name is not a separate LLC
Mara Chen is a fictional US sole proprietor providing a data-migration script under the trade name Lantern Batch Studio. That status and the name on her tax return are stipulated inputs, not conclusions drawn from her occupation. Her invented contract names “Mara Chen, doing business as Lantern Batch Studio,” but the client's draft vendor record says “Lantern Batch Studio LLC.” No LLC exists in this example.
She completes this pre-submission comparison using the IRS instructions:
| Record or field | Completed review for the stipulated facts | Next action |
|---|---|---|
| Contracting party | Mara Chen with a DBA, not a separate LLC | Preserve the actual contract wording |
| Invoice heading | Lantern Batch Studio is the trade name | Explain its relationship to Mara; do not invent an entity |
| Draft vendor record | Added “LLC” is inconsistent with the supplied facts | Ask accounts payable to correct the record |
| W-9 line 1 | Mara Chen, matching the assumed tax-return name | Keep this distinct from the invoice's branding |
| W-9 line 2 | Lantern Batch Studio | Identify the trade name here |
| Line 3a and Part I | Individual/sole proprietor; correct individual name-number pairing | Use the verified permitted TIN privately; no number appears in this case |
| Delivery and receipt | Client's approved tax-document route not yet supplied | Obtain it and request receipt confirmation |
Her completed decision is to request the vendor-name correction and submission instructions before transmitting the form. She does not change her tax name to fit an erroneous vendor record. The comparison identifies a specific administrative inconsistency without claiming that an IRS matching service has validated anything.
Her unsent note reads:
Hi accounts payable, the agreement identifies Mara Chen doing business as Lantern Batch Studio. The draft vendor record adds “LLC,” which is not part of the stipulated business name. Please confirm the corrected payee record and your approved route for receiving the W-9. I will provide the tax information through that route once confirmed; this message contains no TIN. Please also identify how I can confirm receipt and whether any separate invoice setup remains outstanding.
This is a teaching message, not something sent to a real client. Mara keeps payment instructions separate from this name correction. Correcting a vendor label is not authorization to redirect money to a different account.

Verify the handoff without turning a portal label into proof
Obtain the destination from an established client contact or onboarding process. If a new email introduces an unfamiliar upload site, verify that the client authorized that provider before entering a TIN. A familiar logo, a person's display name or an encrypted connection alone does not establish who controls the destination. These are practical verification steps, not a claim that we audited a particular service.
Ask the established payment contact to identify the payer, vendor record, authorized recipient and approved transmission method, plus the acknowledgment you should retain. Those answers connect the tax record to the actual contract. Avoid putting a TIN in a routine project-chat thread, public file link, email subject or broadly shared job-search spreadsheet. Do not send the same complete form to extra recipients just to prove you responded.
W-9 is not a bank-change instruction. Its optional account-reference field does not authorize a new payment destination, and its standard fields do not request a banking password. If onboarding combines tax collection with bank details, distinguish those requests and verify the payment-change process independently. Never treat an unexpected bank update as a necessary consequence of supplying a tax form.
An electronic questionnaire is not automatically improper. The requester instructions allow qualifying substitute forms and electronic submission systems. They describe requirements concerning equivalent information, identity, access documentation and certification, with exceptions where a signature is not required. A form that looks different can still be a legitimate substitute; an ordinary file uploader is not automatically an IRS-compliant tax system.
If the client's substitute form presents unrelated contractual terms alongside the tax certification, read them separately and ask for clarification. IRS instructions address how substitute certifications must be presented; they do not turn every extra contractual provision into an IRS requirement. We did not test a client's system or certify its compliance.
Worked LLC handoff: Damon's tax pairing is settled, the destination is not
Damon Price is a separate fictional consultant using Cedar Span Analytics LLC for an API-integration project. In this case, his qualified adviser has already confirmed that it is a single-member LLC disregarded for federal tax purposes, owned by Damon as a US individual. No election or residency determination is being made here. The entity also has an EIN, which does not change that stipulated classification.
His invented onboarding packet names the LLC as the contract vendor but gives two conflicting delivery directions: an existing accounts-payable checklist specifies a private vendor portal, while a new project email asks for the W-9 through a different shared upload link. No actual website or client message was accessed.
He completes the following handoff record:
| Question | Completed result | Status for this case |
|---|---|---|
| Line 1 tax name | Damon Price, the stipulated owner | Resolved for the example's assumed facts |
| Line 2 entity name | Cedar Span Analytics LLC | Resolved; different from line 1 by design |
| Line 3a | Owner's individual/sole-proprietor classification | Do not select an LLC corporation code just from the suffix |
| Part I pairing | Owner's applicable SSN or owner EIN, not the disregarded LLC's separate EIN | Verify privately with the adviser; no numbers supplied here |
| Signature authority | Correct person must review the certification and applicable signature requirements | Do not ask a project teammate to certify Damon's tax facts |
| Submission destination | Existing checklist and new link disagree | Hold transmission until accounts payable confirms the authorized route |
| Receipt evidence | No upload or acknowledgment exists | Record pending, not received or vendor approved |
The filled record separates an intentional owner/entity-name difference from an unresolved security issue. Damon does not rename the LLC out of the contract to make every field identical. Nor does he replace the owner's pairing with the LLC's EIN to satisfy an unexplained upload field.
His complete, unsent clarification is:
Hi accounts payable, I am preparing the W-9 for the Cedar Span Analytics LLC vendor record. The tax form will reflect the stipulated disregarded-entity owner on line 1 and the LLC on line 2. Please confirm that the vendor workflow supports that distinction and identify the authorized tax-document submission route. The existing checklist and a new project email provide different links, so I have not entered or uploaded tax information. Which destination should I use, who receives it, and what acknowledgment should I retain? I am not requesting a change to payment instructions.
His outcome is “name treatment identified; transmission on hold.” A useful reply would identify which of the two destinations accounts payable authorizes and confirm how its vendor record handles Damon on line 1 and the LLC on line 2. A repeated request for the form without identifying the authorized destination would leave the transmission question unresolved.
Review the certification and keep completion states separate
Read Part II and its instructions before signing. The certification covers tax facts under penalties of perjury, not merely acknowledgment that a document was received. Signature requirements vary: the form's instructions discuss “other payments,” including nonemployee services, and a withholding agent may request a signature even where an exception is described. Do not apply a universal “always sign” or “never sign for contractors” rule. Resolve questions with the requester and a qualified adviser rather than changing certification text to make a portal accept it.
Missing or incorrect information can lead to backup withholding in applicable circumstances. That is a reason to resolve the correct name and TIN promptly, not to invent a number or ignore a legitimate request. Supplying the form does not establish a particular withholding outcome. This guide does not calculate net pay or determine an exemption.
After an authorized submission, retain a private copy of the version supplied and the acknowledgment, date, payer and vendor reference. Keep the TIN out of a general task log. Distinguish “submitted,” “received,” “vendor setup accepted” and “invoice paid”; none is automatically the next. IRS instructions also require updated information when relevant facts such as the account's name or TIN change, so review an old saved form before reusing it.
For the current contract, close the information gap with the responsible payment contact, and preserve the agreed submission route alongside the payee record. Keep recent LandOffer roles separate from tax-document storage. The useful result is a correct, privately delivered record for the right requester, with any classification or personal tax question still routed to appropriate advice.


