Month-end accruals for service spend

Executive Summary

Service spend accruals fail less often on arithmetic than on which contract terms procurement fed into them. An accrual built from a rate card that finance has not checked against the last invoice carries forward whatever drift already exists, uncorrected, month after month.

The mechanism is straightforward: accruals estimate unbilled activity using a rate, a volume, and a set of assumptions about surcharges, minimums and tier triggers. If any of those assumptions no longer match what the vendor is actually charging, the accrual understates or overstates the true liability, and the variance shows up as a "true-up" that nobody investigates because it looks like normal accrual noise.

What changes it is treating the accrual process as a second, lightweight compliance check rather than a bookkeeping task. Procurement holds the contract terms; finance holds the invoice history. Neither owns the comparison on its own, and the accrual is where that comparison has to happen every single month, not just at renewal.

1. Why does a Procurement Director need to be involved in month-end accruals at all?

Because the accrual is only as accurate as the contract terms behind it, and procurement is the only function that holds those terms in full: rate cards, volume tiers, minimum commitments, surcharge schedules. Finance can accrue against a prior invoice trend without ever checking whether that trend still reflects the signed contract. When procurement reviews the accrual basis each month, drift gets caught before it compounds across a fiscal year instead of surfacing as a year-end surprise.

Finance teams building an accrual for freight, contract labor or MRO spend typically default to a run-rate method: take the last few invoices, average them, and book that as the estimate. It is fast and it closes the books on time.

The problem is that a run-rate method assumes the last few invoices were correct. If a carrier's fuel surcharge stopped resetting to the published index, or a staffing vendor's bill rate crept above the rate card, the run-rate accrual simply extends the error forward.

Procurement's contribution is not to redo the accrual. It is to confirm, on a fixed cadence, that the rates and terms feeding the estimate still match the current contract. That single check turns the accrual from a rolling average of whatever was billed into a rolling check against what should have been billed.

2. Which service categories create the most accrual risk?

Freight, contract labor, and maintenance and repair services carry accrual risk because each bills on activity that closes after the accounting period ends: a shipment delivered on the 29th, a temp shift worked through month-end, a repair ticket not yet invoiced. Each also carries contract terms with room to drift: fuel surcharge tables, overtime and shift differential rules, and not-to-exceed caps on scope changes.

Freight accruals depend on knowing which shipments moved before the cutoff and what rate applies to each, including any accessorial or fuel surcharge in effect that week. A stale surcharge assumption in the accrual model repeats the same error the actual invoice will carry.

Contract labor accruals depend on hours worked but not yet invoiced, at the correct bill rate, including any overtime or differential rules in the master service agreement. A vendor that quietly applies a higher rate for the last week of a month will show up first in the accrual variance, not the invoice.

Maintenance and repair work is harder still, because scope often expands mid-job. A not-to-exceed cap in the contract is the control that should stop an accrual, and later an invoice, from simply reflecting whatever the technician billed.

3. How do rate card changes get missed in the accrual process?

A rate card change gets missed when the accrual model is built once, at contract signing, and never refreshed against amendments, renewals or side letters that follow. Procurement negotiates a rate change, files it, and the finance team building the monthly estimate keeps using the original number because nobody routed the update to them. The accrual and the invoice then disagree for months before anyone reconciles the two.

Contract amendments rarely travel with a clear trigger to update downstream processes. A renegotiated volume tier, a new surcharge schedule, or a rebate clause added at renewal lives in a PDF that procurement filed and finance never saw.

The fix is procedural, not technical: every contract amendment needs a one-line notice to whoever owns the accrual model, stating the new rate, the effective date, and the term it replaces. Without that notice, the accrual model has no way to know its own assumptions are out of date.

This is also where invoice-to-contract matching earns its place in the monthly cycle rather than only at audit time. Comparing the current month's actual invoice against the contract, not just against last month's invoice, is what surfaces a missed rate card update before it becomes months of understated accrual.

4. What should a Procurement Director check before signing off on a service spend accrual?

Before signing off, confirm the rate or rate schedule used in the accrual matches the current, fully amended contract; confirm any volume tier or minimum commitment threshold used is the one currently in effect; and confirm any known disputes, credits or pending change orders with the vendor are reflected, not ignored. A signoff without these three checks is an approval of finance's assumption, not a review of it.

None of these four checks require rebuilding the accrual. They require having the current contract terms on hand and comparing them against what finance used, which is a short review once the habit exists.

Skipping the review does not make the accrual wrong immediately. It makes the accrual wrong silently, and the error persists until a large enough invoice variance forces someone to look.

1. Current rate confirmation: Match the rate in the accrual model against the latest signed amendment, not the original contract date. Renewals and side letters change the number without always changing the file name.
2. Volume tier and minimum status: Check whether spend to date has crossed a tier threshold or fallen short of a minimum commitment, since either changes the effective rate for the remaining period.
3. Open disputes and credits: Confirm any credit memo already agreed with the vendor is reflected in the accrual, so the estimate does not overstate a liability that is already being resolved.
4. Surcharge and accessorial basis: Verify the index or table the accrual uses for fuel, expedite or overtime surcharges is the one the contract currently specifies.

5. How does vendor performance tie into the accrual conversation?

A pattern of accrual-to-invoice variance with one vendor is a vendor performance signal, not just an accounting nuisance. A vendor whose invoices consistently exceed what the contract and prior activity would predict is either billing outside the agreed terms or experiencing scope creep procurement has not caught. Tracking that variance by vendor turns the accrual process into an early warning system for the next renewal negotiation.

Most vendor scorecards track on-time delivery, quality and responsiveness. Few track whether the vendor's invoice matches the contract procurement signed, which is a distinct and measurable dimension of performance.

A vendor that repeatedly bills above the accrual, in ways that trace back to a stale surcharge, an expired promotional rate, or scope added without a change order, is telling procurement something about how that relationship is being managed on the vendor's side.

Bringing that variance data into a quarterly business review with the vendor changes the conversation from a general performance discussion into a specific, documented one: here is where the invoice diverged from the contract, and here is what needs to change before the next renewal.

6. Should procurement build the accrual reconciliation process alone or with finance?

Neither function should own it alone. Procurement holds the contract terms and the vendor relationship; finance holds the invoice history, the ERP data and the close calendar. A reconciliation process split across both, with a documented handoff at each amendment and each close, catches drift that either function working in isolation would miss.

The common failure mode is not that both functions try to own the process. It is that both assume the other one is checking, and neither is.

A workable split assigns procurement responsibility for confirming contract terms are current and communicated, and finance responsibility for building the accrual model and flagging any variance against the actual invoice once it lands. The two functions meet at a fixed point each month, not only at contract renewal, to close the loop.

For companies running multiple entities or a high volume of vendor contracts, this reconciliation is one of the areas where a fixed-scope outside review pays for itself: it audits the invoice-to-contract match across a full spend base at once, rather than relying on a monthly review catching every vendor every time.

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

7. Frequently Asked Questions (People Also Ask)

What is a service spend accrual?

A service spend accrual is an estimate, booked at month-end, of the cost of services received but not yet invoiced. It applies a rate and a volume assumption, drawn from the vendor contract and recent activity, to approximate the liability before the actual invoice arrives.

Why does an accrual variance matter if it corrects itself next month?

A variance that reverses next month can still hide a real problem if the underlying rate assumption is wrong in both months. A recurring true-up in the same direction, month after month, usually means the accrual model and the actual invoice are both anchored to a stale contract term rather than converging on the correct one.

Who should own the accrual model for freight and contract labor spend?

Finance typically builds and books the accrual model, since it sits in the general ledger process. Procurement should own confirming the contract terms feeding that model are current, with a documented handoff whenever a rate, tier or surcharge term changes.

How often should procurement review the rate assumptions behind an accrual?

At minimum, every month before close, and again at every contract amendment or renewal. A monthly check is a short review of whether anything changed, not a full re-audit, and catches drift within one cycle instead of letting it compound.

Can a not-to-exceed cap prevent accrual errors on maintenance and repair spend?

A not-to-exceed cap sets an upper bound on what a job can bill, which gives the accrual model a defensible ceiling for open work orders. It does not by itself confirm the vendor is billing within that cap; that still requires checking the invoice against the cap once it arrives.

What is the difference between an accrual error and margin drift?

An accrual error is a forecasting miss inside the accounting close. Margin drift is the underlying gap between the contract terms and the actual invoice that the accrual, if built on stale assumptions, ends up repeating rather than catching.

Does invoice-to-contract matching belong in the month-end close process?

It belongs at least in a lightweight form. Comparing the current invoice against the current contract, not just against last month's invoice, is what reveals a rate or term change the accrual model missed, before that gap accumulates across several close cycles.

How should procurement handle a vendor dispute that is still open at month-end?

State the disputed amount and its likely resolution in the accrual notes rather than omitting it. An accrual that ignores an open dispute either overstates or understates the liability depending on which way the dispute resolves, and the notes give finance a documented basis for the estimate.

What is a general information note procurement should add when discussing accrual disputes with legal implications?

When a vendor dispute involves contract interpretation or potential breach, procurement should flag that the discussion is general information, not legal advice, and route it to counsel before committing to a resolution in the accrual or the vendor conversation.