13th Month Pay Computation: Prorated, Partial, and Special Cases

Every November, payroll teams start the 13th month pay computation with confidence — until the employee list stops being tidy. A regular employee who worked the full calendar year is straightforward arithmetic. The person who resigned in July, the one hired in September, and the one who took six weeks of unpaid leave are where the disagreements begin, and where a wrong figure is hardest to walk back. The rules for those cases are not special. The base you compute from is.

The formula already handles proration

Presidential Decree No. 851 requires employers to pay 13th month pay not later than December 24 of every year, and its implementing rules define the benefit as one-twelfth of the employee's basic salary within a calendar year. Memorandum Order No. 28, signed in 1986, removed the decree's original monthly salary ceiling, so every rank-and-file employee is covered regardless of how much they earn.

That definition is what makes proration automatic. There is no separate formula for a partial year: total the basic salary the employee actually earned inside the calendar year, then divide by twelve. Someone who earned three months of basic salary gets three months' worth out of that division without anyone applying a special rule.

The common shortcut — current monthly rate multiplied by months worked, divided by twelve — usually lands close and occasionally lands wrong. It breaks the moment there is a mid-year increase, a change in daily rate, a month with unpaid days, or a promotion. Summing what was actually earned takes no longer when your payroll records are clean, and it is the only figure you can defend line by line.

Mid-year hires and mid-year rate changes

A September hire is not a special case. Start at the first payroll period in which they appear, total the basic salary through the last December cutoff, and divide by twelve. Do not add a second adjustment for "only worked four months" — the division has already accounted for it. Applying a proration factor on top of an already-correct base is one of the more common ways an employee ends up underpaid.

Mid-year rate changes are the subtler trap. A probationary employee who regularises in June and a staff member who received an increase in August both earned at two different rates in the same calendar year. Their 13th month pay is built from what each period actually paid, not from their December rate projected backwards. Applying the current rate to the whole year overstates the benefit; applying the old rate understates it.

Keep those periods visible in your working file. When an employee questions the amount, the fastest resolution is a short table showing the basic salary earned per payroll period and the single divisor applied at the end.

Resigned, terminated, and end-of-contract staff

An employee who separates before December is still entitled to the benefit in proportion to the basic salary they earned before leaving. That amount belongs in their final pay rather than being held until the December release — waiting until year-end to settle it leaves an obligation open against someone who is no longer on your payroll and no longer easy to reach.

Getting it right at separation also matters for the tax paperwork. When employment ends before the usual January cutoff, the employer must furnish the employee's BIR Form 2316 on the day the last payment of compensation is made. If you recompute the 13th month figure afterwards, you are not simply cutting a supplementary payment — you are reissuing a tax certificate the employee may already have handed to a new employer.

Separation is where disputes concentrate, because the employee's mental model is usually months worked over twelve, times monthly salary. Unpaid days and rate changes make the real figure lower than that estimate. Attach the computation to the final pay breakdown so the difference is explained before it is questioned.

Unpaid leave, absences, and days that never earned basic salary

Unpaid days reduce the benefit, and not as a penalty. Basic salary within the calendar year means basic salary actually earned, so a day with no earnings contributes nothing to the total. Paid leave charged against an employee's leave credits is different — it is paid at the employee's rate, appears as basic salary on the payslip, and therefore does not shrink the base at all.

Leave conversions need a second look. Under the Omnibus Rules implementing the Labor Code, service incentive leave that is unused or unexhausted at the end of the year is commutable to its money equivalent. That payout is a conversion of leave credits, not salary for work rendered, so it does not belong in the 13th month base even though it lands in the same December payroll run.

Maternity leave raises the same question in a heavier form. The SSS maternity benefit is a cash benefit from SSS, while the salary differential under the 105-Day Expanded Maternity Leave Law is advanced and borne by the employer. How each is treated for 13th month purposes should be settled in written policy and checked against current DOLE guidance — not decided by whoever happens to be running the December payroll.

What sits outside the base, and the tax line to watch

The implementing rules draw a line between basic salary and everything layered on top of it. Overtime pay, night shift differential, holiday premium, allowances and the cash equivalent of unused leave credits sit outside the base unless your own policy or CBA has integrated them into basic pay. This matters most for employees whose take-home swings widely from month to month — their payslip totals are a poor proxy for the base, and using those totals inflates the benefit well beyond what the rules require.

Then check the annual ceiling. 13th month pay and other benefits are excluded from gross income and exempt from withholding tax up to a total of ₱90,000 per year, and any excess over that is taxable compensation subject to withholding. A partial-year employee rarely reaches it on the 13th month alone, but the ceiling covers 13th month pay and other benefits together across the whole year. A separated employee whose final pay releases several benefit items at once can cross it, so evaluate the year-to-date total rather than the December release in isolation.

Keeping the computation defensible

Most 13th month disputes are not arguments about the law. They are arguments about the base — which earnings counted, which days did not, and which rate applied in which month. The answer that ends the conversation is a reproducible line: basic salary earned per period, the unpaid days that reduced it, and the divisor applied once at the end.

That is far easier when payroll and attendance are not two separate exercises. ERPat's Compensation module covers earnings, deductions, allowances and payslips, with DOLE-compliant payroll fed straight from attendance — so unpaid days, rate changes and the earnings that belong in the base come from the same records that produced each payslip, instead of being reassembled from spreadsheets in the last week of November.

December 24 is the statutory deadline for everyone still on your payroll, and separated employees should already have received theirs with their final pay. Reconcile the edge cases now, while there is still time to correct one quietly.