Spend is Happening. Visibility Isn't. Fix Your S2P Operating Model.

Your procurement team approved the process. Nobody told the business that.

Money is leaving your organization right now through channels your procurement team cannot see. Not because controls don't exist - they do, on paper, in policy documents, in the ERP that someone spent 18 months implementing. But between the policy and the purchase, there is a gap filled with shadow spend, maverick buying, and suppliers your legal team has never heard of. The system isn't broken. The operating model around it is.

The visibility problem isn't a technology problem.

The instinct, when spend data is fragmented or missing, is to buy another tool. A new analytics layer. A better dashboard. A spend cube someone will look at quarterly and then quietly ignore. But the root cause of poor S2P visibility is almost never a lack of software. It's a lack of clarity about who owns what at each stage of the process - and what "good" looks like when it happens.

Source-to-pay is a chain: sourcing, contracting, purchasing, receiving, invoice matching, payment. When the operating model is vague, each link in that chain is owned loosely by different teams with different incentives. Finance wants clean invoices. Procurement wants preferred suppliers. The business unit wants speed. Nobody is explicitly accountable for the integrity of the whole. Visibility collapses in the gaps between those incentives.

Maverick spend is a symptom, not the disease.

Most procurement leaders know their maverick spend number, or at least they have an estimate they present with appropriate embarrassment in steering committees. What fewer organizations ask is why the maverick spend exists. The honest answer is almost always the same: it's faster and easier to go off-contract than to use the approved process.

When a business unit bypasses procurement, they're not being reckless. They're being rational. They have a deadline, a supplier who picks up the phone, and a process that asks them to raise a requisition, wait for approval, go through a sourcing event, and sign a contract - for something they needed three weeks ago. Until the approved process is genuinely easier than the workaround, the workaround will win. Every time.

Your S2P operating model is probably built for compliance, not adoption.

There's a distinction that most procurement functions miss between a process that is theoretically correct and one that people actually use. A compliance-driven operating model is designed to satisfy an audit. It has the right controls, the right approval thresholds, the right segregation of duties. What it often doesn't have is a user experience that anyone outside of procurement would voluntarily choose.

The organizations that get visibility right design their S2P model with adoption as the primary goal. Controls are still there - but they're embedded into a process that's faster, clearer, and less painful than the alternative. The requisition-to-order journey takes hours, not weeks. Catalogues are current. Approvals are mobile-enabled. The path of least resistance runs through the system, not around it.
‍

Data fragmentation is where operating model failures hide.

Even when the front-end process works, visibility can break down in the middle and back of the process. Purchase orders that don't match invoices. Invoices that arrive outside the system. Contracts that live in someone's email. Suppliers that exist in three different master data records with three different payment terms.

This fragmentation isn't accidental. It's the cumulative result of acquisitions, system migrations, regional autonomy, and years of workarounds that hardened into normal practice. No dashboard can fix it because the underlying data isn't trustworthy. You can't get visibility into spend that's been miscoded, misrouted, or never entered the system at all. The operating model has to address master data governance, supplier onboarding standards, and invoice submission requirements as seriously as it addresses sourcing strategy.
‍

Three questions that expose where your operating model is actually failing.

Before redesigning anything, it helps to be precise about where the breakdown is. Is it upstream - in sourcing and contracting, where preferred suppliers aren't being selected or contracts aren't being signed before spend begins? Is it midstream - in purchasing, where the requisition and PO process is so slow or complex that people route around it? Or is it downstream - in AP and payment, where invoice exceptions, coding errors, and approval bottlenecks mean that even spend that started correctly ends up as noise in the data?

Most organizations have problems in all three places. But they're not the same problem, and they don't have the same fix. Upstream failures need category management discipline and contract coverage. Midstream failures need process redesign and technology that actually serves the buyer. Downstream failures need invoice automation, three-way matching that works, and a supplier base that's been properly onboarded.
‍

The CFO conversation has changed. Procurement hasn't caught up.

Finance leaders are under more pressure than they've been in a decade to demonstrate that spend is controlled, that commitments are visible before they become liabilities, and that working capital is being actively managed rather than passively reported. That's a procurement conversation. It's also a conversation that procurement functions rarely lead, because they're still presenting backwards-looking spend analytics rather than forward-looking commitment data.

The shift from reactive reporting to proactive spend intelligence is an operating model decision, not a technology one. It requires procurement to own committed spend before it becomes actual spend - to have line of sight into what's been contracted, what's been requisitioned, and what's likely to hit the P&L in the next 90 days. That's not something a better dashboard delivers. It's something a better operating model makes possible.
‍

Fix the model before you fix the tools.

Every major S2P platform vendor will tell you their software solves the visibility problem. Some of them are even right - for the slice of spend that flows cleanly through a well-governed process. But software deployed on top of a broken operating model doesn't create visibility. It creates faster, more expensive confusion.

Get the ownership model right first. Clarify who is accountable for each stage, what the handoff criteria are, and what happens when something falls outside the process. Then simplify the process until adoption is the path of least resistance. Then govern the data with the same rigor you'd apply to any other financial asset. After all of that, your technology investment will actually deliver what it promised on the implementation slide deck.

Spend is happening. It will keep happening. The question is whether your operating model gives you any real ability to see it, shape it, and account for it - or whether you find out what your suppliers know three months later, when the invoice lands.