Automating 13th Month Pay: From Attendance Data to Disbursement

December 24 does not move. Presidential Decree No. 851 requires 13th month pay to be released not later than that date every year, and Memorandum Order No. 28 removed the old salary ceiling back in 1986, so every rank-and-file employee is covered. Yet in most small and mid-sized companies the computation still begins in the second week of December, with someone exporting a year of payroll registers into a spreadsheet. The deadline is the easy part. The inputs are what break.

The deadline is fixed, so the work has to move earlier

PD 851 gives you one hard date and nothing else. Whether the computation takes an afternoon or three weeks is entirely a function of how the year's records were kept, and by the time the December cut-off arrives there is no room left to fix a payroll period from March. Companies that struggle with this every year are usually not struggling with the formula — one-twelfth of basic salary earned within the calendar year is arithmetic.

They are struggling because the figures that feed the formula live in four places. Automation changes the sequence rather than the math. If attendance, employment status and earnings are captured in the same system all year, the December run is a report against data that has already settled. If they are not, December becomes a reconciliation project with a legal deadline attached, handled by the same person closing the last regular payroll of the year.

Start with the employment record, not the payroll register

The biggest source of 13th month errors is not pay data but people data. Prorating depends on when someone was hired, when they were separated, whether they moved between rates or cost centres, and whether a stretch of leave was paid or unpaid. A payroll register will not tell you any of that on its own. The employment record will.

In ERPat, the Human Resource module is the system of record for exactly these facts — profiles, schedules, attendance, leaves and holidays held in one place rather than spread across a 201 file, a biometric export and a supervisor's notebook. Because the Compensation module draws from it directly, a mid-year hire's coverage period is not something anyone retypes in December.

So the practical first step is a review of that record: everyone hired or separated during the year, status changes, rate changes, and anyone who spent time on unpaid leave. Fix those in November and the December figures stop needing footnotes.

Decide once what counts as basic salary

The implementing rules of PD 851 define the benefit as one-twelfth of basic salary within a calendar year, which makes classification the real decision. Every earning type your company pays has to sit on one side of a line: part of basic salary, or a premium or allowance that is not. The Labor Code's attendance-driven premiums are the obvious cases — overtime at the regular wage plus at least twenty-five percent, night shift differential of at least ten percent for hours worked between ten in the evening and six in the morning, and at least thirty percent for work on a scheduled rest day.

The mistake is treating this as a December judgement call made line by line under time pressure. It belongs in configuration. The Compensation module holds earnings, deductions and allowances as defined components, so the classification is set once and applied to every period identically. The year-end figure then becomes a query against consistently tagged data rather than an interpretation of a spreadsheet column heading.

Let attendance carry through to the computation

Basic salary earned is not the same as basic salary contracted. Unpaid absences, undertime against a shifting schedule and the unpaid portion of a long leave all reduce what an employee actually earned, and every one of those facts originates in attendance. When attendance sits in one system and payroll in another, that reconciliation happens by export, and every export is a chance for a period to be counted twice or not at all.

The design point in ERPat is that Compensation is fed straight from attendance rather than from a file someone prepared. The same posted attendance that produced each period's payslip is the attendance behind the annual total, so the 13th month figure and the twelve payslips before it cannot disagree. When an employee questions the amount — and someone always does — the answer is a period-by-period breakdown, not a recomputation.

Handle the taxable excess inside the same run

13th month pay and other benefits are excluded from gross income and exempt from withholding tax up to a total of P90,000 per year; anything above that is taxable compensation subject to withholding. Two details make this awkward by hand. The cap is shared with other benefits rather than reserved for the 13th month alone, and it is annual, so it can only be evaluated against a full year's benefit total.

That makes it a computation the payroll system should perform, not an adjustment applied afterwards. Because the Compensation module already holds each employee's earnings and deductions for every period of the year, the benefit total is available at the moment the 13th month amount is produced, and any taxable excess can be withheld in the same run instead of surfacing as a discrepancy in January.

Release it as payroll, with the trail it will need in January

A 13th month payment made outside the payroll system is a payment without a payslip, and it is the one most likely to be queried. Released through the Compensation module it behaves like any other pay item: computed from defined components, documented on a DOLE-compliant payslip the employee can actually read, and recorded against the employee record that produced it. Disbursement then works from a figure with a documented derivation rather than from a spreadsheet cell.

That trail is not only for the employee. January brings the year-end obligations that depend on these same totals — the Certificate of Compensation Payment/Tax Withheld, BIR Form No. 2316, furnished to each employee from whom taxes were withheld on or before January 31, and BIR Form No. 1604-C with the alphalists of employees due on the same date.

Which is the real argument for automating this. The goal is not a faster December; it is a January in which nothing has to be reopened.