Setting Accrual Thresholds So the Close Stops Chasing Small Amounts

The last two days of a slow close are almost never spent on anything that matters. They are spent deciding whether to accrue a courier bill, whether a partial month of a subscription is worth a journal, and whether the hydro estimate should be trued up. None of those answers change what anybody does with the reporting. All of them cost a morning.

A written accrual threshold buys back more close time than any system change I have seen a company make, and it costs nothing but an afternoon and a decision. That is the whole argument. What follows is how to shape it, because the version most companies write is one number, and one number is the wrong shape.

Why one number fails

A single threshold treats a recurring item and a one-off item as the same problem. They are not, and the difference is the entire design.

A one-off below the line is genuinely immaterial. It happens, it is small, it is gone. Leaving it out costs the reader nothing.

A recurring item below the line is different, because it lands the same way every month. If you never accrue the contractor invoices that arrive a week late, every month is understated by roughly the same amount, and the twelve of them add up to something you would not have accepted as a single entry. Companies do this and call the result conservative. It is not conservatism. It is a known, directional, repeating error that you have chosen because each instance is small enough to argue about individually.

So the first rule of a threshold policy: a threshold applies to whether you investigate, never to whether a known recurring item is recorded. If you know it is there and you know roughly what it is, it goes in as a standing entry regardless of size, because a standing entry costs nothing after the first month.

The threshold matrix

The matrix below is the artifact. The numbers in the third column are yours to set, and the second column is the test that tells you where to set each one. Different categories get different lines because they behave differently, not because the accountant enjoys complexity.

Accrual category	The test that sets the line for this category	Below the line, do what	Evidence retained
Payroll, employer contributions, statutory remittances	No line. These are calculable to the dollar from the payroll register.	Not applicable	Register, remittance confirmations
Vacation and other time-off entitlement	No line, because the balance carries forward and an error never washes out	Not applicable	Entitlement schedule by person
Commission and variable pay earned in the period	No line if it is calculable from the period’s own sales data	Not applicable	Calculation tied to the revenue report
Contractor and subcontract work delivered, not yet invoiced	Set against what a full month of the category costs. If a typical single engagement is above your line, this category is a standing accrual.	Standing estimate from the operations schedule, trued next month	Operations schedule or job listing
Professional fees for work in progress	Set against how much of this you buy in a year. Lumpy and infrequent argues for a lower line, not a higher one.	Leave out, note in the file	Engagement letters, scope confirmations
Utilities, telecom, occupancy running costs	Set high. These are predictable, they are billed on a cycle, and a one-month timing shift reverses itself.	Leave out. Do not true up a recurring utility every month.	The prior three bills, as the estimate basis
Software and subscriptions consumed but not billed	Set high, then check whether the category is on a card. If it is, the exposure is receipts rather than accruals.	Leave out	Subscription register
Freight, courier, small consumables	Set high. This is the category that eats close days for nothing.	Leave out	Nothing beyond the policy note
Repairs and maintenance performed, not invoiced	Set against your largest routine job, not your average one	Leave out, unless the work is on the capital list	Work orders
Interest and financing charges	No line. It comes off the lender’s schedule.	Not applicable	Amortisation schedule
Customer credits, rebates and expected concessions	Set low. An understated credit overstates revenue, which is the direction people notice.	Leave out, and record the reasoning once	Correspondence, credit register
Unbilled revenue for work delivered	No line if the operations system tracks it. If it does not, that is a systems problem wearing an accrual costume.	Not applicable	The delivery record, reconciled

Read the column of “no line” rows. It is longer than people expect, and that is the point. A threshold is for the categories where you would otherwise be doing investigation work, not for the categories where the number is sitting in another system already formatted.

The standing accrual list

The second artifact, and the one that does most of the work. A standing accrual is an entry that runs every month at an estimated amount, gets trued when the invoice arrives, and never gets discussed again.

Maintain the list as a register with four fields: what it is, the basis of the estimate in one sentence, who owns the true-up, and the date the basis was last reviewed. Anything on the register runs whether or not it clears a threshold that month, because the decision was already made and re-making it monthly is the cost you are trying to remove.

A category earns a place on the register when it has appeared in three consecutive closes as a judgment call. That is the trigger. If the same argument about the same expense happens three months running, stop having the argument and post the entry.

The discipline that keeps the register honest is the true-up, not the estimate. An accrual that has been posted at the same figure for eleven months with no invoice tested against it is not an estimate, it is a habit. Review the basis annually, and re-check any line where the true-up has been out by a meaningful amount twice in a row.

Items that get accrued at any amount

These have no threshold, ever, and the reason is the same in every case: they change a decision or a commitment at sizes far below where they would otherwise register.

• Anything inside a lender’s covenant definition. A covenant ratio is calculated from named line items, and an omitted accrual flatters a number somebody outside the company will test. If you are unsure which items are in scope, the covenant definitions matrix is the place that gets settled.
• Anything a bonus, commission plan or earn-out is calculated on. The moment a number determines what a person gets paid, a small omission is not a small omission.
• Related party charges of any kind. These get read by outside parties with more attention than any other line on the statements.
• Anything that would change the sign of a reported result or move a subtotal a reader has been watching. Small in absolute terms and large in effect are different measurements.
• Anything already known to be wrong. A threshold is permission not to investigate. It is never permission to leave in an error you have already found.

How to set the lines without a benchmark

There is no correct number and there is no industry figure worth copying, because the right line is a function of what your reporting is used for. Three tests, applied per category.

The decision test. Would this amount, if left out, change anything said or done at your monthly reporting meeting? Not “would somebody notice”, which is a different and much lower bar. Would a decision move. Most categories fail this test at surprisingly large amounts, and the honest answer is the line.

The accumulation test. If this category were understated by roughly this amount every month for a full year, would the annual figure need explaining to a lender, a buyer or whoever reports on your statements? If yes, the line is too high or the category belongs on the standing register.

The effort test. How long does clearing this category take, in minutes, at close? A category that takes forty minutes and moves the result by an amount that fails the decision test is the category the whole policy exists to kill.

Run the three tests in that order and write the answer down the same afternoon. A threshold discussed and not recorded reverts to whatever the tired person decides at six in the evening on day five, which is exactly the state you started in.

The written basis, and what it contains

One page, in the finance file, and short enough to be read by a new bookkeeper in five minutes.

What the page states	Why it is on the page
The line for each category, in a table	So the treatment is looked up rather than reasoned out
The three tests, and which one set each line	So the next person can re-derive it instead of guessing
The standing accrual register, or a pointer to it	Because the register is the exception to every line above it
The no-threshold list	This is the part people forget, and it is the part with consequences
Who approved it and when	A threshold with no name on it is a suggestion
The annual review date, structurally	Reviewed at the start of each fiscal year, before the first close of that year

Four things trigger a rewrite between annual reviews, and all four are events rather than dates: a new borrowing or an amended credit agreement, a change in reporting framework or in who reports on your statements, an acquisition, and any incentive plan whose calculation touches the accounts. Each of those changes what a decision-relevant amount is, which is the only input the policy has.

What a threshold does not do

It does not travel to your practitioner. The materiality set for a review or an audit engagement is theirs, it is set on a different basis, and yours has no bearing on it. This point is made in the close checklist and it is worth repeating here only because a company that has just written a threshold policy tends to assume it has settled a question it has not.

It does not apply to reconciliations. A threshold is about whether an estimate is worth making. Every balance sheet account still gets reconciled and every difference still gets explained, because an unexplained difference is a symptom rather than an amount. Applying an accrual threshold to a bank reconciliation is the single most common way this policy gets misused.

It does not work in one direction. If you leave small accruals out, you also leave small prepayments and small credits out. A policy applied only where it reduces income is not a policy, and it is legible as such to anyone who reads twelve months of it in a row.

And it does not survive being applied by two people who never spoke. The whole return on this document is consistency, so the last step is the smallest one: whoever prepares the close reads the page once, out loud if necessary, before the first close of the year. Everything above is worth roughly nothing if month four is done to a different standard than month three. The page lives with the rest of the monthly close working papers, filed where the preparer already looks, rather than in an inbox somebody has to remember to search.