A cash-flow statement and a cash forecast answer different questions. The statement explains historical cash movement. The forecast estimates future receipts and payments using assumptions about timing and activity. Treating them as interchangeable can give treasury a polished report that does not support the next payment decision.
NetSuite cash flow reporting should therefore begin with the purpose, reporting population and source records. Historical reporting needs a reconciled accounting basis. A short-term forecast needs that starting point plus collection assumptions, payment plans and operational commitments that may not yet exist in the ledger.
This guide provides separate hypothetical examples for both outputs. Accounting classifications, signs and reporting treatment must be reviewed against your organization's policies and configured reports.
For a historical statement, specify the period, entities, currency and accounting book. Identify the reports and classifications finance uses to explain the movement from opening to closing cash.
For a forecast, specify the horizon and decision frequency. A weekly thirteen-week view may support liquidity planning, while a monthly longer-range model may support other decisions. Choose a horizon based on the business need rather than assuming one format fits every organization.
Name the cash population. Decide which bank accounts and entities are included, and how restricted or otherwise unavailable balances are presented under the approved reporting approach. A balance that exists in the ledger may not be available for every planned payment.
Keep historical actuals and forecast assumptions visibly separated so users know what has happened and what is expected.
Consider a hypothetical period beginning with 100,000 currency units of cash. Assume approved classifications show net operating inflows of 25,000, investing outflows of 10,000 and financing outflows of 5,000, with no foreign-exchange effect or other movement in this simplified example.
The net movement is 10,000, giving closing cash of 110,000. The arithmetic is 100,000 plus 25,000 minus 10,000 minus 5,000. The closing amount should reconcile to the approved cash population in the ledger and supporting bank reconciliations.
If the ledger shows a different amount, investigate scope, account mapping, period filters and unrecorded or incorrectly classified activity. Do not change a statement category simply to force the ending total to match.
For a real multi-currency group, translation and exchange effects can add complexity. Preserve the report's currency context and have finance validate the appropriate treatment rather than extending this simplified example unchanged.
Use the latest reconciled cash position appropriate to the forecast's start date. If some bank activity is newer than the completed ledger reconciliation, show how that difference is handled rather than combining inconsistent dates silently.
Then bring in open receivables and payables with their relevant dates, currencies, entities and statuses. These records provide a starting population, not a complete forecast.
Receivable due dates do not guarantee collection. Supplier due dates do not necessarily equal the approved payment date. Add the business assumptions needed to translate contractual timing into expected cash timing, with an owner and evidence.
Avoid including the same event twice. A payroll liability in payables and a separate payroll forecast line may represent the same future cash payment. Reconcile source categories before summing them.
Segment receivables by the factors that affect timing: confirmed promises, disputes, customer payment patterns, payment methods and other relevant facts. Use reliable evidence rather than assuming every overdue invoice will arrive next week.
A hypothetical business has 80,000 of open receivables. Its base forecast expects 60,000 to be collected during the next four weeks, based on reviewed customer expectations. The remaining 20,000 stays outside that window rather than disappearing from the model.
Record the assumed receipt week for each material item or supported grouping. If a customer changes its commitment, update the forecast and retain the reason for the change.
Compare forecast receipts with actual receipts after the period. Separate timing variance from amount variance so collections can improve the assumptions rather than merely explain the total miss.
A payable ledger can omit future payroll, taxes, capital purchases, financing payments and purchase commitments that have not yet become bills. Treasury needs the relevant operational owners to provide these inputs.
Identify the source, amount basis, expected date, confidence and approver for each additional line. Keep tentative plans distinct from approved commitments. Avoid presenting every planned expenditure as equally certain.
For purchasing commitments, reconcile to bills when they are created so the forecast does not retain both the commitment and the payable. Define the event that moves an item from one source category to another.
Where the business uses a separate treasury or planning tool, document the interface and reconciliation. The same ownership principles apply regardless of where the forecast is displayed.
Start with the reconciled opening cash of 110,000. Assume expected customer receipts of 60,000, supplier payments of 45,000, payroll of 25,000, taxes of 10,000 and capital spending of 15,000. These fictional amounts are planning inputs, not recommendations.
Total expected outflows are 95,000. Closing forecast cash is 75,000: opening 110,000 plus receipts of 60,000 minus outflows of 95,000.
In a downside scenario, receipts fall to 45,000 while the assumed outflows stay unchanged. Forecast closing cash becomes 60,000. The 15,000 difference is entirely attributable to collection timing in this scenario, making the driver clear to management.
Distribute the amounts by week before using the result for payment planning. A positive month-end balance can hide a temporary shortfall if major payments occur before expected receipts.
Assign treasury ownership of the consolidated forecast and source owners for collections, purchasing, payroll and other commitments. Set a cutoff for updates and a process for material changes between reviews.
Retain a frozen version for each reporting cycle. Compare actual cash movements with that version, not with a forecast revised after the event. Track which assumptions repeatedly move and whether the source owner can improve them.
Use a short variance explanation focused on decisions: delayed receipts, accelerated payments, new commitments or scope changes. The forecast should help management understand timing risk, not merely display a closing number.
No. It explains historical movement. A forecast adds expectations about future timing and activity, including commitments that may not yet appear in accounting records.
Usually they are only part of the input. Review collections assumptions and operational cash requirements such as payroll, taxes, capital spending and other commitments.
Compare a preserved forecast version with actuals, separating timing, amount and scope differences. A total variance alone can hide the cause.
A defined account population, consistent date and currency context, ledger agreement and supporting bank reconciliation evidence appropriate to the reporting date.
CuriousRubik can help scope a NetSuite cash-reporting review that separates historical reconciliation from forward-looking assumptions. Bring the cash population, open-item reports and the operational commitments your current forecast misses.