Chapter 3: How Process Intelligence Changes the Game
Emma’s job in the CFO office wasn’t meant to be investigative. As an FP&A analyst, her role was to analyze trends, support forecasting, and help explain the “why” behind the numbers. But when the numbers didn’t add up—when actual spend started creeping above budget in strange ways—Emma did what many analysts do: she started digging.
It wasn’t long before she spotted a pattern. A vendor invoice had been paid twice. Then another. They weren’t identical—different approval timestamps, slightly different vendor IDs—but the amounts were the same. The descriptions too.
At first, the team chalked it up to human error. A fluke. But Emma wasn’t so sure. She began pulling more invoices. And while she couldn’t prove it was systemic, she could prove it was expensive. Over $200,000 lost in one quarter to duplicate payments.
Emma raised the issue, and the team decided to test a new approach: Process Intelligence.
Gori von Hirschhausen: Looking at the reality of companies these days, we have some that are very much data-driven, but we still have a lot of companies where you do need to understand the danger of half-truths that constitutes so much conventional wisdom in these companies. What do I mean by this? Looking at process intelligence. When we do as a consultant company, when we have an engagement and we are asked how to optimize a certain function, we of course take a look at the processes. And what we then learn is when we speak to the people about these processes, they have a certain understanding of the process. But if you look into the facts, if you look into the data, you will see that there's a difference. And it's so important to really understand what the truth is, to really understand what the process standards are that you design, but then what the reality of the process flow looks like.
PI helped Emma aggregate and compare information from across IT systems and departments. Data was scattered across SAP, Workday, and Oracle.
But the team could start to see patterns that previously took weeks to unearth. Duplicate payments were suddenly traceable. And root causes began to emerge—Emma found out that there were misaligned vendor records and inconsistent naming conventions. Those were things that Emma suspected, but they now surfaced in black and white.
Process Intelligence didn’t automatically solve the problem. It surfaced it. It showed where the fires were—but the team still had to put them out. Emma’s team had to redesign controls, and clean vendor master data.
Gori von Hirschhausen: This shift goes from more data transactional work to more thinking, advising, consulting work.
Emma did what she’d done from the beginning—she kept digging. She paired process intelligence with context. She traced exceptions and shared evidence, and she drove awareness with the business on the real impact of duplicate payments.
Martin Wolleswinkel: When it comes to driving down cost out of the organization, especially for a CFO in the, let's call it transactional site, it could be transactional finance processes, procurement processes, that are also often part of the CFO's remit, and for that, without process intelligence, they will have, like we discussed before, either to put a ton of effort and people on it, which they don't have anymore. So that's why it's so adamant that process intelligence provide platform to drive out costs for them.
Emma hasn’t stopped questioning things.
Process Intelligence is a tool for Emma to investigate on the business—it’s a better lens for our microscope and the telescope.
Suddenly, the CFO isn’t just reacting to what happened last quarter. Leakages like our duplicate payments can be stopped before the damage is done.
PI hasn’t solved everything. But it’s changed how the CFO works —and more importantly, how they see.