Form 23, Affidavit And Report
Use a Form 23 Download Fillable PDF, Affidavit And Report template to make your document workflow more streamlined.
What Form 23, Affidavit And Report does
Form 23, Affidavit And Report is a document used to record a person’s sworn statement and the facts or activity being reported. Its exact fields, filing agency, deadline, and notarization rules depend on the issuing authority, which is not identified in the supplied form name. Complete every applicable statement, review names and dates against source records, and preserve the signed copy with its audit trail. Electronic signing may be recognized under ESIGN and applicable state law, but agency instructions control whether electronic delivery is accepted.
Who may use this form
Individuals and filers
Individuals use the affidavit to state facts under oath, while businesses use the report to document an event, transaction, or compliance matter for an identified recipient.
Business teams
Operations, legal, compliance, and government-facing teams can prepare the form, route signature requests, and retain the completed record when the issuing authority accepts electronic documents.
How the signing workflow works
Prepare the exact Form 23 file, verify its fields, route it to the authorized signer, and retain the completed evidence.
Upload: Upload the source file Prepare: Detect and review fillable fields Route: Send the form to authorized signers Archive: Store the completed record and audit trail
Quick steps to complete Form 23
Use this sequence to prepare, route, sign, and preserve Form 23, Affidavit And Report in signNow.
Upload:
Upload the current Form 23 file. Review:
Check detected fields and add missing ones. Assign:
Assign each signature, date, and text field. Send:
Send only to authorized recipients. Store:
Download the signed form and audit trail.
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.
What the audit trail records
The audit trail supplements Form 23 with evidence about signer actions, timing, document integrity, and later retrieval.
Authenticate signer:
Capture timestamp:
Hash document:
Seal record:
Review history:
Export trail:
Recommended Form 23 workflow setup
Configure the signing packet around signer identity, document integrity, audit evidence, and the recipient’s specific filing requirements.
| Setting | Recommendation |
|---|---|
| Authentication method | Email verification with SMS OTP |
| Signature type | Typed or drawn electronic signature |
| Audit trail | Enable completion certificate and action log |
| Document retention | Apply the governing agency retention rule |
| Encryption | TLS 1.2/1.3 and AES-256 protection |
Mobile options for Form 23
Sign Form 23 using signNow mobile apps on iOS or Android. Browser access uses TLS 1.2/1.3, while the mobile workflow can support offline signing and camera-based document capture.
Mobile apps iOS and Android apps Offline mode Offline signing available Document capture Camera-based capture
For regulated deployments, administrators should manage devices, confirm the recipient’s acceptance of electronic records, and configure authentication appropriate to the affidavit’s sensitivity. API, SSO, certificate, and long-term validation requirements should be confirmed against the receiving agency’s rules before rollout.
Security for signed records
Transport encryption:
Storage encryption:
Security assurance:
Information security:
Electronic signatures:
Record evidence:
Legal standing and evidentiary value
A completed Form 23 may provide evidence of the signer’s stated facts when the signer’s intent, identity, consent, and record integrity can be shown. ESIGN and applicable UETA provisions generally recognize qualifying electronic signatures, but they do not override exclusions for wills, court orders, family-law decrees, or agency-specific filing rules.
Retention rules depend on record class
Form 23 has no supplied universal retention period; apply the rule governing the underlying transaction or record class.
Three years from filing
Six years from creation
Six years for books
Three years for payroll
Five years after year
Risks of incorrect completion
Incomplete report
Wrong submission channel
Unproven signer intent
Invalid acknowledgment
Potential completion challenges
The issuing authority is not identified, so the correct deadline and submission channel cannot be inferred from the form name alone. An affidavit can contain personal information that requires restricted access, careful recipient selection, and secure archival after signing. A signature request may fail evidentiary review if signer identity, intent, consent, or the final document version is unclear. A signNow workflow cannot replace a required notarial act, in-person appearance, or agency-specific filing procedure.
Form 23 troubleshooting questions
These answers address signing, plan, evidence, security, and submission questions while separating signNow capabilities from agency requirements.
The supplied form name does not identify an issuing agency or filing deadline. Confirm the source instructions before sending; signNow cannot determine which recipient or deadline applies.
Business plans include legally binding eSignatures, templates, audit trails, and mobile apps. Business is listed at $8/user/month with annual billing; confirm the current plan terms before purchase.
Business Premium is listed at $15/user/month with annual billing and includes bulk send. Use it only when the same Form 23 packet must be routed repeatedly.
Electronic signatures generally receive legal recognition under ESIGN and UETA when intent, consent, attribution, and record retention are established. Agency-specific exclusions and filing instructions still control.
A completed affidavit may require notarization, an in-person appearance, or a prescribed submission channel. A signNow signature does not replace those requirements; verify the receiving authority’s instructions.
For sensitive records, signNow lists HIPAA compliance with a BAA requirement, SOC 2 Type II certification, ISO 27001 certification, and TLS 1.2/1.3 and AES-256 protections.
Key performance indicators that demonstrate SignNow's proven track record.
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.