Enterprise Resource Planning systems have transformed modern business.

  • They manage orders.
  • They control purchasing.
  • They maintain ledgers.
  • They process invoices.
  • They provide the financial records upon which organisations depend.

For many companies, the ERP has become the operational backbone of the business.

So, when finance teams struggle to answer a financial question, the natural response is often:

"Surely the ERP should be able to tell us?"

Sometimes it can, sometimes it can't and I think the distinction matters.

Consider this question: "What is our cash position likely to be six weeks from now?"

It sounds like a financial question, but it isn't really an accounting question.

And that's the problem, an ERP is exceptionally good at recording things the organisation knows formally.

  • An invoice has been issued.
  • A purchase order has been approved.
  • A journal has been posted.
  • A customer owes £250,000.
  • A supplier is due £80,000.

These are facts.

But tomorrow's cash position depends upon much more than recorded accounting facts. It depends upon what happens next.

An invoice isn't the same as cash

Suppose the ERP shows that a customer invoice for £1 million is due next Friday.

From an accounting perspective, that's perfectly clear.

From Treasury's perspective, there are several other questions.

  • Will the customer actually pay next Friday?
  • Do they normally pay on time?
  • Has the customer disputed anything?
  • Has delivery been completed?
  • Is contractual acceptance still outstanding?
  • Has Sales heard anything that changes our expectations?
  • Is the £1 million going to arrive as one payment or several?

The ERP may correctly report: £1 million due Friday.

Treasury may reasonably conclude: £1 million is more likely to arrive the following Wednesday.

Neither is wrong. They're answering different questions.

The same problem exists before an invoice is created

It becomes even more interesting if we move further upstream.

Imagine Sales closes a major deal today.

The contract is being prepared.

Payment will eventually be made in US dollars.

There may be a sizeable future FX exposure.

But perhaps nothing has yet happened that requires an accounting entry.

From the ERP's perspective, there may be very little to report.

From the organisation's perspective, something financially significant has just happened.

The business has new information about its future.

The accounting system simply isn't the place where that information currently lives.

That's not an ERP failure

This point is important.

ERP systems were never designed to understand everything happening across an organisation. They were designed to manage and record defined business processes and they do that extraordinarily well.

The mistake is expecting a system of record to become a system of prediction simply because it contains financial data.

Recording the present and understanding the future are different jobs.

Future liquidity is created outside Finance

Think about everything that can alter next month's cash position.

  • Sales wins a contract.
  • Procurement commits to a major purchase.
  • HR approves fifty new hires.
  • Legal agrees a lease.
  • Operations delay a delivery.
  • A customer disputes a milestone.
  • A supplier changes its payment terms.
  • Treasury arranges a new funding facility.

All of those events have financial consequences, some of which will eventually reach the ERP, but they may reach it days, weeks or months after the organisation first became aware of them.

That's important because financial decisions often need to be made in the meantime.

So, what are finance teams doing today?

Usually, they're bridging that gap themselves.

They extract information from the ERP, then they add knowledge from elsewhere.

  • Sales forecasts.
  • Treasury forecasts.
  • Spreadsheets.
  • Email.
  • Meetings.
  • Departmental reports.
  • Management assumptions.

The resulting forecast isn't really an ERP report at all. It's an attempt to create an organisation-wide understanding using the ERP as one of several sources, which is why these processes remain so manual.

The difficult part isn't extracting the ledger.

The difficult part is connecting it to everything else the organisation knows.

Business Intelligence helped, but only partly

Business Intelligence platforms made an enormous improvement.

They enabled organisations to bring information from multiple systems together and visualise it, but most BI remains fundamentally concerned with reporting data.

It can tell us:

  • what invoices are outstanding;
  • what sales have occurred;
  • what purchases were made;
  • what trends exist.

The next problem is more subtle, we need to understand the relationships and uncertainty between those records.

  • Is this opportunity related to that contract?
  • Did this contract produce these three invoices?
  • Did this payment settle those five invoices?
  • How likely is the next payment to occur?
  • When is it genuinely expected?
  • What happens to liquidity if it slips by ten days?

Those aren't simply reporting questions, they're questions of financial understanding.

A different layer

Perhaps, then, we shouldn't try to make ERP systems solve this problem.

Perhaps we need a layer above the operational systems.

One that accepts that:

  • ERP owns accounting records;
  • CRM owns commercial activity;
  • Procurement owns purchasing;
  • HR owns workforce information;
  • Treasury owns treasury activity;
  • banks confirm actual cash.

And then asks: "What do these systems collectively tell us about the organisation's financial position?"

That's a very different architectural responsibility.

From systems of record to Financial Intelligence

For decades, enterprise software has been primarily concerned with establishing reliable records and that remains essential.

But increasingly, organisations also need to understand the financial consequences of activities before all of those activities become accounting records.

That requires connecting information, understanding relationships, representing uncertainty, understanding timing and continually refining the picture as new evidence appears.

That's the role I think a new category of software can fulfil.

Financial Intelligence.

Not a replacement for ERP.

Quite the opposite.

A way of making the information already held within ERP together with information elsewhere in the organisation substantially more useful, not just to Treasury but all departments within a business.

The question therefore isn't: "Why can't our ERP tell us what's going to happen?"

Perhaps the better question is: "Why would we expect a system designed to record what has happened to understand what will or may happen next?"

And once we ask that question, the missing layer in enterprise software becomes much easier to see.

ERP tells us what the organisation has recorded. Financial Intelligence helps us understand what the organisation already knows.

Continue exploring Financial Intelligence Back to all articles