Why Spend Visibility Doesn’t Equal Control Anymore

For years, finance leaders equated visibility with control: 

• If you could see the data, you could manage it 
• If you had dashboards, you had oversight 
• If reports were flowing, the system was working 

But in today’s operating environment, visibility alone is no longer enough. Because seeing spend is not the same as governing it. And governance is not the same as operational control. 

Understanding the difference is what separates reactive finance from strategic finance. 

Achieving Total Spend Visibility: How to See What Already Happened 

Increasing visibility into spending answers one question: What occurred? Dashboards show trends. Reports show variance. And analytics show patterns over time. 

This means that visibility is retrospective. It tells you where money went. And that matters, because you can't manage what you can’t see. 

But visibility is passive. It doesn’t: 

• Prevent out-of-policy purchases. 
• Enforce compliance in the moment. 
• Shape employee behavior upstream. 

It simply reflects spending activity after the point of transaction.

In a slower operating cycle, that may have been enough. But in a compressed, digital, AI-accelerated environment, it simply isn’t. 

Governance: Designing the Rules of a Spend Management System 

Governance answers a different question: How should spend behave? We know that governance defines policy... 

• It establishes approval structures. 
• It sets guardrails and thresholds. 
• It creates accountability frameworks. 

Governance matters. In fact, it is the foundation of responsible spend management. Jonathan Steele, a Product Manager at Motus explains: 

“It is very important that companies have the right type of policies, programs, and awareness in place to identify what that risk may be, and also to catch it before it becomes too much of an issue." 

He’s right. Clear policies and defined programs are essential for identifying risk early. But governance still lives at the policy level. And policy on paper does not equal enforcement in practice. 

Many organizations have governance documentation that looks strong in theory but breaks down in execution because systems do not enforce it consistently. Governance without operational control becomes theoretical. 

And yet, theory does not protect your organization’s margin. 

Operational Control: Engineering Outcomes in Motion 

Operational control answers the most important question: Is the system designed to enforce the right behavior in real time? 

Operational control is not about adding more oversight. It is about embedding policy directly into the system itself. 

As one SAP Concur partner and Co-owner of HR Campus, Philippe Dutkiewicz, explains: 

“If you digitalize [your policy] in the system, then it’s only then visible to your employees when it should show... If somebody does something that is not according to policy, the policy basically becomes invisible.” 

In other words, policy cannot live as static documentation. It must live inside the workflow. 

Operational control is embedded. It operates at the point of action — not after the fact. 

Dutkiewicz expands: 

“Have these rules in your systems and let the system work for you — and make the process clean and easy for your employees... you can keep the hurdles low, put a lot of trust in your employees, and still implement control at the end of the process.” 

This is the meaningful shift. Control doesn't have to mean friction. Governance doesn't have to mean bureaucracy. 

When policy is engineered into the system, the right behavior becomes the easiest behavior. That’s what turns governance from theory into architecture. In practice, that means: 

• Automating approvals 
• Flagging risk before reimbursement 
• Enforcing compliance at the point of transaction, not after the fact 

This is the difference between observing spend behavior and architecting it. Control isn’t just seeing what already happened. It’s putting the right guardrails in place so spend happens correctly in the first place. 

Ryan Hamilton, a Value Consultant at SAP Concur, illustrates this from an operational lens: 

“Look at how many expense reports the average processor is touching, what percent of receipts they are looking at, and how many are flagged as an exception.” 

But the deeper question is this: 

“Of those, how many get reworked before they are ultimately approved, and how many are just sent through? You want to examine how your system is set up and determine whether all those touch points are actually adding value.... or if they exist just because they exist.” 

The issue isn’t how visible your process is. It’s whether your process was engineered intentionally. Every unnecessary touchpoint introduces cost, delay, and risk. 

Operational control doesn’t mean more review. It means fewer, smarter interventions built into the system itself. 

Why Dashboards Are No Longer Enough 

CFOs today are operating in an environment defined by: 

• Distributed workforces 
• Decentralized purchasing 
• Subscription sprawl 
• AI-accelerated procurement cycles 
• Increasing regulatory pressure 

The volume and velocity of spend have changed. 

Nathanael L’Heureux, the Chief Client Officer at Oversight, mentioned that: 

“LLMs are no good at analyzing financial data, but there are a lot of machine learning tools that are excellent at both predicting the future… and identifying abnormalities and fraud detection.” 

So, while dashboards were built for monitoring, now, modern enterprises desperately need spend architecture to keep up.  

This is even more true when spend moves faster than review cycles, reporting becomes a lagging indicator of risk. And lagging indicators don’t prevent exposure. 

They only document it. 

Spend Management as Architecture 

Forward-looking finance leaders are reframing spend management from reporting to design. Because the goal isn’t to make control more restrictive. 

It’s to make it smarter – and easier. As Philippe Dutkiewicz notes: 

“You can make life easier for your employees, you can show how much trust you give your employees. And obviously, you can also think about how you provide a good user experience.” 

This is the shift. Instead of asking: How do we track spend better? Savvy companies are asking: How do we structure spend so it behaves correctly by default? 

And that's where operational control becomes a strategic leverage. Spend architecture embeds: 

• Policy into workflows 
• Compliance into automation 
• Visibility into real-time systems 
• Accountability into design 

That means control becomes proactive, rather than reactive. Governance becomes enforceable, rather than aspirational. And oversight moves from observation to intentional design. 

Compliance Is a System Design Problem 

Up to this point, we’ve discussed visibility, governance, and operational control as structural differences. But there is another layer to this conversation — and it’s cultural. 

Because when compliance fails, most organizations instinctively look at people. They assume: 

• Employees aren’t paying attention. 
• Policies aren’t being followed. 
• And more monitoring is the answer. 

But what if compliance breakdown isn’t a behavior problem? What if it’s a design problem? 

Too often, when policy isn’t followed, organizations respond with more monitoring, more reminders, and more enforcement. But enforcement is a lagging solution. 

A Senior Manager at Deloitte, Oren Geshuri, challenges this assumption directly: 

"One of the myths around compliance is that it is a one-way street… If you’re constantly having to monitor people because they’re doing things wrong, that’s not a problem with your people. That’s a problem with you — the language in your policy, how it is conveyed, or the feasibility of what you’re asking them to do.” 

Compliance, in other words, is not enforcement layered on top of a broken process. It is feedback on whether your system is working. 

If policy lives in a PDF, compliance becomes reactive. If policy lives in the workflow, compliance becomes automatic. Architecture determines behavior. And behavior determines control. 

The Shift from Insight to Infrastructure 

Visibility provides insight. Governance provides intention. And operational control provides infrastructure.  

That distinction matters. 

Because insight tells you what happened. Intention tells you what should happen. And infrastructure determines what actually does happen. 

The companies that outperform in the next era of finance will not simply have better dashboards – they will have better-designed systems. Systems that: 

• Reduce friction for employees while protecting margin. 
• Align people, policy, technology, and behavior. 
• And transform oversight from observation into architecture. 

Because in a world defined by speed and decentralization, observation is no longer enough. 

Rethinking Spend 

If you’re ready to move from reporting on spend to architecting it, it may be time to rethink how your systems are built. Modern spend management replaces oversight with infrastructure that makes the right behavior the default.

Watch how SAP Concur uses AI to help organizations embed governance directly into workflows — so visibility becomes the outcome of control, not the substitute for it.