Yes, FP&A (financial planning and analysis) software can support a three-statement model, linking the income statement, balance sheet and cash flow statement so a change in one flows through the others. The software handles actuals, mappings and refreshes. The finance team still designs the drivers, such as collection days, capital expenditure (capex) timing and debt terms, because those are business judgments the ledger cannot supply.
Can FP&A software forecast the balance sheet, not just the P&L?
Yes, if the model forecasts balance sheet accounts from drivers instead of carrying them flat. FP&A teams often forecast the income statement (P&L) in detail and leave the balance sheet as last month’s actuals. That works until someone asks what cash will be in six months.
Balance sheet forecasting follows a pattern. Receivables come from revenue and collection days. Trade payables come from credit purchases and supplier payment terms. Inventory comes from cost of sales and days on hand. Fixed assets come from capex and depreciation. Debt comes from the borrowing schedule. Equity rolls forward with net income and distributions.
Each driver is a judgment. In an illustrative calculation using a 30-day month and $2 million of monthly credit sales, increasing days sales outstanding (DSO) from 45 to 52 adds roughly $467,000 to receivables: $2 million ÷ 30 × 7. With other assumptions unchanged, that ties up the same amount of cash.
The common shortcut breaks models in another way: a cash plug. When the balance sheet does not balance, some models force cash to the number that makes it balance. The model always balances, and broken links stay hidden. For example, a cash plug can hide a payables formula that stops extending into later forecast months.
Build a balance check instead. Total assets minus total liabilities and equity should be zero in every period, displayed at the top of the model, with any difference investigated.
How is the cash flow statement driven in a three-statement model?
Mostly from the other two statements. Under the indirect method, operating cash flow starts with net income, adds back noncash items such as depreciation, and adjusts for changes in working capital balances. Investing and financing flows come from capex, asset sales, borrowing and repayment schedules.
IAS 7 permits direct or indirect presentation of operating cash flows and distinguishes operating, investing and financing activities (IFRS Foundation, IAS 7, 2026).
Reconcile cash flow to balance sheet movements, separating cash effects from noncash changes such as write-offs or currency translation. If receivables rise because customers pay later, operating cash flow falls with other assumptions unchanged. Ending cash and cash equivalents on the cash flow statement should reconcile to the corresponding balance sheet balances.
Some items do not follow the pattern neatly. Accrued bonuses build through the year and pay out in one month. Deferred revenue rises with annual billings and falls as revenue is recognized. Tax payments follow statutory dates, not profit. Each needs its own schedule.
In a three-statement model, link the cash forecast to the income statement, balance sheet and supporting schedules. A separate direct cash forecast can support short-term liquidity planning, but reconcile it to the integrated model using the same opening cash balance and explaining timing differences.
How do I model capex and prepaids in a forecast?
Use a roll-forward schedule for each: opening balance plus additions, less depreciation or expense, equals closing balance, adjusted for disposals where relevant. Link closing balances to the balance sheet and expense to the P&L. Cash flow follows payment timing, which can differ from when an asset is recorded; noncash additions are not cash outflows.
This illustrative example assumes a calendar-year company with monthly closes, no opening balances, equipment paid for in April with zero residual value, and insurance coverage from January through December.
| Line | Equipment (capex) | Insurance (prepaid) |
|---|---|---|
| Purchase | $1,200,000 in April | $240,000 paid in January |
| Expense method | Straight-line over 60 months from May, when placed in service | Straight-line over 12 months from January |
| Monthly P&L charge | $20,000 depreciation | $20,000 insurance expense |
| Cash flow | $1,200,000 investing outflow in April | $240,000 operating outflow in January |
| Balance at June 30 | $1,160,000 net book value | $120,000 prepaid remaining |
Two details trip up models. Book depreciation begins when an asset is ready for its intended use, which can differ from the payment date. In this example, equipment is paid for in April and available for use in May. The annual insurance premium is paid in January and expensed over the twelve-month coverage period.
Tax depreciation can differ from book depreciation. IRS Publication 946 (2025 edition) explains US tax depreciation methods and recovery periods. Model cash tax payments using the applicable tax rules and payment dates; keep the book depreciation schedule separate.
Capex plans also need timing discipline. Approved projects slip, and a model that assumes every purchase lands on schedule overstates both depreciation and cash outflow early in the year.
Does a three-statement model stay linked when actuals land?
Only if the actuals replace the forecast correctly. Each month, closed actuals should become the opening balances for the next forecast period. If the model rolls forward from last month’s forecast instead of the closed ledger, every balance carries the forecast error forward.
The break is easy to miss. In an illustrative model, March closes with receivables above forecast, but April still opens from the old forecast balance. April’s collections and cash forecast then use a stale starting point. The cash impact depends on the collection assumptions and whether opening cash was also refreshed; it is not automatically equal to the receivables variance.
Retained earnings show the same problem. Actual net income for the closed month has to flow into equity. A model that keeps forecast net income in retained earnings stops balancing against the ledger, and the balance check shows a difference nobody can explain.
Datarails FP&A addresses the data side of this. The three-statement model stays in the Excel or Google Sheets workbook the team built, and DR.GET formulas pull closed actuals for every account and entity from FinanceOS®, the governed data layer underneath Datarails. Once March actuals are loaded, the model must use those balances to open April. Finance configures the actual-versus-forecast cutoff, account mappings and roll-forward formulas, then checks that the refreshed workbook still balances. A data refresh alone does not repair broken model logic.
Which parts of a three-statement model still have to be built by hand?
The judgment and the unusual items. Drivers, such as collection days, hiring plans and capex timing, need people who understand the business. So do debt terms, tax logic and any balance sheet item with its own rules, such as deferred revenue or earn-outs from acquisitions.
Once the connections and model logic are configured, loading mapped actuals and recalculating standard schedules can be automated. Finance still reviews exceptions, unmapped accounts, opening balances and the actual-versus-forecast cutoff. Automation reduces recurring data work; it does not remove model ownership.
Debt schedules are a good example of what stays manual. A revolving credit facility with interest that depends on the average balance creates a circular reference: interest affects cash, and cash affects the balance. Models handle it with iterative calculation or a prior-period approximation, and someone has to decide which and document it.
Covenants are another. Lenders define EBITDA (earnings before interest, taxes, depreciation and amortization), debt ratios and coverage ratios in the credit agreement, and the model has to follow those definitions exactly. A covenant test built from a generic EBITDA figure can pass in the model and fail in the compliance certificate.
The financial modeling software comparison and the guide to AI financial modeling cover which parts tools can take on and which stay with the modeler.
How to test your three-statement model
Add a balance check for every period and reconcile ending cash to the balance sheet. Then change a collection assumption, move a capex payment and load a closed month of actuals. Trace the effects across all three statements. Bring those tests to a Datarails demo to evaluate your own model.
