Form 40 Affidavit

Create a custom Form 40 Affidavit that meets your industry’s specifications.

What is Form 40 Affidavit?

Form 40 Affidavit is a sworn written statement used for a specific legal, business, or administrative purpose identified by the applicable jurisdiction or transaction. Its effect depends on the affidavit’s wording, the signer’s oath or affirmation, and required formalities such as notarization, witnesses, or filing. Form 40 is not a universal federal form with one nationwide procedure, so users should confirm the issuing authority and state rules before completion. signNow can upload the document, detect fillable fields, route it for an electronic signature where permitted, and preserve the completed record with an audit trail.

Real estate

Real estate teams may use an affidavit alongside lease agreements, property records, or transaction documents when state law permits electronic completion. Verify whether notarization, witnesses, recording, or a specific state form is required before sending it for signature.

Business and legal

Legal departments and business operators can prepare affidavits supporting contracts, NDAs, invoices, HR records, or consent documentation when the underlying transaction allows electronic signatures. The affidavit’s required wording, notarization, and filing destination remain matters of applicable state or court rules.

Business types that use Form 40 Affidavit

Form 40 Affidavit workflows differ by state and transaction, but these business types benefit from controlled preparation, signing, and record retention.

A solo attorney can prepare a state-specific affidavit, route it to a client or witness, and retain the signed copy with the matter file. The workflow reduces manual exchanges while leaving notarization and filing obligations for counsel to verify separately.
A regional property-management company can reuse an approved affidavit template for lease, ownership, or property transactions. Centralized document control helps staff send the correct version while preserving each signer’s audit trail for the relevant file.
An enterprise legal or compliance department can standardize affidavit routing across subsidiaries, connect records to existing systems, and apply role-based access. Counsel can still review state-specific language before the document reaches an external signer.

How Form 40 Affidavit works in signNow

Use the approved state or transaction-specific affidavit, then route its required fields through a controlled signing workflow.

Upload form: Upload the approved Form 40 Affidavit file.
Place fields: Review detected fields and add required signer fields.
Send request: Send the affidavit to the authorized signer.
Store record: Collect the signature and preserve the completed 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.

Authenticate signer:

Confirms the signer’s identity using the configured authentication method.

Capture timestamps:

Records signing and delivery events with associated timestamps.

Record document hash:

Associates the completed document with an integrity record.

Seal completion evidence:

Preserves changes and completion evidence in the signing history.

Connect signer actions:

Links signer actions to the executed Form 40 Affidavit.

Export audit trail:

Allows authorized users to retrieve or export the audit trail.

Field placement

Upload the approved affidavit and place signature, date, initials, or text fields without recreating its state-specific wording. Review the final rendering before sending.

Signer routing

Send Form 40 Affidavit to named recipients by email or an available signing link, keeping the intended signing order visible to the sender and recipients.

Audit trail

Capture timestamps, delivery events, signer actions, and completion evidence in an audit trail that can accompany the executed affidavit during internal review.

Signer authentication

Use SMS authentication or other configured controls when the affidavit’s risk profile requires stronger evidence connecting the signer to the transaction.

Mobile access

Access the completed affidavit from desktop or mobile workflows, subject to the state’s requirements for notarization, witnesses, and filing.

Record integrations

Connect the completed record to supported systems such as Google Drive, Box, Salesforce, NetSuite, or Microsoft 365 when the organization’s document process requires it.

Setting	Recommendation
Authentication method	Email verification with SMS for higher risk
Signature type	Electronic signature where state law permits
Audit trail	Enable completion history and export
Document retention	Apply the underlying record rule
Encryption	Use TLS in transit and AES-256 at rest

Security for Form 40 Affidavit

Transport encryption:

TLS 1.2/1.3 in transit

Stored data encryption:

AES-256 at rest

Security certification:

SOC 2 Type II certified

Information security:

ISO 27001 certified

Healthcare protection:

HIPAA compliant with BAA

Electronic signatures:

ESIGN and UETA compliant

Mobile options for Form 40 Affidavit

Form 40 Affidavit workflows can be prepared through signNow’s web experience or mobile apps for iOS and Android. Use an up-to-date browser with TLS 1.2 or TLS 1.3 support, and confirm that the device can open, review, and retain the completed PDF.

Mobile apps iOS and Android apps
Offline mode Offline signing support
Camera capture Camera document capture

Mobile signing is useful when an authorized signer is away from a desk, but it does not replace state-required notarization, witnesses, or filing. Regulated teams should manage iOS and Android devices, restrict document access, configure authentication, and preserve the final affidavit with its audit trail.

Form 40 Affidavit retention schedule

Form 40 Affidavit has no single nationwide retention period; apply the rule governing the record or transaction it supports.

Three years for tax records

Apply IRC §6501(a) to federal tax records; six years may apply when income is understated by 25% or more.

Later of three or one years

Retain employment-related records under 8 CFR §274a.2(b)(2)(i)(A): three years after hire or one year after termination, whichever is later.

Six years for HIPAA records

Retain HIPAA documentation for six years from creation or last effective date under 45 CFR §164.530(j), when the affidavit contains protected health information.

Six years for broker records

Retain broker-dealer books and records for six years under 17 CFR §240.17a-4 when the affidavit belongs to that regulated record set.

Seven years for audit records

Retain Sarbanes-Oxley audit records for seven years under 15 U.S.C. §7245 when the affidavit supports covered audit documentation.

State rules and document exclusions

State formalities

Notarization omitted

Execution challenge

Electronic signature rejected

Excluded document

Will-related use

Excluded proceeding

Court filing use

Recording issue

Deed attachment

Form 40 Affidavit challenges

Using a generic affidavit template can omit state-required wording, acknowledgment language, witness lines, or filing instructions for the transaction.
Treating an electronic signature as sufficient can create problems when the affidavit requires notarization, in-person appearance, or submission to a court or recorder.
Sending the wrong version to multiple signers makes completed affidavits difficult to reconcile and may require the entire signing process to be repeated.
Storing only the final PDF without its audit trail weakens the evidence connecting the signer, timestamps, authentication events, and executed record.

Form 40 Affidavit troubleshooting

Resolve document-version, signer-authentication, consent, and state-law questions before treating the completed affidavit as final evidence.

Upload the exact Form 40 Affidavit version approved for your state or transaction, then compare the rendered PDF with the source. signNow’s document editor can place fields, but it does not determine whether wording or execution formalities satisfy a state rule.

Business includes legally binding eSignatures, templates, and audit trails at $8 per user per month when billed annually. It does not establish that a particular affidavit may be signed electronically under state law.

A signer can receive the request without creating a signNow account, depending on the sender’s workflow. If stronger attribution is needed, configure available authentication such as SMS verification and retain the audit trail with the signed document.

Use Business Premium at $15 per user per month billed annually when bulk send is needed. The verified plan information does not establish a Form 40 Affidavit-specific sending limit, so do not assume one without checking the account configuration.

For a consumer-facing affidavit, ESIGN requires disclosure of the right to paper records, electronic-access capability, and withdrawal procedures under 15 U.S.C. §7001(c). Configure and retain those disclosures when the transaction falls within that rule.

signNow states that it is ESIGN- and UETA-compliant and provides audit trails, but state law may still require notarization, witnesses, or in-person execution. Check the relevant Secretary of State, court, or recorder requirements before relying on electronic completion.

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.