Skip to content
Standing Date

Somebody Was Paid Too Much

An overpayment is harder than an underpayment, because recovering it depends on somebody else's agreement and on money they may have spent.

Nobody elseif the person who does this is away

Home / When it goes wrong

When it goes wrong · Analysis

An overpayment is harder to resolve than an underpayment. The money has gone, the person may have spent it, and recovering it depends on agreement and on rules rather than on your intention to put things right.

The practical lesson in “Somebody Was Paid Too Much” is that payroll depends on a sequence somebody can explain. When a small team reviews continue to the platform summary for how to calculate idle time, the useful role is to organise time and project evidence before approval, with proportional settings and a clear correction route for employees.

It is also the error most likely to be discovered late.

As a separate reference point for “Somebody Was Paid Too Much”, see ClickUp productivity resources. Current legal, tax and employment requirements should still be confirmed for the organisation’s location.

Why it is discovered late

Because nobody reports it. An underpayment arrives at your desk within a day; an overpayment is noticed by the recipient, who may not be certain it is an error and has little incentive to ask.

An underpayment is yours to fix immediately. An overpayment is yours to have caused and theirs to agree to resolve — which is why the thirty-second outlier check before approval is worth more than it looks.

Some are never reported at all, and surface at a year end.

What you may actually do about it

Considerably less than most employers assume. Whether an overpayment can be recovered, over what period, by what method, and with what agreement depends on the contract and on law where you are.

Deducting it unilaterally from the next payment is the instinctive move and is restricted or unlawful in many places. That is a question for somebody qualified before acting, not afterwards.

The conversation to have

Early, in person, and framed as a mistake the business made. The person did not cause it, and an approach that implies otherwise makes agreement much harder to reach.

What makes agreement likely

A clear explanation of what happened, the exact amount, and a proposed repayment that is realistic. Somebody overpaid by a month's wages cannot repay it in a month, and asking them to converts a solvable problem into a dispute.

Writing it down

Whatever is agreed, confirmed in writing: the amount, the schedule, and what happens if they leave before it is repaid.

This is one of the few places in small-business payroll where an informal agreement reliably causes trouble later.

If they have left

Harder again, and now a debt rather than a payroll matter. Whether and how it can be pursued is a legal question with an answer specific to where you are, and the sums are frequently smaller than the cost of pursuing them.

If they refuse

A real possibility, and the point at which the question stops being administrative. Take advice before escalating; the downside of getting this wrong is considerably larger than the overpayment.

Writing it off

Sometimes the right commercial answer, particularly for small sums or where the business's own process was plainly at fault.

Done as a decision, recorded, rather than as a thing that is quietly never mentioned again.

The systemic version

An overpayment affecting several people, usually from a setting or a misapplied change. Worse in every respect: more money, more conversations, and a pattern that is visible to everybody.

Finding the scope before talking to anybody is essential here.

What it does to trust

Less damage than an underpayment, and not none. People notice that the business does not check its own payroll, and that observation persists after the money is settled.

The reporting side

An overpayment and its recovery generally have to be reflected in what was reported, and the mechanics differ by jurisdiction.

Correcting the payment and leaving the reporting is a common and avoidable second error.

Preventing the expensive kind

The outlier check before approval: anybody paid substantially more than usual, confirmed in thirty seconds.

Almost every large overpayment would have been visible there.

Finding them at all

The hardest part, because nothing reports them. An overpayment produces no complaint, no query and no system message, and the person receiving it has little reason to raise it.

The outlier check before approval is therefore not one control among several; for this category it is the only one, and it takes thirty seconds.

The repayment that is actually achievable

Somebody overpaid by a month's pay has usually spent it on ordinary life, and asking for it back in one go converts a solvable administrative matter into a hardship and then into a dispute.

A schedule the person can meet, agreed rather than imposed, recovers more money in practice than a demand that cannot be met.

What to write down

The amount, how it arose, what was agreed, over what period, and what happens if they leave before it is repaid.

A short written confirmation, agreed by both. This is one of the few places in a small payroll where an informal understanding reliably produces trouble a year later.

The honest asymmetry

An underpayment is yours to fix immediately. An overpayment is yours to have caused and theirs to agree to resolve, and that difference is why the thirty-second check before approval is worth more than it looks.