First 100 Days for a New Manufacturing CFO

Executive Summary

A new CFO at a $100M+ industrial manufacturer walks into a cost structure nobody has fully audited in years. Freight contracts renew on autopilot, staffing agencies bill against rate cards nobody rechecks, and the price file in the ERP is only as current as the last manual upload. None of this shows up as fraud.

It shows up as normal-looking invoices that quietly diverge from the underlying agreement, invoice by invoice, month by month.

The mechanism is simple: contracts live in PDFs, invoices live in the ERP, and nothing forces the two to reconcile line by line. AP pays against a purchase order and a receipt, not against a rate card's escalation clause or a rebate threshold. That gap does not close itself.

What changes it is sequencing: get spend visibility first, run a fixed-scope diagnostic before committing to any renegotiation or system project, then build the control that prevents the same drift from re-accumulating. Skipping straight to a renegotiation without first quantifying the leakage means negotiating against a number nobody can defend.

1. What should a new manufacturing CFO prioritize in the first 100 days?

Prioritize spend visibility before any renegotiation, headcount change, or system project. Pull every service vendor contract and match it against 12 to 18 months of invoices before deciding where to cut. A CFO who renegotiates freight or staffing rates before seeing where the current contracts are already being violated is negotiating against the wrong baseline, and usually leaves money on both sides of that conversation.

The instinct in a new seat is to act fast and visibly. Cut a vendor, renegotiate a rate, announce a win in the first board meeting. That instinct is usually pointed at the wrong target.

Before any of that, get a clean picture of what is actually being paid against what was actually agreed. Contracts for freight, contract labor, maintenance, and professional services all carry terms: rate cards, minimum volume commitments, rebate clauses, surcharge schedules, not-to-exceed caps. Invoices rarely get checked against all of them.

A new CFO does not need to build this visibility from scratch internally in month one. A fixed-scope engagement can produce it in weeks rather than quarters, which matters when the board is waiting on a first-90-day narrative.

2. How does margin drift accumulate without anyone noticing?

It accumulates because AP's controls check different things than a contract does. Three-way matching confirms the invoice matches a purchase order and a receipt. It does not test whether a fuel surcharge expired, whether a rebate threshold was crossed, or whether a labor rate matches the master service agreement.

Each of those checks requires the contract text itself, which usually sits outside the ERP.

A surcharge added during a temporary condition, a fuel spike or a capacity crunch, gets coded once and then billed every month after, whether or not the condition that justified it is still true. Nobody removes it because removing it is not anyone's job.

A rate card gets negotiated at the start of a staffing agreement and then the invoice drifts above it a few dollars an hour at a time. AP is checking that the invoice ties to the purchase order, not that the hourly rate ties to the contract's rate card.

This is not a failure of any one person. It is a structural gap: the contract and the invoice live in different systems, checked by different processes, and nothing forces them into the same room. See [n-way invoice matching explained] for what standard AP controls actually test and where the boundary sits.

3. Which vendor categories should a new CFO look at first?

Look first at categories with recurring contract terms that are easy to encode incorrectly once and never revisit: freight and 3PL, contract labor and staffing, maintenance and repair, IT and professional services, and MRO or Class C consumables. Each carries its own contract mechanics, so each needs its own review rather than one generic AP audit pass.

These categories share a structural trait: the pricing terms are complex enough that a one-time setup decision, correct at the time, becomes wrong later without anyone changing it on purpose.

• Freight and 3PL: Fuel surcharges, accessorial charges, and lane rates that move independently of the base contract. See [freight and 3PL audit].
• Contract labor and staffing: Rate cards, shift premiums, and volume rebates that require checking the invoice against the master service agreement line by line. See [contract labor and staffing audit].
• Maintenance and repair: Scope and rate terms that drift as work orders expand past the original agreement. See [maintenance and repair audit].
• IT and professional services: Statements of work where scope creep changes the deliverable without changing the price. See [it and professional services audit].
• MRO and Class C consumables: High transaction volume and low per-line value, which is exactly why substitution pricing and price file errors go unchecked. See [mro and class c consumables audit].

4. When should a new CFO run a formal audit versus wait?

Run it early, inside the first 100 days, rather than waiting for a full annual cycle to close. A fixed-scope diagnostic takes 2 to 4 weeks across ValueXPA diagnostics, short enough to complete before the first board cycle and before any major vendor renegotiation is locked in. Waiting a full year to "get settled" first means a year of drift compounding on contracts nobody has re-examined.

There is a reasonable counter-argument for waiting: a new CFO does not yet know the organization, and running an outside audit before understanding internal politics can look premature. That is a fair concern in general, but it does not apply to a vendor invoice audit the way it applies to, say, a reorganization. Checking an invoice against a contract does not require organizational context.

It requires the contract and the invoice.

The cost of waiting is not neutral. Every month before the review is another month of surcharges, rate deviations, and unapplied rebates accumulating on the same terms. A diagnostic run early gives the new CFO a defensible, sourced number to bring into budget conversations rather than a general sense that "vendor costs feel high."

5. How does a fixed-scope diagnostic differ from a contingency-fee recovery audit?

A fixed-scope diagnostic is priced upfront and the client keeps 100% of what it finds. A contingency-fee recovery audit charges 25% to 50% of recoveries, and typically stops at retrospective recovery without building forward controls or reviewing contract compliance. The fixed-scope model also covers indirect spend categories that many contingency firms treat as out of scope.

Contingency-fee firms are the right choice for some companies, particularly ones without the internal bandwidth to act on findings and no budget for an upfront engagement. That is a genuine trade-off, not a marketing line.

What a fixed-scope diagnostic adds is scope beyond simple recovery: contract compliance checking against rate cards, rebate clauses, and volume tiers, plus a prevention roadmap so the same drift does not recur next quarter. See [what an ap recovery audit actually finds and what it misses] for where a pure recovery pass stops short.

For a new CFO specifically, the fixed-scope model has one more advantage: the finding is fully theirs to present, with no percentage carved out before it reaches the board.

6. What should a new CFO build after the initial review to prevent drift from recurring?

Build the control at the source of drift rather than adding another downstream review. That means surcharge sunset dating so temporary charges expire automatically, price file governance so ERP updates happen more than once a year, and vendor master hygiene so duplicate vendor records stop generating duplicate payments. Each of these is a system change, not a one-time correction.

A one-time diagnostic finds the current gap. It does not by itself stop the gap from reopening. The controls that prevent recurrence are specific to where the drift originated, not generic AP tightening.

A fuel surcharge with a sunset date built into the contract term, checked against a [surcharge sunset dating as a control] rule, expires on schedule instead of running indefinitely. A [price file] updated on a defined cadence, rather than once a year, closes the twelve-month gap that an annual-only upload creates. See [price file governance why annual uploads create twelve] for the mechanism.

These are not FynFlo software claims here, only the underlying discipline: pair each finding with the specific control that would have prevented it, and assign an owner for that control. A finding without a named owner for its fix tends to recur within a year.

For the wider pattern this sits inside, start with the margin drift guide. See also off-contract resources: people billed outside the agreement and unapplied volume rebates in staffing agreements.

7. Frequently Asked Questions (People Also Ask)

How long does a margin drift diagnostic take for a new CFO to commission in their first 100 days?

A fixed-scope Margin Drift Diagnostic produces a prioritized roadmap in 2 to 4 weeks, across ValueXPA diagnostics. That timeline fits comfortably inside a first-100-days window and ahead of a first full board cycle.

Does a new CFO need to wait until they understand the org chart before running a vendor audit?

No. A vendor invoice audit checks the invoice against the contract, which does not require internal organizational context. It can start in parallel with onboarding rather than after it.

What size of company is this relevant for?

The diagnostic is built for US industrial manufacturers and distributors at $100M and above in revenue, where service vendor spend across freight, staffing, maintenance, and professional services is large enough that even small per-invoice drift adds up.

Is this only about finding past overbilling, or does it also fix future billing?

Both. The AP recovery side looks backward at 12 to 18 months of historical spend, across ValueXPA diagnostics. The contract compliance side is forward-looking: it checks current invoices against rate cards, rebate clauses, and surcharge schedules to catch drift before it compounds further.

How much does vendor overbilling typically cost a company this size?

Across ValueXPA diagnostics, typical findings run $300K to $4.5M per year, across ValueXPA diagnostics. The exact figure depends on service vendor spend volume and how long since contracts were last reconciled against invoices.

Should a new CFO renegotiate vendor contracts before or after the diagnostic?

After. Renegotiating before quantifying current drift means negotiating from an unverified baseline. A diagnostic gives a sourced number for what the current contract terms are actually costing, which is a stronger position at the negotiating table.

Does this replace the AP team's existing three-way matching controls?

No. Three-way matching checks the invoice against the purchase order and the receipt. It does not test whether a rate matches a master service agreement or a surcharge has expired. The diagnostic and any resulting controls work alongside existing AP matching, not in place of it.

What happens to the money the diagnostic finds?

The client retains 100% of recoveries. This is a fixed-scope engagement, not a contingency-fee arrangement, so there is no percentage held back from findings.

Can a new CFO use this to build credibility with the board in the first 100 days?

A sourced, quantified finding on vendor spend, delivered inside the first quarter, gives a new CFO a concrete result to report that is independent of budget cycles or headcount decisions still being finalized.

What if the company already uses AP automation software?

AP automation prevents forward-looking errors at the point of invoice receipt. It does not quantify leakage already embedded in 12 to 18 months of historical spend, across ValueXPA diagnostics, or interpret contract terms like rebate clauses that live in PDFs outside the ERP. The two are complementary.