RMC No. 7-2021 makes Alphalist Module Version 7.0 available and requires covered withholding tax filers to follow updated file structures and naming rules.

Withholding agents using alphalist data files must now align their reporting process with Alphalist Data Entry and Validation Module Version 7.0, including the updated file structures and standard file naming convention for specified BIR withholding tax returns. The practical consequence is immediate for businesses that prepare alphalists through their own extract programs: the old file layout and naming practices should no longer be relied upon where the revised structures apply.

What RMC No. 7-2021 changed

RMC No. 7-2021 announced the availability of the updated Alphalist Data Entry and Validation Module, Version 7.0. The module is available for use and may be downloaded from the BIR website. For Philippine companies, accountants, payroll teams, and tax compliance officers, this is not merely a software update. It affects the preparation and validation of alphalist files that support withholding tax returns and related annual or quarterly submissions.

The most important change is that the enhanced module now includes alphalists for BIR Form Nos. 1600-PT, 1600-VT, 1604-C, 1604-F, 1604-E, and the new BIR Form No. 1621. BIR Form No. 1621 refers to the Quarterly Remittance Return of Tax Withheld on the Amount Withdrawn from Decedent’s Deposit Account, which had been prescribed under Revenue Memorandum Circular Nos. 62-2018 and 76-2019.

RMC No. 7-2021 also states that the generation process of the annual alphalists for BIR Form Nos. 1604-E and 1604-F has been simplified under the Quarterly Alphalists of Payees. The practical effect is that taxpayers should no longer need to manually re-encode the information for those annual alphalists when using the updated process. This matters to companies with significant vendor payments, professional fees, rent, commissions, compensation-related withholding records, or final withholding tax reporting obligations, because re-encoding increases the risk of mismatch, typographical errors, and failed validation.

Who is affected by RMC No. 7-2021

The taxpayers most affected are withholding agents that prepare and submit alphalist files in connection with BIR Form Nos. 1600-VT, 1600-PT, 1601-FQ, 1601-EQ, 1621, 1604-C, 1604-E, and 1604-F. This includes corporations, partnerships, employers, professional service payors, businesses with suppliers and contractors subject to withholding taxes, and entities required to remit withholding tax on specific transactions covered by the enumerated forms.

Large corporations and groups with accounting systems that generate BIR alphalist files through an internal extract program should pay particular attention. RMC No. 7-2021 expressly states that all concerned taxpayers using their own extract program shall strictly observe the revised file structures and the standard file naming convention prescribed under the annexes to the issuance. This means that businesses cannot treat the module update as relevant only to those manually encoding alphalist data. Even if the company’s enterprise resource planning system, payroll system, accounting software, or in-house tax tool generates the alphalist file automatically, the output must conform to the revised format.

SMEs are also affected if they act as withholding agents. For example, an SME with employees, independent contractors, leased premises, suppliers subject to expanded withholding tax, or transactions subject to final withholding tax should confirm whether its tax preparer, outsourced accountant, or payroll vendor is using the updated Alphalist Data Entry and Validation Module Version 7.0.

Key compliance requirements and covered BIR forms

RMC No. 7-2021 identifies the revised file structures for three categories of alphalists. First, it covers the Monthly Alphalist of Payees under BIR Form Nos. 1600-VT and 1600-PT. Second, it covers the Quarterly Alphalist of Payees under BIR Form Nos. 1601-FQ, 1601-EQ, and 1621. Third, it covers the Annual Alphalist of Payees under BIR Form Nos. 1604-C, 1604-E, and 1604-F.

Businesses should treat these form numbers as the key compliance map for RMC No. 7-2021. If the company files any of these returns, or if its accountant generates alphalist attachments for any of these returns, the company should verify that the data file is generated using the revised file structures and naming convention. The issuance specifically refers to updated file structures, a revised standard file naming convention, and revised job aids contained in Annexes A, B, and C.

The BIR also specifically highlights the simplification for the annual alphalists under BIR Form Nos. 1604-E and 1604-F. For tax teams, this should be reviewed together with the company’s quarterly alphalist process. If the quarterly data is inaccurate, incomplete, or inconsistent, the simplified annual generation process may simply carry forward those errors. The compliance focus should therefore be on clean payee records, correct tax identification numbers, proper classification of payees and income payments, and consistency between returns, alphalists, books, and withholding tax remittances.

Effective date and immediate action required

RMC No. 7-2021 is dated December 28, 2020. It announced that Alphalist Data Entry and Validation Module Version 7.0 is now available for use. The issuance does not state a separate future transition deadline. For compliance purposes, taxpayers covered by the enumerated forms should act on the basis that the revised module, file structures, standard naming convention, and job aids are already applicable once they prepare the affected alphalist files.

The immediate action item is straightforward: download and use the updated module, review the revised file structure applicable to the company’s returns, and ensure that any internally generated extract file follows the prescribed naming convention and format. Companies that outsource tax filing should require confirmation from their accountant, payroll provider, or tax compliance vendor that the Version 7.0 module and the revised file structures are already being used.

Penalties and risks for non-compliance

RMC No. 7-2021 does not create a new specific penalty rate, surcharge, interest charge, or compromise penalty for failure to use Version 7.0. However, the circular uses mandatory language for taxpayers using their own extract programs: they shall strictly observe the revised file structures and standard file naming convention.

The practical risk is that a non-conforming alphalist file may not validate properly or may cause inconsistencies in the taxpayer’s withholding tax compliance records. For companies with many payees, an incorrect file structure can affect the reliability of alphalist submissions connected with BIR Form Nos. 1600-VT, 1600-PT, 1601-FQ, 1601-EQ, 1621, 1604-C, 1604-E, and 1604-F. Even without a new penalty provision in the issuance, defective or inconsistent withholding tax reporting can expose a business to BIR queries, reconciliation issues, and potential assessment risks under existing tax rules.

Practical steps for CFOs, accountants, and tax teams

First, identify whether the business files any of the affected returns: BIR Form Nos. 1600-VT, 1600-PT, 1601-FQ, 1601-EQ, 1621, 1604-C, 1604-E, or 1604-F. Second, confirm that the company is using Alphalist Data Entry and Validation Module Version 7.0. Third, compare any internally generated alphalist extract against the revised file structures and standard file naming convention. Fourth, check whether annual alphalists for 1604-E and 1604-F are being generated through the simplified process under the Quarterly Alphalists of Payees rather than by manual re-encoding.

Companies should also preserve documentation showing how the alphalist files were generated and validated. This is particularly important for businesses with high-volume withholding tax transactions, multiple branches, shared service accounting functions, or outsourced payroll and tax filing arrangements. Search terms that tax teams are likely to use for this issue include RMC No. 7-2021 alphalist module, Alphalist Data Entry and Validation Module Version 7.0, BIR alphalist file structure, BIR standard file naming convention, and 1604-E 1604-F alphalist generation.

How Ablola, Saribong & Gueco can help

RMC No. 7-2021 is a reminder that BIR compliance is increasingly data-driven. A company may have paid the correct withholding tax but still face compliance problems if its alphalist data, file structure, naming convention, and validation process do not match BIR requirements. For businesses with recurring withholding tax obligations, the safer approach is to review both the legal tax position and the technical filing workflow.

Ablola, Saribong & Gueco assists corporations, SMEs, withholding agents, accounting teams, and in-house counsel in reviewing BIR compliance systems, withholding tax documentation, alphalist preparation issues, and tax audit readiness. For assistance with RMC No. 7-2021, BIR alphalist compliance, withholding tax reporting, or related tax advisory work, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

Your email address will not be published. Required fields are marked *