What Happens If an Employee's BIR Form 2316 Total Doesn't Match Your Alphalist?

When an employee’s issued BIR Form 2316 shows different compensation or tax-withheld figures than that employee’s line on the BIR Form 1604-C Alphalist of Employees, it means one of the two documents is wrong — because both are supposed to come from the same year-end withholding computation. Left uncorrected, the gap can surface through BIR’s data-matching as a discrepancy inquiry, misstate the employer’s reported withholding tax, and leave the employee unable to claim the correct tax credit on their own return.

This alphalist module is in development. QAP, SAWT, RELIEF, and BIR Form 2307 are live today, free.

Why must the Form 2316 and the alphalist match in the first place? #

BIR Form 2316 and the employee’s entry on the Alphalist of Employees are not two independent documents — they’re two outputs of the same annualized withholding computation, so their compensation and tax-withheld figures should be identical, not merely close. Under the withholding-on-compensation rules in Revenue Regulations (RR) No. 2-98, as amended, an employer runs a year-end annualization for each employee, determines the tax due for the year, and then produces both the employee’s Certificate of Compensation Payment/Tax Withheld (BIR Form 2316) and that same employee’s line item in the alphalist attached to BIR Form 1604-C from that one computation.

Because both documents trace back to a single source calculation, any difference between them means the two weren’t actually generated from the same final payroll data — a corrected Form 2316 issued after a payroll adjustment, an alphalist export pulled before a correction was posted, or a manual re-entry error are the usual culprits. Related formatting and data-entry failures on the alphalist file itself are covered separately in Common 1604-C Alphalist of Employees Errors and How to Fix Them Before Filing; this post is specifically about what happens once a real figure mismatch — not a format error — is discovered.

How does BIR discover a mismatch after filing? #

BIR compares withholding tax information across returns, certificates, and third-party records, so a mismatch that survived filing doesn’t necessarily stay hidden — it can resurface through BIR’s own data-matching, sometimes as a discrepancy inquiry known as a Letter Notice. BIR’s Letter Notice process is generally used to flag inconsistencies its systems detect between what one filer reported and what related records show, and while it’s most commonly associated with third-party sales and purchase matching, the same underlying principle applies to withholding tax data: figures that should tie out and don’t are exactly the kind of anomaly BIR’s systems are built to surface.

A mismatch can also surface a second way that has nothing to do with an employer-side audit: if the employee doesn’t qualify for substituted filing and must file their own annual income tax return, they claim their withholding tax credit based on the BIR Form 2316 in their hand. If that certificate’s figure doesn’t match what the employer actually reported to BIR through the alphalist, the employee’s claimed credit and BIR’s own record of that employee’s withholding disagree — a problem for the employee’s return even if the employer’s 1604-C otherwise gets filed on time.

What does an unresolved mismatch put at risk? #

An uncorrected Form 2316-to-alphalist mismatch carries exposure on three fronts: the employer’s filing itself, potential penalty and audit risk, and the affected employee’s own tax position.

None of these risks require BIR to have already opened an examination — they’re consequences of the mismatch existing in BIR’s records at all, whether or not anyone has looked at that specific employee’s file yet.

Pre-filing reconciliation checklist #

Run this check on every employee before submitting BIR Form 1604-C and its alphalist — not just at year-end, but as a final pass right before the January 31 filing deadline:

1. Gross compensation matches — the total gross compensation on each employee’s alphalist line equals the gross compensation shown on that employee’s issued BIR Form 2316, to the peso.
2. Tax withheld matches — the tax withheld figure on the alphalist line equals the tax withheld shown on the Form 2316, with no rounding difference explained away.
3. Employee count matches — the number of employees on the alphalist equals the number of Form 2316 certificates actually issued for the year, including anyone separated mid-year.
4. No one-sided entries — no employee appears on the alphalist without a corresponding Form 2316, and no issued Form 2316 is missing from the alphalist.
5. Both pulled from the same final payroll run — the alphalist export and the Form 2316 batch were generated from the same, final payroll register — not one from an earlier draft and one from a later correction.
6. Alphalist totals tie to monthly BIR Form 1601-C remittances for the year, as a second independent check on the same underlying withholding data.

Governing basis: why the alphalist is required to reconcile #

The alphalist isn’t a courtesy attachment — its submission is a distinct regulatory requirement under RR No. 2-98, as amended by RR No. 1-2014, which rewrote Section 2.83.3 of RR No. 2-98 to require every withholding agent to submit an alphabetical list as an integral part of its annual information return. As BD&P Law Offices summarizes the operative text of that amended section:

“All withholding agents shall, regardless of the number of employees and payees, whether the employees/payees are exempt or not, submit an alphabetical list of employees and list of payees on income payments subject to creditable and final withholding taxes which are required to be attached as integral part of the Annual Information Returns.”

Because the alphalist is legally an integral part of BIR Form 1604-C, not a separate courtesy document, a per-employee figure that doesn’t match the certificate that same employee actually received is a defect in the return itself — the same 1604-C filing obligation that, under Section 250 of the National Internal Revenue Code (NIRC), exposes the employer to a failure-to-file-a-required-information-return penalty when it isn’t corrected.

Worked example: a ₱3,000 payroll data-entry gap #

A logistics company issues its CY2025 Forms 2316 in mid-January 2026, ahead of the January 31 deadline, then exports its alphalist for BIR Form 1604-C a few days later. Cross-checking the two before submission catches one employee out of alignment.

Tracing the gap shows the payroll team corrected a missed commission payment on Renato’s December payslip after his Form 2316 had already been generated and issued, but the alphalist export was pulled from the corrected, final payroll register — meaning the alphalist is actually right, and the already-issued Form 2316 is the document that’s wrong. Filing BIR Form 1604-C with the correct alphalist figure while an outdated Form 2316 remains in the employee’s hands would still leave a live mismatch: if Renato doesn’t qualify for substituted filing and later files his own return, or an outside party ever verifies his prior withholding, the certificate in his file understates what BIR’s own alphalist record shows the employer actually withheld.

The fix: reissue a corrected BIR Form 2316 to Renato reflecting the ₱620,000 / ₱15,000 figures before finalizing the 1604-C submission, so the certificate in his hands and the alphalist entry BIR receives agree — rather than filing the correct alphalist and leaving a stale certificate uncorrected in the field.

How to fix a mismatch discovered after filing #

If the discrepancy isn’t caught until after BIR Form 1604-C has already been filed, don’t wait for BIR’s data-matching to flag it:

1. Confirm which document is wrong by tracing both back to the final, corrected payroll register for that employee.
2. Reissue a corrected BIR Form 2316 to the employee if the certificate is the one in error, documenting the correction.
3. File an amended BIR Form 1604-C with a corrected alphalist entry for that employee, matching the amendment procedures for information returns.
4. Keep the payroll trail (the original figure, the correction, and the date it was applied) on file — it’s the documentation that explains the gap if BIR’s systems flag it independently before the correction is on record.

Frequently asked questions #

What happens if an employee’s Form 2316 doesn’t match the alphalist? #

The two figures should be identical because both come from the same year-end withholding computation. A mismatch means one of the two documents is wrong, and if it isn’t caught before filing BIR Form 1604-C, it can surface later as a BIR discrepancy inquiry, misstate the employer’s reported withholding, and leave the employee unable to claim the correct tax credit on their own return.

Can a Form 2316-to-alphalist mismatch trigger a BIR audit? #

It can contribute to one. BIR’s data-matching systems compare withholding tax information across returns and certificates, and an unresolved inconsistency is a documented trigger for a discrepancy inquiry — sometimes called a Letter Notice — that can escalate into a full examination if the employer doesn’t reconcile and explain the gap.

Should I correct the Form 2316 or the alphalist when they disagree? #

Trace the discrepancy back to the payroll register first — whichever document doesn’t match the final, correct payroll figures is the one to fix. Do not adjust the correct document downward just to make it match the wrong one; both should end up reflecting the employee’s actual annualized compensation and tax withheld for the year.

Does a mismatch affect the employee, or only the employer? #

Both. The employer risks a discrepancy notice, penalties, and possible audit exposure. The employee is affected too — if they qualify for substituted filing, a wrong Form 2316 becomes their income tax return of record, and if they must file their own return, the tax credit they claim may not match what the BIR has on file from the employer’s alphalist.

How do I fix a mismatch discovered after BIR Form 1604-C has already been filed? #

Reissue a corrected BIR Form 2316 to the employee documenting the true figures, and file an amended BIR Form 1604-C with a corrected alphalist entry for that employee as soon as the error is found. The longer a known mismatch goes uncorrected, the harder it becomes to explain if BIR’s data-matching flags it independently.

Summary #

A BIR Form 2316-to-alphalist mismatch is never cosmetic — because both documents are supposed to come from the same annualized withholding computation, any gap between them means one of the two is factually wrong, and it can be discovered either through BIR’s own data-matching or by the affected employee’s tax return not lining up with BIR’s records. Run the pre-filing reconciliation checklist above before every BIR Form 1604-C submission, and if a mismatch is already discovered, fix the source document and reissue or amend rather than letting it sit. For the format and data-entry errors that can produce these mismatches in the alphalist file itself, see Common 1604-C Alphalist of Employees Errors and How to Fix Them Before Filing; for the certificate’s issuance rules and deadlines, see What Is BIR Form 2316 and When Must You Issue It?