Best BIR Excel Uploader Alternative for Annual Alphalist (1604-C/1604-E) Filing

For the Annual Alphalist attached to BIR Form 1604-C or 1604-E, the best BIR Excel Uploader alternative is one that carries employee and payee records forward from the rest of the year’s filings, rather than treating January as a blank-template rebuild. The annual alphalist isn’t a fresh dataset — it’s 12 months of payroll and withholding activity compressed into one filing, so the real risk isn’t the Excel-to-DAT conversion step itself, it’s a mismatch between what the alphalist reports and what was already certified to the same employees and payees all year.

This guide looks at where a basic converter leaves that consolidation work to the filer, and how the Alphalist of Employees and Alphalist of EWT modules in BIR Online Tools are built around it instead.

Why does a once-a-year filing carry more risk than a quarterly one? #

BIR Form 1604-C (Annual Information Return of Income Taxes Withheld on Compensation, with the Alphalist of Employees) and BIR Form 1604-E (Annual Information Return of Creditable/Final Income Taxes Withheld, with the Alphalist of Payees) both consolidate a full calendar year of activity, due January 31 of the following year under BIR regulations — see BIR Annual Alphalist (1604-C, 1604-E, 1604-F) for the underlying deadlines and requirements. Because the alphalist rolls up 12 months at once, an error that would have been caught quickly in a single quarter’s QAP or SAWT filing instead surfaces all at once in January — a departed employee left off the list, a TIN that was mistyped in Q2 and never corrected, or a cumulative compensation figure that doesn’t reconcile with the certificates already issued.

Does BIR Excel Uploader convert the annual alphalist? #

Yes — BIR Excel Uploader supports Excel-to-DAT conversion for 1604E and 1604C (Schedule 1, and Schedule 2 for minimum wage earners), in addition to RELIEF, SAWT, QAP, and Form 2307/2306/2316 certificates. The conversion step itself isn’t the gap. What the tool’s published workflow doesn’t address is what happens before that January upload: it’s a download-template, populate, upload, then validate-separately-through-BIR workflow with no visible link to the same employer’s account history, prior filings, or certificates issued earlier in the year.

Common gaps for annual alphalist filers using a session-based converter:

• No carryover of employee or payee TINs, names, and cumulative figures from the SAWT, QAP, or certificate data already on file for the same year
• No cross-check against BIR Form 2316 certificates already issued to the same employees, so a discrepancy between what an employee received and what the alphalist reports isn’t flagged before filing
• No shared account tying 1604-C/1604-E data to the same payor’s Form 2307 or 2316 issuance history
• Each year’s upload starts from a blank template, with reconciliation against prior-year or prior-quarter data left entirely to the filer

How does BIR Online Tools handle the annual alphalist differently? #

Note that no converter — including BIR Online Tools — replaces the BIR’s own Validation System check before eSubmission. The difference this comparison is about is what happens upstream of that check: whether the data going in already reconciles with what’s been filed and certified all year, or whether that reconciliation is left entirely to the filer working from a blank template.

A worked example #

A company with 40 rank-and-file employees issues BIR Form 2316 to each of them in January, listing each employee’s total compensation and tax withheld for the year. When preparing the 1604-C alphalist for the same filing season, one employee’s cumulative compensation in the alphalist draft doesn’t match the figure on their already-issued Form 2316 — the employee received a mid-year salary adjustment that was reflected in payroll but not consistently carried into every quarter’s withholding records. In a converter with no link between the alphalist and the certificates already issued, that discrepancy would only surface if someone manually cross-checked 40 individual 2316 certificates against the alphalist spreadsheet line by line. Because BIR Online Tools’ alphalist module draws on the same account and payee records used to generate those 2316 certificates, the mismatch is visible before the file is even converted.

Which should you use for the annual alphalist — a basic uploader or a repeat-filing alternative? #

A basic BIR Excel Uploader may be enough if you:

• Have a small, stable employee or payee list with no departures, additions, or mid-year adjustments to reconcile
• Don’t mind manually cross-checking the alphalist against certificates already issued during the year
• File once a year and don’t need that data linked to your quarterly SAWT, QAP, or certificate history

A repeat-filing alternative fits better if you:

• Manage payroll or withholding for an employee or payee list that changes during the year
• Already generate BIR Form 2307 or 2316 certificates for the same people through the same platform
• Want employee/payee TINs and cumulative figures carried forward instead of retyped from a blank template every January

Frequently asked questions #

Does BIR Excel Uploader support the annual alphalist for 1604-C and 1604-E? #

Yes — BIR Excel Uploader supports Excel-to-DAT conversion for 1604E and 1604C (Schedule 1 and Schedule 2/MWE) alongside RELIEF, SAWT, QAP, and Form 2307/2306/2316 certificates. The gap isn’t conversion coverage — it’s that each annual upload is a standalone session with no link to the same employer’s certificates or filings from earlier in the year.

Why is the annual alphalist harder to prepare than a quarterly filing like QAP or SAWT? #

The annual alphalist for 1604-C or 1604-E consolidates 12 months of payroll or withholding activity into one filing, so any TIN typo, missing employee, or mismatched cumulative compensation figure from an earlier quarter surfaces all at once in January rather than being caught closer to when it happened.

When are BIR Form 1604-C and 1604-E due? #

BIR Form 1604-C, the Annual Information Return of Income Taxes Withheld on Compensation with the Alphalist of Employees, is due January 31 of the year following the taxable year. BIR Form 1604-E, the Annual Information Return of Creditable/Final Income Taxes Withheld with the Alphalist of Payees, follows its own annual filing schedule under BIR regulations.

Can the same employee or payee data used in BIR Form 2316 or Form 2307 carry over to the annual alphalist? #

In BIR Online Tools, yes — because the alphalist modules draw on the same company account used to generate BIR Form 2307 and 2316 certificates and file SAWT/QAP throughout the year, employee and payee TINs, names, and cumulative figures don’t need to be re-typed from a blank template at year-end.

Does converting the annual alphalist to DAT format replace BIR’s own validation step? #

No. Any DAT file, however it’s generated, still needs to pass validation through the BIR’s own Validation System before submission — a converter’s job is producing a correctly structured file, not replacing that final BIR-side check.

Summary #

The annual alphalist’s real challenge isn’t converting Excel to DAT — both BIR Excel Uploader and BIR Online Tools handle that — it’s making sure 12 months of payroll or withholding data reconciles with the certificates already issued to the same employees and payees before January’s deadline. See BIR Annual Alphalist (1604-C, 1604-E, 1604-F) for the deadlines and requirements, How to Convert Excel to BIR DAT File for Annual Alphalist for the raw column format, and Best BIR Excel Uploader Alternative for QAP Filing for the same comparison applied to the quarterly alphalist.