Accrual Discipline: Where Mid-Market Accountants Get It Wrong (and What the External Auditor Will Find)

Updated for 2026. Close-cycle tools now ship agent-assisted accrual suggestions; the judgmental layer still belongs to a named human, and the policy attached to it needs the language in our one-page AI governance policy before an external auditor accepts agent-suggested accruals in the workpaper. Why accrual misses are the year's largest adjustments When we walk into a mid-market controller's office for the first time and ask about the prior-year audit adjustments, the conversation almost always lands on the same three or four account areas. Legal and professional fees were under-accrued because the December invoices arrived in late January. The bonus accrual was estimated against a target that had already drifted by Q3 and never re-trued. The vendor rebate was booked against a calendar-year program with a fiscal-year close, and the cutoff was wrong by a quarter. The deferred-revenue rollforward did not tie to the contracts subledger because two enterprise renewals were billed on December 31 and the revenue-recognition memo had not yet been written. These are not arithmetic errors. The controllers are competent; the staff accountants are diligent; the close calendar runs. What fails is the policy layer between "we know we owe something" and "the journal entry is recorded with documented support that an external auditor can pick up cold and follow." The accrual is missed not because the team did not know it existed, but because the documentation discipline that turns a known obligation into a recorded liability with an audit trail was never built. The pattern across the mid-market firms we have audited the close for, in engagements we have run over the last three years, is consistent. Recurring accruals, rent, payroll, utilities, predictable subscription expenses, are accurate. The team has run them every month for years; the calculations are formulaic; the reversals work. Judgmental accruals, warranty reserves, litigation contingencies, restructuring charges, vendor rebate true-ups, bonus accruals against shifting targets, are where the audit adjustments cluster. The judgment is not the problem. The absence of a written, owner-named, evidence-backed policy for how that judgment is exercised, documented, and reviewed is the problem. The auditor finds the misses because the auditor is the first reader who is not already familiar with the firm's mental model of its own accruals. This guide walks through the accrual mistakes we see most often in mid-market private companies and PE-backed portcos, the audit-side procedures that surface them, and the policy artifact every finance organization above roughly forty million dollars in revenue should have in writing and review annually. The under-accrued legal and professional fees The single most common accrual miss we surface in a close diagnostic is the legal and professional fees line. The mid-market firm runs an active matter list with two or three external law firms, a tax advisor, and an audit firm whose engagement letter spans the fiscal year. The internal accounts payable team books invoices when received. The invoices for December services routinely arrive in late January or early February, after the close has been completed and the trial balance locked, and the controller's accrual estimate at year-end is built from whatever invoices were on hand at the time of the cutoff. The miss is structural. Legal counsel bills on time-and-materials, often sixty days in arrears for complex matters. Tax advisors bill in milestones tied to filing deadlines that fall well after the fiscal year-end. The audit firm's December work, the planning meetings, the early interim testing, the controls walkthroughs, is in process during the close itself and gets billed later. A controller who books only what is on the AP desk at cutoff is, by definition, under-accruing professional fees. The auditor's search for unrecorded liabilities procedure, run six to ten weeks after year-end, picks up the invoices that arrived in the post-close window and proposes the adjustment. The adjustment is rarely small in mid-market: we have seen single-engagement adjustments of fifty to two hundred thousand dollars on legal alone for firms in active litigation or M&A. The fix is a standing accrual procedure that does not rely on invoices arriving on time. The controller establishes a quarterly call with each external law firm and tax advisor, conducted in the last week of the quarter, to obtain a work-in-progress estimate at the matter level. The estimate is documented in writing, an email from the partner or a brief memo with hours, rates, and matter status, and forms the basis for the period-end accrual. The same process runs with the audit firm: the engagement partner provides a work-in-progress estimate at year-end as part of the close support, and the controller accrues against that estimate rather than waiting for the invoice. The accrual reverses the following month and replaces with actual invoiced amounts as they arrive, with the variance investigated and explained if material. The procedure is part of the 10-day close calendar on Day 2 alongside the broader expense cutoff, and the work-in-progress emails are filed in the close evidence pack as the accrual support. The discipline turns a recurring audit adjustment into a recorded liability with documented support. The auditor's search for unrecorded liabilities still runs, but now it confirms the accrual rather than producing the entry. Bonus accruals that drift through the year The bonus accrual is the second most common miss, and the failure mode is almost always the same. The annual operating plan sets a bonus target, say four percent of base salary at plan, with a multiplier that ranges from zero to two hundred percent based on company performance against EBITDA, revenue, or a balanced scorecard. The controller accrues one-twelfth of the target bonus pool each month against the assumption that the company will hit plan. By Q3, performance has drifted, the company is tracking at one hundred twenty percent of EBITDA target and ninety percent of revenue, the multiplier is materially different from the plan assumption, and the accrual is now wrong in two directions at once. The true-up at year-end is large, lands in December, and produces a December operating-margin distortion that the CFO has to explain to the board. The structural problem is the absence of a quarterly re-estimate against actual performance. The bonus pool is a function of company performance against the plan metrics; if the metrics drift, the pool moves with them. A controller who continues accruing against the plan assumption, rather than against the most recent realistic estimate of full-year performance, is producing a bonus accrual that is correct only on the day the budget was signed and increasingly wrong every month thereafter. The fix is a quarterly bonus accrual review, owned by the controller in collaboration with the head of HR and the CFO, conducted in the first ten days of the month following each quarter-end. The review takes three inputs: actual performance against the bonus metrics through the most recent month, a forecast of full-year performance against those same metrics from FP&A, and the plan-document multiplier table that converts metric performance into pool sizing. The output is a re-estimated full-year bonus pool, the accrued portion through the current period (a straight-line through the service period for most plans, though plans with cliff vesting require different treatment), and a journal entry that adjusts the cumulative accrual to the re-estimated through-period amount. The re-estimate is documented in a memo signed by the controller and the CFO, filed in the close evidence pack, and reviewed by the audit committee at the quarterly meeting. The procedure also surfaces the plans where the structure itself produces an accrual problem. Discretionary bonuses without documented metrics are difficult to accrue under ASC 710 because the obligation does not crystallize until the discretion is exercised. Plans with retention provisions, bonuses paid only if the employee is still employed on the payment date, require a probability-weighted accrual that reflects historical attrition. Plans with performance-based vesting tied to multi-year metrics require a longer estimation horizon. The accrual policy artifact documents the treatment for each plan structure the firm operates, and the quarterly review applies the documented treatment rather than re-litigating the question every cycle. Vendor rebate true-ups and the calendar-year mismatch Vendor rebates are a quiet source of audit adjustments in industries with high merchandise or component spend, distribution, light manufacturing, retail, certain healthcare verticals. The vendor and the customer enter into a rebate agreement that pays a percentage back to the customer based on annual purchase volume, often on tiered thresholds. The agreement runs on the vendor's calendar year. The customer's fiscal year does not match. The customer's purchasing volume in the first half of the vendor's calendar year is the customer's prior fiscal year; the second half is the current fiscal year. The accrual must be split correctly across the customer's fiscal periods or the revenue (under ASC 705-20, vendor rebates are typically recorded as a reduction of cost of goods sold) is misstated. The miss happens when the controller treats the rebate as a single annual receivable, recorded when the vendor confirms the volume in late February or March of the following year. The full benefit lands in the post-year-end period, the prior-year cost of goods sold is overstated, and the auditor proposes an adjustment to push the rebate back into the year it economically belongs to. We have surfaced six-figure adjustments on this single line in distribution-business diagnostics. The fix is a quarterly rebate calculation against the contract terms, owned by the controller or a designated cost accountant, with the calculation supported by a purchase-volume report from the ERP (NetSuite, Sage Intacct, or whatever the firm runs), the rebate-tier table from the vendor agreement, and a written estimate of the year-end tier the customer is on track to hit. The accrual is recorded against COGS each quarter, builds toward the expected annual amount, and is trued up when the vendor's confirmation arrives. The contract file, the rebate agreement, the tier table, the quarterly calculations, and the vendor confirmation, is filed in the close evidence pack and pulled in the audit's revenue/COGS testing. Most importantly, the controller maintains a one-page rebate inventory that lists every active rebate agreement, the vendor, the contract period, the tier structure, and the assigned owner. The inventory is reviewed quarterly. New rebates are added; expired rebates are removed; the inventory becomes the audit-ready reference document for the entire program. Deferred revenue cutoffs that the audit will probe first Deferred revenue is a high-risk audit area in any subscription, multi-element, or long-term-contract business, and the cutoff at year-end is where the misses cluster. A SaaS company with annual contracts billed up front records the cash receipt on the billing date and the deferred revenue on the same date; revenue is recognized ratably across the service period under ASC 606. The controller's deferred-revenue rollforward, beginning balance, plus billings, minus revenue recognized, equals ending balance, has to tie to the contracts subledger. In practice, this is where the breaks happen. The most common miss is contracts billed on the last business day of the period that are not loaded into the revenue-recognition module of the ERP until the following period. The cash hits the bank, the AR is recorded, the deferred-revenue entry on the contract is missed, and the period's revenue is overstated by the amount that should have been deferred. The mirror miss is a contract that ended on the last business day of the period and was not closed in the rev-rec module; revenue continues to recognize against a stale schedule into the following period, and the deferred-revenue balance is wrong. The fix is a cutoff procedure run by the revenue accountant on Day 1 of the close, before any revenue posting is locked. The procedure lists every contract billed in the last five business days of the period, every contract terminated or amended in the same window, and every renewal that crossed the period-end. Each item is verified against the rev-rec module: the contract is loaded, the schedule is correct, the revenue allocation across performance obligations under ASC 606 is documented, and the deferred-revenue entry is recorded. The list and the verification become the cutoff evidence. The auditor's revenue testing pulls the same list, through their own selection, and the firm's documentation either ties cleanly or does not. When the documentation ties, the audit moves on. When it does not, the auditor expands the sample, finds more breaks, and proposes a cumulative adjustment that lands as a finding in the management letter. For firms with material non-routine contracts, multi-element arrangements, contracts with significant variable consideration, contracts with material right-of-return provisions, the policy artifact requires a contract-specific revenue-recognition memo, prepared at contract execution and refreshed at each period-end if circumstances change. The memo identifies the performance obligations, the standalone selling prices, the allocation, the recognition pattern, and the cutoff treatment. The memo is filed in the contract file and pulled in the audit. Without the memo, the controller is reconstructing the revenue judgment under audit pressure, and the reconstruction rarely produces a cleaner answer than the contemporaneous documentation would have. Capex versus expense at year-end The capex-versus-expense classification question becomes acute at year-end because the timing of the capitalization decision affects both the current-year operating expense and the depreciation schedule that flows through subsequent periods. A three-hundred-thousand-dollar IT infrastructure refresh placed in service on December 28 is a capitalized asset with a five-year depreciation schedule under most useful-life policies, which means roughly a thousand dollars of depreciation in the current year and the remainder spread across five years. The same expenditure treated as an expense lands the full three hundred thousand dollars in the current year's operating costs. Auditors test this classification carefully because the temptation to expense in good years and capitalize in tough years is real and the policy line is judgmental. The mid-market pattern we see most often is inconsistency rather than fraud. The firm's capitalization policy is loosely documented, a five-thousand-dollar threshold mentioned in a controller memo from three years ago, a useful-life table that does not cover the asset categories the firm now buys, no written policy for software development costs under ASC 350-40 (internal-use software) or ASC 985-20 (software for sale), no documented treatment for cloud-computing arrangements under ASU 2018-15. Different staff accountants apply different rules. The fixed-asset rollforward looks consistent because the additions are categorized to match the prior year, but the underlying decisions are not consistent at all. The fix is a written capitalization policy that addresses, at minimum, the dollar threshold, the useful-life table by asset category, the treatment of software development costs (internal-use, for-sale, and cloud-computing arrangements), the treatment of leasehold improvements (which intersects with ASC 842 lease accounting for operating leases), the treatment of repair-versus-improvement decisions, and the approval matrix for capital expenditures over defined thresholds. The policy is reviewed annually and approved by the controller, the CFO, and (for material amounts) the audit committee. Year-end capex review is a documented procedure: every capital project closed in Q4 is reviewed for proper classification, the in-service date is documented, the depreciation schedule is set up in the fixed-asset module (NetSuite Fixed Assets, Sage Fixed Assets, BNA, ProSeries, or whatever the firm runs), and the controller signs off on the rollforward before the trial balance is locked. Accrual reversal hygiene A class of misses that does not get the attention it deserves is the failure to reverse accruals correctly in the period following the accrual. The controller accrues fifty thousand dollars of professional fees in December against estimated work-in-progress. In January, the actual invoices arrive totaling fifty-three thousand dollars. The accrual reverses for fifty thousand and the invoices post for fifty-three thousand, producing the correct three-thousand-dollar variance in January's expense. The mechanics are simple. The failure mode is that the reversal does not happen, or happens partially, and the same accrual lingers on the trial balance for months as a stale liability while the actual invoices post separately. The expense double-counts; the liability double-counts; the trial balance carries a phantom obligation that nobody can tie to a contract or a vendor. The discipline that prevents this is two-part. The first is the use of automatic-reversing journal entries in the GL: every accrual is booked with the reversal date in the GL system, the reversal posts on the first business day of the following period without manual intervention, and the controller does not have to remember to reverse anything. NetSuite, Sage Intacct, Microsoft Dynamics, Oracle Cloud Financials, and Workday Financial Management all support automatic reversal with an effective-date posting. The second is the monthly accrual rollforward review: the controller pulls the accrued-liabilities sub-account list at the start of each month, identifies every accrual older than two months, and either reverses the stale accrual (if the underlying obligation has resolved) or documents why the accrual remains valid. Stale accruals over a documented threshold trigger an investigation that closes the question one way or the other. The rollforward is filed in the close evidence pack and reviewed by the assistant controller as part of the monthly account reconciliation evidence pack. What the auditor actually does to find your accrual misses The audit-side procedures for accrual completeness are well-documented in the AICPA's audit guides and in the planning memos every external auditor produces, but mid-market controllers often respond to them under pressure rather than preparing for them in advance. Three procedures matter most. The search for unrecorded liabilities is run six to ten weeks after year-end. The auditor pulls every payment made by the firm in the post-year-end window, typically all checks, ACHs, and wires above a stated dollar threshold, and traces each payment back to the underlying invoice. For each invoice, the auditor confirms whether the goods or services were received before or after year-end. Goods or services received before year-end with no corresponding accrual are unrecorded liabilities, and the auditor proposes an adjustment. The procedure is mechanical, comprehensive within its threshold, and almost always finds something. A controller who has run a parallel internal procedure two weeks before the auditor arrives, pulling the same payment list, tracing the same invoices, recording the missed accruals as adjusting entries before the auditor sees them, produces a cleaner audit and avoids the proposed adjustments that turn into management-letter findings. The subsequent-events review under ASU 855 is the procedure that surfaces the events between year-end and audit-report-issuance that should have been recorded or disclosed. The auditor reads board minutes through the subsequent period, asks management about material events, and reviews the post-year-end financial activity for items that affect the year-end balances. Mid-market firms with active litigation, M&A activity, or covenant negotiations need a subsequent-events checklist run by the controller through audit completion, with each item evaluated for Type I (recognized) or Type II (disclosed) treatment. The accrual completeness assertion is tested through analytic procedures (current-year accrual balances compared to prior year, ratio analysis against revenue or expense base) and substantive testing (vouching individual accruals to support and recalculation). The substantive testing is where the policy artifact pays for itself: an accrual with a documented basis, a named owner, a contemporaneous estimate memo, and a clear reversal trail passes substantive testing in fifteen minutes. An accrual without the documentation produces follow-up questions that consume audit hours and surface other questions the controller has to answer under deadline pressure. What we recommend Building accrual discipline that survives the external audit is a finite project, not a permanent state of vigilance. The work concentrates in four artifacts and one cadence. Build the accrual policy as a single document that addresses recurring accruals (rent, payroll, utilities, recurring subscription expenses), judgmental accruals (bonus, warranty, litigation, restructuring, vendor rebates), capitalization thresholds and treatment, and the search-for-unrecorded-liabilities procedure run internally before the auditor arrives. The policy is signed by the controller and the CFO, reviewed annually, and filed in the audit evidence repository. Maintain the rebate and contract inventories as living documents updated quarterly. Every active vendor rebate, every multi-element revenue contract, every accrual-bearing arrangement is on a one-page reference document with an owner, a contract period, and the relevant calculation. The inventory is the controller's single source of truth and the auditor's first request. Run the quarterly judgmental accrual review as a documented procedure with the controller, the CFO, and the relevant business-side partner (HR for bonus, legal for litigation, operations for warranty). The review re-estimates each judgmental accrual against the most recent data, documents the basis in a memo, and adjusts the cumulative accrual. The memos are filed and reviewed by the audit committee. Operate automatic accrual reversals in the GL with a monthly rollforward review of every accrual line item. Stale accruals are investigated and closed within a defined window. The rollforward is part of the close evidence pack. Run an internal search for unrecorded liabilities two weeks before the external auditor's procedure begins. The same population, the same threshold, the same trace-back. Adjustments identified internally are recorded as journal entries before the auditor arrives. The audit confirms; it does not propose. The accrual policy template included in the artifact for this guide is the version we install in mid-market engagements when the controller asks for a starting point. It is not exhaustive; every firm tunes it to its own contracts, plans, and industry. It is, however, the structural baseline that turns accrual discipline from a recurring source of audit findings into a documented, owner-named, evidence-backed practice that the auditor confirms rather than corrects.