The Payroll Cutoff Is the Only Fixed Point

Wages have to be in people's accounts on the day they are expected. That date is fixed by contract, by expectation and in several jurisdictions by law, and nothing upstream of it has the same status.

The deadline pressure in “The Payroll Cutoff Is the Only Fixed Point” is a workflow problem before it becomes a people problem. Organisations considering employment of relatives policy with accountable controls in relation to employment of relatives policy can use reminders and current project records to shorten the distance between work and submission, but they should still pay undisputed time and preserve a clear correction route.

Work backwards from it and the whole timetable appears. The bank file goes out some days before the pay date. Payroll needs time to run, check and correct before that. Approvals must be complete before payroll starts. Submissions must be complete before approval starts. Every one of those intervals is compressible except the first, and under pressure the compression lands entirely on the two that involve judgement.

For a separate benchmark relevant to “The Payroll Cutoff Is the Only Fixed Point”, consult the Employment New Zealand recordkeeping guidance. Use it to test record quality, approvals, retention, employee rights and exception handling against the real workflow rather than treating a software report as self-explanatory evidence.

The real timetable

Most organisations have a published timetable and an actual one, and the gap between them is where the process lives.

The published version says submit by Friday, approve by Monday, payroll runs Wednesday. The actual version is that half the submissions arrive Monday, chasing runs until Tuesday lunchtime, approvals happen in a batch on Tuesday afternoon, and payroll starts with a set of records approved in bulk two hours before the file is built.

Map your own. Pull the distribution of submission times and approval times against the published deadlines for the last six periods. It takes an hour and it is the single most useful diagnostic in this area, because almost every complaint about timesheet quality turns out to be a complaint about that distribution.

Why the compression lands where it does

Payroll cannot absorb delay; it has the hard date. So the slack is taken from the step with the least formal standing, which is approval, and from the step with the least visible owner, which is correction.

This is not a failure of discipline. It is the only available response to a late input and a fixed output. Organisations that attempt to fix it by exhortation — asking managers to approve faster — are asking for the same compression under a different name.

The lever that actually exists

Move the submission deadline earlier relative to the period, or decouple payment from approval. Those are the only two structural options and everything else is a variation on one of them.

Submitting earlier means paying on a lagged period: the hours worked up to a week before the pay date, with the remainder carried into the next run. It is standard practice in hourly environments and resisted in salaried ones because it feels like a delay in pay, which it is not — it is a shift in which hours a payment covers, applied once.

Decoupling means paying contracted hours on schedule regardless of timesheet state, and settling variances in the following period. It removes the deadline's grip on approval entirely and is the configuration that makes considered approval possible. It also requires finance to accept a reconciliation they currently avoid, which is the real obstacle.

What the fixed point does to approval quality

An approver with four hours and sixty timesheets will approve in bulk, and every piece of this collection about measuring review intervals will show it. The behaviour is correct given the constraint; the constraint is the problem.

Two numbers tell you whether your approvers have a real window: the median gap between a person's submission and the approval deadline, and the number of timesheets per approver. Four hours and sixty is not a window. Two days and twelve is. The second organisation does not have better managers.

Where the cutoff is doing damage beyond pay

Billing and claims inherit the same timetable even though they have different deadlines, and this is where the cost is highest. A grant claim prepared from records that were rushed to meet a payroll date carries that rush into an audit years later.

Where the two can be separated — where billing and claim preparation work from a slightly later, corrected version of the record rather than the one payroll used — the quality of both improves. That requires the system to keep a version history rather than overwriting, which most do and few are configured to use.

Publishing the real timetable

Most organisations publish the deadlines and not the reasons. People see a Friday submission date and a Monday approval date with no indication of what happens afterwards, which makes both look arbitrary and therefore negotiable.

A single diagram showing the chain — submission, approval, payroll run, bank file, pay date — with the dates on it changes how the deadlines are received, because the Friday date stops being an administrative preference and becomes visibly the last point at which something can still be checked. It also exposes, to whoever draws it, how little slack there actually is, which is frequently the first time anybody has looked.