RMO No. 9-2009 sets new RDO codes and registration data transfer rules for taxpayers affected by split BIR revenue district offices.

Businesses and registered taxpayers located in affected areas must verify the correct Revenue District Office jurisdiction for their registration records because RMO No. 9-2009 directs the splitting and transfer of taxpayer registration data to newly assigned RDO codes. The immediate compliance risk is practical: tax filings, taxpayer registration updates, correspondence, and district-level BIR transactions may be routed to the wrong office if taxpayers, accountants, and corporate compliance teams continue using the old RDO code after the affected RDO split.

What RMO No. 9-2009 Changed

RMO No. 9-2009 prescribed the policies and procedures for assigning and using new Revenue District Office codes for RDOs that were split under Revenue Administrative Order Nos. 1-2008, 2-2008, 1-2009, 2-2009, and 3-2009. The issuance addressed two operational concerns: the splitting of taxpayer registration data and the limitation of the then-current Integrated Tax System, which could not provide a four-digit RDO code.

The most important change is that affected RDOs were assigned alphabetic RDO suffixes, such as 25A, 25B, 54A, 54B, 53A, 53B, 43A, and 43B, instead of entirely new four-digit numeric codes. For taxpayers, this means that their BIR registration jurisdiction may have changed even if their business address did not. For accountants and tax managers, the practical question is no longer simply whether a taxpayer is registered in Bulacan, Cavite, Pasig, Pampanga, Nueva Ecija, Zamboanga, or Davao, but which split RDO now has jurisdiction over that taxpayer.

New RDO Codes Covered by RMO No. 9-2009

RMO No. 9-2009 covers only the RDOs affected by the splitting under the cited Revenue Administrative Orders. The prior RDO Code 25 for Malolos, Bulacan was split into RDO 25A for Plaridel, Bulacan and RDO 25B for Marilao, Bulacan. RDO 54 for Trece Martirez City was split into RDO 54A for Trece Martirez City, South Cavite and RDO 54B for Rosario, North Cavite. RDO 53 for Las Piñas-Muntinlupa City was split into RDO 53A for Las Piñas City and RDO 53B for Muntinlupa City.

The issuance also provides that RDO 43 for Pasig City was split into RDO 43A for East Pasig and RDO 43B for West Pasig. RDO 17 for Tarlac, Tarlac was split into RDO 17A for Tarlac City and RDO 17B for Paniqui, Tarlac. RDO 21 for San Fernando, Pampanga was split into RDO 21A for North Pampanga and RDO 21B for South Pampanga. RDO 23 for Cabanatuan City was split into RDO 23A for North Nueva Ecija and RDO 23B for South Nueva Ecija.

For Western Mindanao, RDO 93 for Zamboanga City was split into RDO 93A for Zamboanga City and RDO 93B for Zamboanga Sibugay. RMO No. 9-2009 also notes that some municipalities or towns previously forming part of RDO 92, Pagadian City, are now under RDO 93B, Zamboanga Sibugay. RDO 92 remains identified as Pagadian City, Zamboanga del Sur. For Davao, RDO 113 for Davao City is identified as RDO 113 for West Davao City and RDO 132 for East Davao City.

Who Is Affected

The taxpayers most affected are businesses, employers, self-employed individuals, professionals, branches, and registered taxpayers located within the split jurisdictions. In practical terms, the issuance matters to taxpayers in Malolos, Plaridel, Marilao, Cavite, Las Piñas, Muntinlupa, Pasig, Tarlac, Pampanga, Nueva Ecija, Zamboanga City, Zamboanga Sibugay, Pagadian City, and Davao City whose registration data may have been moved from the old host RDO to a new RDO code.

Corporate accountants, CFOs, tax compliance officers, bookkeepers, and in-house counsel should pay special attention to this issuance because RDO jurisdiction affects registration records and district-level BIR dealings. Search phrases commonly used for this issue include RMO No. 9-2009 new RDO codes, BIR split RDO taxpayer registration, RDO 25A 25B Bulacan, RDO 53A 53B Las Piñas Muntinlupa, and RDO 43A 43B Pasig.

How Taxpayer Registration Data Will Be Split

RMO No. 9-2009 provides that the Revenue Data Center must generate the list of taxpayers clearly identifiable as belonging to the concerned RDOs. After identification, the Information Systems Group is directed to automatically transfer the registration data of those identified taxpayers to their corresponding RDOs.

For taxpayers whose correct district cannot be clearly identified, the affected RDOs have a validation duty. The RDOs must validate or identify taxpayers from the listings generated by the Revenue Data Center where the taxpayer cannot be clearly identified as belonging to either District A or District B. The same validation rule applies to the Davao City split between RDO 113 and RDO 132, and the Sibugay/Pagadian allocation between RDO 93B and RDO 92.

The issuance authorizes practical verification measures. Both RDOs may conduct actual ocular inspection, access Local Government Unit records, or employ other means to identify the correct jurisdiction. This is important because the BIR did not rely solely on existing database records where the taxpayer’s location or jurisdiction could not be cleanly mapped. For businesses, this means the correct RDO may ultimately depend on actual address verification and LGU records.

Key Deadlines and Implementation Dates

RMO No. 9-2009 states that reports on taxpayers whose proper jurisdiction requires validation must be submitted to the respective Revenue Data Centers within ten days from approval of the Order. For the new RDO, meaning the office that is not the host RDO, the report must be accompanied by a duly accomplished and approved request for data fix form. The Revenue Data Centers must then forward the reports to the Systems Maintenance and Support Division for processing of the registration data split.

The Information Systems Group, through the Systems Maintenance and Support Division, is directed to effect the splitting of registration data and transaction data starting April 1, 2009. The Order also states that it takes effect immediately. Because the issuance is dated March 13, 2009, affected taxpayers and their accountants should treat the RDO data split as an already implemented administrative change, not a prospective or optional update.

Penalties and Compliance Risks

RMO No. 9-2009 does not prescribe a new tax rate, surcharge, interest rate, compromise penalty, or standalone penalty for taxpayers. However, the absence of a specific penalty does not make the issuance unimportant. The compliance risk is administrative: using the wrong RDO code or failing to recognize the transferred registration jurisdiction can delay registration updates, taxpayer verification, correspondence, and other BIR transactions handled at the district level.

For companies with multiple branches or operations in affected areas, the larger risk is internal mismatch. A company’s accounting system, tax calendar, branch registration file, and BIR correspondence records may still reflect the prior RDO code even though the BIR’s registration and transaction data have already been split. This can create confusion when dealing with certificates of registration, transfer of registration, tax clearance concerns, open cases, and district-level filings or requests.

Practical Steps for Businesses and Accountants

First, taxpayers in the affected areas should confirm whether their registered address falls under the prior host RDO or the newly assigned split RDO code. Businesses in Bulacan should check whether they now fall under RDO 25A Plaridel or RDO 25B Marilao. Cavite taxpayers should check whether RDO 54A Trece Martirez City, South Cavite or RDO 54B Rosario, North Cavite applies. Las Piñas and Muntinlupa taxpayers should confirm whether RDO 53A or RDO 53B applies. Pasig taxpayers should confirm whether they are under East Pasig RDO 43A or West Pasig RDO 43B.

Second, corporate taxpayers should update internal tax master files, BIR registration trackers, branch registration records, and compliance checklists to reflect the correct RDO code. This is especially important for companies with branches or employees in Tarlac, Pampanga, Nueva Ecija, Zamboanga, Pagadian, and Davao, where the split may affect which district office handles registration and transaction records.

Third, tax teams should reconcile their records against actual BIR registration data before making filings, requests, or amendments that depend on RDO jurisdiction. Where the correct district is unclear, taxpayers should be prepared to support the jurisdictional location with address records, LGU documents, lease documents, permits, or other location-based records, consistent with the validation methods recognized in the Order.

Fourth, businesses undergoing registration updates, transfers, closure of branch registrations, or correction of registration information should pay attention to whether a request for data fix or coordination with the correct RDO is necessary. While the issuance directs BIR offices to handle the data split, taxpayers still benefit from confirming that their registration and transaction data are properly reflected in the correct district.

Why This Matters for BIR Compliance

RMO No. 9-2009 is an administrative issuance, but it has real consequences for tax compliance operations. A taxpayer may know its tax obligations but still encounter delays if its internal records show an old RDO code or if its accountants coordinate with the wrong district office. For CFOs, accountants, and in-house counsel, the key takeaway is to verify the taxpayer’s correct split RDO and align internal records with the BIR’s post-split registration data.

Ablola, Saribong & Gueco assists businesses, corporate taxpayers, and accounting teams with BIR registration issues, RDO transfers, tax compliance reviews, open case concerns, and district-level BIR coordination. For legal and tax support on BIR compliance, registration corrections, and taxpayer record issues, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

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