Paying Someone Whose Timesheet Has Not Arrived

At the cutoff there will be timesheets that have not arrived. Somebody then decides what to pay those people, and in most organisations that decision is improvised under time pressure by whoever is running payroll.

The deadline pressure in “Paying Someone Whose Timesheet Has Not Arrived” is a workflow problem before it becomes a people problem. Organisations considering this workplace technology guide in relation to how to detect mouse jigglers 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.

It is worth deciding in advance, because the improvised version is what drives almost every bad behaviour upstream: the auto-approval rule, the manager submitting on someone's behalf, the four-hour approval window.

For a separate benchmark relevant to “Paying Someone Whose Timesheet Has Not Arrived”, consult the Canada Revenue Agency payroll 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 three positions

Pay nothing until the timesheet arrives. Defensible only for genuinely hourly workers whose entitlement depends entirely on hours recorded, and even then it carries real risk: in several jurisdictions, withholding pay for hours actually worked because of a missing form is unlawful regardless of policy.

Pay the contracted or scheduled hours and settle the difference later. The standard answer for salaried and rota'd populations, and the one that removes the deadline's destructive grip on everything else.

Pay an estimate based on the previous period. Common, convenient and the worst of the three, because it manufactures a record that nobody asserted and that will be indistinguishable from a real one later.

Why decoupling helps upstream

If payment does not depend on approval, the approval deadline stops being a hard deadline. The approver can take a day. A query can be raised without holding someone's wages. The auto-approval rule can be made to escalate rather than approve, because nothing catastrophic happens when it does.

This single configuration — contracted hours paid on schedule, variances settled in the following period — is the structural change that makes considered approval possible, and it is cheaper than anything else that claims to.

What has to be true for it to work

A reliable record of contracted or scheduled hours to pay against. For salaried staff that is the contract; for rota'd staff it is the published rota, which has to be accurate enough to pay from.

A variance mechanism that actually runs. The hours paid and the hours eventually approved must be reconciled and the difference carried, every period, by somebody whose job it is. Where this is skipped the differences accumulate silently and surface as a reconciliation problem a year later.

And a clear statement to the person that they have been paid provisionally and what the adjustment will be. Discovering an unexplained deduction in a later payslip is a serious matter, and it is the most common way this arrangement goes wrong.

Writing the rule

One page, agreed between payroll, HR and finance, covering: which populations are paid provisionally and which are not, what the provisional amount is based on, how and when the variance settles, what the person is told and when, and who has authority to make an exception.

The exception clause matters. There will be cases — a person who has left, a suspected overpayment, a dispute already running — where the default is wrong, and naming who can decide prevents that decision being taken at the cutoff by whoever answered the phone.

Overpayment, and recovering it

Provisional payment creates the possibility of overpayment, and recovery of overpaid wages is legally constrained in most jurisdictions: there are limits on how much can be deducted, how quickly, and what notice is required.

Know the rules before the arrangement starts rather than at the first recovery. In practice the amounts are small and recovery is straightforward if it is handled promptly, in writing, and over a period the person can absorb. The cases that become disputes are the ones discovered six months late, where the amount has grown and the person has no memory of the hours it relates to.

The number worth tracking

How many people were paid provisionally each period, and how long their timesheets took to arrive afterwards.

If it is a stable small group, the arrangement is working as intended. If it is growing, the provisional payment has become the normal route and the timesheet has become optional, which is a different problem and one worth catching before it is a year old.

What the payslip should say

A provisional payment that looks identical to a normal one is the source of most of the trouble this arrangement causes. The person sees the expected amount, spends it, and encounters an unexplained adjustment two months later.

Mark it. A line on the payslip, or a message when the run is processed, saying that the payment is based on contracted hours because no timesheet was received and that any difference will settle in the next period. It costs one configuration change, it is almost certainly required by the general duty to give an itemised statement of pay, and it converts a surprise into something the person was told about.