Is an electronic signature legally valid?

Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention are present.

How should a payer verify a TIN?

Use the IRS TIN Matching program or obtain supporting documentation such as an SSN card or EIN letter. Verification reduces IRS mismatch notices and potential penalties.

What happens if the TIN is wrong?

An incorrect TIN can trigger backup withholding at 24%, IRS mismatch notices, and information return penalties under IRC §6721 if not corrected promptly.

Can the payee retract or update the form?

Yes. A payee should provide an updated completed form to the payer. Prompt updates minimize withholding and reporting errors.

How long should completed forms be kept?

Retain completed requests at least three years after filing per IRS guidance (IRC §6501(a)); longer retention may apply under HIPAA or state law.

When is notarization required?

Notarization is generally not required for TIN requests. If a state or transaction requires notarization, follow state rules and consider remote notarization where permitted.

Electronic Signature
Templates
Tax
Taxpayer Identification Request Form

Taxpayer Identification Request Form

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

Taxpayer Identification Request Form

Requesting Party Name: Request Date:

Taxpayer Information

Full Legal Name Business Name / DBA (if applicable) Mailing Address Contact Phone Contact Email

Entity Type (Select all that apply)

Individual / Sole Proprietor

C Corporation

S Corporation

Partnership

Trust / Estate

Limited Liability Company (LLC) LLC tax classification:

Other:

Taxpayer Identification Number (TIN)

Provide either Social Security Number or Employer Identification Number. Do not enter both. Check the box to indicate which number is provided.

SSN provided:

EIN provided:

Reason for Request

Provide the legitimate business reason for requesting the TIN

Certification (Under Penalties of Perjury)

By signing below, I certify, under penalties of perjury, that the following statements are true and correct:

1. The taxpayer identification number shown on this form is the correct taxpayer identification number of the person named above.

2. The taxpayer identified above is not subject to backup withholding due to failure to report interest and dividend income, unless the person has been notified that they are subject to backup withholding by the appropriate authority. If notified, the taxpayer has provided notification and the required withholding code or details.

3. The taxpayer is a U.S. person (including a U.S. resident alien) for U.S. federal tax purposes, or, if not a U.S. person, has provided the appropriate foreign status documentation to the requesting party.

4. I agree to promptly notify the Requesting Party if any information provided on this form becomes incorrect or changes, including changes to taxpayer identification number or name.

I acknowledge that providing false information may subject me to civil or criminal penalties under applicable law.

Taxpayer Name:

By:

Date:

What the Taxpayer Identification Request Form Is and when it’s used

A Taxpayer Identification Request Form is a document a payer uses to collect a payee's Taxpayer Identification Number (TIN) and related identification details for tax reporting and withholding. It is typically requested when a person or business will receive reportable payments, such as compensation, interest, dividends, or contract payments. The form documents the payee's name, TIN, entity type, and certification that the TIN is correct; accurate responses reduce the risk of backup withholding and support payer compliance with IRS reporting obligations under federal tax law.

Why collecting accurate taxpayer identification matters

Accurate TIN collection prevents backup withholding, supports correct 1099 and similar filings, and reduces IRS notices. It also documents payer diligence when verifying payees for tax reporting and withholding purposes.

Who typically requests and completes this form

Common requesters include payers, employers, and financial institutions when they need a TIN for tax reporting.

Employers and staffing agencies needing employee or contractor TINs for payroll reporting.
Financial institutions collecting TINs for interest, dividends, or account reporting.
Businesses engaging contractors or vendors who must be reported on 1099 forms.

Payees respond with their legal name, TIN, entity classification, and signature so payers can meet reporting and withholding obligations.

Step-by-step: request and collect taxpayer identification

Follow a simple four-step workflow to request, receive, verify, and retain TIN information while minimizing compliance risk.

01

Request: Send the form or secure link to the payee for completion.
02

Receive: Gather complete fields, signature, and date from the payee.
03

Verify: Confirm TIN with IRS TIN matching or validate supporting documents.
04

Retain: Store the completed form in a secure records system for the retention period.

Digital delivery and technical considerations for eSubmission

Use secure PDF or DOCX files and a compliant eSignature platform to collect taxpayer identification and signatures.

File formats: PDF, DOCX, or fillable form formats supported.
Integrations: Integrates with Salesforce, NetSuite, Google Workspace, Microsoft 365.
Compliance: Supports audit trail and HIPAA BAA where required.

Typical electronic workflow for issuing the request

An efficient eSubmission workflow reduces friction and creates an auditable trail from request to completed form.

Upload document: Load the request form into your eSignature system.
Place fields: Add name, TIN, checkbox, and signature fields.
Send link: Email or share a secure signing link with the payee.
Capture audit trail: Record IP, timestamps, and authentication evidence.

Essential elements of a professional Taxpayer Identification Request Form

A complete form balances clarity for the payee with the payer's compliance needs; include explanatory text and clear certification language.

Clear header

State the purpose of the form and which payer is requesting the TIN to avoid confusion and improper submissions.

Payee identification

Fields for full legal name, DBA if applicable, and business entity structure to match IRS records and prevent mismatches.

TIN entry

Dedicated field for SSN or EIN. Provide format guidance and a checkbox when the TIN is pending or unknown.

Certification statement

Include signed certification language mirroring IRS guidance so the signer affirms TIN accuracy and exemption status.

Payer contact

Provide payer name and contact for questions and to facilitate timely corrections of mismatched information.

Retention note

Indicate record retention period and secure storage requirements so both parties know the document lifecycle expectations.

Security and compliance controls to protect taxpayer data

Encryption: TLS 1.2/1.3 in transit, AES-256 at rest

Access control: Role-based permissions and multi-factor options

Audit trail: Timestamped logs with IP and action history

Certifications: SOC 2 Type II and ISO 27001 compliant

HIPAA support: BAA available for healthcare scenarios

File formats: Retains signed PDF and exportable text

Penalties and tax risks from incorrect or missing TINs

Backup withholding: 24% withholding when TIN is missing or incorrect

1099 filing penalties: $60–$330 per form depending on lateness

Intentional disregard: $660+ per form with no cap

I-9 penalties: $281–$2,789 per violation for paperwork errors

IRS mismatch notices: Can trigger audits and information requests

Business liability: Payer may face assessment for improper withholding

Common mistakes to avoid when preparing the request

Entering an incorrect or transposed TIN that causes an IRS mismatch and potential backup withholding.
Using an informal or preferred name instead of the legal name shown on tax records, creating reporting discrepancies.
Failing to obtain a dated signature or using initials where a full signature is required by the payer.
Transmitting unredacted TINs over unsecured email or storage, exposing sensitive taxpayer data to breach risk.

Timing and related tax-reporting deadlines to keep in mind

Although a Taxpayer Identification Request Form itself has no filing deadline, related informational return deadlines create timing needs for payers.

W-9 provision:

Provide upon payer request; no IRS filing deadline

1099-NEC to recipient:

Jan 31 is the deadline to furnish 1099-NEC to recipients

1099-MISC to IRS:

Paper to IRS by Feb 28, electronic by Mar 31

Individual return:

Form 1040 due April 15; extensions available

FBAR:

April 15 with automatic extension to Oct 15

Key processing milestones after sending the request

Track milestones from request issuance through filing to keep the payer's reporting timeline aligned with IRS deadlines.

01

Request issued

Payer sends the request and sets an internal response deadline.

02

Response received

Payee returns completed form with signature and date.

03

Verification

Payer verifies TIN via IRS TIN matching or document review.

04

Report filing

Payer includes verified data on required 1099 or other information returns.

How a Taxpayer Identification Request Form compares to a W-9

Distinguish the request form from IRS forms to clarify purpose and filing implications for payers and payees.

Criteria	Taxpayer Identification Request Form	W-9
eSignature Validity
Notarization	generally no	generally no
Purpose	collect tin for payer use	provide tin to payer
Filed to IRS

Typical eSignature vendor pricing and feature comparison for TIN collection workflows

Platform pricing and capabilities affect cost and compliance when collecting TINs electronically; signNow is listed first for direct comparison.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	7-day trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

Frequently asked questions about the Taxpayer Identification Request Form

Answers to common questions about electronic signature validity, correcting TINs, backup withholding, retention, and authentication for payers and payees.

Need help? Contact support

Is an electronic signature legally valid?
Yes. Electronic signatures are legally enforceable under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention are present.
How should a payer verify a TIN?
Use the IRS TIN Matching program or obtain supporting documentation such as an SSN card or EIN letter. Verification reduces IRS mismatch notices and potential penalties.
What happens if the TIN is wrong?
An incorrect TIN can trigger backup withholding at 24%, IRS mismatch notices, and information return penalties under IRC §6721 if not corrected promptly.
Can the payee retract or update the form?
Yes. A payee should provide an updated completed form to the payer. Prompt updates minimize withholding and reporting errors.
How long should completed forms be kept?
Retain completed requests at least three years after filing per IRS guidance (IRC §6501(a)); longer retention may apply under HIPAA or state law.
When is notarization required?
Notarization is generally not required for TIN requests. If a state or transaction requires notarization, follow state rules and consider remote notarization where permitted.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now