A company can be profitable on paper and still run out of cash. That is the risk cash flow forecasting exists to catch, and it is also the reason most finance teams still run it in a spreadsheet, rebuilt every week, disconnected from whatever actually landed in the bank.
Cash flow forecasting D365 F&O ships natively is more capable than that reputation suggests. The feature uses machine learning to project cash flow, aimed specifically at replacing the manual, repetitive version finance teams have been building by hand for years. This guide will explore what actually feeds cash flow forecasting D365 relies on, how cash and bank management keeps that forecast honest, and where finance teams still reach for a heavier analytics layer.
What actually goes into a D365 F&O cash flow forecast
A forecast model is where cash flow forecasting D365 F&O actually starts. It sets the frame: base currency, period type, daily, weekly, or monthly, forecast type, optimistic, pessimistic, or most likely, and cash flow type, operating, investing, or financing.
- Liquidity accounts, the company’s cash and cash-equivalent accounts, get identified first, since every forecasted transaction ultimately has to land against one of them.
- Cash flow forecasting D365 F&O integrates directly with the general ledger, accounts payable, accounts receivable, budgeting, and inventory management.
- A forecast model can also pull from project management and accounting, so predictable project costs and revenue show up in the same forecast.
- Setup happens per legal entity, so a multi-entity organization configures this once for every entity it wants a forecast for.
Running more than one forecast model at a time is common, and deliberate. A pessimistic model built around slower collections and a most-likely model built around normal terms can sit side by side, so finance is not forced to commit to a single version of the future before deciding how much cash headroom to plan around. Switching between models later, though, is not free: updating one model and then specifying a different one for the same run can overwrite what was already calculated, so the choice of model matters before the first calculation, well before reporting time.
That per-entity setup is worth remembering. It comes back later, once the forecast needs to say something about the whole business rather than one piece of it.
Period type is a smaller decision than it looks. A daily forecast surfaces every timing gap, useful for a treasury team managing payroll runs and large vendor payments in the same week, but it can bury the signal in noise for anyone trying to spot a quarter-over-quarter trend. A monthly forecast smooths that noise out, at the cost of hiding the exact week a cash shortfall would actually hit. Most organizations end up running more than one period type for more than one audience, rather than picking a single setting and living with the trade-off.
Where the numbers actually come from
Cash flow forecasting D365 F&O draws from several different places at once, well beyond the ledger alone, and getting the full picture right matters more than any single input on its own.
Payment forecasts from accounts payable and receivable
Open vendor invoices and customer invoices generate payment forecasts automatically, projected outflows and inflows based on payment terms already on file, not a manually re-typed estimate. As invoices get entered, paid, or settled, those payment forecasts update in step, so the forecast reflects what is actually open today rather than a snapshot from whenever someone last rebuilt it.
This is also where a forecast tends to be most reliable and most fragile at the same time. Reliable, because the underlying invoices already carry real payment terms and due dates rather than an estimate. Fragile, because a customer who habitually pays 15 days late will keep showing up as an on-time payment forecast until someone adjusts the assumption, quietly overstating near-term cash every single period.
Liquidity planning and liquidity accounts
Liquidity planning in D365 F&O starts with a short list: which bank accounts, and which general ledger main accounts behind them, count as liquidity accounts. Every other forecasted transaction is ultimately measured against this list, so getting it right is the one setup step the rest of liquidity planning depends on.
Project and budget-driven forecasts
A project forecast model can feed forecasted project costs and revenue into the same cash flow forecast, so predictable project cash movements are not left out simply because they have not generated a transaction yet. Budget data can be included the same way, useful for cash needs that are planned but not yet committed.
AP, AR, budget, and project data all feeding one forecast is the easy part. Seeing all of it against what actually happened to cash over time is where the Metrixs analytics suite picks up.
Keeping the forecast honest: bank reconciliation and cash position
Cash flow forecasting D365 F&O relies on is only as trustworthy as the reconciliation behind it. Advanced bank reconciliation, sometimes called Modern bank reconciliation in newer releases, imports electronic bank statements; common formats include BAI2, MT940, and ISO20022 or CAMT.053, and matches them against Finance bank transactions automatically using configurable matching rules.
- Cash application turns an unmatched bank statement line directly into a settled customer or vendor payment, closing the gap between what the bank shows and what Finance has recorded.
- Matching rules and matching rule sets decide what counts as a match, one-to-one, many-to-one, or many-to-many, and how much date difference is acceptable.
- The Cash overview workspaces, current company and all companies, are where cash position actually gets checked day to day, filterable by bank account and financial dimension.
The reconciliation side of this deserves more attention than it usually gets. A matching rule that is too loose will happily pair transactions that only coincidentally share an amount, and a rule that is too strict leaves a growing pile of unmatched lines that someone has to work through manually every period. Either failure mode quietly erodes trust in the cash position the forecast is built on, long before anyone notices the forecast itself is off.
An unreconciled bank account is more than a bookkeeping headache. It quietly puts every forecast built on top of it in question, since the liquidity accounts driving the forecast are the same accounts bank reconciliation is supposed to be keeping current.
If your forecast and your bank reconciliation tell two different stories about cash position, a Metrixs consultant can help find out which one is actually current.
What native cash flow forecasting covers, and where it stops
Cash flow forecasting D365 F&O genuinely uses machine learning to improve projection accuracy, and results surface through Power BI reports and the Cash overview workspaces. That is a real starting point, not a blank canvas. The same is true of the module generally: this is not a case of building analytics on top of nothing, so the gap that remains is specific, not total.
- Forecast setup and results live per legal entity, so a consolidated, cross-entity cash position needs to be assembled by hand.
- Forecast accuracy against actual outcomes, and a multi-month or multi-year cash position trend, are not something the native workspaces hold as history.
- This module sits apart from the rest of financial reporting, general ledger, budget, fixed assets, so a single, unified liquidity view across all of them means exporting from several places.
None of this makes the native tools a bad starting point. It means the same machine learning model that projects next month’s cash position has no memory of how accurate last quarter’s projection actually was, because that comparison is not something the workspace is built to hold. A finance team that wants to know whether the forecasting model is getting better or worse over time has to build that comparison itself, quarter after quarter.
| What you need | Native D365 F&O tools | A dedicated layer such as Metrixs |
|---|---|---|
| Forecast vs. actual, over time | Not held as history in the workspace | Configurable history in one saved view |
| Cross-entity cash position | Assembled by hand, entity by entity | Consolidated across entities automatically |
| Cash flow next to GL, budget, assets | Separate exports from each module | One reporting layer across all of them |
| Refresh | Whatever is loaded when the workspace opens | 15 to 30 minutes via Synapse Link |
How Metrixs extends D365 F&O cash flow data into one liquidity view
Metrixs reads cash flow forecast data, bank reconciliation results, and ledger actuals the same way it reads the rest of D365 F&O, through Azure Synapse Link into the same dedicated Azure Data Lake, built across more than 6,000 D365 F&O backend tables.
- Forecast versus actual cash position, held as configurable history, instead of a workspace snapshot that resets the moment someone reruns the forecast.
- Multi-entity cash position consolidated automatically, including across a multi-ERP treasury setup where that applies.
- Refresh every 15 to 30 minutes, inside the same suite already covering general ledger, budgeting, and fixed assets: 12 analytics modules, 100+ prebuilt reports, 1,000+ configurable metrics.
- Deployment in under 6 weeks, with client ROI running 290% to 450% across engagements.
The practical payoff shows up at treasury decisions that cannot wait for a manual export: whether to move cash between entities before a large payment run, whether a shortfall in one entity can be covered internally rather than through a credit line, and whether the forecasting model has actually been getting more accurate quarter over quarter or just feels that way. None of those questions are answerable from a workspace that only shows the current forecast for the current entity.
For an organization already relying on cash flow forecasting D365 F&O provides, that is the difference between checking cash position once a week and simply knowing it.
This is what a forecast-versus-actual cash position view looks like once it does not need rebuilding every week. See the D365 F&O finance and accounting analytics use case.
Frequently asked questions
What is cash flow forecasting in D365 F&O?
Cash flow forecasting D365 F&O ships natively projects future cash inflows and outflows from data already in the system, open vendor and customer invoices, budget figures, project forecasts, and general ledger activity. It runs per legal entity, uses machine learning to improve accuracy, and surfaces results through Power BI reports and the Cash overview workspaces.
How does cash and bank management support liquidity planning?
Cash and bank management is where liquidity accounts get defined, the specific bank and general ledger accounts every forecasted transaction is measured against. Once those accounts are set, cash flow forecasting draws on accounts payable, accounts receivable, budgeting, and project data automatically, instead of liquidity planning depending on a manually maintained spreadsheet, which is exactly the manual process cash flow forecasting D365 was built to replace.
What is a liquidity account in D365 F&O?
A liquidity account is one of the company’s cash or cash-equivalent accounts, identified during setup and tied to a general ledger main account. Every transaction cash flow forecasting D365 F&O projects is ultimately measured against one of these accounts, which is why configuring them correctly is the first real setup step, not an afterthought.
How does bank reconciliation affect cash flow forecast accuracy?
Bank reconciliation confirms that what the bank shows and what Finance has recorded actually match, using imported bank statements and configurable matching rules. An unreconciled bank account means the liquidity accounts cash flow forecasting D365 depends on may already be wrong, so reconciliation accuracy limits forecast accuracy, not the other way around.
Where do payment forecasts in D365 F&O come from?
Payment forecasts come from open vendor and customer invoices already in the system, projected using the payment terms on file rather than a manual estimate. They update automatically as invoices are entered, paid, or settled, so the forecast reflects what is currently open instead of a snapshot from whenever it was last rebuilt, which is the real-time accuracy cash flow forecasting D365 depends on.
Can D365 F&O forecast cash position across multiple legal entities?
Cash flow forecasting D365 F&O is configured and calculated per legal entity, so each entity needs its own setup before a forecast is available for it. Native tools do not automatically roll several entities’ cash position into one consolidated view, which is usually assembled by exporting each entity’s results and combining them by hand.
Does D365 F&O use AI or machine learning for cash flow forecasting?
Yes. Cash flow forecasting D365 F&O ships through Finance Insights and uses machine learning to help project cash flow more accurately than a manual process typically achieves. It still depends on the underlying data, liquidity accounts, payment forecasts, and reconciliation being accurate and current, since no forecasting model corrects for bad source data.
The verdict
Cash flow forecasting D365 F&O ships is a genuinely strong starting point: real integrations across the general ledger, accounts payable, accounts receivable, budgeting, and projects, real machine learning, and real Power BI reporting. The gap is not native analytics. It is holding forecast accuracy and cash position as history, and consolidating both across legal entities and the rest of financial reporting.
Metrixs closes that gap: reading the same forecast data, bank reconciliation results, and ledger actuals, refreshing every 15 to 30 minutes, and shipping it as part of the same suite that already covers general ledger, budgeting, and fixed assets.
Ready to see your own cash position as one forecast-versus-actual view? Book a Metrixs reporting assessment, and we will map your liquidity accounts and bank reconciliation against what the reporting layer already covers.
