The Gap Nobody Manages: What Happens to Approved Invoices Before They're Paid

Most finance teams have spent the last decade improving how supplier invoices move through Procure to Pay. Receipt is faster, matching is tighter and approval is governed, auditable and visible. By the time an invoice is approved, liability is clear, controls are satisfied and everyone agrees what is owed and why.

And then something interesting happens. Nothing fails. Nothing breaks. The invoice simply waits to be paid.

In many organisations, approval is treated as the end of the finance conversation rather than the beginning of one. Once approval is complete, payment follows a preset path. Fixed terms, fixed methods and fixed calendars. With execution happening later, largely out of sight and largely unchanged by whatever else is happening in the business at the time. This creates a quiet structural gap. Not between good and bad practice, but between control and intent.

It is easy to miss because everything appears to work. Suppliers are paid. Obligations are met. Cash flows. There are no red flags demanding attention. Over time, the way approved invoices are paid becomes inherited behaviour rather than an explicit design choice. What sits inside that gap is not inefficiency, but discretion.

By default, or by design?

Approved invoices represent a moment of confirmed obligation and governance. At that point, many organisations already have more control over when cash leaves the business and how it is settled than they actively exercise. That control is often constrained less by policy than by intent. Shaped instead by habit, tooling and the assumption that payment execution is simply an administrative endpoint.

A gap by default typically looks like this: once an invoice is approved, it is queued and paid according to static rules, regardless of cash position, supplier preference or wider working capital considerations.

A gap by design looks different. The obligation is still honoured, controls are unchanged, but the organisation has made a conscious decision about how much discretion it wants to retain over timing, method and settlement, and when it is appropriate to use it. The difference is not sophistication, but awareness.

Suppliers don't treat payment as passive

Meanwhile, suppliers do not treat payment as passive. Across most supply chains, suppliers actively trade value for access to cash through overdrafts, factoring, supply chain finance and card acceptance. These decisions are often made invoice by invoice, driven by their own liquidity pressures rather than by the buyer's payment intent.

Crucially, much of this activity happens outside the buyer's visibility and beyond their governance boundary. That has implications not just for cost of capital across the supply chain, but for supplier resilience, relationship dynamics and risk exposure. In effect, liquidity decisions are being made on the buyer's behalf, without the buyer ever being part of the conversation.

The result is not a process failure. It is a design choice that has never quite been named.

How this shows up

For finance leaders, this usually shows up indirectly. Cash feels noisy. Trade-offs feel increasingly uncomfortable. Each lever solves one problem while creating another, creating a sense of managing consequences rather than shaping outcomes.

For finance operations teams, it shows up as pressure. Disputes recur. Credits repeat. Controls multiply because inputs cannot always be trusted. Payment itself becomes something to get through rather than something to think about.

None of this implies that anything is wrong. In many organisations, the current approach may be entirely appropriate. Doing nothing remains a valid outcome.

The more useful question is simpler and harder to answer.

Is the way approved invoices are paid a deliberate decision in your business, or just habit?

Why this matters more in 2026

That question matters more in 2026 than it did before. Volatility is no longer episodic. Liquidity and working capital are increasingly treated as strategic levers rather than operational outcomes. Finance leaders are placing greater value on optionality. The ability to adjust without committing to structures that are slow or painful to unwind.

In that context, payment execution is being examined more closely, not as something to optimise, but as something to understand and consciously position within a broader capital strategy. This is not a configuration change, and it is not a programme waiting to be launched. In complex, high-volume environments, even small shifts in intent have material operational implications. Which is precisely why the question needs to be named before it is acted on.