Working Out the Final Payment
The eight components of a final payment, the order to work them out in, and why it should be computed before the last day, not after.
A final payment assembled line by line, as one organisation recorded it
The two outstanding lines were both things that arrived after the payroll cut-off, which is where almost every final payment goes wrong. This is one organisation's own computation, not a statement of what any rule requires.
Work the final payment out before the last day, not in the next ordinary payroll run, and have somebody other than the person who computed it check the arithmetic. A final payment computed after somebody has gone is computed by people who can no longer ask them anything, and it is the single most common reason a departure that was going fine turns into correspondence.
The payment question in “Working Out the Final Payment” depends on a complete and correct work record, not simply the latest dashboard total. For organisations researching employee monitoring for performance reviews, this team-management platform can connect hours with projects and approvals, provided disputed entries remain correctable and payroll applies the relevant contract and local rules.
The components are not complicated. What makes them go wrong is that they arrive from four different places — payroll, the manager, expenses, and whatever system holds leave — and nobody owns the total.
For an independent reference relevant to “Working Out the Final Payment”, consult the Gartner insider-risk resources. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
The components, in the order to work them out
- Pay for time worked up to and including the last day, pro-rated.
- Any variable pay already earned: commission, bonus, overtime, allowances.
- Accrued but untaken leave, with the accrual calculated to the right date.
- Notice, if it is being paid rather than worked.
- Anything contractual on termination, such as a redundancy payment where one applies.
- Expenses submitted and approved, including anything submitted in the final week.
- Deductions, each one checked against the clause that permits it.
- Loans, advances and season ticket balances.
Then the total, and then a check by somebody else. Steps two and six are the ones that arrive late, and the ones most often omitted entirely.
Variable pay already earned
Commission on a sale that has closed but not been invoiced, a bonus relating to a period that has ended, overtime from the last fortnight — each of these is work already done, and each sits in a system that pays on a different cycle from salary.
What is owed depends on the scheme and on what the contract says about leavers. What is avoidable is simply forgetting: nobody looks at the commission system when somebody leaves because it is not part of the payroll process. Putting it on the checklist as a line with a named owner solves most of it.
Pro-rating, and the thing that is pro-rated
A monthly salary pro-rated for a part month can be calculated several ways and they give different answers. Working days in the month, calendar days, a fixed fraction — each is defensible and they are not interchangeable.
The point is to use the same method every time and to be able to say which one. An organisation that calculates it differently for two people in the same month has created a question it cannot answer well.
Cut-offs that do not match last days
Payroll cut-offs sit in the middle of the month. Last days do not. The result is a final payment computed before the final expenses are submitted, before the last week's overtime is approved, and sometimes before the last day itself.
Two things fix most of this: moving the computation forward so it is done deliberately rather than caught by a cut-off, and telling the person explicitly what is in this payment and what will follow separately. A payment with an explanation attached rarely generates a reply.
Showing the working
Send a breakdown, line by line, with the date each part will be paid. Not a payslip — a breakdown in words, because a payslip assumes the reader already knows what the codes mean.
Most disputes about final pay are not disputes about entitlement. They are about a number that arrived with nothing attached, from an organisation the person has just stopped trusting.
Checking somebody else's arithmetic
Have a second person check the figures against the contract and the leave record before anything is sent. This takes ten minutes and catches the category of error that is most damaging: not a wrong principle, but a wrong number.
It also catches the mismatch between a stated total and the lines above it, which is the error nobody notices because everybody reads the total.
Benefits that stop on a different date
Insurance cover, a pension contribution, a subscription, a car — each has its own end date, and those dates rarely coincide with the termination date or with each other. Cover that ran to the end of the month is a different thing from cover that stopped on the last working day.
Tell the person which is which, in the same document as the money. Somebody who believes they still have cover for a fortnight and does not is exposed to a specific risk, and the sentence that prevents it costs nothing to write.
What happens after
Record what was paid, when, and on what basis, in the file. If something was unresolved at the time — a disputed deduction, a commission figure awaiting a decision — record that too, with what was said to the person about it.
Six months later somebody will ask, usually because the person has asked first, and the file is the only thing that will answer. It is a question worth settling once, at the point of payment, rather than reconstructing from three systems and a memory.