Is an electronic decline report legally valid?

Yes. Under the ESIGN Act (15 U.S.C. §7001) and UETA, electronic records and signatures have legal effect for most transactions; ensure exceptions do not apply and that intent, consent, attribution, and retention criteria are met.

When must I preserve audio-video recordings?

Retain session recordings according to state RON rules; many states require multi-year retention and audio-video evidence for RON interactions to support notarization validity and audits.

What if a customer disputes the decline?

Provide the full decline report, audit trail, and evidence; document any remediation steps. Keep communication logs demonstrating timely notification and offered alternatives.

Can the report be amended after submission?

Amendments should be rare and clearly tracked; append a supplemental entry stating the reason for change and preserve the original in the audit trail for chain-of-custody integrity.

Do consumer-facing notices require a disclosure?

Yes. For consumer transactions, comply with ESIGN consumer-consent disclosure requirements, allowing the consumer to receive paper and withdraw consent as described in 15 U.S.C. §7001(c).

How do I fix missing evidence attachments?

Attempt to retrieve original recordings from the RON provider, document retrieval attempts in the report, and escalate to compliance if evidence cannot be recovered.

Electronic Signature
Templates
Finance
Financial RON 95 Decline Report

Financial RON 95 Decline Report

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

Financial RON 95 Decline Report

Report Header

Company Name Service Location / Station ID Station Address

Contact Phone

Prepared By

Report ID: Report Date: Reporting Period: From to

Executive Summary

Decline Summary (RON 95)

Total Prior Period Sales (liters): Total Current Period Sales (liters):

Volume Variance (liters): Percent Change:

Financial Impact

Prior Period Revenue (local currency): Current Period Revenue (local currency):

Revenue Change Amount: Effective Gross Margin Impact:

Primary Cause Codes (select all that apply)

Supply Shortage / Delivery Delay
Pump / Equipment Failure
Price Increase / Competitive Pricing
Competitor Promotion / Market Activity
Regulatory Restriction / Allocation
Payment Processing Declines / Card Declines
Other

If Other, describe

Daily Itemized Sales (Representative Days)

Date	Prior Period (L)	Current Period (L)	Variance (L)	Prior Revenue	Current Revenue	Comments

Adjustments & Calculations

Calculated Subtotal Loss: Estimated Tax Effect:

Inventory Adjustment (liters): Other Adjustments (local currency):

Net Financial Impact (local currency):

Actions Taken / Recommendations

Certification & Legal Notice

I certify under penalty of disciplinary and civil action that the information contained in this Financial RON 95 Decline Report is true, complete and accurate to the best of my knowledge. The signatory acknowledges that intentional misstatement or omission of material facts may result in corrective financial adjustments, disciplinary action, and applicable legal remedies. Supporting documents and transactional records referenced herein are retained at the reporting location and made available to authorized internal audit or regulatory review upon request.

Supporting Documents Attached

Printed Name:

Signature:

Title:

Date:

What the Financial RON 95 Decline Report Is and when it’s used

The Financial RON 95 Decline Report is a standardized record used by financial institutions to document the refusal or failure of a Remote Online Notarization (RON) transaction coded as '95' and the underlying reasons. It captures signer identity checks, authentication results, document metadata, decline reason codes, timestamps, and any communications with the customer. Organizations use this report for internal compliance, regulatory audit trails, dispute resolution, and to provide required consumer notices when an electronic notarization or signature attempt cannot be completed remotely.

Why maintaining a clear decline report matters

A complete Financial RON 95 Decline Report provides consistent evidence for audits, helps meet ESIGN and state RON documentation expectations, and reduces downstream dispute risk by preserving authentication artifacts and communication history.

Who handles and reviews the Financial RON 95 Decline Report

Secondary users include legal counsel, dispute resolution staff, and records retention personnel who access the report for investigations or archival purposes.

Compliance teams reviewing authentication failures and regulatory reporting
Loan or account managers notifying customers and coordinating alternatives
Notary administrators preserving audio-video logs and session metadata for audits

Core sections every professional Financial RON 95 Decline Report should include

A structured report improves consistency and legal defensibility. Include metadata, identity checks, decline reason codes, communications log, evidence attachments, and signatory authorization status.

Metadata

Document identifiers, transaction ID, timestamps, filing channel, and operator or system that initiated the RON session.

Identity Proofing

Record outcomes from KBA, credential analysis, or multi-factor checks including which method failed and any reference numbers.

Decline Reason

Standardized reason code and narrative describing the specific failure (e.g., authentication failure, video quality, ID mismatch).

Communications Log

Time-stamped messages, phone calls, emails, and agent notes showing steps taken to remediate or offer alternatives.

Supporting Evidence

Attachments such as audio-video recordings, screen captures, identity document images, and system logs stored with tamper-evident controls.

Disposition

Final action taken (reschedule, in-person notary, canceled) and any customer acknowledgments or fee adjustments.

Step-by-step: completing the Financial RON 95 Decline Report

Follow these sequential steps to capture all required elements and preserve the audit trail.

01

Open session record: Retrieve the RON session by transaction ID from the notarization platform.
02

Document metadata: Populate document ID, parties, and timestamps.
03

Record decline reason: Enter standardized decline code and a concise narrative.
04

Attach evidence: Include audio-video and identity documents, then save a tamper-evident copy.

How a typical RON decline is captured and routed

A consistent capture-to-notify flow ensures compliance and clear next steps for customers and staff.

Capture: Platform records failure and logs authentication artifacts.
Document: Complete the Financial RON 95 Decline Report with code and evidence.
Review: Compliance or notarization team reviews for remedial action.
Notify: Customer receives required notice and options for next steps.

Recommended digital workflow settings for consistent reports

Configure your RON and records platform so required fields and attachments are enforced at decline.

Field	Configuration
Transaction ID binding	Auto-populate from session logs to ensure one-to-one linkage.
Required attachments	Make audio-video and ID scans mandatory on decline events.
Reason code list	Use a controlled dropdown to prevent free-text variance.
Retention tag	Attach legal retention metadata at creation.

Technical capabilities to support secure RON decline reporting

Verify integrations with your records management and legal hold systems so the Financial RON 95 Decline Report is preserved and discoverable during audits.

Recording retention: Store audio-video securely for the mandated period.
Tamper evidence: Apply checksums or digital seals on exported reports.
Audit trail: Record IP, timestamps, and user actions.

Typical timelines and notification expectations

Time-sensitive handling of declines reduces regulatory exposure and supports customer service obligations.

Immediate logging:

Log the decline in the system at the time it occurs, including timestamps.

Customer notice window:

Notify the customer promptly; industry practice is within 24–72 hours of decline.

Internal review timeframe:

Complete compliance review within 5 business days to determine remedial steps.

Appeal or rescind period:

Document internal deadlines for reattempts or escalation typically 7–14 days.

Record retention start:

Retention begins on the decline date; legal hold may extend retention further.

Key milestones from decline to final disposition

Track these numbered milestones to move a decline from occurrence to resolution while preserving evidence.

01

Report Created

Complete initial report and attach evidence immediately.

02

Compliance Review

Assess cause and regulatory implications within business days.

03

Customer Notification

Send required notices and options for next steps.

04

Disposition Recorded

Record final outcome and retention metadata.

Common preparation and documentation pitfalls to avoid

Incomplete evidence attachments—forgetting to include audio-video or ID images creates gaps in the audit trail and weakens defensibility.
Using free-text decline reasons—this hinders consistent analytics and regulatory reporting; use standardized codes instead.
Mismatched transaction IDs—if the report doesn’t match session logs, evidence cannot be correlated during review.
Delaying customer notification—late notices can raise consumer-protection concerns and complicate remediation.

Potential penalties and operational risks from deficient reports

Regulatory fines: Enforcement actions for poor records may result in monetary penalties.

Consumer disputes: Incomplete reports increase exposure to contested transactions.

Business disruption: Operational delays and remediation costs rise without clear process.

Reputational harm: Public complaints can damage customer trust and market standing.

Legal evidence gaps: Missing audio-video or chain-of-custody compromises admissibility.

Compliance breach: Failure to retain records can violate industry rules or state statutes.

Security and compliance controls to include with the report

Encryption: AES-256 at rest; TLS 1.2/1.3 in transit

Audit Trail: Immutable logs capturing IP, timestamp, and signer actions

Certifications: SOC 2 Type II and ISO 27001 where available

HIPAA Safeguard: BAA required for protected health information

21 CFR Part 11: Controls for FDA-regulated records and signatures

Access Controls: Role-based permissions and two-factor admin access

Common eSignature vendor comparison for handling decline reporting and eEvidence

Compare starting price, trial availability, bulk send, audit trail, HIPAA compliance, and envelope caps across vendors to assess fit for Financial RON 95 Decline Report workflows.

	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	7-day free trial	Verify with vendor	Verify with vendor	Verify with vendor	Verify with vendor
Bulk Send	Yes	Yes	Yes	Yes	Verify with vendor
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

Frequently asked questions and troubleshooting for the Financial RON 95 Decline Report

Answers to common legal and operational questions when a RON session is declined and a report must be produced.

Need help? Contact support

Is an electronic decline report legally valid?
Yes. Under the ESIGN Act (15 U.S.C. §7001) and UETA, electronic records and signatures have legal effect for most transactions; ensure exceptions do not apply and that intent, consent, attribution, and retention criteria are met.
When must I preserve audio-video recordings?
Retain session recordings according to state RON rules; many states require multi-year retention and audio-video evidence for RON interactions to support notarization validity and audits.
What if a customer disputes the decline?
Provide the full decline report, audit trail, and evidence; document any remediation steps. Keep communication logs demonstrating timely notification and offered alternatives.
Can the report be amended after submission?
Amendments should be rare and clearly tracked; append a supplemental entry stating the reason for change and preserve the original in the audit trail for chain-of-custody integrity.
Do consumer-facing notices require a disclosure?
Yes. For consumer transactions, comply with ESIGN consumer-consent disclosure requirements, allowing the consumer to receive paper and withdraw consent as described in 15 U.S.C. §7001(c).
How do I fix missing evidence attachments?
Attempt to retrieve original recordings from the RON provider, document retrieval attempts in the report, and escalate to compliance if evidence cannot be recovered.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now