BIR Form 2316: What Employers Prepare in January
January closes the previous tax year for payroll. Here is what BIR Form 2316 certifies, the order the January deadlines fall in, and where year-end reconciliation usually goes wrong.
In this guide
What to watch for
Use the article to find where source records and approvals need a cleaner audit trail.

In this article
Every January, payroll work splits in two. There is the payroll you are still running for the new year, and there is the close of the year that just ended — and only the second one comes with a hard deadline attached. BIR Form 2316, the Certificate of Compensation Payment/Tax Withheld, has to be in your employees' hands before the month is out, and the figures on it have to agree with what you actually withheld and remitted. Most of the pain in January comes from discovering, in the last week, that they do not.
What the certificate actually reports
Form 2316 is not a tax return. It is the employer's certification, one per employee, of the compensation paid during the calendar year and the tax withheld on it — which is why it is the document an employee is asked for when they apply for a loan, move to a new employer, or file an annual return of their own.
The form separates what was taxed from what was not. On the non-taxable side sit the employee's share of SSS, PhilHealth and Pag-IBIG contributions, de minimis benefits, and 13th month pay and other benefits up to P90,000; anything above that ceiling falls into taxable compensation. For a minimum wage earner, the statutory minimum wage itself is exempt, along with holiday pay, overtime pay, night shift differential and hazard pay. What remains is taxable compensation, run through the graduated income tax rates in force for the year to produce the tax due — then set against the tax actually withheld across twelve months, leaving either a balance to collect or an over-withholding to refund.
The order the January deadlines fall in
Three dates govern the close, and they are far easier to manage in sequence than in parallel.
First, January 31: every employer must furnish each employee from whom taxes were withheld a copy of Form 2316 covering the preceding calendar year. The exception is an employee who left mid-year — their certificate is due on the day the last payment of compensation is made, not in January, which is why terminal pay computations should never be left hanging. That same January 31 date also carries BIR Form 1604-C, the annual information return for income taxes withheld on compensation, filed together with the alphalists of employees.
Then February 28: for employees covered by substituted filing, duplicate copies of their 2316 go to the BIR along with the Certified List of Employees Qualified for Substituted Filing, the return's Annex "F". Behind both sits April 15, the deadline for individual annual income tax returns — and the reason employees who do not qualify for substituted filing need their certificate early enough to actually use it.
Substituted filing, and who it does not cover
Substituted filing means the employer's filing stands in for the employee's. Where it applies, the 2316 you issue and submit is treated as that employee's annual income tax return, and the employee files nothing in April.
It applies narrowly. The employee must have earned purely compensation income for the calendar year, from a single employer in the Philippines, with the tax withheld over the year equal to the tax due on the annualized compensation. The employer must have filed 1604-C with the alphalists, and the certificate itself must be signed by both the employer's authorized representative and the employee. Miss any one of those conditions and the employee is back to filing a return in their own name.
This is why the January reconciliation matters more than the printing. If your annualization is off by even a small amount, that third condition fails, and an employee you listed on Annex "F" is quietly not qualified for substituted filing at all.
An employee who worked for two employers during the year, or who earned income outside compensation, does not qualify no matter how clean your payroll is. Identify those employees in January and tell them, so they are not caught out in April.
Where year-end reconciliation usually breaks
Most January corrections trace back to a handful of recurring causes, and every one of them is visible before the certificates are printed if you go looking.
Mid-year hires are the most common. An employee who joined in August brings a 2316 from their previous employer, and that compensation and withholding has to be consolidated into your annualization; if the certificate was never collected at onboarding, the year-end computation is wrong from the start. Next are benefits that crossed the exclusion ceiling — a large 13th month payout, a bonus, or converted leave credits that together pushed an employee past the exempt cap without a corresponding withholding adjustment in December. Then there are minimum wage earners who picked up taxable compensation during the year, or who moved off minimum wage after a wage order or a promotion, and were left flagged as exempt for the whole period.
Adjustments made after the December cutoff are the quiet one. Final pay corrections, late overtime and reversed deductions all change the annual figures, and a certificate printed from stale payroll data will not tie back to what you remitted.
Getting the numbers to agree before you print
The reconciliation is a data problem before it is a tax problem. You need, per employee for the full calendar year, gross compensation split into taxable and non-taxable components, the employee share of statutory contributions, benefits subject to the exclusion, and the tax withheld each period — and those figures have to match what sat behind your monthly remittances.
That is the practical argument for keeping payroll in one system rather than a folder of spreadsheets. In ERPat, the Compensation module holds earnings, deductions, allowances and payslips as a single continuous record fed straight from attendance, so a year's figures for one employee are a query rather than a reassembly job. The Finance module carries accounts, expenses, payments, loans and reconciliation with automated tax calculations and dynamic reports, which is where the payroll side and the remittance side meet.
Whatever you run it on, do the check in the same order the BIR will: annualize, compare against what was withheld, resolve the difference inside a payroll period, then print.
Start the close in the first week of January
January is short, and the certificate is the last step rather than the first. Pull the year's payroll register early, flag the mid-year hires with no previous employer's 2316 on file, the employees whose benefits crossed the exclusion ceiling, and anyone whose status changed during the year. Settle those adjustments in a live payroll period while you still have one, then issue the certificates, file 1604-C with the alphalists, and build the substituted filing list for February.
Handled in that order, January 31 becomes a printing date instead of a scramble — and the employees who do have to file in April get a certificate they can rely on.
Compliance context
Turn "BIR Form 2316: What Employers Prepare in January" into a compliance checklist
Compliance-heavy articles are most useful when they become a repeatable review habit. Treat the guidance as a way to confirm evidence, ownership and timing before reports or payroll records are submitted.
Part 1Documents and records to prepare
Before the team reviews compliance requirements, make sure the supporting records are complete and traceable.
- Employee master records, pay history, schedules, leaves and attendance logs
- Contribution, tax, deduction and adjustment summaries
- Approval records, exception notes and revision history
Part 2Common gaps to prevent
Compliance gaps often come from missing evidence rather than missing intent. The system should make proof easy to find.
- Late updates to employee status, salary rates or tax/contribution details
- Manual corrections without a reason or reviewer attached
- Reports generated from data that does not match the approved payroll run
Part 3How to make review repeatable
Create a simple rhythm: prepare records, run checks, document exceptions, approve, then lock the final version.
- Use the same checklist every cutoff or reporting period
- Assign one owner for exceptions and one owner for final approval
- Keep final reports and supporting details together for later audit review
Jerome Evangelista
Content & Solutions Writer
Writes about payroll automation, HRIS, and how Philippine businesses run leaner with ERPat.




