Reading a margin drift report: a Controller guide

Executive Summary

A margin drift report is only as useful as the Controller's ability to trace each line back to a contract clause and an invoice. Reports fail in review for one of two reasons: the finding has no cited source document, or it asks for a journal entry before anyone has confirmed the vendor agrees. Both are fixable with a consistent reading order.

Read for source first, dollar amount second. A finding stated without the contract section and invoice number it came from is not yet a finding, it is a lead. Once sourced, sort by whether it changes a prior period, the current close, or a forward control, because each of those has a different accounting and approval path.

The report's real value to a Controller is not the total. It is the list of contract terms nobody was checking, because that list becomes the control you add so the same finding does not reappear next quarter.

1. What should a Controller check first on a margin drift report?

Check that every line cites its source: the contract clause, the invoice number, and the specific rate or term that was violated. A finding without a traceable source is not usable for a journal entry or a vendor dispute. Next, check the audited spend and period the report covers, since a finding is only meaningful against a stated denominator. A report that skips either is not ready for close.

A Controller's first pass is not about the dollar total. It is about whether each line can survive a vendor calling to dispute it.

Look for three things on every line: the contract section referenced, the invoice or invoices involved, and the specific term that was not honored, a rate, a tier, a cap, or an expiration date. If any of those three is missing, the line needs more work before it goes anywhere near the ledger.

Also confirm the report states the audited spend and the period it covers. A finding of a fixed dollar amount means little without knowing what base it was measured against and over how many months. Without that denominator, you cannot judge materiality or explain the number if asked.

2. How should a Controller sort findings for close purposes?

Sort every finding into one of three buckets before close: prior-period corrections that need a restatement or write-off decision, current-period credits still pending from the vendor, and forward-looking control gaps that affect no journal entry at all. Treating all three the same, as one lump adjustment, is the fastest way to create a reconciling item that audit will ask about later.

Not every line on a margin drift report belongs in the same period, and treating them as one number to book is where most close problems start.

Prior-period findings, overbilling from a closed quarter, need a decision on materiality and disclosure before touching the general ledger. Current-period findings tied to an open invoice can often net against the payment or wait for a credit memo. Forward-looking findings, a rate table that will drift again unless someone rebuilds the reference table, need no entry at all: they need an owner.

A report organized this way makes the close conversation shorter. You are not defending one number, you are walking through three decisions with three different owners and three different approval paths.

A. Recognition timing

A credit memo received before the period closes is straightforward. One still pending from the vendor is a receivable judgment call, not a revenue or expense entry, until it is confirmed.

B. Materiality thresholds

Apply the same materiality policy you already use for other adjustments. A margin drift finding is not exempt from your existing thresholds just because it came from an external engagement.

3. What documentation does a finding need before it goes to the vendor?

A vendor dispute needs the exact contract clause, the invoice line it contradicts, and the calculation showing the delta, in a form the vendor's AR team can verify without a call. Anything less invites a stalling response. The report should hand you this packet already assembled per finding, not as a single narrative summary you have to break apart yourself.

The finding that convinces you is not automatically the finding that convinces the vendor's accounts receivable team. They need the same three things you checked in section one, laid out so someone unfamiliar with your operation can verify it in minutes.

That means the exact contract language, quoted, not paraphrased. It means the invoice number and line item. And it means the arithmetic: the rate that should have applied, the rate that was charged, and the difference, shown as a calculation rather than asserted as a total.

If the report gives you this per finding, your AP or procurement team can send disputes without waiting on you to rebuild the case. If it does not, expect the dispute cycle to take longer than the audit did.

4. How does a margin drift report differ from a standard AP exception report?

An AP exception report flags what a three-way match already checks: invoice against purchase order and receipt. A margin drift report tests the invoice against the contract itself, including terms three-way matching was never built to hold, rebate clauses, tier triggers, and surcharge expiration dates living outside the ERP. The two are complementary, not overlapping, and a Controller reviewing both should expect different failure types from each.

Three-way matching checks that the invoice, purchase order, and receipt agree with each other. It does not check any of them against the underlying contract, because the contract terms usually live in a PDF outside the ERP, not in a field the match logic can read.

A margin drift report is testing something three-way matching structurally cannot: whether the agreed rate itself was honored, whether a volume tier discount kicked in when spend crossed the threshold, whether a surcharge that should have expired kept billing.

For a Controller, this means the two reports rarely flag the same invoice for the same reason. An exception report catching a receiving discrepancy and a drift report catching a stale rate card are both correct and both necessary. Reviewing only one leaves the other category of error unmanaged.

5. Should a Controller build a control from a finding, or treat it as a one-time correction?

Build a control whenever the underlying cause is a contract term nobody is checking on an ongoing basis, a surcharge expiration date, a tier trigger, an NTE cap. Treat it as a one-time correction only when the cause was a single data entry error unlikely to recur. Most margin drift findings point to the first case, because the report exists precisely to surface terms invoice review was not built to test.

The test is whether the same mechanism can produce the same error again next month. A one-off keying error on a single invoice is a correction. A surcharge schedule that has no expiration check anywhere in your review process is a gap that will produce another finding on the next invoice from that vendor, and the one after that.

For each finding, ask what would have caught it before the invoice was paid. If the answer is a manual step someone forgot, retrain and move on. If the answer is that no step exists to catch it, that is a control gap, and it belongs on a list separate from the correction itself.

This distinction is what turns a single report into a lasting improvement in your close process rather than a one-time cleanup exercise.

6. How should a Controller present margin drift findings to the CFO or board?

Present findings as three groups, dollars already recovered or credited, dollars in active dispute, and control gaps closed going forward, rather than a single headline total. A blended number invites the question of how much is cash versus how much is prevention, and a Controller who cannot separate the two on request will spend the meeting defending the format instead of the substance.

A single total is the easiest thing to put in a slide and the hardest thing to defend under a follow-up question. Boards and CFOs ask where the number came from, and a blended figure covering confirmed credits, disputed claims, and estimated future savings from a new control cannot answer that in one sentence.

Separate the three explicitly. Confirmed recoveries are cash or credit memos already in hand. Disputed claims are pending vendor response and should be labeled as such, not counted as recovered. Control improvements have no dollar value yet; they are described by what they prevent, not by a number.

This format also protects the Controller specifically, since it is the Controller's signature that will eventually sit under whichever of these numbers reaches the financial statements.

For the wider pattern this sits inside, start with the margin drift guide. See also the six categories drift hides in and margin drift vs. legitimate price increases: how to tell them apart.

7. Frequently Asked Questions (People Also Ask)

Does a margin drift report require any change to how we close the month?

Only if a finding affects a prior or current period balance. Forward-looking control gaps do not require a journal entry, only a process owner. Sort findings by period impact before deciding whether close procedures change at all.

Who should own the vendor dispute once a finding is confirmed?

Whoever already owns that vendor relationship in AP or procurement, using the documentation packet the report provides. The Controller's role is to confirm the finding is sourced correctly, not to run the dispute conversation directly.

What if a finding conflicts with what our ERP shows as paid correctly?

The ERP confirms the invoice matched the purchase order and receipt. It does not confirm the purchase order or receipt reflected the actual contract terms. A conflict usually means the contract term in question was never entered as a rule the ERP could check.

How far back should a margin drift report look?

The diagnostic period is stated in the report itself; confirm it before assuming coverage. Findings outside that window were not tested and should not be assumed absent just because they were not flagged.

Can a finding be booked before the vendor confirms it?

Only as a receivable under your existing policy for disputed claims, not as recognized income. Treat an unconfirmed finding the same way you would treat any other contested vendor balance until it is resolved.

What does 'audited spend' mean on the report and why does it matter?

It is the denominator, the total service vendor spend the report actually reviewed. A finding's dollar value only has context against that base; without it you cannot judge whether the finding is material to your total spend.

Should internal audit be looped in on margin drift findings?

Yes, for any finding touching a prior period or requiring a restatement judgment. Internal audit's existing materiality and disclosure process applies to these findings the same way it applies to any other adjustment.

What is the difference between a recovery and a prevention finding?

A recovery finding has a dollar value tied to a specific past invoice, refundable or creditable. A prevention finding identifies a contract term with no current control, worth building a check for, but with no dollar value to book.

How should a Controller handle a finding tied to a vendor we plan to keep using?

Separate the correction from the relationship. Pursue the credit or recovery through normal AP channels while flagging the underlying contract term for the control gap list, regardless of whether the vendor relationship continues.