Article map
The debate between direct and indirect cash forecasting is sometimes framed as a choice of one superior method. In practice, the methods answer different questions. Direct forecasting asks which cash receipts and payments are expected, when and in which account or currency. Indirect forecasting asks how projected earnings, working capital, investment and financing translate into cash over a broader horizon.
Treasury usually needs both views. The challenge is to select the right method for each decision, connect the horizons and avoid inconsistent assumptions. This article explains the methods, their strengths, limitations and a practical hybrid architecture.
1. Understand the direct method
A direct forecast builds cash from expected inflows and outflows. Sources can include customer invoices, collection schedules, purchase orders, accounts payable, payroll, tax, debt service, capital expenditure and manual business events.
The method can operate at transaction level or through drivers and aggregated categories. Its defining feature is that values are expressed as cash events rather than derived from accounting profit.
Direct forecasting is particularly useful when timing matters. It can show that a company with a positive monthly net cash flow has a deficit during the first week.
2. Understand the indirect method
An indirect forecast begins with projected profit or operating result and adjusts for non-cash charges, working-capital movements, capital expenditure, tax, financing and other balance-sheet changes. It is closely connected to budget and financial-planning models.
The method is useful for understanding structural cash generation, leverage, covenant headroom and strategic funding. It can extend further into the future with less transaction detail.
Its weakness is that it may conceal daily or weekly timing. A projected reduction in receivables does not by itself show which customers will pay before a critical maturity.
3. Match method to decision horizon
Near-term positioning and funding usually benefit from direct cash events. The first few days may use bank balances, payment statuses and confirmed receipts. The following weeks can use invoices, schedules and business submissions.
Medium-term planning may combine direct categories with operational drivers. Long-term planning often relies more heavily on indirect financial statements and scenarios.
The transition should be deliberate. A common design uses a thirteen-week direct forecast followed by monthly indirect projections, with overlapping periods used for reconciliation and learning.
4. Compare data requirements
Direct forecasting needs detailed and timely operational data. It depends on invoice quality, due dates, payment runs, customer behaviour, purchase schedules and debt records. Poor master data or transaction status can create false precision.
Indirect forecasting needs integrated profit-and-loss, balance-sheet and planning assumptions. It depends on working-capital drivers, depreciation, provisions, investment plans and financing schedules.
Neither method is data-light. They require different data disciplines. An organisation should not choose indirect forecasting merely to avoid fixing transaction data if near-term liquidity decisions still depend on that data.
5. Treat working capital differently in each method
In direct forecasting, receivables and payables are converted into expected cash dates using invoice terms, collection behaviour, payment calendars and operational knowledge.
In indirect forecasting, working capital is projected through days sales outstanding, days payable, inventory days or balance assumptions. The resulting change is translated into cash.
The two views should inform each other. Direct collection evidence can improve indirect working-capital drivers; indirect trends can reveal whether the direct horizon is inconsistent with the approved business outlook.
6. Avoid false transaction-level precision
A direct forecast is not automatically more accurate because it contains more lines. Invoice due dates may not reflect actual customer behaviour. Purchase orders may change. Project milestones may shift. Transaction detail can create an impression of certainty that the business does not possess.
The model should use behavioural curves, confidence levels and ranges where appropriate. It should aggregate low-value stable items while preserving detail for concentrated, volatile or decision-critical flows.
Detail should follow risk and ownership, not the capacity of a spreadsheet.
7. Preserve balance-sheet logic in the indirect method
Indirect models can become plug-driven: cash is whatever amount makes the balance sheet balance. A credible forecast should explain the drivers of each major balance and financing item.
Projected receivables should connect to revenue and collection assumptions. Inventory should connect to purchasing and production. Debt should follow contractual schedules and planned financing. Cash should be the result of those drivers, not an unexplained residual.
Balance-sheet integrity is valuable, but treasury must still examine whether the timing and transferability of cash support actual obligations.
8. Create a controlled horizon hand-off
The hand-off determines which method is authoritative for overlapping periods. One approach is to use the direct forecast for the first thirteen weeks and the indirect forecast thereafter. Another blends direct confirmed flows with indirect residual assumptions.
The rule should prevent double counting. If capital expenditure appears as direct project payments, the indirect cash adjustment should not include the same amount again. If direct customer receipts cover the near term, working-capital movement should be calibrated around the closing balance after those receipts.
The hand-off should be tested and documented, not left to manual consolidation each cycle.
9. Reconcile the two methods through drivers
Differences are expected, but they should be understandable. A reconciliation can start with indirect operating cash flow and bridge to direct receipts and payments through timing, scope, classification and assumption differences.
For example, a budget may assume quarterly tax while the direct model uses exact payment dates. Revenue growth may not yet appear in issued invoices. A planned refinancing may sit in the strategic model but lack completed documentation in the near-term forecast.
The bridge helps management understand whether differences reflect horizon, evidence or inconsistency.
10. Use actuals differently but consistently
Direct forecast actuals are usually bank transactions and settled payments classified into cash categories. Indirect actuals derive from financial statements and balance movements. Both should reconcile to the same closing cash universe after scope adjustments.
Timing variance is especially important for direct forecasts. Driver variance and balance-sheet accuracy may be more relevant for indirect forecasts.
A common data foundation should support both views. Otherwise treasury spends time reconciling two versions of actual cash before it can assess either forecast.
11. Apply scenario analysis across both methods
Direct scenarios can delay receipts, accelerate payments, change transaction amounts or add event-specific outflows. Indirect scenarios can adjust revenue, margins, working-capital days, capital expenditure, rates and refinancing.
The effects should connect. A downside revenue scenario may reduce customer receipts in the direct horizon and projected receivables in the indirect horizon. A working-capital stress should be translated into executable cash timing where possible.
Scenario consistency prevents management from seeing a near-term stress and long-term plan based on incompatible assumptions.
12. Allocate ownership by method and driver
Treasury may own the direct forecast framework, while business units own collections, supplier schedules and projects. Financial planning may own the strategic indirect model, with treasury owning funding, interest and liquidity interpretation.
Joint governance is needed where assumptions overlap. Revenue, working capital, capital expenditure and financing should not be independently altered in multiple models without reconciliation.
A forecast owner should be accountable for the combined liquidity view, even when data ownership is distributed.
13. Select the method through a structured assessment
The choice should consider decision horizon, flow concentration, data availability, transaction volume, business volatility, legal-entity complexity and forecast ownership.
A small stable business may use a driver-based direct forecast without invoice-level detail. A complex group may require detailed direct forecasting for material entities and indirect models for less material populations. One design need not apply everywhere.
The methodology should be proportionate but consistent in definitions, controls and consolidation.
14. Design technology for both approaches
The platform should ingest operational transactions, financial plans, master data and actual bank movements. It should support source hierarchy, mapping, versioning, workflow, scenarios and horizon hand-off.
Users should be able to drill from group liquidity to the driver or transaction without forcing every long-term assumption into line-item detail. The system should also show which method produced each period and category.
Automation should reduce manual consolidation, not obscure the calculation logic.
15. Measure each method on its purpose
Direct forecasting can be assessed through timing, amount, category, bias, notice of shortfall and action quality. Indirect forecasting can be assessed through cash-generation, working-capital, capital-expenditure and funding accuracy over longer periods.
Comparing both with one percentage metric is misleading. A direct forecast may be excellent at identifying a weekly funding gap even if monthly receipts differ. An indirect forecast may correctly identify annual financing need while missing daily volatility.
Performance measures should align with the decisions each method is designed to support.
Practical illustration: connecting thirteen weeks to twelve months
A group uses a thirteen-week direct forecast from invoices, payment runs, payroll, tax and debt schedules. Its annual plan projects EBITDA, working-capital days, capital expenditure and refinancing. The first three months overlap.
Reconciliation shows that the indirect plan assumes receivables improve immediately, while the direct forecast reflects slow payment by two major customers. Management revises the working-capital assumption, accelerates collection action and increases short-term facility headroom. The methods did not compete; their difference revealed a planning risk.
Implementation checklist
A connected direct-and-indirect framework should include:
- method selection based on decision and horizon;
- direct cash categories with timing and status;
- indirect profit, balance-sheet and financing drivers;
- common entity, currency and cash scope;
- behavioural treatment of working capital;
- explicit confidence rather than false line-item precision;
- controlled horizon hand-off and overlap;
- reconciliation of scope, timing and assumptions;
- common actual cash foundation;
- aligned scenarios across both methods;
- joint ownership of shared drivers;
- proportionate methods by portfolio or entity;
- transparent technology lineage; and
- performance metrics aligned to purpose.
Common methodological failures
Common failures include choosing one method for every horizon, using indirect cash as a balancing figure, treating invoice due date as certain receipt date, double counting flows across the hand-off, operating two models with different cash scope and comparing methods without explaining timing.
Another failure is regarding reconciliation as proof that one forecast is wrong. Differences can be informative when they are decomposed and used to improve assumptions.
Closing perspective
Direct and indirect forecasting are complementary lenses. Direct forecasting provides near-term cash timing and execution detail. Indirect forecasting connects liquidity to business performance, balance-sheet structure and strategic financing.
The strongest architecture assigns each method to the horizon where it adds value, connects them through shared data and reconciliation, and presents management with one coherent liquidity story rather than competing numbers.
Frequently asked questions
What is direct cash forecasting?
Direct forecasting estimates cash receipts and payments by timing and category, using transactions, schedules, business drivers or submissions. It is typically strongest for near-term liquidity decisions.
What is indirect cash forecasting?
Indirect forecasting begins with projected profit and adjusts for non-cash items, working-capital movements, investment and financing to derive cash. It is often suited to medium- and long-term planning.
Should treasury use direct or indirect forecasting?
Many organisations should use both: direct forecasting for near-term executable liquidity and indirect forecasting for longer-term strategic outlook, connected through reconciliation and horizon hand-off rules.