What a New CFO Always Finds in the First 90 Days

The pattern of inherited margin drift that surfaces when a new finance leader actually looks — and what it reveals about the controls they walked into.

A new CFO joins a $60M industrial manufacturer. Strong company. Clean financials on the surface. Good team. The previous CFO left on good terms.

Within 90 days, the new CFO has found something the previous one either never saw or stopped looking for. It is almost always the same thing.

Vendor spend that does not match vendor contracts.

Rate variances. Scope charges that were never authorized. Service-level credits that should have offset invoices but were never claimed. Payment term discounts negotiated years ago that the AP workflow has never once activated. In some cases, near-duplicate invoices paid months apart under different reference numbers.

The finding is not exceptional. It is consistent enough across CFO transitions at US mid-market industrial and manufacturing companies — in Texas, the Midwest, and the Southeast — that it has a pattern. New CFOs find it because they look. Incumbent CFOs often do not find it because the controls in place were never designed to surface it.

The question is not whether it exists. It is why it takes a leadership change to discover it.

“New CFOs find it because they look. The controls in place were never designed to surface it.”

What the First 90 Days Actually Look Like

A new CFO entering a mid-market industrial company typically spends the first 30 days in three places: understanding the business model, reviewing the balance sheet, and meeting the finance team. Standard onboarding.

Days 30 to 60 usually involve a deeper review of cost structure. This is where the pattern starts to emerge. The new CFO pulls vendor spend summaries, starts asking about contract terms, and requests to see actual contracts against actual invoices — often for the first time in years.

What they find in that comparison is not fraud. It is drift. Systematic, unmanaged drift that has been accumulating since the last time anyone ran the comparison — which in most cases was never, or was during the previous CFO’s first 90 days, two transitions ago.

This is not a story about a failing company. The manufacturer in this example is profitable, growing, and well-managed by any standard operational metric. The drift existed in parallel with a healthy business — invisible inside expense lines that looked unremarkable because they were compared only to budget and prior year, never to contract terms.

Why Incumbent CFOs Often Do Not Find What New CFOs Find

This is the uncomfortable part of the pattern. It is not about attention or capability. Incumbent CFOs at mid-market industrial companies are managing revenue cycles, capital allocation, banking relationships, M&A activity, and board reporting simultaneously. The granular reconciliation of vendor invoice terms against contract clauses is not a strategic priority. It becomes a background assumption: the controls are there, the ERP is running, AP is processing invoices — the system must be working.

The problem is that the system was never designed to catch this category of leakage. The ERP enforces PO tolerance. It does not enforce contract terms. The AP team validates invoices. It does not audit vendor compliance. Procurement negotiates contracts. It does not monitor whether those contracts are being honored at the invoice level.

Vendor invoice compliance — the systematic, ongoing comparison of contracted terms to actual invoices — falls between these three functions. It is designed out of the process at most mid-market industrial companies not through negligence, but through the natural division of labor between departments that each have clear mandates that stop just short of the gap.

No one owns the gap. So no one sees it.

“Vendor invoice compliance falls between AP, procurement, and finance. It is designed out of the process — not through negligence, but through the natural division of labor.”

The Institutional Memory Problem

There is a second dynamic that amplifies drift over time: institutional memory around vendor contracts degrades.

The CFO who negotiated a freight contract in 2021 at favorable lane rates understood exactly what was in it and why. Two years later, that CFO moved on. The new CFO inherited the contract but not the context. The AP team processes invoices against POs, not against contract terms they were never trained to reference. The vendor continues billing. Nobody compares.

Contract renewal dates pass. Escalation clauses trigger. Rates drift upward in small increments that are individually unremarkable but collectively significant. At a $75M manufacturer with 15 to 20 active service vendor contracts, each with a two-to-three year lifecycle, the average contract is likely operating in an enforcement gap of 12 to 24 months by the time anyone runs a systematic review.

A new CFO does not have institutional memory. That is an asset in this context, not a liability. They ask the basic questions. They pull the original contracts. They run the comparison. They find what the system was not designed to surface.

What This Means for Finance Process Architecture

The lesson from the new-CFO pattern is not that companies need more leadership turnover to catch cost leakage. It is that the comparison a new CFO runs in their first 90 days — contract terms against actual invoices, systematically, across all active vendors — should be a standing process, not a one-time event.

Finance leaders who have closed this gap permanently do three things differently. They treat vendor contracts as live operational data, not filed documents. They build a periodic contract-to-invoice comparison into the annual finance calendar — not as an audit triggered by suspicion, but as a routine control alongside budget review and close. And they separate the invoice approval function from the contract compliance function, so the two are not conflated inside AP’s existing workflow.

The result is that the margin drift a new CFO finds in their first 90 days gets found every 90 days — before it compounds, before it requires a leadership transition to surface it, and before it has been accumulating undetected for 18 months.

For most US industrial and manufacturing companies in the $30M–$150M range, this process does not exist today. It is not because it is expensive or complex to build. It is because the urgency to build it has never been created by the current controls — which, by design, do not surface what they cannot see.

A new CFO finds it because they bring fresh eyes to a comparison that should have been running all along. The real question for every incumbent finance leader is: what would you find if you ran the same review this quarter — and what has been accumulating while you haven’t?

Data/Evidence: Typical 90-day finding pattern — new CFO, $80M Texas industrial manufacturer: Week 3: Pulls freight spend vs. contracted carrier rates. Finds 6 of 8 carriers billing above contracted lane rates. Week 5: Reviews maintenance contract portfolio. Identifies 3 vendors with unauthorized scope charges recurring monthly. Week 7: Requests SLA performance data from operations. Matches against contract penalty terms. Finds $44,000 in unclaimed credits across two vendors. Week 9: Reviews payment term configuration in ERP. Confirms early-pay discount workflow inactive for 4 vendors with discount clauses. Week 11: Runs near-duplicate invoice check across 90 days of AP data. Surfaces 5 near-duplicate pairs totaling $31,400. Total annualized margin drift identified: $318,000 Time the previous controls would have surfaced this: Never.

Data/Evidence: What a standing vendor contract compliance process looks like in practice: Quarterly: Contract-to-invoice comparison across all active service, freight, and maintenance vendors Monthly: Near-duplicate invoice check across the prior 30 days of AP data At every contract renewal: Full rate and term reconciliation before signing the next period At every invoice above a defined threshold: Automated rate verification against contracted terms Tools required: The contract (as structured data). The invoice data (from existing ERP export). A comparison engine. Tools not required: Enterprise procurement software. ERP integration. Additional headcount.

Data/Evidence: If you are a CFO or finance leader at a US industrial or manufacturing company ($30M–$150M revenue): ValueXPA runs a Margin Drift Diagnostic that quantifies margin drift across freight, maintenance, contracted labor, and professional services — using 90 days of your own AP and contract data. If we find less than $50,000 in systemic drift, you pay nothing. If we find more, the fee is $10,000–$15,000. 2–4 weeks. 2–4 hours of your team’s time. No ERP integration required. Visit valueXPA.com or contact us directly.