✦ Insights

Cash Visibility Is the First Treasury Problem

Before forecasting or optimising, a treasury team has to see its cash. Why the picture is blurry, and a practical way to build a trustworthy view.

FintechAltisly Studio4 February 20263 min read
All posts

Ask a finance director how much cash the company has, and you will often get an answer that begins with "roughly". Roughly, because the balances sit in six bank accounts across three banks, two currencies and a payment processor, and the last time anyone added them up was Tuesday.

That is not a forecasting problem or a strategy problem. It is the first treasury problem: you cannot manage what you cannot see.

Why the picture is blurry

Cash visibility fails for ordinary reasons.

Accounts multiply. A new subsidiary, a new product, a payment provider that holds a balance for you. Each adds a place where money sits, and rarely does anyone remove the old ones.

Each bank shows its own view. Different portals, different cut off times, different export formats. Getting one picture means logging into several and copying numbers into a spreadsheet.

Balances are not the same thing as usable cash. The ledger balance may include items that have not cleared. Money in a processor wallet is yours but not yet in your bank. A figure that looks comfortable can hide a gap.

The data is stale on arrival. A morning spreadsheet is already out of date by lunch, especially when payments can move at any hour.

What good visibility looks like

You do not need sophistication to start. You need four things.

  • One list of every account and wallet the company controls, with an owner for each.
  • A balance for each, refreshed at a known time, with the source and timestamp visible.
  • A split between ledger balance and available balance where the bank provides it.
  • A single view in your reporting currency, with the exchange rate used written beside it.

That is a start. Many companies do not have it.

How to build it

Start with the inventory, and expect it to surprise you. Ask each team which accounts they use, then compare with what the banks say you hold. The mismatch is the first useful finding, and sometimes includes a dormant account that nobody has looked at in a year.

Next, automate the collection of balances. Banks offer several routes: statement files, reporting through standardised formats, and in some markets APIs. Which is available depends on the bank and country, so ask each one what they provide and how often. Automating even a daily pull removes the copying and the typing errors.

Then pick a rhythm. A daily position by a set time is a good first target. Intraday refreshes can follow, when your payment patterns need them.

Finally, put it where decisions are made. A visibility dashboard that sits in a corner of the finance system, and is looked at once a month, does not change behaviour. Put the balance in front of whoever approves payments.

What it makes possible, without the fuss

Once you can see cash, other things become possible, and they are much easier. Forecasting starts from real balances. Idle money in one account can cover a shortfall in another, instead of borrowing. Banks can be compared fairly, because you see what each really holds. Approvals get better, because a person can see whether a payment will leave the account short.

None of that works well on top of a blurry picture.

The caveats

Visibility has a ceiling. You cannot see what banks do not report, and some partners deliver data late or in a poor format. In some countries, access to automated reporting is limited, and manual steps remain. Be honest about which balances are live and which are estimates, and label them.

Do not overbuild at the start either. A well kept spreadsheet fed by a daily statement is better than an elaborate system nobody trusts.

Start with a list

Open a blank page and write down every account and wallet your company controls, with the balance and the date you last saw it. The act of finishing that list is often the most useful treasury work of the quarter.

TreasuryCash ManagementVisibility
A

Altisly Studio

Writing about systems architecture, operations software and what it takes to keep a build coherent, at Altisly.

Have a problem worth solving?

Tell us what is not working, what you are trying to build, or where you want to go next.

What happens next
01You describe the operation.
02We reply within one business day.
03If there is a fit, we tell you what the next step looks like.