Can I use an electronic signature on a recon report?

Yes. Electronic signatures are legally valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention are demonstrated. Ensure consumer disclosures where required and retain a reproducible record.

What level of authentication is recommended?

Use at least email verification plus account access controls for internal approvals. For higher‑risk approvals consider two‑factor or advanced signer authentication available on enterprise eSignature plans.

How do I correct a signed recon report?

Create a new corrected version, document the reason for correction, reference the original file, and obtain signatures from the original approvers to maintain an auditable trail of amendments.

Do I need a BAA for healthcare-related recons?

Yes — if the report contains protected health information, execute a Business Associate Agreement with the eSignature vendor and use HIPAA‑compliant workflows and storage.

Can I bulk send recon reports for multiple approvers?

Bulk send streamlines distribution for high-volume workflows; select a plan that includes bulk send capability if sending many individualized recon packages in one operation.

What documentation do auditors typically request?

Auditors commonly request the recon summary, line‑item workpapers, supporting source documents, approval timestamps, and change history. Maintain these artifacts for the retention period required by applicable regulations.

Electronic Signature
Templates
Finance
Financial Accounts Recon Report

Financial Accounts Recon Report

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

FINANCIAL ACCOUNTS RECON REPORT

Entity and Report Identification

Company Name Business Unit / Department

Report Period: From through .

Account Name Account Number / GL Code

Statement Date: — Statement Ending Balance: — GL Ending Balance:

Prepared By

Prepared Date: Contact / Ext:

Reconciliation Details

Enter all reconciling items and adjustments identified between the general ledger and statement. Each listed item must be supported by source documentation and cross-referenced in the supporting schedule.

#	Date	Description	Reference	Amount	Adjusting Entry
1
2
3
4
5
6
7
8

Subtotal of Reconciling Items Outstanding Checks (Total) Deposits in Transit (Total) Adjustments Recorded in GL (Total)

Summary and Variance

Reconciled Balance (per statement, adjusted): Unreconciled Difference:

Narrative Explanation of Unreconciled Items and Required Actions

Supporting Documentation & Controls

Supporting documents attached (check if all items have source documentation).

Adjusting journal entries required have been posted to the general ledger.

Prior-period reconciling items identified and documented.

Notes / Terms & Conditions

Certification

I certify that this reconciliation has been prepared in accordance with the organization's accounting policies and that the items listed are accurate to the best of my knowledge. All reconciling items are supported by source documentation which will be retained in accordance with record retention policy. Any adjustments recorded to the general ledger are authorized and referenced.

Reviewer acknowledges that the reconciliation has been reviewed for completeness, that supporting documentation is adequate, and that exceptions have been escalated in accordance with escalation procedures. Approval indicates reviewer acceptance of the reconciliation status and required follow-up actions.

Preparer Name:

By:

Date:

Reviewer Name:

By:

Date:

What the Financial Accounts Recon Report Is

A Financial Accounts Recon Report is a structured reconciliation document that compares ledger balances, bank statements, and subledger details to identify variances, timing differences, and posting errors. It documents adjustments, outstanding items, and approved corrections, and provides an auditable trail for month‑end close, internal controls testing, and external audit support. The report typically includes account identifiers, opening and closing balances, recon items by category, explanations for differences, and preparer and reviewer sign-offs to establish accountability and traceability.

Why the Financial Accounts Recon Report Matters

Consistent recon reporting reduces misstatements, supports accurate financial close, and documents controls for auditors and regulators. It helps detect fraud, ensures correct tax and regulatory filings, and provides a single source of truth for accounts payable, receivable, cash and investment reconciliations.

Typical Teams and Roles That Prepare or Review This Report

Finance, accounting, and internal audit teams usually prepare and review Financial Accounts Recon Reports as part of the close process and ongoing control testing.

Accounts payable and receivable teams reconcile vendor and customer ledgers to cash and subledger balances.
Treasury and cash management reconcile bank statements, investments, and intercompany cash movements.
Internal audit and external auditors use reconciliations to test control effectiveness and confirm balances.

External auditors, controllers, and regulatory examiners rely on reconciliations to validate balances; legal and tax teams consult recon reports when assessing exposures or preparing disclosures.

Who Signs and Approves the Recon Report

Controller

The Controller typically approves the final reconciliation package, certifies accuracy for financial statements, and signs to attest that unresolved items have been properly disclosed or scheduled for correction.

Staff Accountant

Staff accountants prepare detailed recon workpapers, document recon items and supporting evidence, and include preparer name, date, and contact information to support reviewer follow-up and audit sampling.

Core Sections a Professional Recon Report Should Include

A clear structure improves reviewability: separate summary, detailed line‑item recon, supporting evidence, variance explanations, adjustment entries, and sign‑off records to streamline approvals and audits.

Executive Summary

Concise overview of net recon variance, material exceptions, and status of outstanding items to highlight risks for management and auditors.

Account Detail

Line‑by‑line comparison between ledger and source statements with running totals, recon item IDs, and references to supporting documents for traceability.

Outstanding Items

List of uncleared checks, deposits in transit, or unresolved intercompany transfers with aging and proposed resolution dates.

Adjusting Entries

Proposed journal entries needed to correct ledger balances, including account codes, amounts, and authorization status.

Supporting Attachments

Bank statements, invoices, remittance advices, and system extracts attached or linked to each recon line for audit evidence.

Signatures & Audit Trail

Preparer and reviewer names, dates, electronic signature timestamps, and change history to demonstrate review and approval.

Required Information and Metadata to Record

Report Title: Document name and period

Period End: MM/DD/YYYY date

Account Identifier: GL code or account name

Preparer: Name and contact

Reviewer: Name and approval date

Audit Trail: Timestamps and change log

Step‑by‑Step: Preparing a Financial Accounts Recon Report

Follow a consistent sequence from data extraction to review to ensure each recon is complete, supported, and approved in the close cycle.

01

1. Extract Data: Export GL and bank statements for the period.
02

2. Match Transactions: Auto‑match by reference, then flag exceptions.
03

3. Investigate Variances: Document cause and required adjustments.
04

4. Review & Sign: Reviewer validates, then signs and timestamps.

How to Configure an Online Recon Workflow

Set up consistent automation and approval routing to reduce manual effort and speed month‑end close.

Field	Configuration
Data Source	Connect GL export and bank feeds
Matching Rules	Auto‑match on amount and reference
Approval Path	Preparer → Supervisor → Controller
Notifications	Email/SMS alerts for exceptions

Where to Send or File the Completed Report

Determine official storage and distribution locations to meet audit, regulatory, and internal control requirements.

Accounting Repository: Central document repository for financial records
Internal Audit: Upload to audit workpaper library for testing
External Auditor: Provide via secure link or portal
Tax & Legal: Share supporting recon for tax positions

Distribution and eSubmission Options

Ensure the chosen method supports retention policies, reproducible audit trails, and any required regulatory protections.

Secure Cloud: Controlled access with audit logs
Signed PDF: Embed eSignature and timestamp
Direct Portal: Encrypted upload to auditor portal

Typical Timing and Deadlines to Respect

Recon schedules align to the close calendar, external filing deadlines, and internal control review cycles.

Monthly Close:

Complete recons within 5–10 business days after month end

Quarterly Review:

Controller sign‑off for material accounts each quarter

Year‑End Audit:

All recons finalized and evidence provided to auditors

Tax Filing Support:

Maintain recons to support annual tax positions

Exception Resolution:

Resolve outstanding items within reporting period plus 30 days

Common Mistakes to Avoid

Using inconsistent account naming or GL codes that prevent automated matching and create manual reconciliation overhead.
Failing to attach primary evidence (bank statements, invoices) so auditors cannot verify recon adjustments or items.
Posting adjustments without appropriate authorization or documentation, increasing the risk of control deficiencies.
Neglecting to clear recon items promptly, which inflates suspense balances and masks operational issues.

Penalties and Risks from Incorrect Reconciliations

Tax Exposure: IRC §6721 penalties

Audit Findings: External audit adjustments possible

Regulatory Risk: Potential regulator enforcement

Financial Misstatement: Material misstatement of statements

Operational Loss: Unidentified fraud losses

Control Weakness: Internal control deficiency

eSignature Vendor Pricing Comparison for Recon Report Workflows

Compare common pricing and capability dimensions for electronic signing when distributing or approving Financial Accounts Recon Reports; signNow is listed first per vendor ordering rules.

	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, no card required	Varies by plan	Varies by plan	Varies by plan	Varies by plan
Bulk Send	Yes	Yes	Yes	Yes	Varies by plan
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

FAQs and Troubleshooting for Recon Reports

Answers to common questions about preparing, signing, submitting, and retaining Financial Accounts Recon Reports, including eSigning considerations and audit readiness.

Need help? Contact support

Can I use an electronic signature on a recon report?
Yes. Electronic signatures are legally valid under the ESIGN Act (15 U.S.C. ch. 96) and UETA in most states when intent, consent, attribution, and retention are demonstrated. Ensure consumer disclosures where required and retain a reproducible record.
What level of authentication is recommended?
Use at least email verification plus account access controls for internal approvals. For higher‑risk approvals consider two‑factor or advanced signer authentication available on enterprise eSignature plans.
How do I correct a signed recon report?
Create a new corrected version, document the reason for correction, reference the original file, and obtain signatures from the original approvers to maintain an auditable trail of amendments.
Do I need a BAA for healthcare-related recons?
Yes — if the report contains protected health information, execute a Business Associate Agreement with the eSignature vendor and use HIPAA‑compliant workflows and storage.
Can I bulk send recon reports for multiple approvers?
Bulk send streamlines distribution for high-volume workflows; select a plan that includes bulk send capability if sending many individualized recon packages in one operation.
What documentation do auditors typically request?
Auditors commonly request the recon summary, line‑item workpapers, supporting source documents, approval timestamps, and change history. Maintain these artifacts for the retention period required by applicable regulations.

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now