Common 1604-C Alphalist of Employees Errors and How to Fix Them Before Filing

Most BIR Form 1604-C Alphalist of Employees rejections or post-filing corrections trace back to five patterns: TIN and identity errors, missing or wrong Minimum Wage Earner (MWE) tagging, incorrect exemption or status codes, omitted separated employees, and totals that don’t reconcile to monthly BIR Form 1601-C remittances or to the compensation shown on employees’ BIR Form 2316 certificates. Each one is a data problem in the source payroll file, not something the BIR’s alphalist module can silently correct — catching them before the January 31 deadline avoids a rejected submission or, worse, a filing the BIR later flags for review.

This guide walks through each failure mode for the employee alphalist specifically. For the return it attaches to and its deadline, see BIR Annual Alphalist (1604-C, 1604-E, 1604-F); for the certificate its totals should reconcile against, see What Is BIR Form 2316?

Why does the alphalist reject a TIN? #

A TIN error on the Alphalist of Employees usually means a placeholder value, a formatting problem, or an unconfirmed number for a recently hired employee. The BIR’s validation logic treats the TIN as the primary identity key for every employee record — the alphalist module strictly rejects placeholders and structurally invalid entries rather than flagging them as a soft warning.

Typical causes:

• Placeholder TIN such as 000-000-000-000 left on a record for a new hire whose TIN wasn’t confirmed before the payroll cutoff
• TIN pasted with dashes, spaces, or extra characters instead of digits only
• A TIN transposed between two employees during manual data entry
• Special characters (ñ, extra commas, misplaced suffixes like Jr./Sr.) elsewhere in the name fields that cause the record as a whole to fail structural validation, even when the TIN itself is correct

Fix: confirm every employee’s TIN against BIR registration or their own Form 2316 from a prior employer before the file is finalized, format the column as text, and never submit a placeholder value — hold the record for correction rather than filing it incomplete.

Why does MWE tagging matter, and what goes wrong? #

Incorrectly tagging an employee’s Minimum Wage Earner (MWE) status distorts the annualized withholding computation, because the alphalist module applies different tax logic to MWE and non-MWE employees. MWE compensation is exempt from withholding tax, along with certain related pay items (holiday pay, overtime pay, night differential, and hazard pay for a qualified MWE); non-MWE employees don’t get that exemption.

Fix: re-verify MWE status against the region’s current minimum wage order at year-end, not just at hiring — an employee’s MWE status can change mid-year with a wage increase, and the alphalist should reflect their status for the periods actually worked under each classification.

Wrong exemption or employee status codes #

A 1604-C alphalist record can carry the correct TIN and MWE flag but still fail on the wrong employee status or exemption code, which the module uses to determine how compensation and withholding were computed. Using a Regular code for someone actually employed as Casual, or leaving an exemption-related field blank where the layout requires an entry, produces a record that’s structurally valid but substantively wrong.

Fix: pull status and exemption codes from the same payroll records used to compute monthly withholding — not from a prior year’s template — and confirm the code set matches the current alphalist format version before filing.

Omitted separated employees #

Every employee who received compensation during the taxable year belongs on the Alphalist of Employees, including someone who resigned or was terminated as early as January of that same year. A common gap is an employer preparing the alphalist from the current headcount rather than the full year’s payroll register, which silently drops anyone no longer on staff by the time the alphalist is compiled.

Fix: build the alphalist from the full-year payroll register, not the year-end active employee list, and cross-check the employee count against every Form 2316 actually issued for the year — a separated employee still received one, and their alphalist entry should mirror it.

Amount mismatches: 1601-C, and Form 2316 #

A 1604-C alphalist that structurally validates can still misreport tax if its totals don’t reconcile to the twelve months of BIR Form 1601-C remitted during the year, or to the compensation and withholding shown on the Form 2316 certificates actually issued. Both checks catch different kinds of errors.

A defective or non-reconciling alphalist is treated as a failure to file a required information return under Section 250 of the NIRC — ₱1,000 per failure, capped at ₱25,000 per calendar year, with compromise-penalty practice under RMO No. 7-2015 — the same exposure that applies to a missed BIR Form 2307 or BIR Form 2316.

Worked example: catching a compensation mismatch before filing #

A retail business with 12 employees prepares its CY2025 alphalist for the January 31, 2026 deadline. Cross-checking the alphalist against the Form 2316 certificates already drafted for each employee turns up one discrepancy, for a fictional employee.

Tracing the ₱24,000 gap shows the alphalist export was pulled before a mid-December payroll adjustment (a ₱24,000 retroactive salary correction covering October and November) was posted, while the Form 2316 draft — generated later — already included it. The fix is to regenerate the alphalist export from the updated, final payroll register, not to adjust the Form 2316 downward to match the earlier alphalist figure, since the Form 2316 reflects the employee’s actual annualized compensation for the year.

Pre-filing checklist #

• TINs digits-only, correctly formatted, no placeholder values, verified against BIR records
• MWE flag current as of each employee’s actual pay periods, including mid-year wage-order changes
• Employee status and exemption codes drawn from the same records used for monthly withholding computation
• Every employee paid during the year included, including those separated early in the year
• Alphalist totals reconcile to the sum of monthly BIR Form 1601-C remittances for the year
• Per-employee alphalist figures match the Form 2316 actually issued to that employee

Frequently asked questions #

Why does my 1604-C alphalist fail TIN validation? #

The most common causes are a placeholder TIN like 000-000-000-000 left on an incomplete employee record, a TIN copied with dashes or spaces instead of digits only, and a TIN that doesn’t match BIR registration records because an employee was recently hired and their TIN wasn’t yet confirmed.

What happens if I forget to include a resigned employee on the alphalist? #

Every employee who received compensation during the taxable year must appear on the Alphalist of Employees, even if they resigned or were terminated in January of that same year. Omitting them understates the employer’s total reported compensation and withholding, and creates a gap between the alphalist and the Form 2316 that employee should have received.

What is the MWE flag and why does it matter on the alphalist? #

The MWE (Minimum Wage Earner) flag tags employees whose compensation is exempt from withholding tax under the applicable minimum wage rules. Tagging a non-MWE employee as MWE, or the reverse, distorts the annualized tax computation the BIR alphalist module applies, since MWE and non-MWE employees are computed under different logic.

Why do 1604-C totals need to match Form 1601-C returns filed during the year? #

BIR Form 1604-C is meant to reconcile a full year of monthly withholding already reported through Form 1601-C. If the sum of the alphalist’s reported tax withheld doesn’t match the total remitted across all twelve monthly 1601-C filings, the discrepancy signals either a payroll error during the year or a data-entry mistake in the annual alphalist itself.

What penalty applies to a defective 1604-C alphalist? #

A late, missing, or defective 1604-C alphalist is treated as a failure to file a required information return under Section 250 of the NIRC, carrying a P1,000 penalty per failure capped at an aggregate of P25,000 per calendar year, with compromise-penalty guidance under RMO No. 7-2015.

Summary #

A 1604-C Alphalist of Employees usually fails — structurally or substantively — for one of five reasons: bad TINs, wrong MWE tagging, incorrect status/exemption codes, omitted separated employees, or totals that don’t reconcile to monthly Form 1601-C remittances and issued Form 2316 certificates. All five are source-data problems fixable before the January 31 deadline if the alphalist is built from the full-year payroll register and cross-checked against Form 2316, not assembled from a snapshot of current staff. See BIR Annual Alphalist (1604-C, 1604-E, 1604-F) for deadlines across all three annual alphalists, and What Is BIR Form 2316? for the certificate the alphalist should always reconcile against.