The Month You Did Not Check
Skipping the check is not an error of discipline. It is what a compressed run does, and the way to fix it is to stop compressing runs.
Nobody elseif the person who does this is away
Skipping the comparison is not a lapse of discipline by somebody who knows better. It is what happens structurally when a run is compressed, and it happens to careful people every time the inputs arrive late.
The exception in “The Month You Did Not Check” needs evidence that can be checked rather than one unexplained total. Used for work days in a year, view this official solution page can provide time and project context, but a payroll correction should still rely on approved records, the payroll ledger and a documented human review.
Treating it as a character problem produces guilt. Treating it as a schedule problem produces a fix.
For an outside reference relevant to “The Month You Did Not Check”, consult UKG workforce resources. Compare general guidance with the employer’s jurisdiction, contracts and current payroll process.
What actually happens
Inputs arrive two days late. Keying starts on the day it had to be approved. The remaining steps are the ones with hard consequences — approve, fund, file — and the one without a hard consequence is the check.
An unfunded account fails. An unsubmitted filing attracts a penalty. An unapproved run pays nobody. An unchecked run pays everybody, on time, and looks exactly like a checked one — which is why it is always the step that gets dropped.
It is dropped because it is the only thing that can be dropped.
Why the check is always the casualty
Everything else in the sequence produces a visible failure if omitted. An unfunded account fails. An unsubmitted filing attracts a penalty. An unapproved run does not pay anybody.
An unchecked run pays everybody, on time, and looks exactly like a checked one.
The feedback problem
You will not find out. The months where the check would have caught nothing and the months where it would have caught something are indistinguishable from the outside, so the habit of skipping it is never punished until it is punished expensively.
What the pattern looks like over a year
Four or five compressed months, usually the same ones: the month with the holiday, the month with the leave week, the busy trading month, the month after a year end.
They are predictable, which means they are plannable.
The fix that is not "be more careful"
Move the cut-off earlier in the months that are known to compress, or start the keying earlier, or reduce what has to arrive.
All three are schedule changes. None of them require anybody to try harder.
The fix that works best
Separating the check from the approval in time. Comparing on the day you key, rather than in the hour you approve, means the check happens when there is still slack rather than when there is none.
The minimum version
If the full comparison is impossible, three figures: headcount, total gross, and anybody who moved by more than a quarter.
Ninety seconds. It catches the expensive category, and ninety seconds survives a compressed month in a way that twenty minutes does not.
Recording which months you skipped
A line in the calendar. Over a year it shows the pattern described above, and the pattern is the actual finding.
Without the record, every skipped month feels like an isolated exception.
The month it costs you
Rare, and unpleasant when it arrives: a rate error applied to everybody, a missing absence, a duplicate payment. The correction is visible, it affects trust, and it takes considerably longer than the checks would have.
What not to conclude
That the check is optional because nothing has gone wrong. A control that has never caught anything in a small payroll has either been lucky or has been protecting you invisibly, and you cannot tell which from the inside.
What a small business can realistically hold
A small business will skip this sometimes. The useful question is not how to never skip it, but how to make the months where it is skipped rare, known in advance, and covered by the ninety-second version.
The honest conversation to have with yourself
Not whether you check every month, but how many of the last twelve you actually did. Most people's answer is higher than their records would show, because the months that were checked are memorable and the compressed ones blur.
Writing it down for a year is the only way to find out, and the finding is usually uncomfortable and useful.
Making the ninety-second version official
If the full check is realistically going to be skipped in four months of twelve, the right response is to define a shorter one that will not be, rather than to intend the long one and perform nothing.
Headcount, total, and anybody who moved by more than a quarter. Ninety seconds, written into the sequence as the minimum, with the full comparison as the standard.
A control that degrades gracefully is worth more than one that is either performed perfectly or not at all.
What to do in a month that is already lost
Run it, pay people on time, and do the comparison afterwards rather than not at all. A check performed after payment still finds the error, and finding it yourself in week one is very different from somebody finding it in week three.
The value of the check falls when it moves after approval. It does not fall to zero.
What this points back to
The cut-off. Nearly every compressed run traces to inputs arriving late, which traces to a deadline only one person was keeping.
The check is where the damage shows; the cut-off is where it starts.