What should a support schedule include?

Include account descriptions, GL codes, ending balances, reconciliations, variance explanations, and direct references to supporting documents so reviewers can verify each line without redoing the accounting work.

Who must sign the schedule?

The preparer and a reviewer (controller or CFO) should sign. For external reliance, a manager-level sign-off provides attribution and is standard practice for auditors and lenders.

Can the schedule be signed electronically?

Yes. Electronic signatures meet legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.

What supporting documents are required?

Attach or reference bank statements, invoices, contracts, depreciation schedules, and reconciliations. Missing evidence is the leading cause of auditor follow-up and increased testing.

How long should final signed schedules be retained?

Follow retention rules applicable to your records: at least 3 years for tax, 6 years for HIPAA-relevant records (45 CFR §164.530(j)), and longer where industry rules apply.

What if balances do not reconcile?

Document the variance, explain causes, and list corrective actions. Unexplained differences should be investigated before final sign-off to avoid audit adjustments.

Electronic Signature
Templates
Other
Balance Sheet Support Schedule

Balance Sheet Support Schedule

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

What the Balance Sheet Support Schedule Is

A Balance Sheet Support Schedule is a detailed, line-by-line accompaniment to a company balance sheet that explains and documents the composition of reported assets, liabilities, and equity. It ties general ledger balances to source records such as bank statements, invoices, contracts, depreciation schedules, and reconciliations. Typical uses include internal close procedures, external audits, lender due diligence, and transaction diligence. The schedule improves traceability by listing account codes, amounts, reconciliations, variance notes, and links or references to supporting documents so reviewers can verify the numbers without re-creating the accounting work.

Why a Support Schedule Matters for Financial Accuracy

A well-prepared schedule clarifies account composition, reduces auditor and lender questions, and documents assumptions used in valuation and cutoffs.

Who Prepares and Who Uses the Schedule

The Balance Sheet Support Schedule is prepared by accounting staff and reviewed by finance managers before distribution.

Corporate accounting and controllers preparing month-end and year-end close deliverables.
Internal and external auditors who require line-item substantiation for testing.
Lenders, investors, and acquirers conducting due diligence or covenant testing.

Step-by-Step: Prepare the Schedule

Follow a consistent sequence to create a complete, verifiable support schedule that ties to source records.

01

Gather records: Collect bank statements, invoices, contracts, depreciation schedules and GL extracts.
02

Map accounts: Assign each balance to the corresponding GL code and explain unusual items.
03

Attach evidence: Link or attach supporting documents and reconciliations for each line.
04

Review and sign: Controller reviews, signs, and timestamps the schedule before distribution.

Where the Schedule Goes and Who Sees It

The schedule passes through internal review, external verification, and long-term retention steps—each with specific routing practices.

Internal routing: Send to controller and CFO for review and approvals.
Audit delivery: Provide a copy and supporting documents to external auditors on request.
Lender submission: Share with lenders or underwriters during covenant testing or diligence.
Records retention: Archive final signed schedules in secure long-term storage.

Configure an Efficient Digital Workflow

Standardize field mappings and routing rules to reduce manual work and speed reviewer access.

Field mapping	Map GL exports to schedule fields automatically.
Preparer role	Assign a preparer role with edit permissions only.
Review step	Add a controller approval step before sign-off.
Evidence attachments	Require PDF or native file attachments for each material line.
Retention tag	Apply a retention metadata tag when final signed copy is archived.

Technical Considerations for eSubmission and Storage

Choose a platform that supports secure file formats, audit logs, and common integrations to minimize manual transfers.

File formats: PDF, DOCX, XLSX
Integrations: Salesforce | NetSuite | Google Workspace
Security: TLS in transit, AES-256 at rest

Security and Compliance Essentials

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

Access control: Role-based permissions and SSO

Audit trail: Timestamps, IP, and action logs

HIPAA readiness: BAA available when required

Retention policy: Configurable legal hold capabilities

Document integrity: Tamper-evident storage and version history

Timing Considerations and Recommended Deadlines

While timing depends on your close cadence and audit cycles, set clear internal deadlines to avoid late submissions and rework.

Monthly close deliverable:

Prepare within 10 business days after month-end close.

Quarterly reporting:

Finalize schedules prior to quarter-end review meetings.

Year-end audit:

Provide requested schedules to auditors within 15 business days.

Lender testing:

Deliver current schedules during covenant testing windows.

Ad hoc requests:

Respond to diligence requests within agreed timelines.

Key Milestones in Preparation and Review

Track milestone stages from initial preparation through final archival to maintain visibility and control.

01

Preparation

Collect source documents and populate schedule fields.

02

Internal review

Controller/editor verifies reconciliations and notes anomalies.

03

External submission

Provide signed schedules to auditors or lenders.

04

Archival

Store signed final copies in secure records management.

Common Preparation Mistakes to Avoid

Omitting direct links or identifiers to supporting documents, making verification slow and error-prone.
Reporting balances that do not reconcile to the general ledger due to timing or classification errors.
Failing to document assumptions, leading reviewers to re-create calculations and question conclusions.
Using inconsistent account naming or currency treatments that cause duplicate entries or misstatements.

Consequences of Inaccurate or Missing Schedules

Audit Adjustments: Material misstatements may trigger restatements.

Loan Covenant Breach: Incorrect balances can cause covenant violations.

Tax Exposure: Misstated assets may affect taxable income.

Delayed Close: Missing schedules prolong audit and reporting timelines.

Regulatory Inquiry: Inaccuracies can prompt regulator reviews.

Reputational Risk: Persistent errors erode stakeholder confidence.

How This Schedule Differs from Similar Documents

Compare common deliverables to choose the right artifact for reconciliation, audit support, or management review.

Criteria	Balance Sheet Support Schedule	Account Reconciliation
Primary purpose	line-item substantiation	gl tie-out
Frequency	as-needed or month-end	periodic (monthly)
Typical preparer	controller or preparer	staff accountant
Audit use	direct evidence	supporting control evidence

eSignature Vendor Comparison for Signatures and eSubmission

Compare basic vendor differences relevant to signing, bulk submissions, and compliance needs; signNow appears first per comparison convention.

	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	Varies by edition	Varies by edition	Varies by edition	Varies by edition
Bulk Send	Yes	Yes	Yes	Yes	Varies by plan
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes (BAA available)	Varies by plan	Varies by plan	No	No
Envelope Cap	No envelope cap	100 envelopes/user/year	Varies by plan	Varies by plan	Varies by plan

Frequently Asked Questions About the Schedule

Answers to common questions about preparation, signatures, e-signing, and retention to reduce review cycles and control exceptions.

Need help? Contact support

What should a support schedule include?
Include account descriptions, GL codes, ending balances, reconciliations, variance explanations, and direct references to supporting documents so reviewers can verify each line without redoing the accounting work.
Who must sign the schedule?
The preparer and a reviewer (controller or CFO) should sign. For external reliance, a manager-level sign-off provides attribution and is standard practice for auditors and lenders.
Can the schedule be signed electronically?
Yes. Electronic signatures meet legal standards under the ESIGN Act (15 U.S.C. ch. 96) and UETA where adopted, provided intent, consent, attribution, and retention requirements are met.
What supporting documents are required?
Attach or reference bank statements, invoices, contracts, depreciation schedules, and reconciliations. Missing evidence is the leading cause of auditor follow-up and increased testing.
How long should final signed schedules be retained?
Follow retention rules applicable to your records: at least 3 years for tax, 6 years for HIPAA-relevant records (45 CFR §164.530(j)), and longer where industry rules apply.
What if balances do not reconcile?
Document the variance, explain causes, and list corrective actions. Unexplained differences should be investigated before final sign-off to avoid audit adjustments.

Explore Templates

Employment Post Job Offer Medical History Questionnaire Employment Agreement Employment Agreement Overseas Employment Agreement Overseas Employment Transportation Agreement Employment Offer and Agreement

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now