Why Cash Gets Harder to See With Every New Branch
A single-branch business checks its balance by opening the banking app. A company with six branches in Riyadh, Jeddah, Dammam and Abha has a cash box in every branch, accounts at three or more banks, POS terminals that settle a day or two late, cheques under collection, and sales reps collecting cash from customers. Meanwhile salaries, VAT and large rents are paid centrally. The usual result is a CFO who starts each morning stitching balances together from branch managers' messages and bank portals, and a company where one branch sits on idle cash while another delays a supplier or head office draws on a short-term facility.
Multi-branch cash flow management means seeing all cash in one place, knowing what will come in and go out over the coming weeks, and moving liquidity between branches deliberately with correct entries. This guide shows how to build that visibility step by step, with worked examples of a daily cash position and a 13-week forecast, the right way to book inter-branch transfers, branch cash controls, and the fixed Saudi obligations that belong in every cash calendar.
Branch or Subsidiary? The Answer Changes the Treatment
| Aspect | Branches of one legal entity | Separate companies in a group |
|---|---|---|
| VAT number | One number for the entity, even if each branch has its own sub-CR | One per company, or a single group number if registered as a VAT group |
| VAT return | One return covering all branches | One per company, or one for the VAT group |
| Moving cash between units | An internal movement between the entity's own accounts | An intercompany loan that needs documentation |
| Financial statements | One set for the entity, with management reports per branch | One set per company, then consolidated statements with intercompany eliminations |
| E-invoicing | Each invoice-generating device or system needs its own cryptographic stamp identifier | The same, per company |
Most mid-sized businesses we are describing here are branches of one entity. That simplifies VAT because there is one return, but it also means VAT on every branch's sales is paid from one place on one date, which must show up in head office's forecast.
The Foundation: One Chart of Accounts, Branches as Cost Centers
The biggest obstacle to central visibility is each branch booking things its own way. One posts rent to one account, another to a different one, a third lumps it into general expenses. The fix is not a chart of accounts per branch but one chart for the company, with the branch captured as an analytic dimension on every entry through a cost or profit center. You can then produce an income statement per branch, cash box balances per branch and receivables per branch with no manual mapping. Our article on cost center types and uses goes deeper into the design.
For cash accounts specifically, create a separate ledger account for every real bank account, every branch cash box and every POS terminal or payment provider. A single "Bank" account that combines three real accounts makes bank reconciliation practically impossible.
The Daily Cash Position
The cash position is a report reviewed every morning that answers one question: how much cash is available right now, and where is it? Hypothetical example for a distributor with four branches (SAR):
| Branch | Banks | Cash boxes | POS settlements in transit | Minimum required | Surplus or shortfall |
|---|---|---|---|---|---|
| Riyadh (HQ) | 1,450,000 | 15,000 | 40,000 | 900,000 | +605,000 |
| Jeddah | 180,000 | 22,000 | 35,000 | 250,000 | -13,000 |
| Dammam | 720,000 | 18,000 | 28,000 | 200,000 | +566,000 |
| Abha | 95,000 | 9,000 | 12,000 | 120,000 | -4,000 |
| Total | 2,445,000 | 64,000 | 115,000 | 1,470,000 | +1,154,000 |
The company as a whole has more than SAR 1 million of headroom, yet two branches are below their minimum. Without this report, the Jeddah manager might ask head office to hold a supplier payment, or the company might draw on a facility, while Dammam holds over half a million it will not need for two weeks.
A branch minimum is not a fixed number. Base it on expected outflows over a set period, for example two weeks of local supplier payments and operating costs. The more accurate the payables data in the ERP, the better the minimum.
The 13-Week Rolling Forecast
The cash position tells you about today; the forecast tells you what is coming. The workhorse tool for finance teams is a rolling 13-week forecast, roughly one quarter, updated weekly. Its inputs come straight from the ERP:
- Expected collections: open customer invoices by due date, adjusted for each customer's actual payment behavior. If a customer typically pays 20 days late, do not put their cash in the due week.
- Cash sales: average POS takings per branch, adjusted for seasons such as Ramadan, Eid and back-to-school.
- Supplier payments: approved supplier invoices by due date, plus open purchase orders that will turn into invoices.
- Fixed commitments: payroll, rents, loan instalments and taxes.
Hypothetical four weeks of the forecast (SAR thousands)
| Line | Week 1 | Week 2 | Week 3 | Week 4 |
|---|---|---|---|---|
| Opening balance | 2,624 | 2,759 | 2,289 | 1,209 |
| Customer collections | 620 | 540 | 580 | 700 |
| Branch cash sales | 310 | 290 | 300 | 420 |
| Supplier payments | (780) | (650) | (810) | (600) |
| Payroll | 0 | 0 | 0 | (980) |
| Rent and loan instalments | (15) | (650) | (30) | (15) |
| Quarterly VAT | 0 | 0 | (1,120) | 0 |
| Closing balance | 2,759 | 2,289 | 1,209 | 734 |
The opening balance is the banks, cash boxes and POS settlements from the cash position above. The forecast shows the quarterly VAT payment landing in the same week as heavy supplier payments, followed by payroll. The week-four closing balance of SAR 734,000 is well below the combined branch minimum of SAR 1.47 million. Knowing that three weeks ahead allows calm options: chase specific customers early, reschedule non-urgent supplier payments, or arrange a facility in advance on better terms than an emergency draw.
For broader cash management tools, see our article on cash flow management for Saudi companies.
The Fixed Saudi Obligations Calendar
| Obligation | Timing | Note |
|---|---|---|
| Payroll and WPS file | Monthly, with the WPS upload within 30 days | The deadline was 60 days until 1 March 2025 |
| VAT | Monthly if annual taxable supplies exceed SAR 40 million, otherwise quarterly | Return and payment due by the last day of the following month |
| Late VAT payment | If missed | Penalty of 5% of unpaid VAT for each month of delay |
| Corporate income tax return | Within 120 days of year-end | For entities subject to income tax |
| Zakat | Annually with the zakat return | A large amount that needs planning |
| Annual or semi-annual rents | By contract | Common for branches and warehouses, and cause big spikes |
At 5% a month, the late payment penalty on VAT is far more expensive than any bank facility. VAT should never be the item that slips when cash is tight.
Inter-Branch Transfers: Getting the Entries Right
When head office moves SAR 300,000 from the Dammam account to the Jeddah account, and both are branches of one entity, the company-level entry is simple: debit Jeddah bank, credit Dammam bank. But if you track results and a management balance sheet per branch, you need inter-branch current accounts:
- In Dammam's books: debit "Jeddah branch current account", credit bank, SAR 300,000.
- In Jeddah's books: debit bank, credit "Dammam branch current account", SAR 300,000.
- At company level the two current accounts offset to zero.
The classic problem is that one side is booked on the day of transfer and the other days later when the receiving branch notices the money, so the current accounts do not agree at month-end. In an integrated system the transfer is created once as a document and generates both sides at the same moment.
If the units are separate companies, the transfer is intercompany financing and must be eliminated on consolidation so it does not appear as both an asset and a liability. For how these balances affect the statement of financial position, see our guide to the balance sheet.
Branch Cash Controls
- Imprest petty cash: a fixed float per branch, for example SAR 5,000, topped up only by the value of documented expenses.
- Daily deposit of takings: no more than a set amount stays in the branch overnight; each deposit is recorded with a copy of the bank slip.
- Daily POS reconciliation: system sales = cash in drawer + card sales + credit sales. Any difference is recorded against the cashier and followed up.
- Payment provider settlement matching: card money reaches the bank net of commission a day or two later, and must be matched to recorded card sales.
- Surprise cash counts: at least monthly, by someone independent of the branch.
Working Capital by Branch
Cash is ultimately the result of three numbers: days to collect, days stock sits before it sells, and days you take to pay suppliers. Cash conversion cycle = days sales outstanding + days inventory outstanding minus days payables outstanding.
| Branch (hypothetical) | DSO | DIO | DPO | Cash conversion cycle |
|---|---|---|---|---|
| Riyadh | 45 | 40 | 60 | 25 days |
| Jeddah | 75 | 55 | 45 | 85 days |
| Dammam | 30 | 35 | 60 | 5 days |
Jeddah is not necessarily less profitable, but it ties up cash more than three times as long as Riyadh because customers pay late and stock moves slowly. The fix starts with credit limits and receivables ageing for Jeddah's customers and a look at slow-moving items in its warehouse, not with more transfers from head office.
Speeding Up Collections Without Losing Customers
- Credit limit per customer: the system blocks a new credit sale when the customer is over limit or has invoices overdue beyond a set period, unless a higher authority approves.
- Ageing by sales rep: each rep sees their overdue customers weekly, and part of their incentive depends on collections, not just sales.
- Monthly customer statements: disputes surface early, instead of discovering months later that a customer is refusing an invoice over an unrecorded return.
- Same-day recording of field collections: reps log cash or cheques from their phones at once and deposit within a set time.
In the Jeddah example, cutting DSO from 75 to 55 days releases twenty days of the branch's credit sales, which may remove the need for any transfer from head office.
The Weekly Liquidity Meeting
Tools are not enough without a fixed moment for decisions. Many multi-branch businesses hold a half-hour weekly meeting with the CFO and treasury, inviting managers of branches with a large surplus or shortfall. The agenda: last week's actuals versus forecast and why they differed; today's position per branch against its minimum; the ten largest overdue invoices and who owns each; large commitments in the next four weeks; and transfer or payment timing decisions. Record every decision with an owner and review it the following week. After two or three months of this rhythm, the forecast becomes far more accurate because the team learns which customers always pay late and which items get forgotten.
Common Mistakes
| Mistake | Result | Fix |
|---|---|---|
| One ledger account for several real bank accounts | Impossible reconciliation, unreliable balances | A separate account per bank account and cash box |
| Monthly bank reconciliation only | Differences found weeks late | At least weekly for active accounts |
| Inter-branch transfer booked on one side | Branch current accounts that never agree | One transfer document that posts both sides |
| Spreadsheet forecast nobody updates | Surprises at payroll and VAT time | Rolling forecast built from ERP receivables and payables |
| Broad payment authority for branch managers | Payments outside company priorities | A branch payment cap; anything above goes to head office |
How Tranquil Supports Multi-Branch Cash Management
Tranquil brings financial accounting, sales, purchasing, inventory and POS into one cloud system, so every branch's transactions reach the ledger from the transaction itself. Bank integration handles direct salary transfer to employee accounts. The Tranquil team also customizes reports, screens and multi-level approval chains and builds API integrations to fit your branch structure. Explore accounting and finance and financial management, or contact us.
Frequently Asked Questions
Does each branch need its own VAT number?
Not if the branches belong to one legal entity. All branches invoice under the entity's VAT number and file one return. Under Phase 2, though, each device or system that issues e-invoices needs its own cryptographic stamp identifier.
What is the difference between a cash position and a cash forecast?
The cash position is a snapshot of cash in banks and cash boxes today. The forecast estimates what will come in and go out over the coming weeks, based on receivables, payables and fixed commitments.
How often should the cash forecast be updated?
At least weekly, comparing the week just ended with what was forecast. That comparison improves accuracy over time by exposing the customers and items that are consistently misjudged.
How do I book a cash transfer between two branches?
At company level, debit the receiving branch's bank and credit the sending branch's bank. If you track a balance sheet per branch, use inter-branch current accounts posted at the same moment and offsetting at company level.
How much cash should a branch keep in its cash box?
It depends on cash sales and small daily expenses. What matters most is a fixed ceiling, daily deposits of takings and regular surprise counts.