Rolling 13-Week Cash Forecast Governance and Assumption Control in the UAE

A 13-week forecast should start from reconciled cash, use evidence-based receipts and payments, assign every material assumption to an owner, preserve approved versions, and compare actual outcomes with the frozen forecast before rolling the horizon forward.

This guide describes a practical UAE finance control. Management should adapt thresholds, roles and evidence to its legal entities, systems and approved policies. Regulatory or tax conclusions require review of current official material and the specific facts.

1. Reconcile opening cash

Reconcile opening cash should be evidenced from the relevant source system or approved record, assigned to a named owner and reviewed at a defined frequency. Record exceptions separately, preserve the original evidence and document the action, approver and completion date. This makes the control repeatable without implying that one workflow fits every entity or transaction.

2. Assign assumptions to operating owners

Assign assumptions to operating owners should be evidenced from the relevant source system or approved record, assigned to a named owner and reviewed at a defined frequency. Record exceptions separately, preserve the original evidence and document the action, approver and completion date. This makes the control repeatable without implying that one workflow fits every entity or transaction.

3. Separate base and scenario cases

Separate base and scenario cases should be evidenced from the relevant source system or approved record, assigned to a named owner and reviewed at a defined frequency. Record exceptions separately, preserve the original evidence and document the action, approver and completion date. This makes the control repeatable without implying that one workflow fits every entity or transaction.

4. Freeze weekly approved versions

Freeze weekly approved versions should be evidenced from the relevant source system or approved record, assigned to a named owner and reviewed at a defined frequency. Record exceptions separately, preserve the original evidence and document the action, approver and completion date. This makes the control repeatable without implying that one workflow fits every entity or transaction.

5. Feed variance causes into the next roll

Feed variance causes into the next roll should be evidenced from the relevant source system or approved record, assigned to a named owner and reviewed at a defined frequency. Record exceptions separately, preserve the original evidence and document the action, approver and completion date. This makes the control repeatable without implying that one workflow fits every entity or transaction.

Review checklist

1. Confirm the complete source population and reporting cut-off. 2. Assign preparer, reviewer and exception owners. 3. Reconcile the control output to the ledger, filing or operating record. 4. Retain approvals, corrections and unresolved items. 5. Revisit the control when systems, regulation or operating scope changes.

Source and scope note

Primary source reviewed on 19 September 2026. The source establishes the relevant reporting, regulatory or governance context; the workflow above is professional judgement for operational control design, not legal, audit or assurance advice.