# Month-end accruals for service spend: a Controller guide > A Controller's guide to accruing service spend correctly: what drives the accrual, which controls catch drift, and how it affects the close. Source: https://valuexpa.com/insights/month-end-accruals-for-service-spend-a-controller-guide Publisher: ValueXPA (https://valuexpa.com) Updated: 2026-09-06 --- Margin drift is the gap between what a vendor contract says and what the invoice actually charges. For a Controller closing the books, that gap surfaces first as an accrual estimate that misses the eventual invoice, not as a line item anyone flagged during the month. Service spend accrues differently than goods. There is no receiving dock, no PO line that closes on delivery. The work is done, the invoice arrives late, and the amount depends on contract terms a close checklist rarely touches. ## Executive Summary Service spend breaks month-end accrual routines that were built for goods receipt. A freight bill, a staffing invoice, or a maintenance ticket can lag the work by weeks, and the contract terms that would tell you the right accrual amount, rate cards, volume tiers, NTE caps, sit in PDFs outside the ERP. The result is an accrual built on last month's invoice total rather than on what the contract says this month should cost. That gap shows up twice: once as a close-cycle guess that gets trued up later, and once as a margin drift the reconciliation never explains, because nobody checked the accrual against the underlying contract term. The mechanism causing both is the same. Three-way matching validates an invoice against a purchase order and a receipt; it has no equivalent for a service contract's rate schedule, so the accrual estimate and the eventual invoice are both unverified against the same document. What changes it is treating the contract, not the prior invoice, as the accrual's source document, and building a reconciliation step that flags the variance between accrual and actual invoice by cause, not just by amount. That single change turns a plug into a control and gives the close a defensible number instead of a rounded one. ## 1. Why does service spend break the standard accrual process? **Standard accrual processes assume a three-way match: purchase order, receipt, invoice. Service spend has no receipt document, so the accrual defaults to an estimate built from the prior invoice or a percentage of budget. That estimate never checks the vendor's rate card, volume tier, or not-to-exceed cap, so it carries forward any error already in the run rate instead of correcting it, and the variance surfaces only when the real invoice lands weeks later.** A purchase order for goods closes against a receiving document. The system can compare quantity ordered, quantity received, and quantity invoiced, and an accrual for goods in transit has a paper trail behind it. A service invoice for freight, contract labor, or maintenance has no equivalent receipt. The accrual is built on an estimate, commonly last month's invoice amount, or an average of the trailing three months. That estimate is silent on whether last month's invoice was itself correct. If a surcharge stayed on the bill after its trigger condition expired, or a rate card was superseded by a new contract, the estimate simply repeats the error going forward. The close books a number that reconciles internally but was never checked against the document that actually governs the charge: the contract. ## 2. What should a Controller actually accrue for service categories? **Accrue against the contract's rate schedule and volume commitment for the period, not against last month's invoice. For freight and 3PL, accrue on shipped volume times the contracted rate, adjusted for any fuel surcharge formula in the contract. For contract labor, accrue on hours or headcount times the contracted bill rate, checked against any not-to-exceed cap. For MRO and maintenance, accrue on work orders completed times the contracted rate, not the vendor's invoice history.** Each service category has a different accrual driver, and the driver should come from the contract, not the general ledger history. Freight and 3PL: accrue on shipment volume for the period, multiplied by the contracted base rate, then adjusted by whatever fuel surcharge formula the contract states. A fuel index that moved during the month changes the accrual; a flat prior-month estimate will not catch that. Contract labor and staffing: accrue on approved hours or headcount for the period at the contracted bill rate, and check the result against any not-to-exceed cap in the statement of work before booking it. [Maintenance, calibration, and professional services](/guides/mro-spend-control-in-industrial-distribution): accrue on completed work orders or milestones at the contracted rate, not on the vendor's typical invoice size, since a vendor can bill a flat fee that includes work not yet performed. ## 3. Which controls catch drift before it reaches the close? **Three controls close most of the gap: an invoice-to-contract match performed before the accrual is booked, a variance review that separates volume change from rate change, and a standing register of active rate cards, volume tiers, and NTE caps that AP and accounting both use. None of these require new software; they require the contract terms to be extracted into a form the close process can check against.** ### A. Invoice-to-contract matching before the accrual Before booking the month's accrual, match the prior invoice against its contract line: rate, tier, and surcharge basis. If the prior invoice already drifted from contract, correct that first so the accrual is not built on a bad base. ### B. Variance review by cause, not amount When the real invoice arrives and differs from the accrual, classify the variance as volume change, rate change, or contract violation. A volume-driven variance needs no action. A rate-driven variance means the accrual driver needs updating. A contract violation needs a credit memo, not a plug to the P&L. ### C. A standing rate card and terms register Keep one register, shared by AP and accounting, listing each active vendor's rate card, volume tier thresholds, surcharge formulas, and NTE caps. Contract terms live in PDFs signed by procurement; without a register, accounting rebuilds the accrual driver from memory every month. ## 4. How does this affect the gross margin bridge at close? **An accrual built on contract terms produces a smaller true-up when the real invoice lands, which means less noise moving through cost of goods sold in the following period. A recurring true-up in the same direction, accrual consistently low or consistently high, is itself a signal that the accrual driver is wrong, not that the vendor's billing is volatile. Tracking the direction and size of true-ups by vendor turns the close into a diagnostic instead of just a plug.** A [gross margin bridge](/guides/building-a-gross-margin-bridge-that-separates-inflation-from) separates volume, price, and mix effects, but a badly built accrual introduces a fourth, unlabeled effect: timing error that gets misread as one of the other three. If accruals consistently run low for a freight vendor, the true-up lands as an unfavorable price variance in the month it is caught, even though the actual cause is a fuel surcharge formula the accrual never priced correctly. That miscodes the variance and makes the bridge harder to explain to a board or a sponsor. Tracking true-ups by vendor and by category, not just by total dollar amount, shows which accrual drivers need correction. A vendor with a consistent one-direction true-up over several months has a contract term the accrual formula is not capturing, and that is worth fixing once rather than replugging every close. ## 5. Who should own the accrual driver for service spend? **Accounting should own the accrual entry, but the accrual driver, meaning which rate, tier, and formula applies, should be sourced from whoever owns the vendor contract: procurement or the category manager. Without that handoff, accounting estimates a number it has no basis to challenge, and procurement negotiates terms accounting never applies. A monthly sync between the two closes that gap without adding headcount.** Contract terms are negotiated by procurement or a category owner and often never reach the accounting team that books the accrual. The accountant closing the freight accrual has no reason to know a new fuel surcharge formula took effect this quarter unless someone tells them. A short monthly sync, or a shared terms register updated whenever a contract renews, moves that information across the handoff. This is not a system requirement. It is a process requirement: someone is responsible for updating the accrual driver whenever a contract changes, and someone is responsible for asking. In [a multi-entity manufacturer](/guides/month-end-close-for-multi-entity-manufacturers), this handoff multiplies by every entity with its own vendor contracts and its own close calendar, which is exactly where a shared register earns its cost. ## 6. When does a service spend accrual gap justify a deeper review? **A repeated true-up in the same direction for the same vendor, a contract with a surcharge or tier clause nobody can currently locate, or a category where the accrual driver has not been checked against the contract in over a year are each a reason for a deeper review. None of these require a full audit to investigate; they require pulling the contract and the last several invoices side by side and checking the math once.** Not every accrual variance needs a project. Small, alternating true-ups that net near zero over a quarter are normal estimation noise and do not need escalation. A pattern is different from noise. If the same vendor produces a true-up in the same direction for three consecutive months, the accrual driver is wrong, not the estimate. If nobody in accounting or procurement can locate the current signed contract for a vendor category, that is a control gap independent of any specific accrual. When a category has not had its contract terms checked against actual billing in over a year, treat that as due for review regardless of whether a variance has shown up yet, since the absence of a flagged variance can mean the accrual and the invoice are both wrong in the same way. For the wider pattern this sits inside, start with the [margin drift](/guides/cfo-agenda-mid-market-manufacturing) guide. ## 7. Frequently Asked Questions (People Also Ask) ### What is the right accrual basis for freight when the fuel surcharge changes mid-month? Use the contract's stated surcharge formula and the fuel index value for the period, not last month's invoiced surcharge amount. If the formula references a published index, the accrual should reference the same index reading, so the variance at true-up reflects only volume, not a stale rate. ### Should accounting book an accrual based on the vendor's typical invoice amount? Only as a fallback when no contract terms are available. A prior-invoice-based accrual carries forward any error already present in that invoice, including a surcharge that should have expired or a rate that was superseded by a new agreement. ### How do not-to-exceed caps affect a labor accrual? Accrue on approved hours times the contracted bill rate, then compare the result to the statement of work's not-to-exceed cap before booking. If the calculated amount exceeds the cap, the accrual should reflect the cap, not the uncapped calculation. ### Who should maintain the rate card and terms register mentioned in this guide? Ownership works best when shared: procurement or the category manager supplies and updates contract terms, and accounting maintains the register as the reference accounting uses to build accrual drivers. Neither function should maintain it alone. ### What is the difference between a true-up from volume and a true-up from a contract violation? A volume true-up reflects a change in shipped units, hours, or work orders and needs no correction beyond the entry itself. A contract violation, such as a surcharge applied outside its trigger condition, needs a credit memo from the vendor, not just a journal entry adjustment. ### Does a multi-entity manufacturer need a different accrual process for service spend? The mechanism is the same, but the coordination burden multiplies: each entity may hold separate contracts with the same vendor at different rates, so a shared terms register needs an entity dimension or accruals across entities will use the wrong rate. ### How often should the accrual driver be checked against the actual contract? At minimum, whenever a contract renews or its terms change, and as a standing check whenever a true-up recurs in the same direction for two or more consecutive months for the same vendor. ### Can a Controller catch this without new software? Yes. The core fix is process: source the accrual driver from the contract register instead of the prior invoice, and classify every true-up by cause. A spreadsheet register is sufficient at a single-entity scale; the requirement is discipline, not a system purchase. ### What does an unexplained margin gap at the gross margin bridge usually trace back to at close? It often traces back to an accrual built on the wrong driver rather than a genuine price or volume shift. Separating timing error from real variance before presenting the bridge avoids miscoding a contract issue as a market-driven price effect. ### Is a contract compliance audit the same thing as fixing the accrual process? No. A contract compliance audit checks whether past invoices matched contract terms and quantifies what was missed. Fixing the accrual process is a forward-looking control change that uses the same contract terms to make future close cycles more accurate. ### Is contract complexity quietly draining your operating margin? A small systematic drift between your negotiated contracts and your actual vendor billing compounds quietly across a year of invoices. Stop guessing at your exposure and run a targeted audit. **[Take the Free Screener → https://valuexpa.com/margin-drift-screener](https://valuexpa.com/margin-drift-screener)** ## Executive Summary Service spend breaks month-end accrual routines that were built for goods receipt. A freight bill, a staffing invoice, or a maintenance ticket can lag the work by weeks, and the contract terms that would tell you the right accrual amount, rate cards, volume tiers, NTE caps, sit in PDFs outside the ERP. The result is an accrual built on last month's invoice total rather than on what the contract says this month should cost. That gap shows up twice: once as a close-cycle guess that gets trued up later, and once as a margin drift the reconciliation never explains, because nobody checked the accrual against the underlying contract term. The mechanism causing both is the same. Three-way matching validates an invoice against a purchase order and a receipt; it has no equivalent for a service contract's rate schedule, so the accrual estimate and the eventual invoice are both unverified against the same document. What changes it is treating the contract, not the prior invoice, as the accrual's source document, and building a reconciliation step that flags the variance between accrual and actual invoice by cause, not just by amount. That single change turns a plug into a control and gives the close a defensible number instead of a rounded one. ## 1. Why does service spend break the standard accrual process? Standard accrual processes assume a three-way match: purchase order, receipt, invoice. Service spend has no receipt document, so the accrual defaults to an estimate built from the prior invoice or a percentage of budget. That estimate never checks the vendor's rate card, volume tier, or not-to-exceed cap, so it carries forward any error already in the run rate instead of correcting it, and the variance surfaces only when the real invoice lands weeks later. A purchase order for goods closes against a receiving document. The system can compare quantity ordered, quantity received, and quantity invoiced, and an accrual for goods in transit has a paper trail behind it. A service invoice for freight, contract labor, or maintenance has no equivalent receipt. The accrual is built on an estimate, commonly last month's invoice amount, or an average of the trailing three months. That estimate is silent on whether last month's invoice was itself correct. If a surcharge stayed on the bill after its trigger condition expired, or a rate card was superseded by a new contract, the estimate simply repeats the error going forward. The close books a number that reconciles internally but was never checked against the document that actually governs the charge: the contract. ## 2. What should a Controller actually accrue for service categories? Accrue against the contract's rate schedule and volume commitment for the period, not against last month's invoice. For freight and 3PL, accrue on shipped volume times the contracted rate, adjusted for any fuel surcharge formula in the contract. For contract labor, accrue on hours or headcount times the contracted bill rate, checked against any not-to-exceed cap. For MRO and maintenance, accrue on work orders completed times the contracted rate, not the vendor's invoice history. Each service category has a different accrual driver, and the driver should come from the contract, not the general ledger history. Freight and 3PL: accrue on shipment volume for the period, multiplied by the contracted base rate, then adjusted by whatever fuel surcharge formula the contract states. A fuel index that moved during the month changes the accrual; a flat prior-month estimate will not catch that. Contract labor and staffing: accrue on approved hours or headcount for the period at the contracted bill rate, and check the result against any not-to-exceed cap in the statement of work before booking it. [Maintenance, calibration, and professional services](/guides/mro-spend-control-in-industrial-distribution): accrue on completed work orders or milestones at the contracted rate, not on the vendor's typical invoice size, since a vendor can bill a flat fee that includes work not yet performed. ## 3. Which controls catch drift before it reaches the close? Three controls close most of the gap: an invoice-to-contract match performed before the accrual is booked, a variance review that separates volume change from rate change, and a standing register of active rate cards, volume tiers, and NTE caps that AP and accounting both use. None of these require new software; they require the contract terms to be extracted into a form the close process can check against. ### A. Invoice-to-contract matching before the accrual Before booking the month's accrual, match the prior invoice against its contract line: rate, tier, and surcharge basis. If the prior invoice already drifted from contract, correct that first so the accrual is not built on a bad base. ### B. Variance review by cause, not amount When the real invoice arrives and differs from the accrual, classify the variance as volume change, rate change, or contract violation. A volume-driven variance needs no action. A rate-driven variance means the accrual driver needs updating. A contract violation needs a credit memo, not a plug to the P&L. ### C. A standing rate card and terms register Keep one register, shared by AP and accounting, listing each active vendor's rate card, volume tier thresholds, surcharge formulas, and NTE caps. Contract terms live in PDFs signed by procurement; without a register, accounting rebuilds the accrual driver from memory every month. ## 4. How does this affect the gross margin bridge at close? An accrual built on contract terms produces a smaller true-up when the real invoice lands, which means less noise moving through cost of goods sold in the following period. A recurring true-up in the same direction, accrual consistently low or consistently high, is itself a signal that the accrual driver is wrong, not that the vendor's billing is volatile. Tracking the direction and size of true-ups by vendor turns the close into a diagnostic instead of just a plug. A [gross margin bridge](/guides/building-a-gross-margin-bridge-that-separates-inflation-from) separates volume, price, and mix effects, but a badly built accrual introduces a fourth, unlabeled effect: timing error that gets misread as one of the other three. If accruals consistently run low for a freight vendor, the true-up lands as an unfavorable price variance in the month it is caught, even though the actual cause is a fuel surcharge formula the accrual never priced correctly. That miscodes the variance and makes the bridge harder to explain to a board or a sponsor. Tracking true-ups by vendor and by category, not just by total dollar amount, shows which accrual drivers need correction. A vendor with a consistent one-direction true-up over several months has a contract term the accrual formula is not capturing, and that is worth fixing once rather than replugging every close. ## 5. Who should own the accrual driver for service spend? Accounting should own the accrual entry, but the accrual driver, meaning which rate, tier, and formula applies, should be sourced from whoever owns the vendor contract: procurement or the category manager. Without that handoff, accounting estimates a number it has no basis to challenge, and procurement negotiates terms accounting never applies. A monthly sync between the two closes that gap without adding headcount. Contract terms are negotiated by procurement or a category owner and often never reach the accounting team that books the accrual. The accountant closing the freight accrual has no reason to know a new fuel surcharge formula took effect this quarter unless someone tells them. A short monthly sync, or a shared terms register updated whenever a contract renews, moves that information across the handoff. This is not a system requirement. It is a process requirement: someone is responsible for updating the accrual driver whenever a contract changes, and someone is responsible for asking. In [a multi-entity manufacturer](/guides/month-end-close-for-multi-entity-manufacturers), this handoff multiplies by every entity with its own vendor contracts and its own close calendar, which is exactly where a shared register earns its cost. ## 6. When does a service spend accrual gap justify a deeper review? A repeated true-up in the same direction for the same vendor, a contract with a surcharge or tier clause nobody can currently locate, or a category where the accrual driver has not been checked against the contract in over a year are each a reason for a deeper review. None of these require a full audit to investigate; they require pulling the contract and the last several invoices side by side and checking the math once. Not every accrual variance needs a project. Small, alternating true-ups that net near zero over a quarter are normal estimation noise and do not need escalation. A pattern is different from noise. If the same vendor produces a true-up in the same direction for three consecutive months, the accrual driver is wrong, not the estimate. If nobody in accounting or procurement can locate the current signed contract for a vendor category, that is a control gap independent of any specific accrual. When a category has not had its contract terms checked against actual billing in over a year, treat that as due for review regardless of whether a variance has shown up yet, since the absence of a flagged variance can mean the accrual and the invoice are both wrong in the same way. For the wider pattern this sits inside, start with the [margin drift](/guides/cfo-agenda-mid-market-manufacturing) guide. ## Common questions ### What is the right accrual basis for freight when the fuel surcharge changes mid-month? Use the contract's stated surcharge formula and the fuel index value for the period, not last month's invoiced surcharge amount. If the formula references a published index, the accrual should reference the same index reading, so the variance at true-up reflects only volume, not a stale rate. ### Should accounting book an accrual based on the vendor's typical invoice amount? Only as a fallback when no contract terms are available. A prior-invoice-based accrual carries forward any error already present in that invoice, including a surcharge that should have expired or a rate that was superseded by a new agreement. ### How do not-to-exceed caps affect a labor accrual? Accrue on approved hours times the contracted bill rate, then compare the result to the statement of work's not-to-exceed cap before booking. If the calculated amount exceeds the cap, the accrual should reflect the cap, not the uncapped calculation. ### Who should maintain the rate card and terms register mentioned in this guide? Ownership works best when shared: procurement or the category manager supplies and updates contract terms, and accounting maintains the register as the reference accounting uses to build accrual drivers. Neither function should maintain it alone. ### What is the difference between a true-up from volume and a true-up from a contract violation? A volume true-up reflects a change in shipped units, hours, or work orders and needs no correction beyond the entry itself. A contract violation, such as a surcharge applied outside its trigger condition, needs a credit memo from the vendor, not just a journal entry adjustment. --- ValueXPA runs a fixed-scope Margin Drift Diagnostic that validates every service vendor invoice against contract terms, for $100M+ US industrial manufacturers and distributors. Two to four weeks. The client retains 100% of recoveries. https://valuexpa.com/contact-us