Suppose a Treasury Manager knows with near certainty that the company will receive £5 million. That's valuable information, but it isn't enough to make a decision.
There's another question: When?
£5 million arriving tomorrow and £5 million arriving two weeks from now have exactly the same accounting value, but they can have completely different consequences for Treasury.
One might allow the organisation to meet upcoming obligations comfortably, while the other might require short-term borrowing.
One might offset a foreign currency payment naturally, but the other might arrive too late, requiring an FX transaction.
One might allow surplus cash to be invested. The other might leave cash sitting unnecessarily because Treasury cannot confidently commit it.
For Treasury, timing isn't supplementary information about a financial event.
It is part of the financial event.
Accounting Dates and Cash Dates
This creates an interesting problem.
Most accounting records already contain dates.
- Invoice date.
- Due date.
- Posting date.
- Accounting period.
So, it can appear that we already know when future cash events will occur.
But consider an invoice due on 30 September.
What does that date actually tell us?
It tells us when payment is contractually due. What it doesn’t tell us when cash will actually move.
- Perhaps the customer always pays on the following Friday.
- Maybe the invoice will be collected by Direct Debit three working days later.
- Or the customer routinely pays several days late.
- Pay runs only occur at month end.
- It could be there is an approval process that hasn't yet completed.
The due date is still correct. It simply answers a different question.
Due date is a contractual fact.
Expected settlement date is a financial expectation.
Treasury needs both.
The Difference Can Be Expensive
Imagine Treasury has €8 million of supplier payments due next Tuesday and there is also a €10 million customer receivable due on Monday.
Looking purely at due dates, the position appears straightforward. The expected receipt naturally funds the expected payments and therefore no action is required.
But suppose that customer historically pays seven to ten days late. The economic picture is now quite different. Treasury may need to obtain temporary Euro liquidity, or buy Euros, or delay another transaction.
The amount hasn't changed. The accounting records haven't changed. Only our understanding of timing has changed.
And that change can significantly affect cost and risk.
Sometimes There Isn't One Date
There's another complication.
We often represent expected financial events using a single date because databases and spreadsheets like single dates, but reality isn't always that precise.
Suppose a customer typically pays between five and nine days after due date.
Which expected settlement date should we use: due date, day five, day seven, or day nine? Any single answer introduces artificial precision.
Perhaps the more truthful representation is:
Expected settlement: 6–10 October
That tells Treasury something genuinely useful. That the receipt is expected within a window and as new evidence appears, that window might narrow.
- The customer approves the invoice.
- A remittance advice arrives.
- The payment is submitted.
Each event improves our knowledge of timing and eventually the expected window collapses into an actual settlement date.
Timing and Confidence Are Independent
This builds on another important distinction: timing and confidence are not the same thing.
Consider a customer with an impeccable payment record. We're highly confident that a £500,000 invoice will be paid, but their payment timing varies considerably.
We may therefore have:
High confidence in receipt: Low confidence in exact timing.
Now consider a potential contract.
If signed, the customer will make a £2 million deposit exactly five working days later.
We understand the timing very well, but we're not yet certain the contract will be signed.
So, we have:
Lower confidence in the event: High confidence in timing if it occurs.
Those are very different situations for Treasury and a useful financial model should be able to distinguish them.
Organisations Already Contain Timing Evidence
The interesting thing is that we often don't need to invent this information, the evidence about timing already exists throughout the organisation.
- Accounts Receivable tells us contractual due dates.
- Historical bank transactions tell us when customers actually paid.
- Accounts Payable tells us when supplier invoices are due.
- Payment runs tell us when the organisation actually intends to pay them.
- Contracts may specify milestones.
- Operations may know when delivery is expected.
- CRM may contain anticipated close dates.
- Procurement may know when commitments are likely to crystallise.
Each provides a different piece of timing evidence, the challenge is connecting them.
Learn From What Actually Happened
This is one reason connecting accounting information to bank settlement data is so interesting. Suppose;
ERP tells us: Invoice due: 1 September
Bank tells us: Payment received: 9 September
One transaction isn't particularly informative, but repeat that comparison across thousands of transactions and patterns begin to emerge.
- Maybe Customer A pays consistently seven days late.
- Customer B pays on the final working day of each month.
- Customer C pays invoices above £100,000 more slowly because they require additional approval.
- Perhaps a particular subsidiary only executes supplier payments on Tuesdays and Thursdays.
The contractual dates haven't become less useful we've simply acquired another layer of knowledge.
We can begin moving from: When should this settle?
towards: When does the evidence suggest it will actually settle?
That's Financial Intelligence.
Earlier Information Means Wider Windows
The same principle applies as we move upstream.
An invoice might allow us to estimate a settlement within a few days.
A signed contract might identify the likely month.
A sales opportunity six months earlier may only indicate a broad period.
That's perfectly acceptable. Earlier visibility naturally carries greater uncertainty.
We can’t solve that by pretending the uncertainty doesn't exist, but we should be recording and representing it.
For example:
- Sales opportunity: likely Q1.
- Contract signed: expected February.
- Delivery scheduled: 12–16 February.
- Invoice issued: due date 20 March.
- Remittance received: 22 March.
- Bank settlement: 22 March.
The financial event hasn't suddenly appeared at the end. Our understanding of its timing has progressively improved.
Don't Throw Away the Original Dates
Importantly, Financial Intelligence shouldn't replace source information.
If an invoice is contractually due on 1 October, that fact matters and we shouldn't overwrite it because we think the customer will pay on the 8th. Instead, retain both:
Contractual due date: 1 October
Expected settlement: 7–9 October
Confidence in receipt: High
Evidence: customer payment history, invoice status, current activity.
Now Treasury can see both the underlying fact and the interpretation and if the interpretation changes, we can understand why.
A Financial Event Is More Than a Number
Traditional financial reporting naturally emphasises amounts and that's appropriate when describing what has happened, but understanding what is going to happen requires more.
A future financial event has several characteristics:
Value: How much?
Timing: When?
Confidence: How certain are we?
Evidence: Why do we believe it?
All of those characteristics may evolve.
That's a much richer representation of the future than putting £5 million into a spreadsheet column labelled "October".
From Dates to Understanding
This doesn't require an enormous transformation programme. Start with what the organisation already knows.
- Take Accounts Payable and Accounts Receivable and keep their contractual dates.
- Compare those dates with actual settlements.
- Learn how counterparties really behave.
- Improve expected settlement timing.
- Represent uncertainty honestly.
- Then add earlier sources of timing evidence where they provide value.
The objective isn't perfect prediction, there will always be uncertainty.
The objective is to give Treasury a progressively better representation of the financial future based upon the evidence currently available because £5 million isn't simply £5 million for the person responsible for ensuring the right money is in the right place, in the right currency, at the right time:
£5 million tomorrow and £5 million next month are two completely different financial positions.
That's why Financial Intelligence needs to understand not only value and confidence. It needs to understand time. When we can do this better financial decision can be made.
