BIR Excel Uploader Alternative for BIR Form 1604-F: Preparing the Final Withholding Tax Alphalist

For the BIR Form 1604-F alphalist, a BIR Excel Uploader alternative is worth considering when you need more than a one-off Excel-to-DAT conversion — specifically, when you want the payee list and annual totals checked against the BIR Form 2306 certificates already issued that year, before the file is even generated. Both a standalone converter and BIR Online Tools can turn a completed spreadsheet into a valid DAT file. The difference shows up earlier, in whether that spreadsheet’s numbers already agree with what was certified to each payee months before January.

This post looks specifically at the 1604-F final withholding tax alphalist — a narrower, less-discussed filing than its 1604-C and 1604-E siblings — and where a session-based converter leaves reconciliation work to the filer.

What makes the 1604-F alphalist different from a routine conversion job? #

BIR Form 1604-F reports only payees who received income subject to final withholding tax during the calendar year — dividends, certain interest, and similar income types where the tax withheld is the complete settlement, not a credit the payee applies elsewhere. Every row on that alphalist should trace back to a BIR Form 2306 certificate the same withholding agent already issued to the same payee during the year. That makes the 1604-F alphalist less a data-entry task and more a reconciliation task: the spreadsheet has to match figures that already exist somewhere else in the filer’s records. For the return itself and how it differs from 1604-C and 1604-E, see What Is BIR Form 1604-F?; for the column layout and ATC codes the DAT file needs, see How to Convert Excel to BIR DAT File for BIR Form 1604-F.

Does BIR Excel Uploader handle the 1604-F alphalist? #

Yes — BIR Excel Uploader supports Excel-to-DAT conversion for the standard alphalist forms, including the annual returns, alongside RELIEF, SAWT, QAP, and Form 2307/2306/2316 certificates. Conversion coverage isn’t where a basic uploader falls short for 1604-F specifically. What its published workflow doesn’t address is the step before conversion: a download-template, fill-in, upload, validate-separately-through-BIR sequence with no visible connection to the BIR Form 2306 certificates the same payor already issued to the same payees earlier in the year.

Gaps that show up specifically for 1604-F filers using a session-based converter:

• No cross-check between the alphalist’s payee totals and the BIR Form 2306 certificates already issued for those same dividend, interest, or other final-tax payments
• No shared record tying 1604-F payee data to the withholding agent’s Form 2306 issuance history across the year
• No carryover of payee TINs and registered names from certificates already generated, so they’re re-typed into a fresh template
• Manual template work each filing season, with reconciliation against prior certificates left entirely to the filer

How does BIR Online Tools approach the 1604-F alphalist differently? #

BIR Online Tools’ DAT file generation and BIR Form 2306 certificate features sit in the same company account, so the payee records behind a 1604-F alphalist come from the same place the certificates themselves were generated — rather than a separate, disconnected upload. That doesn’t change what the DAT file needs to contain; it changes where the underlying numbers come from and what they’re checked against before the file is produced.

No converter — BIR Online Tools included — replaces the BIR’s own Alphalist Data Entry and Validation Module check before eSubmission. The comparison here is about what happens upstream of that check, not about skipping it.

A worked example: reconciling a 1604-F alphalist against certificates already issued #

Consider a holding company that distributed cash dividends to eight corporate and individual shareholders during the year and paid final-tax interest on a time deposit through its bank. Over the year, it issued eight BIR Form 2306 certificates — one per shareholder for the dividend payment, using ATC code WC160, and a separate certificate for the bank interest under a different final-tax ATC.

When the 1604-F alphalist is drafted in January, one shareholder’s row shows a dividend amount that’s ₱5,000 lower than the figure printed on their already-issued BIR Form 2306 — a correction was made to that shareholder’s payment mid-year through an adjusting journal entry, but the update never made it into the alphalist working file, which had been copied from an earlier draft. In a converter with no link between the alphalist and the certificates already on file, that kind of discrepancy surfaces only if someone manually pulls all eight 2306 certificates and checks each figure against the alphalist line by line — easy to skip when there are only eight payees, easier to miss when there are eighty. Because the payee records in BIR Online Tools’ alphalist and certificate features share the same company account, the two figures are visible side by side before the DAT file is generated.

Which fits better — a basic uploader or a reconciliation-aware alternative? #

A basic BIR Excel Uploader may be enough for a straightforward 1604-F filing; a repeat-filing alternative fits better once the payee list needs to stay in sync with certificates issued earlier in the year. The right choice depends less on file size and more on how much manual cross-checking you’re willing to do every January.

A standalone BIR Excel Uploader may be enough if you:

• File 1604-F for a small, stable set of final-tax payees with no mid-year corrections
• Don’t mind manually comparing the alphalist against each BIR Form 2306 already issued
• Have no ongoing need to keep payee records linked between certificates and the annual filing

A reconciliation-aware alternative fits better if you:

• Issue multiple BIR Form 2306 certificates during the year for dividends, interest, or other final-tax payments
• Want the 1604-F alphalist’s payee totals checked against those certificates before generating the DAT file
• Prefer payee TINs and names carried forward rather than retyped into a blank template each January

Frequently asked questions #

Do I still need BIR Excel Uploader for BIR Form 1604-F if I already use BIR Online Tools? #

No. BIR Online Tools generates the same Excel-to-DAT conversion for the 1604-F alphalist that a standalone BIR Excel Uploader provides, and it draws on the same company account already used to issue BIR Form 2306 certificates during the year, so payee records don’t need to be re-typed from a blank template in January.

What does BIR Excel Uploader do for BIR Form 1604-F alphalist prep? #

BIR Excel Uploader converts a completed Excel template into the BIR’s DAT format for the 1604-F alphalist. That conversion step is the same regardless of which tool performs it — the difference is what happens before conversion, specifically whether the payee list and totals already reconcile with certificates issued earlier in the year.

Why is the 1604-F alphalist prone to reconciliation errors? #

The 1604-F alphalist reports final withholding tax payees only, and each row’s income payment and tax-withheld totals should match the sum of what was already certified on that payee’s BIR Form 2306 certificates during the year. A converter with no link to certificate history can’t flag a mismatch before the file is generated — the filer has to catch it manually.

When is BIR Form 1604-F due? #

BIR Form 1604-F is due on or before January 31 of the year following the calendar year in which the final withholding taxes were accrued or paid, the same deadline as BIR Form 1604-C, under Revenue Regulations No. 11-2018.

Does converting the 1604-F alphalist through any tool skip BIR’s own validation? #

No. Regardless of which converter produces the DAT file, it still has to pass validation through the BIR’s own Alphalist Data Entry and Validation Module before eSubmission. A converter’s job is producing a correctly structured file, not replacing that check.

What Section 58 of the NIRC requires #

The Excel-to-DAT conversion step, and the choice of which tool performs it, sits downstream of a statutory requirement, not a BIR-invented one. Section 58 of the National Internal Revenue Code, as amended, requires every withholding agent that deducted and withheld tax to submit an annual information return to the Commissioner listing its payees, the income payments made to them, and the tax withheld from each. Multiple secondary sources summarizing Section 58(B) consistently describe the final-withholding-tax deadline in substantially the same terms:

“Every withholding agent required to deduct and withhold taxes under [the withholding tax provisions] shall submit to the Commissioner an annual information return containing the list of payees and income payments… In the case of final withholding taxes, the return shall be filed on or before January 31 of the succeeding year.”

— Section 58(B) of the National Internal Revenue Code, as amended, per secondary legal/tax commentary summarizing the provision. This excerpt is drawn from secondary sources rather than a direct fetch of the primary NIRC text in this session; verify the exact wording against the BIR or an official copy of the Tax Code before relying on it for a filing position. BIR Form 1604-F, and the alphalist filed with it, is how that statutory return is implemented for payees subjected to final tax specifically. Revenue Regulations No. 11-2018 then layers on the requirement that the accompanying alphalist be submitted electronically through the BIR’s Alphalist Data Entry and Validation Module rather than as a printed listing — which is the reason a DAT file, not a paper attachment, is what either BIR Excel Uploader or BIR Online Tools ultimately produces.

Summary #

For the BIR Form 1604-F alphalist, both a standalone BIR Excel Uploader and BIR Online Tools can convert a completed Excel file into a valid DAT file — that part of the job is the same either way. The difference is upstream: whether the payee list and annual totals going into that file already reconcile with the BIR Form 2306 certificates issued to the same payees during the year, or whether that reconciliation is left entirely to the filer working from a blank template every January. See What Is BIR Form 1604-F? for the return itself, How to Convert Excel to BIR DAT File for BIR Form 1604-F for the column-level conversion process, and BIR Annual Alphalist (1604-C, 1604-E, 1604-F) for how all three annual alphalists relate.