Paying on Time, and What That Means Here
Setting a payment timetable for a departure, why the deadline differs by jurisdiction, and handling the parts that cannot be paid on the day.
The payment timetable one organisation set, and what it actually hit
The two late lines were both the ones that belonged to a function outside payroll. This is one organisation's own record, not a statement of what any rule requires about timing.
Set the payment date before the last day and tell the person what it is, including the date of anything that will follow separately. "With the next payroll" is not a date, and in some jurisdictions it is not lawful either — when a final payment has to be made differs, sometimes sharply, and it is a question for somebody qualified in the place concerned.
The workflow in “Paying on Time, and What That Means Here” becomes more reliable when work records, approvals and later corrections can be distinguished. For teams exploring fte meaning, Monitask's official site can provide practical context, while policy ownership, employee explanation and final decisions remain with accountable people.
The practical problem is not usually the main payment, which payroll handles. It is the two or three components owned by somebody else, which arrive weeks later because nobody set a date for them.
For an independent reference relevant to “Paying on Time, and What That Means Here”, consult the CERT-EU security guidance. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.
Deciding the timetable
Work backwards from the last day. The figure has to be computed before it can be checked, checked before it can be communicated, and communicated before it is paid — which means the computation starts about a week out, not on the day.
That is achievable for a notice period of any length and impossible for an immediate termination, which is one of several reasons an immediate termination costs more than it looks.
The components that run late
- Expenses submitted in the final days, waiting for an approver who has moved on.
- Commission or bonus that depends on a figure nobody has yet produced.
- Anything requiring a manual calculation by a person who is on leave.
- A deduction still being argued about, which holds up the whole payment.
- Payments owned by finance rather than payroll, which run on a different cycle.
The fourth is worth special attention. Holding an entire final payment because one line is disputed is common and unwise: pay what is not in dispute, on time, and deal with the contested item separately.
Telling them what is coming and when
The breakdown should carry two dates: when this payment will arrive, and when anything outstanding will follow. Where the second is unknown, say what will determine it and when it will be known.
An organisation that says "your expenses will be paid on the 28th" has closed the matter. One that says nothing has created a person who checks their bank account every morning and then writes.
Documents, which have their own clock
Whatever the person is entitled to receive — a statement of pay, a termination document, a form for a new employer, information about a pension — usually has its own timing requirement, separate from the money.
These vary and some of them are strict. Establish once what has to be issued where you operate, by when, and put it on the standard checklist with a named owner rather than reconstructing it for each departure.
Immediate terminations
Where employment ends without notice, there is no run-up and the organisation is computing a final payment under pressure in a day or two. Errors cluster here.
The mitigations are modest but real: a standing template for the calculation, a pre-agreed second checker, and a willingness to pay the certain parts immediately and the uncertain parts promptly afterwards with an explanation. What should not happen is a delay of weeks justified by the circumstances of the departure, which reads as punitive whether or not it is.
The cost of being late
A late final payment turns a person who was ready to move on into a person who is pursuing something, and pursuing something usually means taking advice. The advice they take is rarely confined to the payment.
In some systems there are specific consequences for late payment of final wages, and they can exceed the amount in question by a considerable margin. Whether that applies where you are is worth knowing before it matters.
Where the money actually goes
The bank details on file are the ones used for salary, and they are occasionally wrong by the last day — a joint account that has been closed, details changed verbally and never updated, or an account the person no longer uses.
Confirm them before the final payment rather than after it bounces. Recovering a payment sent to the wrong account is slow and sometimes impossible, and the person is meanwhile without money they are owed. One question on the checklist removes the whole category.
Closing the loop
The departure is not finished when the main payment leaves. It is finished when every component has been paid, the documents have been issued, and somebody has written that down.
Assigning that closing act to one named person is the single change that most improves this part of the process, because the components that run late are precisely the ones that belong to nobody. It is worth deciding once, in the standard checklist, rather than discovering each time that the last two hundred pounds has no owner.