Ask who owns an organisation's financial information and the obvious answer is probably Finance.

Ask who owns its cash and the answer might be Treasury.

But ask who owns the information that determines the organisation's future financial position and the answer becomes much less obvious. In reality, that information is distributed throughout the business.

Sales knows about future revenue.

Procurement knows about future expenditure.

Legal knows about contractual commitments.

HR knows about future people costs.

Operations knows whether goods and services will actually be delivered when expected.

Finance knows what has reached the accounting system.

Treasury knows what has reached or is expected to reach cash.

Each department owns part of the financial story. The problem is that nobody necessarily sees the whole story.

Financial Events Begin as Business Events

We tend to think about financial events in terms of invoices, payments and accounting entries. But most financial events don't begin in Finance.

Consider a customer payment. The final event might be £500,000 arriving in a bank account, but its story may have started months earlier.

Sales identified an opportunity. A quotation was issued. The customer agreed to proceed. Legal negotiated a contract. Operations delivered a product or service. Finance raised an invoice. The customer approved it. Treasury eventually saw the cash arrive.

What appears on the bank statement as a single £500,000 receipt is actually the final stage of a much longer business process and at every stage, the organisation knew something about the eventual financial outcome.

The certainty may have changed, the expected timing may have changed, the amount may have changed.

But the financial story existed long before the cash did.

Different Departments See Different Parts

The difficulty is that each department naturally views that story through its own responsibilities.

Sales might ask: Is the customer going to buy?

Legal might ask: Can we agree acceptable contractual terms?

Operations might ask: Can we deliver this on time?

Finance might ask: Can we raise the invoice?

Treasury might ask: When will the cash arrive?

These aren't separate stories. They're different perspectives on the same underlying financial lifecycle. Yet our enterprise systems frequently treat them as unrelated records.

The CRM contains an opportunity. The contract management system contains an agreement. The ERP contains an invoice. The bank contains a transaction.

Humans understand intuitively that these things may all be connected. Our systems often don't.

The Problem Gets Harder in the Real World

Real businesses are rarely as tidy as diagrams suggest.

One contract may generate dozens of invoices, one invoice may be settled by several payments and one customer payment may settle several invoices.

Purchase orders change. Invoices are disputed. Contracts are renegotiated. Delivery dates slip. Customers pay early. Customers pay late.

Amounts change because of foreign exchange movements, credits or adjustments.

Even identifiers may not survive the journey intact.

The customer name in the CRM may not exactly match the legal entity on the contract. The invoice may use a different account identifier. The bank payment may contain only an abbreviated reference.

The financial story is still there, but reconstructing it requires understanding relationships, not merely matching database fields.

Why This Matters to Treasury

Treasury sits unusually close to the end of many of these financial stories. By the time Treasury sees a bank transaction, uncertainty has disappeared. The payment has already happened.

But that certainty comes at a price: it arrives very late. The greatest opportunity for improving financial visibility therefore lies upstream.

If Treasury can understand financially significant events as they develop elsewhere in the organisation, it gains earlier visibility of future liquidity and risk.

A signed contract may provide strong evidence of a future receipt months before an invoice exists.

A delayed project milestone may indicate that the expected receipt will move into the following month.

A customer dispute may reduce confidence that an invoice will settle on its due date.

A large purchase commitment may reveal future FX exposure before a payment instruction exists.

None of this requires Treasury to take ownership of Sales, Legal, Procurement or Operations, but it does require the financial consequences of their activities to become visible.

One Organisation, Many Perspectives

Creating a common financial understanding does not mean every department needs the same screen, report or workflow. They don't.

Sales may want to know which apparently successful deals repeatedly fail during contracting.

Legal may want to understand the financial consequences of contractual changes.

Procurement may care about future commitments.

Treasury may care about liquidity and FX.

The CFO may simply want to ask: Is there anything I need to know about today?

The underlying information can be shared while the perspective remains appropriate to each role.

That is very different from attempting to force the entire organisation into one application.

Connecting Rather Than Replacing

This is why I don't think the answer is another enormous enterprise system attempting to own every business process. The specialist systems already exist and many of them are excellent.

The opportunity is to connect the financially significant information within them.

CRM should continue to manage customer relationships.

ERP should continue to manage accounting and operations.

Contract systems should continue to manage contracts.

Treasury systems should continue to manage treasury.

The missing capability is understanding how the events recorded within those systems relate financially to one another and presenting the information to the relevant people.

From Departmental Information to Financial Intelligence

Once those relationships can be understood, something changes.

A sales opportunity is no longer merely a CRM record.

It becomes early evidence of a possible future cash event.

A signed contract strengthens that evidence.

An invoice strengthens it again.

A customer dispute may weaken confidence or change the expected timing.

A bank transaction finally confirms what happened.

The organisation hasn't created more information. It has connected the information it already possessed.

And that is the distinction I think matters.

Financial Intelligence isn't about moving ownership of information into Finance or Treasury.

It's about recognising that financially significant information is created throughout the organisation and making its consequences understandable to the people who need them.

For decades we've organised enterprise software around departments and business processes and that made enormous sense. But money doesn't respect departmental boundaries.

A financial outcome may begin in Sales, change in Legal, depend on Operations, appear in Finance and finally complete in Treasury. Perhaps our financial understanding should be able to make the same journey.

Every department owns part of the financial story.

Financial Intelligence is what happens when we finally connect those parts.

Continue exploring Financial Intelligence Back to all articles