The consequences of inherited spend

By the time AP receives an invoice, leakage may already be built into the transaction.

The purchase has happened.

The supplier has been selected.

The terms have been agreed upon.

The invoice simply reveals the outcome of decisions made earlier.

That’s inherited spend.

And it limits what finance can do to prevent margin erosion.

Maverick buying erodes negotiated savings

Organizations invest significant effort in negotiating better supplier terms.

But those savings only matter if employees actually buy through the agreed upon channels.

Research cited in the chapterfrom the Hackett Group shows organizations lose as much as 16 percent of negotiated savings to maverick buying.

For a company expecting $10 million in negotiated savings, that could mean between $500,000 and $1.6 million disappears before AP ever processes an invoice.

The problem is not that AP processed the invoice too slowly.

The problem is that finance didn’t have enough visibility when the commitment was made.

Automation doesn’t automatically equal control

Automating invoice capture has obvious benefits.

It can eliminate repetitive keying and accelerate invoice processing.

But speed alone doesn’t protect margin.

If the organization never controlled the underlying purchase, the invoice can move through the process quickly and still represent:

An off-contract purchase  An unauthorized commitment  An incorrect unit cost  A supplier choice that ignored negotiated terms

Finance may simply process the wrong transaction more efficiently.

Connect purchasing to payment

Preventing inherited spend requires connecting the points where financial decisions happen.

Purchasing → Approval → Purchase order → Receiving → Invoice → Payment

When those steps remain connected, finance can validate the invoice against the original commitment.

It no longer has to ask:

Who approved this?  Was this the agreed price?  Did we receive the full order?  Was this supplier authorized?

The answers are already part of the transaction.

Control should happen before cash leaves

Reactive AP processes discover errors after the fact.

A duplicate appears during reconciliation.

A pricing mismatch is noticed after payment.

A missing approval surfaces when someone starts investigating an exception.

At that point, the organization is trying to recover value it should never have lost.

The objective should be prevention.

The earlier finance sees the commitment, the more opportunity it has to question unexpected spend, correct policy failures, and protect margin before cash leaves the business.

That’s why AP cannot begin with the invoice.

It begins with the decision to spend.