Margin drift checks for a new CFO's first 100 days

Executive Summary

A new CFO at a $100M+ industrial manufacturer or distributor typically finds margin sitting lower than the board deck implies, and the gap is rarely one clean number. It is scattered across freight accessorials, contract labor rate escalations, MRO catalog pricing and rebate clauses nobody reconciles against the invoice. None of it shows up in the P&L as a labeled line; it shows up as gross margin that does not match the volume and pricing story finance tells about it.

The mechanism is structural, not a vendor acting in bad faith. Contracts get negotiated by procurement, invoices get paid by accounts payable, and nobody sits between the two checking that the invoice still reflects the contract. Rate cards expire, surcharges outlive their trigger condition, minimum commitments get invoiced as if they were never met.

Each error is small. Held constant across a year of invoice volume, the pattern is not.

What changes it in the first 100 days is sequencing: pull the contracts before pulling a vendor spend list, pick two or three high-volume categories rather than trying to audit everything at once, and treat any finding as a baseline for your own tenure rather than a verdict on the last CFO's team.

1. Why does the first 100 days matter for finding margin drift?

The first 100 days are the one window where a new CFO can ask why an invoice looks the way it does without the question landing as criticism of the team that approved it. Vendor contracts, rate cards and rebate terms are easiest to request before you own the relationships they govern. Waiting past this window does not make the drift smaller; it just makes the questions harder to ask.

A CFO who joins mid-year inherits budgets, forecasts and a finance team's working assumptions about what spend looks like. What they do not inherit is a record of every place a contract term and an invoice line stopped matching.

That mismatch does not announce itself. A surcharge that should have expired keeps appearing on invoices that otherwise look ordinary. A volume tier that should have triggered a lower rate does not, because nobody rechecked the trailing twelve months against the tier trigger.

None of this fails a standard three-way match, because three-way matching checks the invoice against the purchase order and the receipt, not against the contract's rate schedule.

Asking for the underlying vendor contracts in week one is a normal onboarding request. Asking for them in month eight, after signing off on eight months of invoices against those same contracts, is a different conversation. The sequencing matters more than the depth of any single check.

2. Which spend categories should a new CFO check first?

Freight and 3PL, contract labor, and MRO are the categories worth a first look, because they combine high invoice volume with contract terms that live outside the ERP: rate tables, surcharge schedules and volume tiers sitting in PDFs rather than in the system that pays the bill. Checking all indirect spend categories at once in the first 100 days spreads attention too thin to find anything; checking three well finds real issues.

Freight and 3PL invoices carry base rates, fuel surcharges and accessorial charges that are renegotiated on a different schedule than the invoice is generated. A rate that was correct at contract signing can drift months later without anyone updating the invoice logic.

Contract labor billing carries its own version: rate escalations tied to a contract anniversary, overtime rules, and not-to-exceed caps that get billed past the cap without anyone flagging it. Labor contracts change hands between account managers more often than most vendor relationships, and each handoff is a chance for the original terms to get lost.

MRO spend, fasteners, safety supplies and Class C items, is high in transaction count and low in per-line dollar value, which is part of why line-by-line review is uncommon. Catalog pricing changes are a recurring drift source here: a price increase applied without a corresponding contract amendment.

A new CFO does not need to audit indirect spend broadly in the first 100 days. Naming two or three categories and pulling the underlying contracts for those is enough to establish whether a pattern exists worth pursuing further.

3. What questions should you ask your AP and procurement teams?

Ask AP whether invoices are matched against the contract's rate schedule or only against the purchase order and receipt. Ask procurement when each major vendor contract was last renegotiated and whether AP received the updated terms. The answers to these two questions, more than any spreadsheet, tell you whether a control exists between the contract and the invoice, or whether one was assumed and never built.

Three-way matching is standard in most AP departments and it is a real control. It confirms the invoice matches the purchase order and the goods or services were received. It does not test whether a surcharge's trigger condition still applies, or whether a rebate clause earned in a given quarter was ever credited back.

Asking AP directly whether rate schedules, rebate clauses and volume tiers are checked against invoices, separately from the PO match, usually surfaces the honest answer quickly: that check exists for large or unusual invoices and not for routine ones.

Asking procurement when a vendor contract was last renegotiated closes the other half of the gap. A contract renegotiated eighteen months ago with new rates that AP never received as an updated reference table is a documented, findable source of drift, not a hypothetical one.

This conversation also shows where the two teams' incentives diverge. Procurement is measured on the rate it negotiates. AP is measured on invoices processed and cycle time. Neither is measured on whether the rate on the contract is the rate on the invoice six months later.

4. How should a worked check actually run?

Pull the current contract for a high-volume vendor, pull twelve months of invoices against it, and check the invoiced rate, surcharge conditions and volume tier against what the contract states, line by line, for a sample large enough to draw a conclusion from. The output is not a dollar figure yet: it is a list of line items where the invoice and the contract disagree, sorted by how often the disagreement recurs.

Take one vendor where spend is material and the contract is recent enough to be unambiguous. Request the full contract, not a summary: rate card, surcharge schedule, volume tiers, rebate terms and any minimum commitment language.

Line up twelve months of invoices against it. For each line, check three things: is the base rate the contracted rate, is any surcharge's trigger condition still true, and does the invoice reflect the volume tier the trailing spend should have earned.

A single mismatched line could be a one-off billing error. The same mismatch recurring across multiple invoice cycles points to a control gap rather than an error, because nothing catches it between the vendor sending the invoice and AP paying it.

This exercise, done properly for two or three vendors, tells a new CFO more about the state of vendor billing controls than a spend analysis across the whole vendor file, because it tests whether contract terms are enforced rather than whether spend is categorized correctly.

5. What does a worked example of the exposure look like?

Take your total service vendor spend and the share of it running through freight, contract labor and MRO combined. Multiply that share by the 1% to 3% band margin drift typically represents across a full diagnostic, and the result is a rough order of magnitude, not a finding: only a line-by-line check against the actual contracts turns that estimate into a number you can act on.

Worked example, using the 1% to 3% band: a manufacturer's own service vendor spend is a number already sitting in its ERP. Applying a range rather than a single guess reflects that some vendor relationships are tightly controlled and others are not, and a new CFO does not yet know which is which for this company.

The purpose of this arithmetic is not to produce a number for the board in week two. It is to decide whether pursuing a fuller check is worth the time, given the size of the exposure it is plausible to be sitting on. A company with modest indirect spend and tight existing controls may conclude the exposure is small enough to deprioritize.

One with high indirect spend as a share of revenue usually will not reach that conclusion.

Either way, the estimate is a planning input, not a claim to repeat externally. Margin drift across a full diagnostic typically runs 1% to 3% of service vendor spend, but that figure describes the portfolio as a whole, not any one vendor or category, and should be presented to a board as a hypothesis to test, not a finding already proven.

6. Should you build the check in-house or bring in outside help?

Building the check in-house works when AP and procurement have spare capacity and the contract volume is manageable, because the reviewer does not need external context, just time. It works less well when the review needs to happen inside a fixed onboarding window, spans several categories and vendors at once, and has to compete with the closing calendar for the same finance staff's attention.

An in-house review has one real advantage: the people doing it already know the vendor relationships, the ERP configuration and where past exceptions were made. That context speeds up interpretation of what a mismatch means.

It has one real constraint: the same team is running month-end close, managing the transition to a new CFO's reporting preferences, and now being asked to review a year of invoices against contracts, often for the first time.

A fixed-scope external diagnostic exists for exactly this trade-off: an engagement that reviews invoice-to-contract matching across categories in 2 to 4 weeks, without pulling AP off close. It is not a replacement for building the ongoing control. It is a way to get the first 100 days' worth of findings without spending the first 100 days doing nothing else.

Either path answers the same underlying question: is the current gap between contract terms and invoiced amounts big enough to justify the ongoing control that would close it going forward.

7. What should you do with the findings once you have them?

Sort findings by whether they are recoverable, a credit or refund claimable now, or preventable, a control that stops recurrence, and treat them differently: recoverable findings go to AP for follow-up with the vendor, preventable findings go into a roadmap for the systems and process changes that stop the next twelve months looking the same as the last. Presenting both together as one undifferentiated number understates the second, more durable, category.

A finding that a rebate was never claimed is recoverable: it is a credit memo request against a vendor, bounded and one-time. A finding that surcharge trigger conditions are never checked is preventable: it is a process gap that will keep producing the same category of drift every quarter until something closes it.

Boards and sponsors respond to these differently, and conflating them undersells the case for the second. A one-time recovery number is compelling but finite. A description of the control gap that produced it is what justifies the ongoing investment, whether that is a managed AP process, a periodic contract compliance check, or a forward enforcement layer.

The roadmap that comes out of the first 100 days should therefore separate the two explicitly: what to claim back now, and what to change so the next audit finds less. A new CFO who presents only the recovery number has made a strong first impression and left the actual fix for someone else to discover next year.

For the wider pattern this sits inside, start with the margin drift guide.

8. Frequently Asked Questions (People Also Ask)

How long should a first-100-days margin drift check take?

A focused check across two or three high-volume categories, freight, contract labor or MRO, can be scoped and run within a diagnostic window of 2 to 4 weeks, across ValueXPA diagnostics. Trying to cover every indirect spend category in the same window usually means none of them get reviewed at the line-item level that actually surfaces drift.

Is this the same thing as a standard AP audit?

No. A standard AP or SOX-driven audit tests controls and sampling for financial statement accuracy. This check tests whether invoiced amounts match the specific rate, surcharge and volume terms in the underlying vendor contract, which most standard audit procedures do not review line by line.

Do I need to involve procurement or just AP?

Both. AP holds the invoice history and can say whether contract terms are checked against invoices. Procurement holds the contracts and knows when terms last changed. A check run through only one of the two teams will miss either the paid-invoice evidence or the current contract terms.

What if I don't have twelve months of clean invoice data?

Use whatever period is available and state that period explicitly rather than assuming a full year. A shorter, clearly stated sample is more useful and more credible than an assumed annualized figure built on a gap-filled dataset.

Should I mention this to the board before I have findings?

Framing it as a planning exercise, not a discovered problem, is safer and more accurate. Telling a board you are establishing a baseline on vendor contract compliance is a normal first-100-days action. Implying a specific dollar figure before the line-by-line check is done risks a number you later have to walk back.

Does this apply if the company already has AP automation software?

AP automation tools generally test the invoice against the purchase order and receipt at the point of entry. They do not typically interpret unstructured contract terms, rebate clauses or volume tier triggers sitting in a separate PDF contract, so a check of this kind is complementary to that software rather than duplicating it.

What's the first document I should actually request?

The signed contract, including any amendments, for your highest-volume service vendor in each of the two or three categories you choose to check first. Not a spend report, not a vendor master list: the contract itself, with its rate schedule and any surcharge or rebate language attached.

Is this general information or legal advice on contract terms?

This is general information about how to structure a vendor contract compliance review, not legal advice. Interpreting specific contract language, especially around rebate triggers or minimum commitment penalties, should involve counsel or a contracts specialist familiar with the agreement.

What's a realistic outcome to expect from this exercise?

A list of specific line-item mismatches between contract terms and invoiced amounts, sorted into what is recoverable now and what needs a process or system change to prevent going forward. It is not, on its own, a finalized recovery number; that requires validating each mismatch against the actual contract language.