The Instrument Was Acknowledged Before Me On Date, By Form

Use a The Instrument Was Acknowledged Before Me On date, By template to make your document workflow more streamlined.

What this acknowledgment form records

The Instrument Was Acknowledged Before Me On Date, By Form records that a signer acknowledged executing an instrument before a notarial officer on a stated date. It is evidence of acknowledgment, not proof that the instrument’s contents are truthful or legally sufficient. Complete the signer, date, venue, and notarial information exactly as required by the applicable state law. ESIGN and UETA generally recognize electronic signatures in qualifying transactions, but exclude wills, codicils, testamentary trusts, court orders, and certain family-law or real-estate documents. Confirm state notary requirements before using an electronic workflow.

Business and legal teams

Legal departments and business administrators use this acknowledgment form to document execution of agreements, powers of attorney, and other instruments when state law permits electronic processing. They verify the notarial wording, signer identity, venue, and date before sending the record for completion.

Notaries and regulated organizations

Notaries and regulated organizations use the form to preserve a clear acknowledgment record alongside contracts, healthcare documents, tax materials, or property records. State-specific requirements determine whether electronic notarization, in-person notarization, or wet-ink execution is required.

Platform requirements for this form

Complete The Instrument Was Acknowledged Before Me On Date, By Form through Chrome, Firefox, Safari, or Edge on Windows or macOS. signNow uses TLS 1.2/1.3 for data in transit and provides mobile apps for iOS and Android.

Supported browsers Chrome, Firefox, Safari, and Edge
Desktop systems Windows and macOS desktops
Mobile access iOS and Android mobile apps

Organizations handling acknowledgment records should use managed devices, current browser security updates, and controlled user accounts. Enterprise deployments may also require API access, SSO provisioning, and retention or certificate settings aligned with state notary rules and the underlying instrument.

How to complete this acknowledgment form

Use signNow to prepare the instrument, confirm its acknowledgment fields, route it to the correct participants, and preserve the completed record.

Upload form:
Upload the acknowledgment form.
Check fields:
Review detected fields and add missing date, signer, venue, and signature fields.
Assign roles:
Assign the signer and authorized notarial participant.
Send document:
Send the instrument through signNow.
Store evidence:
Review the completed form and Audit Trail.

How the digital workflow works

The signNow workflow converts the prepared acknowledgment instrument into a controlled signing transaction while preserving the document and its completion evidence.

Upload: Upload the source PDF to signNow.
Detect fields: Auto-detect fillable fields and verify acknowledgment details.
Route: Send the instrument to assigned participants.
Preserve: Store the signed form with its Audit Trail.

be ready to get more

Get legally-binding signatures now!

Start free trial

Request a call

Best ROI. Our customers achieve an average 7x ROI within the first six months.
Scales with your use cases. From SMBs to mid-market, airSlate SignNow delivers results for businesses of all sizes.
Intuitive UI and API. Sign and send documents from your apps in minutes.

Signer authentication:

Confirm signer identity through the configured authentication method.

Timestamp capture:

Capture the exact completion timestamp for each participant action.

Action logging:

Record signer views, field entries, and acknowledgment completion events.

Document sealing:

Apply tamper-evident controls to the completed document record.

Certificate creation:

Generate the completion certificate with transaction evidence.

Audit retrieval:

Retrieve or export the signed form and Audit Trail.

Setting	Recommendation
Authentication and provisioning	Use role-based accounts with verified signer email
Signature type	Use an intent-based electronic signature
Audit trail	Enable completion certificate and Audit Trail export
Document retention	Apply the underlying record’s legal retention period
Encryption	Protect records with TLS 1.2/1.3 and AES-256

Security for acknowledgment records

Data in transit:

TLS 1.2/1.3 encryption

Data at rest:

AES-256 encryption

Independent controls:

SOC 2 Type II certified

Security management:

ISO 27001 certified

Electronic signatures:

ESIGN and UETA compliant

Protected health data:

HIPAA compliant with BAA

Prepare the document

Upload the source instrument and confirm required acknowledgment fields.

Deliver to signers

Send the instrument to the assigned signer and notarial participant.

Complete signer review

Signer turnaround depends on participant availability and required authentication.

Archive completion

Export the completed form and Audit Trail for archival.

Document preparation:

Upload the acknowledgment form and confirm the notarial date, signer, and venue fields.

First send:

Send the completed acknowledgment form to the signer through a controlled signNow workflow.

Team onboarding:

Train authorized staff to distinguish acknowledgments from jurats, wills, and court filings.

Signer completion:

The signer reviews the instrument and completes the required acknowledgment process.

Audit export:

Export the completed document and Audit Trail after every signing transaction.

Three-year tax records:

Retain related federal tax records three years from filing under IRC §6501(a), when applicable.

Six-year HIPAA records:

Retain PHI-related records six years under 45 CFR §164.530(j), when applicable.

Secure archival:

Store the signed instrument, certificate, and audit evidence in access-controlled archival storage.

Retention periods for related records

The acknowledgment itself has no single universal federal retention period; retain it according to the underlying transaction, industry rule, and applicable state law.

Three years from filing

Apply IRC §6501(a) when the acknowledgment supports federal tax records.

Six years from creation

Apply 45 CFR §164.530(j) to documentation containing protected health information.

Three years for payroll records

Apply 29 CFR §516.5 to covered FLSA payroll records linked to the instrument.

Five years after record year

Apply 29 CFR §1904.33 to covered OSHA injury records related to the transaction.

Seven years for audit records

Apply 15 U.S.C. §7245 to covered Sarbanes-Oxley audit records supporting the transaction.

Best practices for signed acknowledgment records

Preserve the completed instrument and evidence of signing in a retention process tied to the document’s actual legal and business purpose.

Classify the underlying record before archiving

Identify whether the instrument is a business record, tax record, healthcare record, or another regulated document before choosing a retention period. Federal rules differ: IRC §6501(a) generally uses three years for tax assessment, while HIPAA requires six years for specified documentation.

Export the Audit Trail with every signed instrument

Download the signed instrument together with its signNow Audit Trail, completion certificate, signer events, timestamps, and access history. Keep these files together so the acknowledgment date and signing sequence can be reconstructed without relying solely on the live workspace.

Apply the controlling retention rule

Apply the controlling rule to the underlying transaction rather than assuming one universal period. Tax records generally follow IRC §6501(a), while PHI-related documentation follows 45 CFR §164.530(j); state requirements may require longer retention.

Archive records with controlled access

Use encrypted, access-controlled storage for the instrument, notarial information, and signer data. Restrict downloads to authorized personnel, maintain an administrative access log, and test document retrieval so the record remains readable throughout its required retention period.

Privacy and disclosure pitfalls

Leaving the acknowledgment date, venue, or signer name incomplete can make the record difficult to authenticate later.
Using electronic signing without checking state notary law can produce a record that does not satisfy the required execution method.
Sending the form to the wrong participant can weaken attribution and leave the notarial acknowledgment disconnected from the signer.
Including unnecessary personal information increases disclosure risk when the completed instrument and Audit Trail are shared.

State rules and document exclusions

State law controls

Notary rule

Invalid testamentary use

Wills excluded

Electronic exception

Court filings excluded

Recording rejection

Deed requirements

Troubleshooting this acknowledgment form

These answers address field setup, signer authentication, electronic-signature rules, plan limits, retention, and excluded document categories.

Upload the PDF again and confirm that the acknowledgment date, signer, venue, and signature fields are assigned to the correct participants. signNow’s field editor lets you add or reposition fields before sending, while the Audit Trail records later changes and completion events.

A signNow electronic signature can support ESIGN and UETA requirements when intent, consent, attribution, and record retention are established. Those statutes do not override state notary rules or exclude wills, court orders, and certain family-law records.

The Business plan includes legally binding eSignatures, templates, and Audit Trails at $8 per user per month when billed annually. Subscription plans include 100 signature invites per user annually; overage fees may apply.

Use stronger signer authentication when the instrument or organization requires it. Enterprise adds advanced signer authentication, while configured workflows can use email or SMS-based verification; authentication does not replace an in-person or remote-notarization requirement imposed by state law.

Export the completed instrument and Audit Trail from the transaction record, then store them together under the retention rule for the underlying record. signNow supports audit evidence, but IRC, HIPAA, state, or industry rules determine how long records remain available.

Do not use this workflow as a substitute for excluded records. ESIGN exceptions include wills, codicils, testamentary trusts, court orders, certain family-law decrees, and specified notices. Confirm with the relevant state notary authority before processing a restricted instrument.

28M+Documents signed

13+Years in business

4.6/5Average G2 rating

BE READY TO GET MORE

Get this form now!

If you believe that this page should be taken down, please follow our DMCA take-down process.