Coordinate Offboarding and Final Pay Inputs With One Checklist

Start from the last working date

Confirm the last working date in writing before building the packet. Record the notice date, the source document, the approver, and any transition arrangement such as leave or a shorter schedule. The date drives the time cut-off, the benefit period, and the access removal, so an unconfirmed date creates errors in every later step.

If the date changes, version the packet and recalculate the dependent items. Do not edit the original date in place. A short change log with the old date, the new date, the reason, and the approver keeps the history clear when payroll or counsel reviews the file.

Track time and attendance inputs

Freeze the attendance extract at the agreed cut-off and record the source, the extraction time, and the person who pulled it. List approved overtime, rest day work, holiday work, leave, and any manual adjustment with its approver. Do not let a late adjustment slip in without a correction record.

Reconcile the extract to the schedule and the leave system. Explain every gap: an absence without leave, a missed punch, a shift swap, or a correction. The payroll owner needs the unresolved items listed, not a clean total that hides them.

Keep the schedule version beside the attendance extract. A shift that was swapped before the last working date can change which hours are final, and the reviewer needs to see the approved schedule rather than the original plan.

Reconcile assets and access

List every asset issued to the employee: laptop, phone, headset, token, badge, vehicle, or equipment. Record the serial or asset id, the issue date, the return state, and the person who received it. A missing asset is a business issue for the owner, not a reason for the support lane to invent a deduction.

Run the access removal checklist with named systems and owners. Record the time access ended, not only the request time. Confirm that shared credentials were rotated where the employee knew them. Access removal is a security control and should not wait for the final pay discussion.

Collect clearance evidence

Clearance items vary by role: finance, inventory, client property, confidentiality, or pending case files. Give each item an owner, a due date, and a state. The support lane can chase and record, but the owner decides whether the clearance is satisfied.

Keep clearance evidence separate from the pay calculation. A cleared item is a fact; whether it affects pay is a policy question. Mixing the two invites an unauthorized deduction or a promise that the team cannot keep. Route the question with the evidence attached.

Some clearances belong to another company or client. Record the external owner and the expected response time, then treat a missing response as an open item rather than a cleared one.

Flag deductions and advances as questions

List possible deductions, advances, loans, or recoveries as questions with the source document and the amount stated by the system. Do not calculate a net amount or apply an offset. The payroll owner and qualified counsel decide whether an item is valid, how it is treated, and what evidence is required.

Record the question, the facts provided, the answer, and the person who answered. If an item remains unresolved at the release date, the packet should show it as open rather than silently excluding it. A visible open item is easier to defend than a surprise correction later.

Keep the payroll owner in the approval path

The packet moves from preparation to payroll review to approval. Name the reviewer, the approval criteria, and the evidence they will see. The support lane should not release a payment file or communicate a final amount to the employee without the payroll owner's approval.

Build a short approval note that lists the last working date, the attendance cut-off, open items, and the payment instruction reference. The note should show what the approver accepted, not just a signature. This is the record that answers a later question about who authorized the release.

Hand off a complete packet

Assemble the packet in a fixed order: confirmed dates, attendance extract, leave and adjustment evidence, asset and access record, clearance states, open questions, and the payroll calculation reference. Add an index with page or file names so the reviewer can find each item without searching.

Send the packet through the approved channel and record the handoff time and receiver. If an item is missing, send the packet with the gap listed rather than delaying everything. A partial packet with a clear gap is easier to act on than a promise that everything will follow.

Use a file naming rule that includes the employee key, the last working date, and the packet version. A folder of files named final makes the reviewer's job harder and increases the chance that an old version is paid.

Close the record after payment

After payment, attach the payment evidence and the final approval to the packet. Close the access and asset items with dates, then record the retention period and the owner of the closed file. Do not leave the packet open in a working folder where it can be edited later.

Review the cycle for misses: late clearances, missing attendance, unresolved questions, and access removed after the deadline. Count them against the number of offboardings in the period. Assign repairs to the owners and check the next cycle. Offboarding quality is visible in the closure record, not in the farewell message.