Three Types of Financial Statements: What Goes Where in a Financial Model | ModelReef
back-icon Back

Published February 13, 2026 in For Teams

Table of Contents down-arrow
  • Overview
  • Before You Begin
  • Step-by-Step Instructions
  • Tips, Edge Cases & Gotchas
  • Example
  • FAQs
  • Next Steps
Try Model Reef for Free Today
  • Better Financial Models
  • Powered by AI
Start Free 14-day Trial

Three Types of Financial Statements: What Goes Where in a Financial Model

  • Updated February 2026
  • 11โ€“15 minute read
  • How to Build a Financial Model
  • Accounting basics
  • financial statements
  • Forecast modeling

๐Ÿงญ Overview: What This Guide Covers

If your model outputs don’t “feel right,” the cause is often classification – not math. This guide explains the three types of financial statements (P&L, balance sheet, cash flow), what belongs in each, and how to map real accounts into a forecast without creating phantom profit or phantom cash. It’s for finance teams, advisors, and operators building statement-based forecasts for management, lenders, or investors. You’ll learn a repeatable “where it goes” method, plus the most common misplacements (working capital, capex, debt, deferred revenue). For the end-to-end build process, anchor this in how to build a financial model.

๐Ÿงฐ Before You Begin

To classify correctly, start with source truth: your trial balance or general ledger extract, plus the most recent set of financial statements. Confirm your accounting basis (cash vs accrual) and whether you have one entity or multiple entities rolling up. Decide the level of detail you need – too granular early makes modeling slow; too aggregated hides working capital and timing effects.

You’ll also want an agreed mapping logic: which GL accounts feed revenue, COGS, opex, staff costs, tax, working capital, capex, and financing. If you’re working with a team, align on naming conventions so everyone classifies consistently across scenarios and periods. This matters whether you’re using spreadsheets or financial modeling software, because inconsistent mapping makes scenario comparisons unreliable.

Finally, be clear on the outcome: are you preparing a full forecast pack, or are you supporting a 3-statement financial model build where linkage and error checks are the priority? If you’re doing the latter, it helps to understand the structure and failure modes first, then come back to classification with that context. Once you’re ready, you can map accounts with confidence instead of “guess and reconcile.”

๐Ÿ› ๏ธ Step-by-Step Instructions

Step 1: Define or Prepare the Essential Foundation

Create a mapping table that lists every account you plan to model and assigns: (1) statement (P&L, balance sheet, cash flow), (2) category/subcategory, (3) driver (if forecasted), and (4) timing rules (when cash moves vs when expense is recognised). This mapping becomes the backbone of repeatable forecasting.

If you’re importing data, keep your categories consistent with the way you report to stakeholders. For example, “sales commissions” might sit under staff costs internally, but you may prefer it under sales & marketing for management reporting – choose once and document it. A clean mapping approach also makes it easier to reuse the logic across entities and scenarios. If you want a structured method for grouping accounts into model categories so rollups stay stable, follow the category mapping workflow here. Your checkpoint: every account has one clear home.

Step 2: Begin Executing the Core Part of the Process

Classify P&L items by the economic question they answer: “What performance happened in the period?” Revenue, COGS, operating expenses, staff costs, depreciation/amortisation, interest, and tax belong here. The core rule: the P&L is primarily accrual-based, so it should reflect when value is delivered/consumed – not when cash moves.

This matters for planning, budgeting, and forecasting because the P&L is the statement most leaders manage. Keep recurring costs separate from one-offs so your run-rate forecast isn’t polluted. Also, ensure non-cash expenses (depreciation) are explicit, because they affect profit but not cash directly. If you need a reference structure for how P&L lines typically map and what they affect downstream, use this P&L overview. Your checkpoint: EBITDA and net income are interpretable and consistent with your business narrative.

Step 3: Advance to the Next Stage of the Workflow

Now classify balance sheet items by the question: “What do we have and what do we owe at this point?” Assets (cash, AR, inventory, PP&E) and liabilities (AP, accrued expenses, deferred revenue, debt) live here, along with equity. The balance sheet is not “another P&L” – it’s a stock of positions that explains timing gaps between profit and cash.

This step is where forecasting balance sheet discipline separates robust models from fragile ones. For each working capital account, define a driver (DSO, DPO, inventory days) rather than forecasting balances directly. For long-lived assets and debt, use roll-forward schedules. If you want to see how these accounts connect cleanly inside a three-statement model, use the linking explanation here. Your checkpoint: Assets = Liabilities + Equity every period, before building cash flow.

Step 4: Complete a Detailed or Sensitive Portion of the Task

Finally, classify cash flow lines by the question: “What changed cash this period?” The cash flow statement is a movement report, usually split into operating, investing, and financing sections. Operating cash flow reconciles profit to cash (via non-cash add-backs and working capital changes). Investing is capex and asset sales. Financing is debt draws/repayments, equity raises/buybacks, and dividends.

The common trap is mixing accrual events into cash flow lines without timing logic. For example, recording “revenue” as a cash inflow ignores collections timing; that cash belongs in AR changes or receipts schedules. Another trap is mishandling deferred revenue and accruals – these sit on the balance sheet and unwind into the P&L with timing. If you model these items, follow a proven approach so you don’t break statement linkage. Your checkpoint: every cash movement is explainable from the balance sheet and schedules.

Step 5: Finalise, Confirm, or Deploy the Output

With classification complete, run validation that proves the mapping is correct. Start with hard checks: balance sheet balances, cash ties, and retained earnings roll-forward. Then add “reasonableness checks”: margins stay within realistic bounds, working capital ratios don’t jump without a driver change, and capex aligns to the business plan.

Now connect classification to your operating assumptions so the model becomes a decision tool, not a reporting replica. This is where financial analysis software principles help: traceability, clear inputs, and consistent outputs across scenarios. If you’re building in a team, make classifications and drivers visible so reviewers can confirm that the P&L and balance sheet are telling the same story. Apply a standard error-check set so classification mistakes surface immediately rather than at reporting time. Your checkpoint: the model is both accurate and explainable.

โš ๏ธ Tips, Edge Cases & Gotchas

Most “what goes where” errors come from timing confusion. A few high-frequency gotchas: (1) treating loan principal as an expense (it’s financing cash flow; interest is P&L); (2) putting capex in the P&L (capex is investing cash flow + PP&E roll-forward; depreciation is P&L); (3) missing working capital entirely (AR/AP/inventory sit on the balance sheet and drive cash); and (4) confusing deferred revenue with revenue (deferred revenue is a liability until earned).

Edge cases: subscription businesses often have material deferred revenue; project businesses have WIP and retentions; fast-growing businesses see working capital consume cash even when profit rises. Use consistent financial methodologies for classification so these edge cases don’t become ad hoc exceptions.

If you want a concrete blueprint for working capital schedules that tie cleanly inside a 3-statement build, use this working capital guide as your reference point. It reduces rework because you won’t “discover” timing logic late in the build.

๐Ÿงช Example: Quick Illustration

Input – Action – Output example: You invoice a customer $100k in December, payable in 30 days. In December, the P&L shows $100k revenue (accrual). The balance sheet shows AR up $100k. The cash flow statement shows a negative working capital adjustment (cash didn’t arrive yet). In January, when the customer pays, AR decreases and cash increases – cash flow improves, but P&L may show no new revenue from that payment.

Now add a $40k equipment purchase. The P&L does not show a $40k expense; instead, the balance sheet increases PP&E, and cash decreases. Depreciation then flows through the P&L over time.

If you’re importing historicals and want a clean starting point for mapping, an Excel import with structured category assignment can accelerate setup.

โ“ FAQs

Not directly - cash flow reflects cash movements, while revenue and expenses are accrual measures on the P&L. Cash flow starts from net income (or operating profit), then adjusts for non-cash items and balance sheet movements that explain timing differences. That's why a business can be profitable and still run out of cash. The next step is to ensure your model's AR/AP/inventory logic is explicit so the bridge from profit to cash is transparent.

Working capital lives on the balance sheet, but its changes show up in operating cash flow. AR, inventory, and AP are balance sheet accounts; when they move, they explain why cash differs from profit. In practice, you forecast the policies (days) or drivers, then the balances, then the cash impact. If your tooling supports it, treating working capital as a first-class schedule improves reliability and speeds review. Once working capital is structured, cash forecasting stops feeling random.

Depreciation is an expense on the P&L, but it's non-cash, so it's added back in operating cash flow. The cash outflow happens when you buy the asset (capex), which sits in investing cash flow and increases PP&E on the balance sheet. This is one of the most important "what goes where" rules because misplacing it can swing cash outputs dramatically. If you're troubleshooting this kind of mapping issue across many accounts, using financial analysis software workflows can help you trace where values originate and how they roll forward. The next step: separate capex schedules from depreciation schedules.

Use a documented mapping table, lock your category definitions, and enforce review before changes hit the master forecast. In spreadsheets, mapping drift happens when people add "just one more line" without updating rollups. In a platform, governance is easier when integrations and data structures are stable and repeatable. If you're selecting a tool, prioritise deep, reliable data connections and a structured way to manage account mappings across scenarios. Consistent mapping is a process problem first, a tooling problem second - and you can solve both.

๐Ÿš€ Next Steps

With the three types of financial statements mapped cleanly, your next step is to turn classification into a forecasting engine: driver-led P&L, policy-led working capital, and schedules for capex and debt. If you’re using Model Reef, this is where structured inputs and repeatable mappings reduce spreadsheet drift and make scenario updates faster and safer for teams. Keep your mapping table as a living control document, and treat changes as governed decisions, not ad hoc edits.

Start using automated modeling today.

Discover how teams use Model Reef to collaborate, automate, and make faster financial decisions - or start your own free trial to see it in action.

Want to explore more? Browse use cases

Trusted by clients with over US$40bn under management.