AWRA OpsHub Search
Intermediate Certificate on pass

The 13-Week Cash Forecast and What-If Scenarios

Read cash week by week for the next thirteen weeks from the invoices, bills, orders, payroll and tax already in AWRA, find the low point before it arrives, and test a what-if without changing a single document.

3 lessons 35 min 6-question assessment 70% to pass

What you’ll learn

  • Explain where the forecast’s opening cash comes from and which documents become inflows and outflows
  • Open the documents behind any weekly figure and download the forecast as CSV
  • Set a low-cash threshold and choose between due dates and each customer’s payment history
  • Build a scenario that moves receipts, trims collections, delays supplier payments or adds a one-off amount

Course content

3 lessons · 35 min of reading
01
Lesson 1 of 3 Reading 12 min

What the forecast counts, week by week

Open the 13-week cash forecast from the Accounting overview, or type Cash Forecast in the command palette. Anyone who can view accounting can read it. Week 1 starts on this week’s Monday and each column is labelled Wk 1, Wk 2 and so on with its start date. The forecast opens at today’s ledger balance of your cash and bank accounts, the same accounts the cash-flow statement treats as cash, and the summary cards show Opening cash, Expected in, 13 weeks, Expected out, 13 weeks and the Low point with the week it falls in. The chart, Closing cash by week, draws money in and out as bars and closing cash as a line.

Inflows are open customer invoices by their due date, the invoices your active recurring schedules will raise, and recurring journals that bring cash in. Outflows are payable supplier bills by due date; issued purchase orders not yet fully billed, placed at their expected delivery plus that supplier’s usual terms (30 days when there is no bill history to learn from); payroll runs not yet paid, with months that have no run projected from the last regular one; unpaid approved expenses; VAT and withholding owed per the ledger, due on the 20th of the following month; and recurring journals that pay cash out. Anything already overdue lands in week 1, because it is still owed and the earliest it can move is now. Anything expected after week 13 is left out.

In practice: a Nairobi distributor’s controller opens the forecast on a Monday. Opening cash is KES 3.2 million; Wk 6 shows a large Supplier bills figure and closing cash dips to KES 410,000. She clicks that amount, and the panel below lists the documents behind it: two import bills due that week, each with its supplier, due date and a link to the bill. Download CSV gives the same weeks and categories for the board file. Nothing on the page changes a document; it reads what AWRA already holds.

Key takeaways

  • The forecast opens at today’s ledger balance of cash and bank accounts and runs thirteen weeks from this Monday.
  • Inflows are open and scheduled invoices and cash-in recurring journals; outflows are bills, open purchase orders, payroll, unpaid expenses, VAT and withholding, and cash-out recurring journals.
  • Overdue items sit in week 1; items expected after week 13 are left out.
  • Click any amount to see the documents behind it; Download CSV exports the grid.
02
Lesson 2 of 3 Practice 10 min

The low-cash threshold, payment history and currencies

Under How the forecast is built, someone with the manage cash forecast permission sets two workspace defaults and clicks Save defaults. Low-cash threshold is an amount in your base currency: when a week’s closing cash falls below it, the page shows a warning naming the first week it happens, how many of the thirteen weeks stay under it and the low point, and the chart draws the threshold as a dashed line. Left blank, the page warns only when cash goes negative. Shift receipts by each customer’s payment history moves every customer’s expected receipts by that customer’s average days late over the last year, once they have at least two paid invoices; a customer who pays early moves the other way.

Anyone reading the page can also try a different view without changing the defaults, from the filter bar: Receipt dates switches between Shift by payment history and Due dates as written, and Low-cash threshold takes a one-off figure. Currency shows one currency at a time, base by default. A forecast in another currency opens at the bank accounts held in that currency, from the amounts on their own ledger lines, and only counts documents in that currency: unlike currencies are never added together or converted, so a USD shortfall is not hidden by a KES surplus.

In practice: a Kampala contractor sets the threshold to UGX 50 million and turns on payment history. Its largest customer, a ministry, pays 47 days late on average, so that customer’s invoices move seven weeks to the right and the warning appears: cash falls below UGX 50 million in Wk 9 and stays under it for three of the thirteen weeks. Switching Receipt dates to Due dates as written shows the same weeks with no warning, which is the gap between what is owed and what history says will arrive. The finance director then checks the USD view separately, for the dollar account that pays the equipment lease.

Key takeaways

  • Save defaults stores the low-cash threshold and the payment-history switch for everyone; it needs the manage cash forecast permission.
  • Below the threshold, the page names the first week, how many weeks stay under and the low point.
  • Payment history moves each customer’s receipts by their average days late over a year, with at least two paid invoices.
  • One currency at a time: a foreign-currency view uses the accounts held in that currency and never converts.
03
Lesson 3 of 3 Practice 13 min

What-if scenarios beside the base forecast

A scenario is a named what-if shown beside the base forecast. The invoices, bills and orders themselves are not changed. Click New scenario, give it a Name and an optional Description, and add Adjustments. There are five kinds: Move receipts by N days, for all customers or one; Collect only part of receipts (%), entered as Not collected (%); Delay supplier payments by N days, for all suppliers or one; and a One-off inflow or One-off outflow with an Amount, a Date and a Label. Negative days bring a date forward, and a receipt already overdue is moved from today. Save scenario, then pick it in the Scenario filter.

With a scenario chosen, the page shows the base and the scenario as two grids and two lines on the chart, the summary cards add the scenario’s figures, and a Scenario less base row shows the difference week by week. One-off amounts appear under their own Scenario one-offs category, so they are never mistaken for documents. Because a scenario is a list of adjustments applied to the same documents, it stays current: tomorrow’s new invoice appears in the base and the scenario alike. Scenarios can be edited or deleted by anyone with the manage cash forecast permission.

In practice: before a board meeting, a Dar es Salaam importer builds “Largest customer pays 30 days late”: one Move receipts adjustment of 30 days for that customer, plus a One-off outflow of TZS 85 million on the date a container duty is due, labelled Duty on container 14. The scenario line drops below the threshold in Wk 7 while the base stays above it. A second scenario adds Delay supplier payments by 14 days for two local suppliers and a One-off inflow for an agreed loan drawdown, and the board compares the two lines against the base before deciding which to negotiate.

Key takeaways

  • A scenario never changes a document; it applies adjustments to a copy of the forecast.
  • Five adjustments: move receipts, collect only part, delay supplier payments, one-off inflow, one-off outflow.
  • A chosen scenario shows beside the base, with a Scenario less base row and its own line on the chart.
  • Scenarios stay current because they are re-applied to whatever documents exist today.

Finished the material?

Take the 6-question assessment and earn your certificate — 70% to pass.

Take the assessment

Help Center

Need a quick answer while you read?

Run inventory, procurement, assets, sales, and field work with approved AWRA guidance for setup, migration, integrations, security, pricing, and support.

Search all approved AWRA public help articles.

Open Help Center