Cut-Off Rules: Deciding What Belongs in the Month You Are Closing

Most close disputes are not accounting disputes. They are arguments about which month a transaction belongs to, held under time pressure, between people who each have a reason to prefer a different answer. The sales lead wants the order in the month that closes their quarter. The operations manager wants the supplier invoice in next month because this month’s cost line already looks bad. The bookkeeper wants whatever ends the conversation. Nobody is being dishonest and the outcome still moves depending on who is in the room.

An unwritten cut-off rule gets bent by whoever pushes hardest, and it gets bent slightly differently every month, which is worse than being bent consistently. The reported months stop being comparable, and comparability is the entire reason anybody reads a monthly number.

So write it down. One page, four transaction streams, a gate time for each, and exactly one person who may grant an exception. This is the first document we publish when we take a close on, ahead of the calendar, because a calendar built over an unsettled cut-off just schedules the same argument. Publish it to the whole company rather than to finance, because every one of the four streams is fed by someone outside finance and none of them will change behaviour because of a rule they were never shown.

One thing before the standard itself. Cut-off is an accounting policy decision, and the company owns it. A finance provider drafts it, argues for it and applies it, and the owner agrees it in writing before it is published. That is not a formality. The whole force of the standard comes from the fact that the company adopted it, and a rule imposed by a provider is a rule that gets tested the first month it costs somebody something.

The one page

This is the shape of the standard. Fill in your own gate times and your own names, keep it to a page, and put a version date on it.

Stream	The event that decides the month	The evidence of that event	The gate	Who may grant an exception
Revenue	The month the work was delivered, the goods shipped or the milestone accepted. Not the month the invoice was raised, and not the month the customer paid	A signed delivery note, an acceptance email, a completed timesheet, a shipping record, a milestone sign-off. Something dated by somebody outside finance	Invoicing for the period closes at a stated hour on a stated business day, and the delivery evidence has to be in the file by then, not promised	Named individual, normally the finance lead, with the owner as the only escalation
Purchases and payables	The month the goods were received or the service was performed. Not the invoice date and never the payment date	The receiving record, the timesheet of the contractor, the period stated on the invoice itself where it is a service period	AP entry for the period closes at a stated hour, after which the received-not-invoiced list is prepared and accrued	Same named individual
Payroll	Set by the pay calendar and by statute, not by preference. Days worked in the month and not yet paid are accrued	The payroll provider’s register, the pay calendar published at the start of the year, the timesheet lock	Fixed by the pay calendar. The only decision is whether the accrual is calculated, and it always is	Nobody. This row has no exception path, which is the point of it
Employee expenses and card spend	The month the expense was incurred, which is the transaction date on the receipt	The receipt, dated. A card statement line without a receipt is not evidence of anything except that money left	Expense reports and card receipts due by a stated hour on a stated day, published in the notice with the date in the subject line	Named individual, and the standing rule below removes most of the requests

The fourth row is where the standard earns its keep, and it does it by having a default that nobody has to approve. An expense report that arrives after the gate is posted to the month it arrives in, not to the month the expense was incurred, unless it is above the written threshold. That rule is slightly wrong in accounting terms and it is right in practice, because the alternative is a close held open every month for a handful of small items, and because a rule with a visible consequence is the only thing that ever moves the behaviour. Publish the threshold with the rule so nobody has to guess whether their claim is the exception.

The second row is the one that costs the most when it is missing. A company that dates purchases by invoice date rather than by receipt date will have a cost base that moves with its suppliers’ billing habits, and the variance commentary will spend the year explaining supplier administration rather than anything about the business.

Building the standard, step by step

Executable in an afternoon, and then once a year to review it.

1. Write down what you do now. Not what the policy says, what actually happens. Ask the bookkeeper how they decide, and expect the answer to be a set of habits rather than a rule. That description is the starting draft, and about half of it is usually already correct.
2. Decide the four gate times. Work backwards from the lock date on your close calendar, not forwards from month end. If the package is due on a given business day and the reconciliation work takes what it takes, the gates fall where they fall. A gate chosen for tidiness rather than from the calendar will be missed every month.
3. Name one exception approver, and one escalation. One. Two approvers is no approver, because a request that fails with the first one goes to the second, and everybody learns the order within a month.
4. Write the threshold. Above it, a late item is worked into the month it belongs to. Below it, the default applies. Use the review threshold the close already sets rather than inventing a second one, because two thresholds doing similar jobs will eventually be quoted against each other.
5. Get the owner’s agreement in writing. An email is enough. What matters is that the rule is the company’s rule and can be pointed at.
6. Publish it to everyone, with the gates in the subject line of a recurring notice. Not an attachment in a shared drive. The notice goes out before every close, and it names the gate times and the person to ask.
7. Make the system enforce it where the system can. Close the AP entry date, lock timesheets, restrict posting to a closed period by role. A rule that depends on people remembering which dates are special survives about one busy month. A rule the software enforces survives the person who wrote it.
8. Open an exception log. Date, item, amount, who asked, who approved, which month it landed in. Two lines per exception.
9. Read the log once a quarter. This is the step everybody skips and it is where the standard actually improves. Ten exceptions from the same source is not ten exceptions, it is one gate in the wrong place or one process that does not fit the business. A log that is mostly the same source every quarter, month after month, is usually telling you the close needs remediation rather than a tighter gate.

When something arrives after the gate

Three questions, in this order, and the order matters because the second one closes most cases.

One: is it above the written threshold? If not, the default applies, it goes to the current month, and nobody is asked anything. Most late items stop here.

Two: would including it change something a person will rely on? A covenant calculation, a bonus or commission figure, a distribution decision, a figure already given to a lender, a reported result somebody is about to price a decision from. If none of those is true, the default still applies even above the threshold, and the item is noted in the exception log so it is visible at the next close.

Three: is the period locked? If it is not, the exception approver may take it into the closing month, and their name goes on the log entry. If it is locked, the answer is almost always no. Reopening a locked period means reissuing the statements and telling everyone who read the first version, which is the correct cost and the reason the answer is almost always no. The narrow case where you do reopen is the one where the reported figure was materially wrong and somebody has already acted on it.

The step that gets skipped in practice is the second one, because it requires knowing what the number is going to be used for. That is a finance judgement and it does not delegate well. It is also the reason the exception approver should be the finance lead rather than the person who prepared the entry.

The two arguments you will actually have

Nearly every cut-off dispute at this size is one of these two, and they are not the same argument.

The quarter-end order. Sales has an order signed on the last day and wants the revenue. The rule does not care when the order was signed, it cares when the work was delivered. This is not a negotiation and it should not be handled as one, but it is worth being clear that the rule is not a judgement about the sales team. Two things make the conversation survivable: settle the rule before the quarter that will test it, and make sure the sales compensation plan measures signed orders rather than recognised revenue, so the two documents are not asking the same person to want two different things. Where the compensation plan does measure recognised revenue, that is a design problem to raise with the owner rather than a cut-off problem to solve at close.

The invoice that arrives on day four. A supplier invoice for work done last month, arriving after the AP gate. This one is easy and it is misunderstood constantly. The invoice arriving late does not move the cost; the cost belonged to the month the work was done and it should already be on the received-not-invoiced accrual. If it is not, the failure is upstream in the receiving process rather than in the cut-off, and the fix is a receiving record rather than an exception.

What the standard deliberately does not cover

It does not decide how revenue is recognised over time on a contract. That is a revenue recognition policy question, it is a different document with a different owner, and the cut-off standard assumes it has already been answered. Cut-off decides which month an event lands in. The policy decides how much of a contract’s value that event represents. Conflating the two produces a cut-off rule that quietly rewrites a revenue policy, which is exactly the kind of change nobody notices until an external reader asks about it.

It also does not decide materiality for the close as a whole. It borrows the review threshold that the close already sets.

What we do not do

We do not enforce a cut-off standard the owner has not agreed in writing, because it is the company’s accounting policy and not ours to set.

We do not accept an invoice date as evidence of a delivery date, in either direction, and that includes the invoices that would help.

We do not let the exception approver be the person who benefits from the exception, which sounds obvious until the requester is the owner and the approver reports to them. In that case the exception still gets logged, with both names on it, and it gets read out at the quarterly review of the log.

And we do not hold a close open for a late item below the threshold. The month closes. The item lands where the rule says it lands, and if that happens often enough to matter, the gate moves at the next annual review rather than every month by request.