Common 1604-E Alphalist of Payees Errors and How to Fix Them Before Filing

Most BIR Form 1604-E Alphalist of Payees rejections or post-filing corrections trace back to five patterns: payee TIN or name mismatches against the Certificate of Registration (COR), wrong Alphanumeric Tax Code (ATC) or Schedule 3/Schedule 4 classification, duplicate payee rows left over from quarterly QAP files, tax-withheld totals that don’t reconcile to the four quarters of QAP already filed, and an incorrect RDO code on the return itself. Each is a source-data problem the BIR’s Alphalist Data Entry and Validation Module won’t silently fix for you — catching them before the March 1 deadline avoids a rejected eSubmission or a filing the BIR later flags for reconciliation.

This guide walks through each failure mode for the expanded-withholding payee alphalist specifically. For the return it attaches to and its March 1 deadline, see BIR Annual Alphalist (1604-C, 1604-E, 1604-F); for the employee-side counterpart, see Common 1604-C Alphalist of Employees Errors; and for the quarterly filing these annual totals should reconcile against, see Common QAP DAT File Errors.

Why does the 1604-E alphalist reject a payee’s TIN or name? #

A 1604-E TIN or name error usually means the entry doesn’t match the payee’s Certificate of Registration (COR) or a Form 2307 already issued to them — a placeholder value, a transposed digit, or a registered name typed as a trade name instead of what the BIR has on file. The Alphalist Data Entry and Validation Module treats the payee’s identity as the primary key for the record, so a structural mismatch fails the row outright rather than producing a soft warning.

Typical causes:

• Placeholder TIN carried over from a template row that was never replaced with the payee’s confirmed number
• A digit transposed when the TIN is copied from an old Form 2307 rather than pulled fresh from the payee’s COR
• Registered name entered as a trade name, abbreviation, or “DBA” instead of the exact registered name on the COR
• A payee’s TIN or registered status changed mid-year (for example, a sole proprietor who incorporated) without updating later-quarter records to match

Fix: verify every payee’s TIN and registered name against their COR — or the most recent BIR Form 2307 issued to them — before compiling the annual file, and never carry forward a row with an unconfirmed placeholder.

Why do ATC codes and Schedule 3/Schedule 4 assignment fail? #

An ATC or schedule error means the 1604-E row doesn’t reflect the income type, payee category, or withholding status actually applied to that payment, even when the payee’s TIN and name are both correct. BIR Form 1604-E splits its alphalist into two schedules: Schedule 3 for payees actually subjected to expanded withholding tax (the same payees who received a Form 2307), and Schedule 4 for payees whose income is exempt from withholding but still subject to income tax, reported instead under Form 2304. Getting the ATC right but the schedule wrong is just as much a rejection risk as the reverse, since each schedule implies a different withholding treatment for the same payee.

Fix: pull the ATC and schedule assignment from the same records used to prepare that payee’s Form 2307 (Schedule 3) or Form 2304 (Schedule 4) during the year — not from a prior year’s alphalist template, which can carry forward a code that no longer applies.

Duplicate payee entries left over from quarterly QAP files #

A duplicate-entry error happens when a payee paid in more than one quarter ends up with several separate rows on the annual 1604-E alphalist instead of a single consolidated figure for the year, inflating the payee count and splitting one payee’s totals across multiple lines. QAP is filed quarterly, with one row per payee per quarter; 1604-E is filed annually, and should carry exactly one row per payee summarizing the full calendar year. The gap usually appears when the annual file is assembled by simply appending four quarters of QAP data together rather than merging them by TIN.

Fix: consolidate every payee by TIN across all four quarters before generating the 1604-E DAT file — sum that payee’s income and tax withheld into a single annual row, rather than exporting quarter-by-quarter rows side by side.

Amount mismatches: 1604-E totals vs. the four quarters of QAP #

A 1604-E alphalist that structurally validates can still misreport tax if its totals don’t reconcile to the same payee data already filed quarterly through QAP with BIR Form 1601-EQ or 1601-FQ. Because 1604-E is a year-end consolidation of transactions the withholding agent already reported quarterly, a gap between the two filings signals either a mid-year correction that wasn’t carried through to a later quarter, or a data-entry error introduced while compiling the annual file from twelve months of records.

A defective, missing, or non-reconciling 1604-E alphalist is treated as a failure to file a required information return under the National Internal Revenue Code (NIRC). Section 250 of the NIRC, as amended, states the rule plainly:

“In the case of each failure to file an information return, statement or list, or keep any record, or supply any information required by this Code or by the Commissioner on the date prescribed therefor, unless it is shown that such failure is due to reasonable cause and not to willful neglect, there shall be paid, upon notice and demand by the Commissioner, … One thousand pesos (P1,000) for each such failure: Provided, That the aggregate amount to be imposed for all such failures during a calendar year shall not exceed Twenty-five thousand pesos (P25,000).”

That P1,000-per-failure, P25,000-per-year cap applies with compromise-penalty guidance under RMO No. 7-2015 — the same exposure that applies to a missed Form 2307 or a defective 1604-C alphalist.

Wrong RDO code on the 1604-E return #

An RDO code error on 1604-E is usually about the withholding agent’s own Revenue District Office code entered on the return header, not a per-payee field — and it goes stale when a business relocates or transfers RDOs without updating its filings. A return filed under an outdated RDO code can create a processing mismatch against the withholding agent’s current BIR registration, separate from any payee-level data issue.

Fix: confirm the current RDO code against the withholding agent’s BIR Form 2303 (Certificate of Registration) before filing, especially if the business moved offices or was reassigned to a different RDO at any point during the taxable year.

Worked example: catching a payee TIN mismatch before filing #

A single mismatched TIN is often enough to bounce an otherwise-correct 1604-E Schedule 3 alphalist back to the withholding agent for correction, even when every other field on that payee’s row — name, ATC, income, and tax withheld — is accurate. The payee below is fictional.

A withholding agent compiling its CY2025 Schedule 3 alphalist for the March 1, 2026 deadline cross-checks its data against payees’ Certificates of Registration and finds one discrepancy:

Fix-and-resubmit steps:

1. Request a current copy of the payee’s COR (or their most recent Form 2307 acknowledgment) rather than relying on the TIN already stored in the payroll/AP system.
2. Correct the TIN field in the source spreadsheet, format it as text to prevent future digit loss, and re-check every other payee sharing a similarly old record.
3. Regenerate the 1604-E DAT file from the corrected source data.
4. Re-run the file through the BIR Alphalist Data Entry and Validation Module and confirm a zero-error report before eSubmission — the same pre-filing discipline described in How to Validate a BIR DAT File Before eSubmission.
5. Resubmit before the March 1 deadline; if the deadline has already passed, file the corrected version as soon as the error is found rather than leaving a known mismatch on record.

Pre-filing checklist #

• Every payee’s TIN and registered name verified against their COR or a recently issued Form 2307
• ATC codes match income type and payee category (individual WI-series vs. corporate WC-series)
• Every payee assigned to the correct schedule — Schedule 3 for actual EWT, Schedule 4 for exempt-but-taxable payees
• Payees consolidated by TIN into one annual row each, not left as separate rows per quarter
• Annual tax-withheld totals reconciled against the sum of all four QAP quarters filed during the year
• RDO code on the return matches the withholding agent’s current BIR Form 2303
• Final DAT file cleared through the BIR Validation Module before eSubmission

Frequently asked questions #

Why does my 1604-E alphalist fail TIN or name validation? #

The most common causes are a placeholder TIN never replaced with the payee’s actual number, a digit transposed while copying a TIN from an old Form 2307 instead of the payee’s Certificate of Registration, and a registered name entered as a trade name or abbreviation instead of the exact name on file with the BIR.

What is the difference between Schedule 3 and Schedule 4 on the 1604-E alphalist? #

Schedule 3 lists payees actually subjected to expanded withholding tax, the same payees who received a BIR Form 2307 during the year. Schedule 4 lists payees whose income payments are exempt from withholding tax but still subject to income tax, reported instead under BIR Form 2304. Placing a payee in the wrong schedule misstates whether withholding tax was actually collected on that income.

Why does a payee show up more than once on my 1604-E alphalist? #

This usually happens when the annual file is assembled by appending four quarters of QAP data instead of consolidating them, so a payee paid in more than one quarter gets a separate row per quarter rather than one summed annual row. The 1604-E alphalist should have exactly one row per payee for the full calendar year.

What happens if my 1604-E totals don’t match the four quarters of QAP I already filed? #

If the annual tax withheld reported on 1604-E doesn’t reconcile to the sum of the same payee’s entries across all four quarters of QAP already filed with BIR Form 1601-EQ or 1601-FQ, the file may still pass structural validation but creates a matching gap the BIR can query later. Fix the source data and reconcile before filing, not after.

What penalty applies to a defective or late 1604-E alphalist? #

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

Summary #

A 1604-E Alphalist of Payees usually fails — structurally or substantively — for one of five reasons: bad TINs or names against the payee’s COR, wrong ATC or Schedule 3/Schedule 4 classification, duplicate rows left over from quarterly QAP exports, totals that don’t reconcile to the year’s four QAP quarters, or a stale RDO code on the return itself. All five are source-data problems fixable before the March 1 deadline if the annual file is built by consolidating verified payee records, not by appending quarterly exports. See BIR Annual Alphalist (1604-C, 1604-E, 1604-F) for deadlines across all three annual alphalists, Common 1604-C Alphalist of Employees Errors for the compensation-side counterpart, and Common QAP DAT File Errors for the quarterly filing these annual totals should always tie back to.