Get FP&A best practices, research reports, and more delivered to your inbox.
Most bad purchases here start by taking a weekly liquidity requirement into an FP&A demo. The platform will show you a cash flow statement, and at a monthly grain it will be right. It still won't tell you whether you clear payroll on the 15th, because that answer lives in open invoice due dates, customer payment behavior, and your AP run calendar. A monthly model driven off the income statement has nowhere to put any of it.
Bottom line: pick the method before you pick the vendor. Weekly, bank-balance-anchored liquidity forecasting points to a cash or treasury tool (Agicap, Trovata, Kyriba, or Tesorio when the real constraint is collections). Indirect cash forecasting and runway inside your planning model point to an FP&A platform (Cube, Datarails/FinanceOS, Jirav, Drivetrain, Runway, Workday Adaptive Planning, Aleph). Buy the wrong category and you burn a quarter of implementation before anyone admits the model can't answer the question that triggered the purchase.
The three jobs buyers call "cash flow forecasting"
Job 1: 13-week direct-method liquidity forecasting
A 13-week forecast starts from today's bank balances and lists the specific cash events expected in each of the next 13 weeks. Receipts come from open AR at the invoice level, adjusted for how each customer actually pays. Outflows come from open AP, scheduled payment runs, payroll dates, debt service, rent, and tax. The output is a weekly closing position per account and currency, checked against your minimum operating balance or a lender covenant.
The owner is normally the controller or a treasury lead, and the cadence is weekly. You build this forecast when cash is tight, when a revolver carries a borrowing-base test, or when a lender wants a rolling 13-week view as a condition of the facility. Accuracy is measured against actual bank activity, week by week, not against budget.
Job 2: indirect-method cash forecasting from a P&L and balance sheet
The indirect forecast is derived rather than scheduled. Start from forecast net income, add back non-cash items such as depreciation and stock compensation, then adjust for working capital movements using assumptions like days sales outstanding and days payable outstanding. Cash falls out of the balance sheet forecast.
This is the version most FP&A platforms produce, and it is the right one for a board deck, a 12-to-24-month plan, or a covenant model that runs on monthly financials. It is fast to maintain and it ties to your three-statement model. What it cannot do is tell you which week the money arrives.
Direct versus indirect, precisely. IAS 7, the IFRS standard on the statement of cash flows, permits either presentation for operating cash flows. Under the direct method, "major classes of gross cash receipts and gross cash payments are disclosed." Under the indirect method, profit or loss is adjusted for non-cash items, for deferrals and accruals of past or future operating cash flows, and for items belonging to investing or financing activities. US GAAP draws the same distinction in ASC 230. Both standards govern reporting rather than forecasting, but the definitions transfer exactly: direct means you enumerate the cash events, indirect means you derive cash from accrual profit.
Job 3: runway and scenario modeling for VC-backed companies
Runway modeling asks a different question: how many months of cash remain at planned burn, when the zero-cash date lands, and what changes if you slow hiring, miss plan on new bookings, or raise later than intended. The inputs are a hiring plan, a bookings ramp, and a handful of spend drivers, at a monthly grain over 18 to 24 months.
Precision matters less here than flexibility. You need to fork a model in an afternoon, compare cases side by side, and show a board the delta. That is scenario planning work, not treasury work, and a treasury system is the wrong purchase for it.
Which method does your forecast actually need?
You need direct-method, weekly forecasting if any of these are true:
- A lender, sponsor, or board asks for a rolling 13-week cash view.
- You have missed, or come close to missing, a payment run or payroll.
- Cash timing inside the month materially changes the decision you're making.
- Your AR is concentrated and a single late payer moves the position.
- You hold cash across multiple entities, banks, or currencies and need a consolidated position.
You need indirect-method forecasting if your questions are quarterly or annual: what the plan does to cash by year-end, whether the model holds a covenant on monthly financials, how working capital behaves as revenue scales. Most companies with comfortable cash cover live here and are fine.
You need runway and scenario modeling if you are venture-backed, pre-profitability, and the operative question is timing a raise rather than clearing a payment run. Plenty of teams need two of the three, which is the honest reason cash forecasting so often ends up split across a planning platform and a spreadsheet.
Cash flow forecasting software compared (2026)
The single most useful filter when shortlisting cash flow forecasting software is method: direct-method tools start from bank balances and scheduled cash events, indirect-method tools derive cash from a P&L and balance sheet forecast, and only a few support both.
Pricing models describe how each vendor charges, as of August 2026. No dollar figures appear here: most of this category quotes rather than lists, and published tiers change. Confirm current terms with each vendor.
A few adjacent names worth knowing. Tesorio is the strongest fit when your cash problem is really a collections problem: it pairs AR automation with payment-timing prediction at the customer level. Centage and Abacum both do capable indirect cash forecasting for mid-market planning teams. Anaplan and Pigment can be built into a genuine direct-method weekly model, since their engines are flexible enough to hold invoice-level detail, but that is a build project rather than a configuration and should be priced as one. Planful and Vena sit in the same indirect-plus-consolidation lane as the rest of the mid-market EPM group. Mosaic now sits inside HiBob as Bob Finance, worth checking on if it is still on your list.
Why weekly direct-method forecasting breaks most FP&A tools
This is the gap that costs teams a purchase cycle, so it is worth being specific about the mechanics.
Grain. Most FP&A platforms are built on a monthly time dimension. Some configure down to weeks, but the model, the actuals load, and the reporting layer were all designed around periods that match your close. A weekly cash forecast needs 13 columns that do not correspond to accounting periods at all, plus a mid-week actuals refresh.
Direction of the arithmetic. An indirect model computes cash as an output of accrual profit and balance sheet movement. A direct model computes cash as a sum of dated events. You cannot get the second from the first by changing the grain, because the underlying data is not in the model. Slice a monthly working-capital assumption into four weekly pieces and you get a smooth line that is wrong every week and right at month end.
AR timing at invoice level. A direct forecast needs the open AR sub-ledger: invoice, customer, amount, due date. A DSO assumption is an average of that detail, and the average hides the thing you care about, which is the one large invoice sitting past due. Most FP&A platforms pull trial-balance or summarized AR rather than open-item detail, so the data to build the schedule never arrives.
Collections behavior. Due date is not payment date. Real forecasting applies each customer's historical lateness plus the promise-to-pay information your AR team already holds in email and notes. Encoding that per customer is a collections workflow, which is why the tools that do it well (Tesorio, Agicap) come from the AR and treasury side rather than the planning side.
Fixed-date outflows. Payroll on the 15th and last day, an AP run every other Thursday, quarterly estimated tax, monthly debt service, annual insurance. These are calendar events, not ratios. A monthly model spreads them; a weekly model has to land them on the right date or the covenant test is meaningless.
Bank balance as the anchor. A direct forecast opens with the actual balance in each account, per currency, this morning. That means a bank feed or a disciplined manual refresh. Most FP&A platforms have no production bank connectivity at all, which is exactly why treasury tools exist as a separate category. Aleph is no exception: its Plaid connector is in beta, not generally available.
The variance loop. The value of a 13-week forecast comes from comparing last week's forecast to what actually cleared, then fixing the assumption that missed. That means storing every weekly version and reconciling it against bank activity: the same discipline as running a rolling forecast, applied to cash weekly.
How to build a 13-week cash forecast without buying a treasury system
Plenty of mid-market teams do not need a treasury workstation. If your cash position is one or two banks and a few hundred open invoices, a spreadsheet on live data will hold, provided you solve four things.
Pull open AR and AP at line level, not as summaries. That needs a connector that reaches sub-ledger detail — the NetSuite integration path matters here, as do the QuickBooks, Xero, and Sage Intacct equivalents. A monthly trial-balance extract is not enough.
Refresh on a schedule rather than by hand. A forecast rebuilt manually every Monday gets abandoned inside two months. That is the case for real-time spreadsheet syncing over export-and-paste.
Keep the customer-level collections adjustment as a visible input, not a hidden fudge. One column of expected days-late per customer, owned by whoever runs collections, beats a blended DSO and is far easier to defend when the forecast misses.
Version every week and keep the misses. Save last week's file, compare, and write down which assumption was wrong. That log is what makes the number defensible.
For the same discipline on the P&L side, our rolling forecast template is a workable starting structure, and the broader question of when spreadsheet-native beats a web-based platform is covered in our spreadsheet-native versus web-based FP&A comparison.
Runway and scenario modeling: what actually matters
Three things separate a runway model that survives a board meeting from one that does not.
The zero-cash date has to be driven by the hiring plan, not a burn average. Trailing three-month burn is a lagging number; an offer accepted in September moves the date more than any assumption you will tune.
Scenarios have to move both sides. A downside case that cuts revenue without cutting the spend it would trigger is not a scenario, it is a worse forecast. Runway, Drivetrain, and Jirav all handle linked scenario logic; so does a spreadsheet with the drivers wired properly.
And the model has to reconcile to actuals monthly. Runway credibility comes from showing last quarter's projection was close, not from the elegance of the build. Our FP&A software evaluation guide covers how to test that in a demo rather than taking it on trust.
Where Aleph fits
Aleph is the spreadsheet-native modeling and reporting layer, not a treasury system. The boundary matters: Aleph has no production bank connectivity, so it is not the tool for daily multi-bank cash positioning or for initiating payments. If that is the requirement, Kyriba, Trovata, or Agicap are the honest answers.
What Aleph does is keep the cash model where finance already works and remove the manual refresh. Roughly 150 no-code connectors pull NetSuite, QuickBooks, Xero, Sage Intacct, and the rest of the stack into Excel or Google Sheets, so a weekly direct-method schedule can sit on live AR and AP detail instead of a Monday-morning export. Forecast versions are stored, so variance runs against actuals automatically. Scenarios live in a shared repository, which is what makes a runway model forkable without copying the workbook.
In practice, teams use Aleph for the indirect cash forecast and the runway model as part of their financial modeling and forecasting work, then build the 13-week direct schedule in the same environment when their cash footprint doesn't warrant a treasury tool. When it does, running Aleph alongside a treasury system beats forcing either one to do the other's job.
Get FP&A best practices, research reports, and more delivered to your inbox.
