Many Riyadh businesses forecast cash in a spreadsheet built from a budget rather than from operational reality. The result is a forecast that is directionally plausible but practically unreliable, so it rarely informs a financing or investment decision.

Building a forecast that earns trust is a process and data problem before it is a tool problem. That is where this work starts.

Building from operational drivers

A reliable short-term forecast is built from what the business knows. That means the receivables ledger with realistic collection patterns by customer, the payables ledger with actual payment terms, confirmed payroll and statutory payments, and committed capital spend. Historical collection behavior drives the receipts line instead of stated payment terms. A customer who has consistently paid late will not start paying on time just because the invoice says so.

Horizon and granularity

Different horizons serve different decisions and need different construction. A rolling short-term forecast at weekly granularity supports operational liquidity decisions and is where many businesses get the most immediate value. A monthly view over the year ahead supports financing and facility planning, and connects to broader financial forecasting and budget processes.

Variance analysis as the improvement engine

The discipline that makes a forecast better over time is comparing each period’s forecast to actuals and understanding the variance. Was the miss a timing difference or a real surprise? Did it come from one customer or from systematic optimism in the collection assumptions? Without this loop a forecast never improves, and most forecasts stay unreliable because nobody goes back to check them.

A hypothetical example

Consider a Riyadh contracting business that forecasts cash from its budget and is repeatedly surprised by shortfalls. A variance review might show that collections are forecast at contractual terms while main contractors pay later. It might also show that retention releases are assumed at the certificate date instead of the date cash arrives.

Saudi-specific timing factors

Payroll and GOSI dates, VAT payment deadlines, Zakat settlement timing and the effect of Ramadan and Eid on both collection and operating spend all shape the Saudi cash calendar. A generic forecast template does not capture them. Building these in explicitly often turns a broadly right forecast into one fit for decisions. It also feeds directly into liquidity planning.

Who owns the forecast

A forecast without a named owner degrades quickly. The owner updates the assumptions, runs the variance review and presents the result. That person needs enough authority to challenge a sales or operations input that experience says is optimistic. Where treasury is thin, this often sits with the financial controller. Linking it to liquidity planning and the wider forecasting calendar keeps the cash view and the P&L view on the same assumptions, so they do not diverge quietly.

Presenting the forecast so it supports a decision

A forecast delivered as a very long spreadsheet does not support a decision. We design the output around the question leadership faces: when does the balance reach its lowest point, how much headroom remains there, and which assumptions would change the answer. A single chart with a few key numbers is more useful than a full model nobody reads.

Tying the forecast to specific decisions

A forecast that changes no decision has little purpose. We tie each version to the decision it will inform: do we draw on the facility this month, do we defer a supplier payment, do we start extension talks? Once the team knows which decision depends on the forecast, input quality improves because accuracy has a visible consequence.