Balance-sheet reconciliation and financial control

From Month-End Task to Controlled Financial Assurance

Closing the General Ledger is an important milestone, but it does not by itself prove that every balance-sheet balance is correct, complete and properly supported.

A bank account may agree only after outstanding deposits and unpresented payments are explained. A receivables control account may differ from its customer ageing because of a manual journal. An accrual may remain on the balance sheet after the related supplier invoice has arrived. A prepayment may be mathematically correct but unsupported by the original contract or an up-to-date amortisation schedule.

These are not simply bookkeeping issues. They are questions of financial control:

• Does the balance exist?
• Is it complete and accurately valued?
• Does it belong to the business?
• Is it recorded in the correct accounting period?
• Can a reviewer understand and verify it without rebuilding the analysis?

RavenLedger's Balance Sheet Review workspace brings those questions into a structured, evidence-driven process. It gives finance teams a dedicated place to configure review requirements, analyse balances, maintain supporting schedules, investigate exceptions, attach evidence, route work for approval and monitor completion.

The result is not another spreadsheet folder. It is a controlled reconciliation workflow connected to the accounting environment while remaining independent from journal posting and General Ledger period closure.

Why traditional balance-sheet reconciliations become difficult

Many finance teams still manage reconciliations through disconnected spreadsheets, shared folders and email approvals. The individual documents may be sound, but the overall process often develops weaknesses:

• It is difficult to know which accounts require review and which are overdue.
• Different preparers use different formats and definitions.
• Supporting documents are stored separately from the reconciliation.
• Review comments and approval decisions are lost in email threads.
• A reconciliation can remain approved even though the underlying balance later changes.
• Management reporting depends on manually consolidating multiple trackers.
• Prior-period items are copied forward without a clear audit trail.

These weaknesses become more visible as an organisation adds locations, entities, users or transaction volume. A process that worked for ten accounts and one preparer may not remain reliable across hundreds of accounts and several reviewers.

RavenLedger addresses this by treating balance-sheet review as an ongoing control process rather than a collection of files.

One workspace for the full review lifecycle

The Balance Sheet Review workspace is organised around four practical areas:

1. Dashboard — a management view of review status, workload and items requiring attention.
2. Reconciliations — the working list for preparing, investigating, submitting and approving individual account reviews.
3. Account Review Setup — the control centre for deciding which balance-sheet accounts are reviewed, how frequently they are reviewed and what process applies.
4. Templates — reusable structures that determine how different types of accounts should be supported.

This separation matters. Configuration is managed deliberately, day-to-day review work remains focused, and reporting does not depend on opening each reconciliation individually.

Risk-based setup instead of a one-size-fits-all checklist

Not every balance-sheet account carries the same risk or needs the same review frequency. A high-volume bank account may require monthly reconciliation, while a low-activity long-term deposit may only need quarterly review.

RavenLedger allows review frequency to be configured by account using monthly, quarterly or annual cycles. Finance teams can also define the appropriate first or historical review period when bringing an account into the process.

The system uses conservative defaults: an account is not automatically made mandatory, and automatic approval is not switched on without a deliberate decision. This allows the finance team to introduce the control according to its own risk assessment and governance model.

Purpose-built templates for different accounting questions

A bank reconciliation is not performed in the same way as an accrual review. RavenLedger therefore provides specialised templates rather than forcing every account into a generic worksheet.

The available template families include:

• General Account Support
• Receivables
• Payables
• Accruals
• Prepayments
• Bank
• Retained Earnings and Equity

Templates can be suggested using existing account mappings and descriptions, but the finance team remains in control of the final selection. Future reviews can use an updated template without silently reinterpreting the structure of completed work.

This is important for auditability. A review should preserve the accounting logic that applied when it was prepared, even if the organisation later improves its standard template.

From ledger balance to explainable support

At the centre of every review is a simple question: What makes up this General Ledger balance at the reporting date?

RavenLedger separates the ledger balance from its supporting analysis. Depending on the account and the reliability of its source attribution, support may come from native receivables or payables information, structured schedules, manual lines, documents or a combination of these.

Preparers can record descriptions, signed amounts, explanations, timing adjustments, exceptions and linked evidence. This makes the reconciliation more useful than a single unexplained difference number.

Where system attribution is not sufficiently reliable, the workspace supports a complete manual fallback. It does not create a false impression of precision or combine system and manual support in a way that double-counts the same balance.

Example: explaining a receivables control account

Assume the receivables control account has a General Ledger balance of 450,000 at month-end. The validated customer ageing totals 443,000.

The preparer identifies a 7,000 manual journal posted directly to the control account. In the review, the preparer can retain the receivables support of 443,000, add the 7,000 reconciling line, explain why the journal was posted, attach the journal support and flag it as an exception if direct posting is contrary to policy.

The review now explains the full 450,000 balance. More importantly, it distinguishes normal subledger support from an unusual item that management may wish to prevent in future.

Structured schedules without losing control

Some balances require detailed schedules containing many rows. RavenLedger supports manual schedule entry as well as controlled bulk imports using spreadsheet or CSV templates.

The import process follows a review-before-commit approach: users download the relevant template, populate the schedule, validate the file and review the result before committing it. Imported schedules append to the review and retain their source file as evidence.

The safeguards are designed to prevent common spreadsheet risks, including stale submissions, duplicate imports, partial invalid saves and unintended interpretation of formulas or macros.

Example: reviewing an accrual

Suppose the legal-fee accrual account carries a balance of 85,000. The supporting schedule contains 40,000 for work completed by Firm A but not yet invoiced, 25,000 for a regulatory matter estimated by internal legal counsel and 20,000 brought forward from the previous month.

During review, the preparer discovers that the supplier invoice for the final 20,000 was received and posted before month-end. That item should no longer remain in the accrual schedule.

The preparer updates the schedule, records the exception and explains the required correction. The reviewer can see the calculation, supporting correspondence and treatment of the old item in one place.

Evidence that supports—not replaces—the accounting analysis

Documents are essential, but uploading a file does not by itself reconcile an account. RavenLedger deliberately separates documentary evidence from the amount supported.

Users can attach multiple supporting files and link documents to relevant schedule lines. Evidence can be retained when it is superseded, preserving the historical record rather than overwriting the original support.

This allows the review to answer two different questions:

1. What accounting analysis explains the balance?
2. What evidence allows another person to verify that analysis?

Example: reviewing a prepayment

A business pays 120,000 for a 12-month insurance policy beginning on 1 January. At the end of February, cumulative insurance expense should be 20,000 and the remaining prepayment should be 100,000.

The review can include the policy period, original amount, recognition method, calculated balance and relevant timing information. The signed insurance agreement and payment evidence can be attached to the same review.

If the General Ledger balance is 110,000, the reconciliation clearly exposes a 10,000 difference for investigation. The document proves the policy exists; the schedule proves how much should remain on the balance sheet.

A controlled Draft-to-Approval workflow

Each review follows a clear status path:

The preparer develops the analysis in Draft, resolves validation issues and submits the review when it is complete. The approver then evaluates the balance, support, evidence, explanations and open exceptions before approving it.

Submitted or approved reviews cannot simply be reworked without control. They must be returned to Draft with a reason, preserving the prior review and approval history.

Tenant administrators can use a separately controlled override where permitted, but the action requires a reason and acknowledgement and remains part of the audit trail. Administrative authority does not remove the need for the review to balance or for required evidence and source checks to be satisfied.

Protection when the underlying accounting data changes

A major weakness in file-based reconciliation processes is that the approved spreadsheet can remain unchanged even after someone posts another transaction to the account.

RavenLedger tracks the source data used for the review. Relevant changes can reopen a Submitted or Approved review to Draft while retaining the previous approval and supporting evidence.

This creates an important distinction between the reporting cutoff date, when supporting information was captured, when the source was last checked and the current revision of the review.

Example: a late bank posting

A bank reconciliation is approved with a General Ledger balance of 1,250,000. Later, a valid backdated bank charge of 5,000 is posted into the same accounting period.

In a disconnected spreadsheet process, the approved reconciliation may still show the old balance. Within the RavenLedger workflow, the relevant source change can reopen the review, retaining the earlier approval history but requiring the revised balance and support to be assessed.

That is a stronger control than merely recording who last edited a spreadsheet.

Exceptions and timing items remain visible

Not every difference is an error. Some differences are legitimate timing items; others are unresolved exceptions requiring corrective action.

RavenLedger allows these items to be identified and explained separately. Unresolved exceptions do not silently increase the supported balance and can block approval. Resolved timing items remain part of the historical analysis without continuing to distort the current reconciliation.

This helps finance teams focus on the nature of a difference, not just whether a spreadsheet happens to add to zero.

Management visibility through the Reporting Center

The workspace includes six dedicated reports in RavenLedger's existing Reporting Center:

1. Balance Sheet Reconciliation Register — a consolidated view of reviews, balances, differences and status.
2. Balance Sheet Review Audit History — workflow and change history for governance and audit support.
3. Completion and Account Coverage — expected, completed and missing reviews based on the current setup.
4. Open Reconciling Items and Ageing — unresolved items organised by age and status.
5. Approval Controls and Reopened Reviews — approval activity, exceptions and reviews reopened after source changes.
6. Supporting Schedule and Evidence Detail — detailed schedule lines and their associated evidence.

The distinction between dashboard completion and coverage reporting is useful. A dashboard shows progress on reviews that exist; the coverage report also highlights reviews that should exist under the current setup but have not yet been created or completed.

Reports use saved review data and do not post journals, refresh sources or modify the underlying accounting records. Exports run through the existing background reporting process so users can continue working while larger files are prepared.

Automatic approval—only where the control supports it

RavenLedger includes an optional automatic-approval capability, but it is deliberately conservative.

Automatic approval is not a blanket shortcut for unchanged accounts. It requires an eligible configuration and a valid prior approval, with no balance change or posted activity, no unresolved or overdue items and no requirement for fresh evidence. The General Account Support template is the initial eligible use case.

This allows low-risk, genuinely unchanged accounts to be handled efficiently without weakening controls over balances that require fresh judgement or documentation.

Independent from General Ledger posting and period closure

The Balance Sheet Review workspace is a financial-control layer. Saving a schedule, attaching evidence, submitting a review or approving it does not post a journal or alter a General Ledger balance.

The General Ledger close process also remains independent. An incomplete review does not silently manipulate or block accounting balances. Organisations can govern their close and reconciliation timetables according to policy while retaining visibility of incomplete or overdue review work.

This separation is fundamental: the workspace explains and governs accounting balances; it does not change those balances to make a reconciliation appear correct.

What this means for finance teams

• Preparers gain consistent templates, clearer requirements and one place for schedules, explanations and evidence.
• Reviewers gain a structured view of the balance, support, exceptions, revisions and approval history.
• Financial controllers gain coverage, overdue-item and reopened-review visibility across the company.
• Auditors gain a traceable record of what was reviewed, what evidence was used, who approved it and whether the underlying source changed afterward.
• Management gains greater confidence that reported balance-sheet positions are supported—not simply carried forward from the previous month.

A practical month-end operating model

1. Define the review population based on account risk, materiality and activity.
2. Set the frequency and template appropriate to each account.
3. Prepare the period review using validated source information and structured schedules.
4. Investigate differences and classify timing items or exceptions.
5. Attach and link evidence that verifies the accounting analysis.
6. Submit and approve through the controlled workflow.
7. Monitor coverage and ageing through dashboards and Reporting Center reports.

This turns balance-sheet review from an informal month-end task into a sustainable control environment.

Better reconciliations create better financial decisions

A balance sheet is more than a list of closing balances. It represents cash, obligations, customer amounts, supplier liabilities, estimates, rights and accumulated business decisions.

The quality of those balances depends on the quality of the review behind them.

RavenLedger's Balance Sheet Review workspace helps organisations move from scattered spreadsheets and email approvals to a connected process built around accountability, evidence and financial discipline. It supports the people preparing the reconciliations, strengthens the work of reviewers and gives leadership a clearer view of financial-control performance.

The goal is straightforward: every material balance should be understood, supported, reviewed and ready to withstand scrutiny.