Skip to main content

Financial Statement Bridge Case

Business Scenario​

The finance team needs to explain how operating activity, control accounts, finance journals, and year-end close produce the reported statements. Process pages already explain where transactions begin. This case starts later. It asks whether the posted ledger ties cleanly into the trial balance, whether major control accounts reconcile to source activity, and whether annual net income closes into retained earnings the way it should.

Management and audit both care about the same question. If the statement bridge breaks, where does it break first? A clean answer must separate operating history from finance presentation logic. It must also show how a statement-level variance can be narrowed into source-level evidence instead of staying trapped inside summary totals.

Your job is to build that bridge from the ledger outward, then follow one variance path all the way into revenue cutoff detail.

The Problem to Solve​

You need to prove how posted operational and finance-controlled activity builds the trial balance, which control accounts can be reconciled from source activity, how year-end close changes presentation without changing operating history, how annual net income ties into retained earnings, and how a statement-level variance can be narrowed into annual net-revenue and cutoff evidence.

What You Need to Develop​

  • A statement-level bridge from ledger activity into reported balances.
  • A control-account explanation grounded in operational source documents.
  • A clear separation of recurring or manual journals from close entries.
  • An annual net-income to retained-earnings explanation.
  • One drill-down path from statement variance into revenue cutoff evidence.

Before You Start​

Step-by-Step Walkthrough​

Step 1. Define the statement scaffold from the trial balance​

Start with the posted ledger structure. Before you reconcile anything, you need to see the period-by-period account scaffold that supports the statements and where the largest balances already sit.

What we are trying to achieve

Establish the posted trial-balance structure by fiscal period, account type, and account subtype.

Why this step changes the diagnosis

This step gives you the statement frame. Without it, later reconciliation and close analysis will not have a stable ledger baseline.

Suggested query

Trial Balance by Period

Use this first to build the ledger-level statement scaffold by fiscal period and account classification.

What this query does

It summarizes posted GLEntry activity by fiscal year, fiscal period, and non-header account.

How it works

The query joins GLEntry to Account, groups by period and account attributes, and returns debit, credit, and net debit-less-credit balances for each active account.

What to look for in the result

  • the main asset, liability, equity, revenue, and expense categories
  • the accounts carrying the largest balances by period
  • whether the ledger structure already suggests where major statement movement sits
  • which control-account families deserve deeper reconciliation

Step 2. Reconcile key control accounts back to operational source activity​

Once the trial balance is clear, test whether the major control accounts can be supported by source logic.

What we are trying to achieve

Prove that major control-account balances can be tied back to expected subledger and operational activity.

Why this step changes the diagnosis

Statement trust starts with control-account trust. If a control account does not reconcile, the statement bridge is already under pressure before close logic enters the discussion.

Suggested query

Control Account Reconciliation

Use this to compare key control-account balances with expected source-derived balances.

What this query does

It compares expected source-driven balances with actual posted balances for major control areas such as AR, AP, GRNI, inventory, customer deposits, sales tax payable, and sales returns.

How it works

The query builds expected balances from operational tables, builds actual balances from non-JournalEntry GL rows, and then compares the two at the control-area level.

What to look for in the result

  • control areas with the smallest and largest differences
  • whether the mismatch sits in an operational account or a finance-controlled account
  • which control area is easiest to support from process evidence
  • where you would need process-specific follow-up from the process pages or posting reference

Step 3. Separate recurring journals, finance-controlled activity, and close-cycle volume​

Now move from control accounts to finance activity. The ledger carries both operating history and finance-controlled journals, and those layers have to stay separate if the statement bridge is going to hold.

What we are trying to achieve

Show how finance-controlled journal activity differs from year-end close and how close entries affect retained earnings presentation.

Why this step changes the diagnosis

Students often mix recurring journals with close entries. That makes it hard to explain why reported balances change while the underlying operating history stays the same.

Suggested query

Journal and Close Cycle Review

Use this first to measure journal-entry volume by posting month and entry type.

Retained Earnings and Close Entry Impact

Use this follow-through query to separate pre-close P&L activity from retained-earnings close impact.

What this query does

The first query summarizes journal-entry activity by entry type and month. The second separates raw P&L activity from year-end close impact on retained earnings.

How it works

The journal review reads JournalEntry directly and groups volume by posting month and EntryType. The retained-earnings query filters close-step journal logic through GLEntry, Account, and JournalEntry to compare pre-close net income, statement net income, and retained-earnings close impact.

What to look for in the result

  • recurring journal families versus year-end close volume
  • whether close activity is concentrated where expected
  • whether pre-close income and retained-earnings close already appear aligned
  • where finance presentation logic starts changing the statement view

Step 4. Tie annual net income into retained earnings and test the close​

This is the core statement-bridge step. You are now validating the annual close itself rather than only describing the ledger.

What we are trying to achieve

Prove that annual net income, close entries, retained earnings, and the post-close statement state line up correctly.

Why this step changes the diagnosis

This is the decisive statement test. If annual net income does not tie into retained earnings or if P&L accounts leak after close, the financial-statement bridge is incomplete.

Suggested query

Annual Income to Equity Bridge

Use this first to reconcile annual net income, retained-earnings close, and the annual balance-sheet residual.

Post Close Profit and Loss Leakage Review

Use this follow-through query to identify revenue, expense, or income-summary balances that remain after close.

What this query does

The first query bridges annual income-statement net income into retained earnings and the year-end balance-sheet presentation. The second flags revenue, expense, or income-summary accounts that still carry a balance after close.

How it works

The income-to-equity bridge computes pre-close income, statement income, retained-earnings close amounts, and balance-sheet residual logic by closed fiscal year. The leakage review scans closed years for non-zero ending balances in P&L and income-summary accounts.

What to look for in the result

  • whether annual net income ties into retained earnings cleanly
  • whether the balance sheet still carries residual current-year earnings after close
  • whether any P&L or income-summary accounts leak past close
  • whether a problem looks like close-process logic or earlier posting logic

Step 5. Drill from statement variance into annual net revenue and cutoff exceptions​

Finish the case by taking one statement-level variance path into source-level evidence. Revenue is the cleanest drill-down path because the repo already provides a summary-and-trace pair that forces you to decide when summary evidence is enough and when line-level proof is required.

What we are trying to achieve

Show how a statement-level variance can be narrowed from annual net-revenue mismatch into invoice-level cutoff evidence.

Why this step changes the diagnosis

A statement bridge is only complete when it ends in source-level proof. Summary reconciliation alone does not show whether the problem sits in statement logic, posting logic, or source timing.

Suggested query

Annual Net Revenue Bridge

Use this first to reconcile operational net revenue, pre-close GL net revenue, and annual income-statement net revenue.

Invoice Revenue Cutoff Exception Summary

Use this summary to isolate invoice-level revenue cutoff exceptions that affect annual reconciliation.

Invoice Revenue Cutoff Exception Trace

Use this trace when you need line-level order, shipment, invoice, and revenue-GL evidence for the cutoff exceptions.

What this query does

The first query reconciles annual net revenue from operational source documents into pre-close GL and the annual income statement. The second narrows the problem to invoice-level exceptions. The third traces those exceptions down to invoice lines and related operating-revenue GL rows.

How it works

The annual bridge compares invoice-line and credit-memo totals with pre-close revenue GL and the income-statement view. The cutoff summary identifies invoice headers where invoice year, shipment timing, or revenue GL fiscal year diverge. The trace query expands those exception invoices into detailed order, shipment, invoice-line, and GL evidence.

What to look for in the result

  • whether operational net revenue ties to pre-close GL
  • whether the remaining variance is summary-level or invoice-specific
  • invoices whose revenue GL fiscal year differs from the invoice year
  • whether the root cause is a seeded timing anomaly, a posting defect, or a broader statement-query issue

Required Student Output​

Submit a short case memo or notebook note with these four artifacts:

  • Evidence summary: identify the key result rows, metrics, timing patterns, or exception families that changed your diagnosis.
  • Accounting or business interpretation: explain what the evidence means for the process, accounting treatment, managerial decision, or control risk.
  • Database explanation: name the source tables, row grain, join keys, or trace path that make the evidence defensible.
  • Management or audit conclusion: state which driver, document path, or exception family should be followed up first and why.

Optional Excel Follow-Through​

  1. Build a period-by-period trial-balance pivot by FiscalYear, FiscalPeriod, AccountType, and AccountSubType.
  2. Add a control-account support tab that compares source-derived expectations with posted balances.
  3. Add a journal-and-close tab that separates recurring or manual finance activity from retained-earnings close impact.
  4. Build one annual-close tab that compares pre-close income, retained-earnings close, and post-close leakage.
  5. Finish with one narrow revenue drill-down tab for annual net revenue and cutoff exceptions instead of turning the workbook into a broad process workbook.

Wrap-Up Questions​

  • Accounting/process: Where does the statement bridge break first: control-account support, finance presentation, annual close, or source timing?
  • Database/source evidence: Which account, journal, retained-earnings, invoice, or GL trace path proves the break?
  • Analytics judgment: Which bridge issue changes management confidence in the statements most?
  • Escalation/next step: When should you stop at summary evidence, and when should you open the line-level cutoff trace?

Next Steps​

Notice a mistake?Report an error on this page