Alphalist Season: Getting Annual BIR Reporting Right
January and February carry the heaviest BIR reporting load an employer faces all year: certificates to employees, the annual return with its alphalists, and the duplicate copies that follow. Here is what each one depends on.
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
The payroll year closes on December 31, but for the people who run it the work starts in January. Within a few weeks an employer has to hand every employee a certificate of the tax withheld from them, file the annual return that summarises all of it, and then send the BIR its own copies of those certificates. None of it is difficult in itself; it is simply unforgiving of records that were never quite reconciled during the year.
The three deliverables of alphalist season
Three obligations sit close together at the start of the year and are easy to blur into one. The first is BIR Form 2316, the Certificate of Compensation Payment/Tax Withheld: every employer must furnish it to each employee from whom taxes were withheld on or before January 31 of the succeeding calendar year, or on the day the last payment of compensation is made if the employment ended earlier.
The second is BIR Form 1604-C, the Annual Information Return of Income Taxes Withheld on Compensation, filed together with the alphalists of employees and carrying the same January 31 deadline.
The third lands a month later. In cases covered by substituted filing, duplicate copies of Form 2316 go to the BIR not later than February 28 of the succeeding year, together with the Certified List of Employees Qualified for Substituted Filing. Same certificates, different recipient, different deadline.
What the alphalist is actually reporting
The alphalist is the employee-level detail behind the summary on the return. For each person it restates the year as a whole: total compensation paid, the portions that are not taxable, the taxable balance, and the tax withheld against the tax due. The return has to agree with the alphalist supporting it, so a single uncorrected employee row shows up as a mismatch on the face of the filing.
That detail comes out of year-end annualisation, not from adding up twelve months of withholding. When the December payroll is computed, the year's taxable compensation is measured against the annual graduated schedule, and the difference between tax due and tax already withheld is collected or refunded then. If that step was skipped, or was run before a late adjustment was posted, the alphalist inherits the error, and so does every Form 2316 printed from the same figures.
Where the P90,000 cap decides the outcome
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; any excess over P90,000 is taxable compensation subject to withholding. The cap is annual and aggregate, which is what makes it a reporting problem rather than a December one. The 13th month pay that Presidential Decree No. 851 requires to be paid not later than December 24 is only part of what counts toward it.
The question at year-end is therefore not what a particular payment was called, but what the running total of 13th month pay and other benefits reached by December 31 for each employee. The exempt portion and the excess are reported separately, and the excess should already have passed through withholding in the period it was paid. Where it did not, annualisation is the last chance to fix it before the figures become a filed return.
Minimum wage earners, joiners and leavers
Minimum wage earners are exempt from income tax and withholding tax on the statutory minimum wage fixed by the regional wage board for their place of assignment, and the exemption also covers their holiday pay, overtime pay, night shift differential pay and hazard pay. Few employee records stay still for twelve months, though. Someone moved above the minimum wage in August was a minimum wage earner for part of the year and not for the rest, and the alphalist has to reflect both halves.
Employees who joined mid-year bring figures from a previous employer on an earlier Form 2316. Those amounts belong in the annualisation, and they also decide whether the person still qualifies for substituted filing or has to file an individual annual income tax return, which is due on or before April 15. Anyone who left during the year should already have received a certificate on the day of their last payment.
Reconciling the year before you file
The first reconciliation worth doing is between what was remitted month by month and what the alphalist says was withheld for the year. The two will not match line for line, because the December annualisation collects or refunds a difference, but the reconciling items should be few and identifiable. If they are not, the gap is usually an adjustment posted outside payroll, a correction made in a spreadsheet that never went back into the system, or a final pay computed by hand.
The second reconciliation is to the books. Compensation expense, withholding tax payable, and the employee and employer shares of SSS, PhilHealth and Pag-IBIG should tie back to the same payroll register the alphalist was built from. Doing this before filing is considerably cheaper than doing it afterwards in reply to a notice.
Two tax tables are in play this month
Worth stating plainly, because it catches people every January: the return you file this month is not computed on the table you are using for this month's payroll. Compensation earned in taxable year 2022 falls under the graduated schedule that applied from 2018 through 2022 — nothing on the first P250,000, then 20% of the excess over P250,000 up to P400,000, and on up the brackets.
Compensation earned from January 1, 2023 onwards uses the revised schedule: still nothing on the first P250,000, but 15% of the excess over P250,000 up to P400,000, then P22,500 plus 20% of the excess over P400,000. The BIR's revised withholding tax table effective January 1, 2023 reflects the same change. Running January payroll on last year's table is an error you will be correcting in next year's annualisation, so confirm the switch before the cut-off.
Building the records January depends on
Everything above is a records problem before it is a filing problem. Nothing in an alphalist is created in January; it is assembled from twelve months of payroll runs, adjustments and remittances that either agreed with each other as they happened or did not. That is the case for keeping compensation, statutory deductions and the ledger in one system instead of three. ERPat's Finance module covers accounts, expenses, payments and reconciliation with automated tax calculations and dynamic reports, so the figures a year-end return draws on come from one place all year, while the Compliance module adds policy tracking and audit trails — the documentation that turns "this amount changed in October" into an answer rather than an argument.
A system keeps the record consistent, but it cannot know that a bonus was posted to the wrong employee or that a final pay was computed outside payroll. The January reconciliation is still a person's job.
Treat the end of January as a checkpoint rather than a sprint: certificates to employees, then the annual return and alphalists, then the February submission prepared from exactly the same figures. Worked in that order, from one reconciled set of records, the season is administrative rather than fraught.
Compliance context
Turn "Alphalist Season: Getting Annual BIR Reporting Right" 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.




