Final Pay in 30 Days: Clearance to Release

Final pay becomes a dispute when HR, payroll, the asset custodian, and finance each believe someone else owns the next step. In the Philippines, that uncertainty also consumes a defined release window. We recommend opening a dated offboarding case as soon as the separation date is known, with a computation owner, a clearance owner, and a reviewer who can resolve exceptions. The employee should receive an intelligible breakdown and a traceable payment, while the employer retains the records used to reach the amount.

Put the release date on the case first

The Department of Labor and Employment's January 2026 reminder cites Labor Advisory No. 06, Series of 2020: final pay is to be released within 30 days after separation, unless a more favorable company policy applies. It also says a certificate of employment must be issued within three days after an employee requests it. Record the actual separation date and calculate the target release date immediately. Do not let an internal clearance spreadsheet become the only clock the team watches.

For a hypothetical employee whose separation takes effect on 30 April, the case can mark that date as Day 0 and set Day 30 as the outside target under the advisory, subject to a better applicable policy. We would set earlier internal milestones so finance has time to verify bank details and release funds. The exact calendar should be checked by HR for the actual case; the point of the example is to reserve review time before the deadline, not to make Day 30 the normal payment day.

Keep the certificate of employment request as a separate dated task. A worker can need a COE before final-pay computation is complete. Do not wait for the payment handoff to start the COE request clock.

Inventory what may be owed

DOLE's reminder lists unpaid salaries, proportionate 13th-month pay, separation or retirement pay when applicable, cash for unused leave when applicable, tax refunds, and other amounts owed under policy or agreement. That list is a prompt to investigate, not a statement that every departing employee receives every item. For each possible component, record the source, period covered, calculation, and reviewer.

The payroll preparer should reconcile the last regular payslip to the final one. Check worked days after the previous cutoff, approved overtime or night work, unpaid absences, allowance changes, and any earlier advances already settled. For proportionate 13th-month pay, use the underlying basic-salary history rather than simply dividing the most recent monthly salary by 12; the worker's service period and prior payments matter. For unused leave, distinguish a statutory or policy-based cash entitlement from a balance displayed for scheduling purposes.

The review sheet can have columns for item, input record, period, gross amount, tax or deduction treatment, approver, and employee-facing explanation. A second person should be able to reproduce the total without asking the original preparer to recall a private conversation.

Run clearance alongside computation

Suppose the employee has a laptop, a building pass, and an expense claim awaiting review. Assign each to its owner: IT confirms account and device return, administration checks the pass, finance reviews the claim, and payroll computes earnings. If the laptop is disputed, record the asset assignment, return request, employee response, condition evidence, and escalation owner. Do not convert an unresolved asset question into an unexplained final-pay deduction.

We would place any proposed deduction in a separate review queue. The person requesting it must show its basis and supporting records; HR or the appropriate adviser must decide whether it is permissible in that case. Different obligations have different rules, and a signed checklist alone does not answer every deduction question. An open dispute should be visible to the final-pay reviewer early enough to decide the proper release approach within the applicable timeframe.

This division of work protects both sides. The employee can see what remains to be returned or resolved, and the company can demonstrate that it did not wait until the last day to discover a missing asset. Clearance status should be a live task list with due dates and evidence, not a single “cleared/not cleared” cell.

Make the handoff measurable

Our practical case checklist is short enough to use for every departure:

1. Confirm the separation date, employment record, contact details, and preferred payment channel.
2. Assign computation, asset clearance, COE, review, and release owners with internal due dates.
3. Reconcile final attendance and all earnings, benefits, prior payments, and proposed deductions.
4. Obtain a second review of the itemized statement and resolve exceptions in writing.
5. Send the employee the statement and retain payment proof and any acknowledgment.

Track the age of open cases, missing inputs, unresolved proposed deductions, COE requests approaching their own due date, and payments awaiting bank confirmation. An offboarding dashboard is useful only if each exception points to the person who can act on it. A generic “pending HR” status will not shorten a queue.

ERPat's module directory describes Offboarding clearance and final-pay handoff, Assets custody records, and Compensation earnings and payslips. A product demonstration should use an anonymized departing-employee case to verify how those steps connect in the offered setup. Ask to see the dated task list, proposed correction path, reviewer sign-off, and release evidence rather than assuming that a module name proves the entire workflow. If your professional-services team needs a clearer exit process, explore our systems for professional services.