Establishing secure connection…Loading editor…Preparing document…

Identification Declaration

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

IDENTIFICATION DECLARATION

This Identification Declaration (the "Declaration") is made as of by and between:

Declarant Name:    Date of Birth:

WHEREAS

WHEREAS, Declarant possesses certain identifying information and documentary evidence required by Recipient to confirm Declarant's identity for business, contractual, or regulatory purposes; and

WHEREAS, Recipient requires a written declaration and certification of identity from Declarant and may rely upon the representations herein in conducting business or completing verification obligations; and

WHEREAS, the parties wish to record the scope of identification, the obligations of each party, payment for any verification services, and the terms governing reliance upon this Declaration.

SCOPE OF WORK

Declarant shall provide the following identification information and documentary evidence to Recipient. The parties agree the services and actions to be performed are described below:

Issuing Authority:    Issue Date:    Expiration Date:

PAYMENT TERMS

For any verification services performed by Recipient at Declarant's request, Declarant shall pay Recipient the fees set forth below.

Late Fee:    Payment Address/Method:

TERM AND TERMINATION

Term Commencement Date:    Term End Date (if applicable):

Either party may terminate this Declaration for convenience upon days' prior written notice to the other party. Termination shall not relieve either party of obligations accrued prior to termination.

CONFIDENTIALITY

All identifying information, copies of identification documents, and any supporting materials provided by Declarant to Recipient in connection with this Declaration constitute Confidential Information. Recipient shall maintain such information in confidence and shall not disclose it except (a) as required by law or regulation, (b) with Declarant's prior written consent, or (c) to third-party service providers bound by written confidentiality obligations no less protective than those contained herein. Recipient shall use Confidential Information solely for the purposes set forth in this Declaration.

GOVERNING LAW

This Declaration shall be governed by and construed in accordance with the laws of the State of without regard to conflict-of-law principles.

ENTIRE AGREEMENT

This Declaration, together with any exhibits or schedules attached hereto, constitutes the entire agreement between the parties with respect to the subject matter hereof and supersedes all prior and contemporaneous agreements, understandings and communications, whether written or oral. Any amendment must be in writing and signed by both parties.

DECLARATION AND CERTIFICATION

I, the undersigned Declarant, declare under penalty of perjury that the information and copies of identifying documents provided to Recipient are true, correct, and complete to the best of my knowledge. I authorize Recipient to rely upon this Declaration for identity verification and related business purposes.

Additional Declarations or Conditions:

Declarant:

By:

Date:

Recipient:

By:

Date:

Enter text✕

What an Identification Declaration Is and When it’s Used

An Identification Declaration is a written attestation in which a person affirms specific identity details for a defined purpose. It typically lists full legal name, date of birth, government ID type and number, current address, and a short sworn statement verifying that the information is true. Organizations use this document for identity verification when primary identity documents are unavailable or when a record must show the declarant’s self-attested information. The form may be executed on paper, notarized, or signed electronically depending on legal and recipient requirements.

Why an Identification Declaration Matters for Compliance and Records

Identification Declarations create a clear, auditable record of a person’s asserted identity, reduce onboarding friction, and support downstream processes such as benefits enrollment, vendor setup, and property transactions while preserving legal traceability under U.S. e-signature frameworks.

Why an Identification Declaration Matters for Compliance and Records

Who Typically Prepares or Signs an Identification Declaration

Typical users include employers, landlords, financial institutions, legal teams, and government or benefits administrators who need a signed identity attestation before granting access or services.

  • New hires and HR teams verifying identity and eligibility for employment documentation.
  • Property managers and leasing agents confirming tenant identity during intake.
  • Small-business vendors and procurement departments collecting identity details for onboarding.

Use the declaration when formal ID copies are not available or when a concise sworn statement of identity is sufficient for the receiving party.

Step-by-step: Completing an Identification Declaration

Follow these sequential steps to complete a compliant and accurate declaration.

  • 01
    Prepare Documents: Gather government ID and proof of address before starting.
  • 02
    Enter Identity Data: Fill full name, DOB, ID type and number in required formats.
  • 03
    Describe Purpose: Write a clear, concise purpose to limit ambiguity.
  • 04
    Sign and Authenticate: Sign, date, and add notarization or witness if required.

Typical Processing Flow for an Identification Declaration

This sequence outlines common routing from completion to acceptance by the receiving party.

  • Initiate Request: Requester sends form or signing link to the declarant.
  • Complete Form: Declarant fills fields and attaches supporting ID if requested.
  • Authenticate: Signer completes required authentication or notarization step.
  • Receive and Review: Recipient reviews submission and confirms or requests corrections.

Online Workflow Settings to Reduce Processing Errors

Configure basic form and routing options to improve accuracy and compliance.

Field Configuration
Required Fields Mark name, DOB, ID type and signature as mandatory.
Field Validation Enable format checks for MM/DD/YYYY and numeric ID values.
Authentication Require email or SMS code; escalate to KBA for higher risk.
Attachments Allow upload of ID images in PDF or JPG formats.

Technical Considerations for eSubmission and Integration

Confirm platform compatibility and authentication before accepting electronic Identification Declarations.

  • Supported Formats: PDF, DOCX, and common image formats are widely accepted.
  • Integrations: Link to systems such as Salesforce, NetSuite, and Google Workspace.
  • Authentication Options: Use email, SMS, KBA, or advanced signer authentication as needed.

Ensure your chosen eSignature vendor supports required integrations and retention of an audit trail for dispute resolution and compliance.

Core Elements to Include in a Professional Identification Declaration

A complete declaration contains identity details, purpose, signature, and data about how it was verified.

Declarant Details

Full legal name, date of birth, and contact information so the declarant is unambiguously identified and reachable for follow-up.

Government ID Data

Type of ID, issuing state or country, and the ID number to allow cross-checking against official records where permissible.

Attestation Statement

A short sworn sentence stating the accuracy of the information and, when applicable, the consequences of false statements.

Execution Block

A space for signature, printed name, and date; include notary or witness lines when required by recipient or jurisdiction.

Purpose and Scope

A clear description of why the declaration is provided and any limits on its use to prevent mission creep or unauthorized reuse.

Audit Metadata

For electronic execution include signer IP, timestamps, authentication method, and a downloadable certificate of completion.

Security and Compliance Features to Consider

Encryption: TLS 1.2/1.3; AES-256 at rest
Audit Trail: Time-stamped signing events and IP logging
HIPAA Support: BAA available where required
21 CFR Part 11: Controls for FDA-regulated electronic records
SOC 2: Type II reporting and controls
Accessibility: WCAG 2.0 Level AA compatibility

Principal Risks and Potential Consequences

Perjury Risk: False statements may trigger criminal or civil perjury actions
Administrative Rejection: Incomplete or inconsistent data can lead to denial of service
Privacy Breach: Improperly secured personal data risks regulatory violations
I-9 Issues: Employment identity errors may cause DHS fines
Tax Withholding: Incorrect TINs can trigger backup withholding
Fraud Exposure: Unauthorized declarations may enable identity fraud

Common Mistakes When Preparing an Identification Declaration

  • Using a nickname or abbreviated legal name that does not match government ID, causing verification failures and delays.
  • Entering date fields in nonstandard formats (e.g., DD-MM-YYYY) when the recipient expects MM/DD/YYYY, which can invalidate automated checks.
  • Failing to attach required supporting identification images or scans, resulting in requests for re-submission and longer processing time.
  • Skipping notarization or witness steps when the recipient’s policy or the governing law requires them, causing rejection or lack of enforceability.

eSignature Pricing and Feature Snapshot for Identification Declarations

Compare baseline pricing and select capabilities relevant to signing and storing Identification Declarations; signNow appears first for reference.

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 by plan Varies by plan Varies by plan Varies by plan
Bulk Send Yes (Business Premium) Varies by plan Varies by plan Varies by plan Varies by plan
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes (BAA required) Varies by plan Varies by plan Varies by plan Varies by plan
Envelope Cap No cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Real-world Examples of Identification Declaration Use

Two concise examples illustrate how organizations use declarations in day-to-day operations.

Martin Properties — Tenant Intake

A rental property manager used a signed Identification Declaration to accept a remote lease application

  • The declaration included ID number and purpose
  • Martin Properties reduced in-person appointments and documented identity intent while following state notarization rules when required.

Fertility Centers of Illinois — Patient Records

A healthcare clinic accepted electronic declarations to confirm patient identity for nonclinical administrative processes

  • Each form was stored under HIPAA controls
  • The clinic combined declarations with BAA-covered workflows and retained records per HIPAA retention requirements.

Timing Expectations and Common Processing Deadlines

Understand typical turnaround times and statutory retention of notarization or RON session records.

Response on Request:

Provide a completed declaration upon written request; no universal statutory deadline.

Recipient Review:

Organizations commonly review submissions within 1–5 business days.

RON Record Retention:

Audio-video recordings typically retained 5–10 years per state RON rules.

Notary Journal:

Notaries must keep journal entries per state requirements, often several years.

Dispute Window:

Retain records to cover potential statute of limitations exposure for the underlying matter.

Practical Tips for Accurate and Efficient Declarations

Adopt consistent form controls and authentication to reduce errors and speed acceptance.

Use Exact Names and Formats
Always capture the declarant’s full legal name and standardized date formats. Consistency prevents identity mismatches during automated or manual verification and reduces rework by the recipient.
Require Supporting Attachments
Ask for a clear image of the government ID and a proof-of-address document when needed. Attachments provide corroborating evidence and reduce repeated requests from recipients.
Choose Appropriate Authentication
Match authentication strength to transaction risk: email or SMS for low-risk, knowledge-based or multi-factor verification for high-risk identity assertions or regulated industries.
Document Purpose Clearly
State the declaration’s specific purpose and permitted uses. Limiting scope reduces the chance of improper reuse and clarifies retention and privacy handling.

Frequently Asked Questions and Troubleshooting

Answers to common questions about validity, authentication, notarization, and corrections for Identification Declarations.


Need help? Contact support

be ready to get more
Join over 28 million airSlate SignNow users