Offboarding and Clearance: Closing the Employment Loop

Most companies have a hiring process. Far fewer have an exit process written down anywhere except in the head of whoever handled the last resignation. The result is familiar enough: the laptop comes back but nobody logs it, the last payroll runs without the proportionate 13th month pay, and three weeks later a former employee is emailing to ask where the money and the certificates are. Offboarding deserves at least as much structure as onboarding, because the obligations at the end of employment are heavier than the ones at the start.

Why exits fall through the cracks

An exit is the one HR event with no single owner. The immediate supervisor knows what work is still open. IT knows which accounts and devices are outstanding. Finance knows about the unliquidated cash advance. Payroll knows what the last cutoff looks like. HR is supposed to hold all of it together, usually while the person is still reporting for the rest of the notice period.

Nothing about that is unreasonable, but it depends on five people remembering five different things at roughly the same time. When one of them is on leave, or the departure date lands in the middle of a cutoff, the pieces simply do not meet. And unlike a late report, an incomplete exit does not surface immediately. It surfaces months later, when a device cannot be accounted for during inventory, or when a former employee asks for a document you assumed someone had already issued.

The fix is not more diligence. It is making the exit a defined process with named steps, the way a new hire's first week already is.

A clearance checklist is a list of accountabilities, not a signature hunt

Clearance forms often become a race to collect initials. Someone walks a piece of paper from desk to desk, each person signs without much thought, and the signed form gets filed. It proves that a form circulated. It does not prove that anything was actually returned or settled.

A useful clearance checklist starts from a different question: what does this person hold that belongs to the company, and who confirms its return? That list is concrete. Physical assets such as laptops, phones, SIM cards, tools, uniforms, IDs and keys. System access across email, payroll, accounting and any operational applications. Financial items such as unliquidated cash advances, outstanding company loans and revolving fund balances. Custody items such as client files, signed contracts, petty cash and physical records.

Each line needs three things: the accountable department, a due date, and a status that someone updated deliberately. Roles differ, so the checklist should differ too. A field sales representative and a bookkeeper do not surrender the same list of items, and pretending otherwise is how real accountabilities get missed.

Turnover is a deliverable with a name and a date

The half of offboarding that never fits on a clearance form is the work itself. Someone leaves holding the only version of a reconciliation file, the running context on a client account, or the reason a certain process has an odd extra step. None of that is an asset you can log at the guardhouse.

Treat turnover as a deliverable. Name the receiving person before the notice period is half over, list what has to change hands, and set a date that is not the last day. A turnover that starts on the final afternoon is a formality, not a handover. What should be produced is unglamorous and specific: where the files live, which recurring tasks fall due and when, what is currently unfinished, and who outside the company expects a reply.

Written turnover also protects the person leaving. Once the deliverables are documented and accepted, the question of whether something was properly handed over stops being a matter of memory.

What final pay is actually made of

Final pay is not one number that appears at the end. It is a computation with parts, and each part comes from somewhere. There are unpaid earnings for the last cutoff worked, including any overtime, differentials or allowances already earned. There is the proportionate 13th month pay, since the benefit is defined as one-twelfth of the basic salary earned within the calendar year, which means an employee who leaves in May has already accrued a share of it. There is the cash conversion of unused service incentive leave, which the Omnibus Rules Implementing the Labor Code make commutable to its money equivalent when it is not used. There may be other amounts owed under company policy or a collective bargaining agreement.

Against that sit the deductions: the outstanding loan balance, the unliquidated advance, unreturned property valued under an existing policy. Every one of them should trace to a written authorization or an established policy, not to a manager's recollection of an arrangement.

The paperwork that legally closes the year

A departing employee takes a tax history with them, and that history has to be settled at separation rather than at year-end. The last payroll should reflect the compensation actually paid for the year to that point, so any under- or over-withholding is resolved while you still have a payroll to resolve it in.

Then there is the certificate itself. Employers must furnish each employee from whom taxes were withheld a BIR Form 2316 on or before January 31 of the following year, or on the day the last payment of compensation is made if employment ends earlier. For a resignation in May, that second clause is the operative one. The employee's next employer will need that certificate to consolidate their compensation for the year, and chasing it from a previous employer months later is a genuine burden. Remember too that 13th month pay and other benefits are excluded from gross income only up to a total of P90,000 per year, with the excess treated as taxable compensation.

Contributions follow their own calendar. The SSS, PhilHealth and Pag-IBIG amounts for the last month worked are still remitted on their normal schedules after the person has gone, so the exit does not end your reporting obligation for that month.

Where the handoff between HR and payroll breaks

Almost every failed exit is a handoff failure. Clearance lives in HR's folder. Final pay lives in payroll's spreadsheet. The two are reconciled by someone walking over and asking whether the clearance is done yet, and the answer depends on who they happen to ask.

ERPat's Offboarding module is built to remove that walk. It holds the structured exit itself: the clearance checklist, the turnover of accountabilities, and the handoff of the result to final pay. Because ERPat is one platform, the cleared and uncleared items are not sitting in a separate file from the computation that depends on them. The Compensation module then does what it does for every other payroll run, handling earnings, deductions, allowances and the payslip, with final pay treated as a computation rather than a manual exception typed in at the end of the month.

The practical gain is visibility. At any point in the notice period, you can see what is still outstanding and who owns it, instead of finding out on release day.

Closing the loop properly

An exit is a closing entry. Until the assets are back, the accountabilities are transferred, the final pay is computed against real figures and the certificates are issued, the employment relationship is still open on your books even though the person has stopped coming in. Most of the cost of a messy offboarding is paid later and by someone else: the colleague reconstructing a lost file, the finance team writing off an advance nobody documented, the former employee who leaves with a bad last impression of an otherwise good employer.

Write the checklist once, per role. Give every line an owner and a date. Make final pay a computation rather than a negotiation. Done that way, the last week of employment is simply the last step of a process you already run, and nothing is left hanging behind it.