Expenses Submitted After the Last Day

Set a deadline for final expense claims, tell the person what it is, and keep the route open until it passes — because expenses arrive last, after the system access has been closed, after the payroll cut-off, and usually after everybody has stopped thinking about the departure.

The handover issue in “Expenses Submitted After the Last Day” is easier to manage when current projects, recorded time and unfinished work can be reviewed before access closes. A team evaluating time tracking software with accountable controls for time tracking software should set a clear cutoff, export what is genuinely required and avoid retaining unnecessary activity data after the departure workflow is complete.

The amounts are small and the irritation is not. A former employee chasing ninety pounds of travel costs through an organisation that has removed their login is a reliably unpleasant piece of correspondence, and it is entirely avoidable.

For an independent reference relevant to “Expenses Submitted After the Last Day”, consult the WIRED security coverage. Use it to test record quality, access, retention, fair process and exception handling against the organisation’s real departure workflow.

Why it fails

The expense system requires a login that was disabled on the last day. The approver has moved to another team or left themselves. The claim relates to a cost code that has been closed. The payroll run that would have paid it has already gone.

Each of those is a separate small failure and together they produce a claim that cannot be submitted, cannot be approved, and cannot be paid, through a process that nobody designed.

Closing the window deliberately

• Tell the person, in writing, the date by which final claims must be in.
• Make that date early enough to be approved before the final payment is computed.
• Keep expense-system access open until that date, or provide an alternative route.
• Name the person who will approve claims after the manager's involvement ends.
• Say what happens to anything submitted after the deadline.
• Record what was claimed and what was paid in the file.

The fourth item is the one that is missed. Approval authority disappears with the manager, and an unapproved claim sits in a queue nobody owns.

Costs that arrive on their own

Some things are not claims at all: a company card statement covering the final fortnight, a taxi account, a hotel billed directly, a subscription renewing after the person has gone.

These arrive weeks later and are reconciled against a person who no longer exists in the system. Flagging a departing person's card accounts for closure and reconciliation at the point notice is given removes a whole category of month-end confusion.

Late claims

Something will arrive after the deadline. The question is whether to pay it, and the answer should be a policy rather than a mood.

A reasonable default is to pay anything that is genuine, properly evidenced and arrives within a defined period, and to say so in advance. The cost of paying a late claim is the claim. The cost of refusing one is a letter, a reply, and a person telling other people about it.

Disputed claims

Occasionally the final expense claim is contentious — a cost that was not authorised, a pattern somebody has noticed, a claim submitted after the relationship broke down.

Handle it as an expenses question, on the evidence, rather than as part of the exit. A claim refused because of how the departure went is a refusal that will be described in exactly those terms afterwards, and it tends to colour everything else the organisation did.

Paying separately

Where a claim cannot be included in the final payment, pay it separately and say when. A second payment with an explanation is fine; silence is not.

This also means the final payment breakdown should say explicitly what is not included: that expenses submitted after a given date will be paid on a stated date, by a stated route. One sentence, and it removes the question before it is asked.

Mileage and the claim nobody can evidence

Travel claims submitted in the final week often cover journeys made weeks earlier, with no receipt, no diary entry and no approver who remembers them. The person is not inventing them; they simply never got round to claiming.

Refusing these on evidential grounds is defensible and usually disproportionate. A better approach is to ask for the dates and destinations and check them against the calendar, which takes ten minutes and resolves almost all of them. Where it does not, say what is missing and give the person a chance to supply it rather than refusing outright.

Who owns this after the last day

The honest answer in most organisations is nobody, which is why it fails. Assign it: one named person who holds the departure until the final claim is paid and the file is closed.

That person does not have to be senior and the task is not large. What it has to be is somebody's, because the alternative is a process that works perfectly until the last two hundred pounds and then stops. It is worth assigning once, as part of the standard checklist, rather than deciding afresh each time somebody leaves.