Establishing secure connection…Loading editor…Preparing document…

Acknowledgement of Identity ID

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

ACKNOWLEDGEMENT OF IDENTITY ID AGREEMENT

Parties

Recitals

WHEREAS, Requesting Party requires formal verification and written acknowledgement of an individual's identity for business, regulatory or recordkeeping purposes; and

WHEREAS, Verifying Party represents that it is duly qualified and authorized to examine, authenticate and record identity documents and to deliver an Acknowledgement of Identity ID consistent with accepted verification practices; and

WHEREAS, the Parties desire to set forth the terms under which Verifying Party will perform identity verification services and provide an Acknowledgement of Identity ID to Requesting Party.

Scope of Work

Verifying Party shall perform the identity verification services described below. Verifying Party shall examine original or certified identity documents, record identifying data, and prepare a signed Acknowledgement of Identity ID certifying the details of the verification performed. The method and extent of verification shall be consistent with industry-standard reasonable diligence for the stated purpose.

Identity Details

Provided identification documents (check all that apply):

Expiration date:

Date of verification performed:

Payment Terms

As consideration for the verification services performed by Verifying Party, Requesting Party shall pay the fees set forth below.

Term and Termination

This Agreement shall commence on the Start Date and shall remain in effect until the End Date, unless earlier terminated in accordance with this Section.

Start Date:

End Date:

Either Party may terminate this Agreement for material breach by the other Party if the breaching Party fails to cure the breach within the notice period specified above. Termination shall not relieve the Requesting Party of obligation to pay fees for services performed prior to termination.

Confidentiality

Each Party shall maintain in strict confidence all non-public information disclosed by the other Party in connection with this Agreement, including identity documents, personally identifiable information, verification results and related records (collectively, Confidential Information). Confidential Information shall be used solely to perform the services and for no other purpose. Confidential Information may be disclosed only to employees, agents or contractors who have a need to know and who are bound by confidentiality obligations at least as protective as those set forth herein. The obligations under this Section shall survive termination of this Agreement for a period of five (5) years.

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 that would apply the laws of another jurisdiction.

Entire Agreement

This Agreement, including any attachments or acknowledgements issued by Verifying Party pursuant to this Agreement, 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.

Acknowledgement

The undersigned certify and acknowledge that the information recorded in this Acknowledgement of Identity ID is true and accurate to the best of their knowledge. Verifying Party certifies that it examined the identification documents described above and that, on the date of verification, the person identified appeared before the Verifying Party and presented the referenced documents. Requesting Party acknowledges receipt of the written Acknowledgement and agrees to retain it in accordance with applicable recordkeeping obligations.

By checking the box below, Requesting Party confirms it has authorized the verification and accepts responsibility for the use and onward sharing of any resulting acknowledgement consistent with applicable law:

Requesting Party - Printed Name:

By:

Date:

Verifying Party - Printed Name:

By:

Date:

Enter text✕

What an Acknowledgement of Identity ID Is and When it’s Used

An Acknowledgement of Identity ID is a short written statement that a signer provides to confirm their identity for a transaction or record. It typically records the signer’s legal name, a government-issued identifier or document type, the method used to verify identity, and the date and place of acknowledgement. The form is used across onboarding, records verification, and compliance workflows where a receiving party needs documented proof that the person presenting credentials is the intended signer. Electronic versions are generally allowed under federal ESIGN (15 U.S.C. ch. 96) and state UETA law where adopted.

Why an Acknowledgement of Identity ID Matters

Provides a concise, auditable record of identity verification that supports contract enforceability and regulatory compliance.

Why an Acknowledgement of Identity ID Matters

Who Typically Prepares and Signs This Document

Organizations, individual signers, and agents use an Acknowledgement of Identity ID whenever identity confirmation must be recorded.

  • Financial services and lenders verifying customer identity for account opening or loan servicing.
  • Healthcare providers and clinics confirming patient identity for records or treatment authorizations.
  • Real estate firms and title companies documenting signer identity during remote closings.

The form is adaptable to many workflows — from consumer onboarding to internal approvals — and should match the receiving party’s verification policies.

Step-by-step: Complete an Acknowledgement of Identity ID

Follow these core steps to complete the form accurately and create a defensible record of identity verification.

  • 01
    Prepare: Gather government ID and document metadata before starting.
  • 02
    Enter Identity: Type full legal name and ID details exactly as shown on the ID.
  • 03
    Confirm Method: Record how identity was verified (in-person, ID scan, RON KBA, video).
  • 04
    Sign and Date: Have the signer execute the acknowledgement and include the date and location.

Configure a digital workflow for completion and tracking

Common configuration settings support secure capture, authentication strength, and long-term storage of the acknowledgement.

Field Configuration
Authentication Method Email link + SMS code or KBA when required
Signature Type Typed, drawn, or uploaded image depending on risk
Audit Trail Enable full IP, timestamp, and action logs
Storage Format Store signed copy as PDF/A for long-term preservation

Delivery channels, integrations, and technical needs

Choose platforms and integrations that support the authentication and retention your workflow requires.

  • Integrations: Salesforce, NetSuite, Google Workspace
  • File formats: PDF, DOCX, HTML supported
  • Security: TLS in transit; AES-256 at rest

Where to send or file the completed acknowledgement

Routing depends on purpose: legal file, HR record, client onboarding folder, or transaction repository.

  • Recipient Copy: Send signed PDF to the requesting party or account record
  • Internal Records: Save copy to secure document management system
  • Notary or Registrar: Forward a notarized acknowledgement where required
  • Backup Archive: Retain an immutable archived copy for audit purposes

Core elements to include in a professional acknowledgement

A complete document balances identity data, verification method, signer intent, and retention metadata to ensure legal usefulness.

Signer Identity

Full legal name, date of birth, and contact information captured exactly as shown on the supporting ID for unambiguous identification.

ID Details

Type of ID, issuing jurisdiction, ID number, and expiration date recorded to tie the acknowledgement to a specific credential.

Verification Method

Record whether verification was in-person, via remote online notarization, credential analysis, knowledge-based authentication, or documentary review.

Statement of Intent

A clear declarative line where the signer affirms the identity confirmation and acknowledges the purpose of the verification.

Execution Details

Signing date, location, and witness or notary information included where required by law or policy.

Audit metadata

System-generated IP, timestamp, and event log that supports attribution and non-repudiation for later review.

Required data points to capture

Legal Name: Exact name
Date of Birth: MM/DD/YYYY
ID Type: Driver’s license/passport
ID Number: Full ID value
Issuer: State or country
Expiry Date: MM/DD/YYYY

Typical timelines and processing expectations

Timelines vary by use case; set expectations up front and record response windows on the form.

Issue on Request:

Provide acknowledgement within the timeframe set by the requesting party

Expected Response:

Recipients often require return within 3–7 business days

Notary Retention:

RON recordings retained per state rules, commonly 5–10 years

Processing Time:

Verification and sign-back often complete same day for digital workflows

Record Availability:

Store signed copy accessible for audit when requested

Key milestones from request to archived record

A clear milestone sequence helps stakeholders track completion and escalate when delays occur.

01

Request Sent

Receiving party issues acknowledgement request with required fields and deadline.

02

Identity Verified

Verifier confirms ID via chosen method and records the result on the form.

03

Signed and Returned

Signer signs the acknowledgement and returns it to the issuing party.

04

Archive

Store the signed acknowledgement in the designated records repository.

Comparison: signNow and common eSignature vendors for acknowledgement workflows

Feature and starting-price overview for typical business tiers. Use vendor sites for full plan detail and to confirm feature availability for high-compliance needs.

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 Yes, 7-day free trial Varies by vendor Varies by vendor Varies by vendor Varies by vendor
Bulk Send Yes (Business Premium) Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No
Envelope Cap No envelope cap 100 envelopes/user/year Varies by plan Varies by plan Varies by plan

Common mistakes when preparing an acknowledgement

  • Entering a name that does not match the supporting ID, causing verification delays or rejections.
  • Omitting the verification method (in-person, RON, KBA), which weakens evidentiary value in disputes.
  • Failing to capture audit metadata (IP, timestamps), reducing ability to attribute the signature later.
  • Using initials instead of a full signature when the form requires a complete execution block.

Consequences of an incorrect or incomplete acknowledgement

Rejection: May be rejected
Regulatory Fine: Potential fines
Backup Withholding: Trigger 24% withholding
HIPAA Violation: Breach penalties
Notarization Failure: Record deemed invalid
Litigation Risk: Weakened evidence

Industry examples: how acknowledgements are used in practice

Real-world scenarios show how the acknowledgement supports different verification needs without replacing required legal steps.

Healthcare Intake

A clinic collects a signed identity acknowledgement during telehealth registration

  • Verifier records the patient’s ID type and number
  • The signed record is stored with the medical chart to meet HIPAA retention and audit needs.

Real Estate Closing

A title company requests identity acknowledgement before releasing closing documents

  • Identity verified via RON with audio-video record
  • The acknowledgement is saved with closing package to support chain-of-title and defend against fraud claims.

Who can sign and attest to identity

Authorized Signer

An individual who is the subject of the identity verification and who signs the acknowledgement to confirm their own identity. The text should note the signer’s capacity if signing for an organization.

Verifier / Notary

An authorized verifier, witness, or notary who confirms the presented credentials. Their entry should include name, commission information (if applicable), and signature or stamp per state rules.

Practical tips for accurate and efficient completion

Adopt consistent templates, require minimum authentication strength, and automate audit capture to reduce errors and processing time.

Standardize Templates
Use a single validated template across the organization to avoid missing fields and ensure consistent evidence capture.
Choose Authentication
Match authentication level to risk: email/SMS for low risk, KBA or RON for higher-risk transactions.
Capture Audit Data
Ensure the platform records IP, timestamps, and signer actions automatically to support attribution.
Train Staff
Provide short job-aid training on acceptable IDs, format rules, and state-specific notarization differences.

FAQs and troubleshooting for Acknowledgement of Identity ID

Answers to common questions about legality, notarization, digital signing, and correcting errors when an acknowledgement is incomplete.


Need help? Contact support

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