Establishing secure connection…Loading editor…Preparing document…

Declaration of Authenticity of Document

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

Declaration of Authenticity of Document

IN THE OF THE

OF

IN THE MATTER OF THE ESTATE OF Deceased

CAUSE NO.

I declare under penalty of perjury under the laws of the State of that the following is true and correct to the best of my knowledge:

1. My name and address are as follows:

2. The original of Decedent's Will has not been found. I have attached to this Declaration what I believe to be a true and correct copy of Decedent's Will because of the following reasons:

Witness my signature this the

Enter text

What the Declaration of Authenticity of Document Is

A Declaration of Authenticity of Document is a signed statement attesting that a specific paper or electronic record is genuine, unaltered, and originates from the named parties. It identifies the document, the signer, date of execution, and any attachments or versions covered, and typically describes the basis for authenticity (original, certified copy, electronic record). Organizations use it to support chain-of-custody, compliance, and evidentiary needs in audits, transactions, or legal proceedings. The declaration can be executed on paper, notarized, or completed electronically subject to ESIGN/UETA requirements.

Why a Declaration of Authenticity of Document Matters

Use a Declaration of Authenticity to document provenance, reduce disputes over alterations, and provide a clear audit trail for legal, regulatory, or business reviews. It strengthens evidentiary value, supports compliance with ESIGN/UETA when signed electronically, and clarifies custody.

Why a Declaration of Authenticity of Document Matters

Who Typically Prepares and Relies on This Declaration

Common users include legal teams, compliance officers, records managers, and transactional staff responsible for document integrity.

  • In-house counsel verifying evidence for litigation, contracts, and corporate records.
  • Records and compliance teams maintaining chain-of-custody and audit trails for regulated data.
  • Real estate and HR departments attaching declarations to leases, titles, or personnel files.

Core Elements to Include in a Professional Declaration of Authenticity of Document

Core elements define a complete Declaration of Authenticity, ensuring it is specific, signed, dated, and supported by identifying information and evidence of provenance.

Document ID

List the document title, version or control number, and page range. Include any prior identifiers to link copies and prevent ambiguity across versions.

Signer Details

Provide full legal name, role or capacity (e.g., custodian, author), contact information, and the relationship to the document or organization.

Authenticity Statement

A concise declaration that the record is original or an accurate copy, describing how authenticity was determined and any actions taken to verify integrity.

Attachments

Enumerate attached exhibits, certificates, notarizations, digital hash values, or related files and state whether those attachments are originals or copies.

Execution Data

Date and location of signing, signature type (wet, electronic), and any authentication method used such as email verification, SMS code, or credential analysis.

Certifier Info

Name, title, organization, and authority to make the declaration. If notarized, include notary details and notary commission information.

Step-by-Step: Completing a Declaration of Authenticity of Document

Follow these sequential steps to complete and execute a Declaration of Authenticity accurately, whether on paper or electronically.

  • 01
    Identify Document: Record title, version, and control number.
  • 02
    Describe Basis: State why document is authentic and verification steps.
  • 03
    Signer Info: Enter full legal name, capacity, and contact.
  • 04
    Sign & Date: Sign, date, and add notarization if required.

Where to Send or File a Completed Declaration

Typical routing for a completed declaration includes internal records, external recipients, and filing with courts or regulators when required.

  • Internal File: Store in records management system with index.
  • Recipient Delivery: Email certified copy or provide physical copy.
  • Regulatory Filing: Submit to agency or court if requested.
  • Audit Archive: Retain per retention schedule and access controls.

Configuring an Online Workflow for Declarations

Configure the online declaration workflow to collect identity, capture signature intent, and preserve an auditable record for compliance and retrieval.

Workflow Field Name | Configuration Value Configuration and Options for Online Setup
Identity Verification Method and Field Name Email confirmation and optional KBA
Signature Field Type and Placement Accept typed, drawn, or uploaded signature
Authentication Method and Strength Options SMS code, email link, or OAuth SSO
Audit Preservation and Export Settings Immutable audit trail and downloadable certificate

Technical Requirements for Electronic Distribution and eSubmission

To distribute a Declaration of Authenticity electronically, ensure your platform supports secure delivery, audit trails, and recipient authentication that meets legal requirements.

  • Formats: PDF, DOCX, and image archives supported
  • Integrations: Connectors for Salesforce, NetSuite, Google Workspace
  • Storage: Encrypted cloud storage with access controls

Typical Timelines and When to Provide a Declaration

Timing depends on recipient needs: provide declarations when requested for audits, closings, employment verification, or before regulatory submissions.

Upon Request:

Provide immediately when a counterparty or regulator requests documentation.

Real Estate Closings:

Deliver prior to closing or recording as requested by title company.

Employment Verification:

Provide with personnel file during onboarding or audit.

Regulatory Submission:

Attach to filings when agency requires evidence of authenticity.

Litigation Hold:

Preserve and produce on legal hold timelines.

Key Processing Milestones for a Declaration

Key milestones for processing a declaration from creation to archival ensure traceability and compliance across audit and legal workflows.

01

Draft and Review

Create the declaration and verify document identifiers before signature.

02

Execute and Authenticate

Obtain signatures and apply authentication or notarization as required.

03

Distribute and File

Send copies to stakeholders and store originals in the records system.

04

Archive and Retain

Move to long-term storage and apply retention schedule and legal holds.

Security and Compliance Considerations

Encryption in transit: TLS 1.2 or 1.3 protects data in transit
Encryption at rest: AES-256 encryption used for stored data
Audit Trail: Comprehensive timestamps, IP, and action logs
Access Controls: Role-based access, SSO and MFA available
HIPAA: HIPAA compliant when BAA in place
ESIGN / UETA: Meets ESIGN and UETA legal tests

Penalties and Risks of an Incorrect Declaration

Perjury risk: False declarations may trigger criminal charges
Civil liability: Contract disputes, rescission, damages possible
Regulatory fines: Industry-specific penalties may apply
Tax consequences: Backup withholding or IRS penalties
Notary rejection: Improper execution may invalidate notarization
Evidence value loss: Court may discount unreliable documents

Common Preparation Mistakes to Avoid

  • Incomplete identification fields or mismatched signer names create ambiguity and often require affidavits or corrected declarations to resolve disputes.
  • Incorrect dates or inconsistent date formats may undermine the effective date and complicate compliance or filing timelines.
  • Unsigned pages, initials only, or missing capacity designations can render a declaration ineffective for legal or regulatory use.
  • Attaching uncertified copies without noting copy status often leads recipients to request certified originals or refuse acceptance.

Practical Examples of Using a Declaration of Authenticity of Document

Real-world examples show how a Declaration of Authenticity supports transactions, audits, and disputes across industries.

Real Estate Closing

A title agent attaches a notarized Declaration of Authenticity to scanned closing documents to confirm originals were delivered and reviewed during escrow.

  • This clarifies chain-of-custody for recording.
  • When a post-closing dispute arose over an addendum, the recorded declaration and notarization shortened discovery and proved the executed version matched the filed instrument, reducing litigation time and preserving clear title transfer documentation.

Healthcare Records

A hospital attaches a Declaration of Authenticity to electronic patient records transferred between facilities to document extraction methods and confirm unaltered content.

  • This supports auditability and consent verification.
  • During a regulatory review, the declaration and retained audit trail demonstrated chain-of-custody and access controls, satisfying HIPAA reviewers and avoiding fines by proving records were authentic and access-limited.

Updating or Revising a Declaration While Preserving the Audit Trail

Use this grid to update or revise a declaration while keeping an auditable history of changes and approvals.

01

Initiate Revision:

Create a new amendment referencing the original control number
02

Record Changes:

List edits, reasons, and who authorized them
03

Re-sign Required:

Ensure all parties sign the amendment when material changes occur
04

Notify Stakeholders:

Distribute amended copies to original recipients and auditors
05

Archive Prior Version:

Retain the superseded declaration with version metadata
06

Update Indexing:

Refresh document indexes and searchable metadata for retrieval

eSignature Pricing Comparison for Executing Declarations of Authenticity

Compare baseline pricing and common plan capabilities across leading eSignature vendors to evaluate cost and compliance fit for processing declarations.

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 trial No No Yes, limited Yes, limited
Bulk Send Yes Yes Yes Yes No
Audit Trail Yes Yes Yes Yes Yes
HIPAA Compliant Yes Yes Yes No No

FAQs and Troubleshooting for the Declaration of Authenticity of Document

Answers to common legal, technical, and procedural questions when preparing, signing, or storing a Declaration of Authenticity of Document.


Need help? Contact support

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