Can this form be signed electronically?

Yes. Electronic signatures are generally enforceable under the ESIGN Act and UETA when intent, consent, attribution, and retention are demonstrable.

Is notarization always required?

Not always. Notarization depends on the transaction type and state law; certain documents or recordings may require notarized acknowledgment.

What authentication strength is recommended?

Use multi-factor authentication or identity proofing (KBA or credential analysis) for high-risk transactions to reduce fraud and disputes.

How should supporting ID images be handled?

Store scanned IDs in encrypted storage, limit access by role, and include the verification result in the audit trail.

Can remote online notarization be used?

If your state permits RON and your platform meets technical and recordkeeping requirements, RON can be used for notarized identity attestations.

How long must these records be kept?

Retention varies: follow the longest applicable regulatory requirement such as IRS, HIPAA, or industry-specific rules when setting your retention policy.

Electronic Signature
Templates
Miscellaneous
Identification Request Form

Identification Request Form

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

IDENTIFICATION REQUEST FORM

Parties and Recitals

This Identification Request Form (the Agreement) is entered into by and between Requesting Party: and Subject/Individual: .

WHEREAS, Requesting Party requires verification of identity and related identifying documentation for the purpose set forth below; and

WHEREAS, Subject is the legal holder of the identifying documents described in this Agreement and has authority to provide the requested information and consent to its limited use; and

WHEREAS, the parties desire to set forth the scope, handling, payment terms, confidentiality, and governing law applicable to the request and delivery of identification materials.

Requesting Party Contact

Organization / Company Contact Person Contact Address Contact Phone / Email

Subject Identity Details

Full Legal Name

Date of Birth: Place of Birth:

Residential Address Identification Documents

Passport Driver's License State ID Other:

Issuing Authority: ID Number:

Issue Date: Expiration Date:

Copies Requested: Front Back Scan/PDF

Scope of Work

The Requesting Party engages the Subject and/or Document Custodian to produce, verify, and deliver the requested identification materials and associated attestations described herein. The services include collection, verification against presented documents, notarization (if requested), and delivery of certified copies in the format specified below.

Detailed Scope (describe exactly what is requested)

Purpose and Use

Purpose of request (check applicable): Employment verification Contractual compliance Legal requirement Other:

Payment Terms

Fee for identification verification and delivery: $.

Payment Schedule

Late fee: . Any unpaid amounts incur interest and collection costs as permitted by law.

Term and Termination

Term Commencement Date: Termination Date (if any):

Either party may terminate this Agreement for convenience upon written notice to the other party not less than days prior to the effective termination date. Termination for cause is permitted upon material breach that remains uncured for thirty (30) days following written notice.

Confidentiality and Data Handling

The Requesting Party and any agents shall treat all identity materials, copies, and related personal data as Confidential Information. Confidential Information shall be used solely to accomplish the Purpose described in this Agreement and shall not be disclosed except as required by law or with the prior written consent of the Subject. Each party shall implement administrative, technical, and physical safeguards appropriate to the sensitivity of the data.

In the event of any compelled disclosure, the party receiving a legal demand to disclose shall provide prompt written notice to the other party (to the extent legally permitted) and shall cooperate in any lawful effort to limit disclosure or obtain protective measures.

Representations and Warranties

Subject represents that the identifying documents presented are genuine to the best of Subject's knowledge and that Subject has authority to provide them for the Purpose. Requesting Party represents that the information supplied shall be used only for the stated Purpose and in compliance with applicable privacy and data protection obligations.

Governing Law

This Agreement shall be governed by and construed in accordance with the laws of the State of without regard to choice-of-law principles. The parties consent to the exclusive jurisdiction of the courts located therein for any action arising from this Agreement.

Entire Agreement

This Agreement, including any attachments and written exhibits signed by the parties, constitutes the entire agreement between the parties with respect to the subject matter and supersedes all prior or contemporaneous understandings, proposals, and communications, whether written or oral. Amendments must be in writing and signed by authorized representatives of both parties.

Subject Attestation and Consent

By signing below, the Subject attests under penalty of perjury that the information and documents provided are true and correct and consents to the use and limited disclosure of this information for the stated Purpose and as permitted by law.

Additional Instructions or Special Handling

Requesting Party (Print):

By:

Date:

Subject / Individual (Print):

By:

Date:

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

An Identification Request Form is a standardized document used to collect verified identity details from an individual or organization for onboarding, recordkeeping, compliance, or transaction purposes. Typical uses include verifying a payee’s taxpayer identification for payments, confirming a client’s identity for access to sensitive services, or documenting identity for contractual approvals. The form generally asks for full legal name, government-issued ID number, date of birth, contact information, and a signer declaration. It can be completed on paper or electronically and must preserve an audit trail when used in regulated contexts.

Why a clear Identification Request Form matters

A complete and accurate form reduces identity-related delays, supports regulatory compliance, and minimizes the risk of payment or access errors. Properly capturing identity data also establishes an auditable record to support backups, tax reporting, and later dispute resolution.

Who typically completes and relies on this form

Organizations across finance, healthcare, real estate, and legal services use the Identification Request Form to confirm identities before paying, delivering services, or granting access.

Payroll and accounts payable teams that need accurate taxpayer identification and remittance routing for vendor payments.
Healthcare intake and billing staff who must link identities to protected health information and billing records.
Real estate and title professionals verifying parties during lease or closing workflows to satisfy state recording requirements.

Choosing a consistent form and process reduces follow-up requests and supports faster, auditable processing across departments and third-party integrations.

Step-by-step: Complete and verify the Identification Request Form

Follow this sequence to collect identity data, authenticate the signer, and retain a compliant record.

01

Step 1: Provide the requester’s contact and reason for the request.
02

Step 2: Collect full legal name, DOB, ID type, and ID number.
03

Step 3: Authenticate identity (compare ID, use KBA, or use RON where allowed).
04

Step 4: Obtain signature and record the audit trail with timestamp and IP.

Typical process flow for handling an Identification Request Form

This outline shows routing from request to storage, useful when designing automated workflows or manual handoffs.

Initiate Request: Requester creates and sends the form to the subject.
Complete Form: Subject fills fields and attaches supporting ID images.
Authenticate: Verifier performs identity checks and documents results.
Archive: Signed form and audit trail stored in secure record system.

How to configure an online workflow for this form

Configure fields, authentication, and routing to ensure captured data meets your verification requirements and retention policies.

Field	Configuration
Required Fields	Make name, ID type, ID number, and DOB mandatory.
Authentication	Enable SMS or KBA for high-risk verifications.
Routing	Auto-route completed forms to compliance and AP teams.
Storage	Send signed PDFs to encrypted document repository.

Technical and integration considerations

Choose a platform that supports secure storage, strong authentication, and audit trails suitable for identity verification.

File formats: PDF, DOCX supported
Integrations: Connects to CRMs and cloud storage
Auth options: SMS, KBA, SSO available

Ensure the selected platform can enforce retention policies, provide export formats, and integrate with existing systems for secure long-term storage.

Timing considerations and common deadlines

Some identity-related workflows are time-sensitive; follow deadlines to avoid penalties or reporting delays.

Tax reporting timing:

Provide identity data to payers as requested to avoid backup withholding.

Document retention:

Retain records per applicable retention schedule and regulatory rules.

Notarization windows:

Schedule in-person or RON sessions within issuer or transaction deadlines.

Respond to audit:

Produce identity records promptly when required by regulator or auditor.

Form updates:

Update information promptly when identity data changes to remain current.

Frequent errors to avoid

Incomplete fields that require follow-up and delay processing.
Mismatched name or SSN that triggers backup withholding or rejections.
Low-strength authentication allowing identity disputes later.
Improper storage lacking encryption or sufficient audit logs.

Consequences of incorrect or missing identity information

Backup withholding: Missing or incorrect TIN can trigger 24% backup withholding.

Information return penalties: Failing timely or accurate 1099 filings can incur IRC §6721 penalties.

I-9 violations: I-9 paperwork errors may result in civil penalties under 8 CFR rules.

Breach exposure: Inadequate storage can lead to HIPAA or state breach notifications.

Contract disputes: Weak proof of identity can undermine enforceability in disputes.

Recordkeeping fines: Failure to retain required records may trigger agency penalties.

Essential security and compliance elements for identity data

Encryption in transit: TLS 1.2/1.3

Encryption at rest: AES-256

Audit trail: Timestamp, IP, action log

Access controls: Role-based access

HIPAA support: BAA required for PHI

Authentication: 2FA, KBA, and SSO options

Comparing eSignature providers for Identity Request workflows

This table summarizes common plan attributes for eSignature platforms. signNow appears first per comparative convention and includes entry-level pricing details.

	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 free trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
Envelope Cap	No cap	100 envelopes/user/year	Varies	Varies	Varies

How organizations use Identification Request Forms in practice

Real-world examples illustrate typical adaptations of the form across departments and industries.

Real Estate Closing

A title company collects IDs and notarized attestations for all parties

Uses RON where permitted to speed closings
The result is faster closings and a complete audit trail stored with the closing package.

Vendor Onboarding

A finance team requires a completed form and W-9 for new vendors

Identity and TIN are verified before payments are approved
This prevents backup withholding and ensures timely 1099 reporting.

Frequently asked questions about the Identification Request Form

Answers to common questions about completion, electronic signing, notarization, and storage of identity records.

Need help? Contact support

Can this form be signed electronically?
Yes. Electronic signatures are generally enforceable under the ESIGN Act and UETA when intent, consent, attribution, and retention are demonstrable.
Is notarization always required?
Not always. Notarization depends on the transaction type and state law; certain documents or recordings may require notarized acknowledgment.
What authentication strength is recommended?
Use multi-factor authentication or identity proofing (KBA or credential analysis) for high-risk transactions to reduce fraud and disputes.
How should supporting ID images be handled?
Store scanned IDs in encrypted storage, limit access by role, and include the verification result in the audit trail.
Can remote online notarization be used?
If your state permits RON and your platform meets technical and recordkeeping requirements, RON can be used for notarized identity attestations.
How long must these records be kept?
Retention varies: follow the longest applicable regulatory requirement such as IRS, HIPAA, or industry-specific rules when setting your retention policy.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now