RMO No. 23-2004 sets BIR rules for archiving, purging, and restoring ITS taxpayer data, affecting old tax cases and record retrieval.

Businesses with old tax cases, pending investigations, or historical taxpayer records should understand that BIR access to archived Integrated Tax System data is governed by a formal approval and restoration process. RMO No. 23-2004 matters now because taxpayer data that has reached the minimum three-year age period may be archived or purged annually, while restoration of archived data is allowed only through an approved Data Archiving/Purging/Restoration Request Form and only for defined operational purposes, including investigations involving taxpayers with existing tax cases.

What RMO No. 23-2004 Changed

RMO No. 23-2004 prescribed the policies, guidelines, frequency, run dates, and office responsibilities for selective data restoration, data archiving, and data purging activities involving BIR ITS data. The official subject of the issuance is selective data restoration and time frame and adhoc run for data archiving and purging activities.

The central rule is that all ITS data that have reached the minimum required three-year age period shall be archived or purged annually. The Order states that the preferred timing for these annual archiving and purging activities is the year-end long vacation period. This is significant because the BIR’s operational access to older taxpayer information may depend on whether the data remains in the live environment or has already been moved into archived storage.

The Order also recognizes that tax collection operations may take priority. If planned purging or archiving activities coincide with the end-of-year collection rush schedules, the activities must be rescheduled to the next available long vacation period. In practical terms, the BIR’s year-end enforcement and collection work may delay archiving and purging, but the policy remains that aged ITS data is subject to periodic cleanup.

Who Is Affected by the Data Archiving and Restoration Rules

RMO No. 23-2004 is primarily an internal BIR systems and operations issuance. The offices directly assigned responsibilities include the Information Systems Group, SMSD-ISDS, Security Management Division, Regional Data Centers, National Office and RDC System Administrators, Database Administrators, Revenue District Offices, and Operations Group personnel.

However, the business impact is real for taxpayers involved in audits, assessments, refund verification, collection cases, compromise discussions, reconciliation of historical tax records, and other tax controversies where older BIR ITS data may be relevant. A corporation, withholding agent, accountant, or tax counsel dealing with a tax case involving historical filings or registrations should be aware that archived data may not be immediately available on demand. The restoration must follow the approval route under RMO No. 23-2004.

The issuance is particularly relevant to businesses searching for guidance on BIR archived taxpayer records, ITS data restoration, old BIR tax case records, BIR data purging rules, and RMO 23-2004 data archiving. These are not ordinary tax rates or filing deadline rules; they are procedural controls on how the BIR handles aged electronic taxpayer data.

Key Compliance Requirements and Approval Controls

An adhoc run for data archiving or purging is allowed only upon submission or satisfaction of specific conditions. The requesting office or Regional Data Center must submit a duly accomplished Data Archiving/Purging/Restoration Request Form, identified as Annex A. The form must be approved by the concerned RDC Head, the Deputy Commissioner for the Information Systems Group, and the Deputy Commissioner for the Operations Group.

The Order identifies two operational grounds for an adhoc archiving or purging run: not enough available disk space and unsuccessful annual purging. This means that adhoc purging is not treated as a casual or discretionary systems activity. It is permitted only when the required form and approval route are satisfied and when the operational condition justifies the run.

For restoration of archived data, the rule is similarly controlled. Archived data may be restored only upon submission of a duly accomplished and approved Data Archiving/Purging/Restoration Request Form. The Order specifically states that archived data may be restored to facilitate investigation of a taxpayer with an existing tax case. The request may be made by the Revenue District Office and other concerned Operations Group personnel, if necessary, and must be approved by the Deputy Commissioner for the Operations Group.

The TIN List must be executed by National Office and Regional Data Center Operators after accomplishment and submission of the request form. The request form must be submitted by the Regional Data Center to SMSD-ISDS on the third week of November. A work plan for data archiving, purging, and restoration must be prepared and presented by SMSD-ISDS to ISG managers two weeks before the start of pre-archiving or pre-purging activities.

Important Dates and Operational Timeline

RMO No. 23-2004 provides a detailed timetable for pre-archiving and pre-purging activities. TIN List generation is scheduled on the first Friday of December, or the first week of December, after submission of the required request form. Submission of the TIN List to the Revenue District Offices for verification is scheduled on the following Monday, or the second week of December, after execution of the TIN List.

The meeting of concerned ISG personnel on purging and archiving activities must occur three working days after TIN List submission, during the second week of December. Review of the TIN List to identify TINs to be included in purging is given a period of ten working days, during the third week of December, upon receipt of the TIN List from the Regional Data Center.

The preparation of the migration request for TINs to be included in purging is scheduled on Wednesday of the fourth week of December, or a day before December 25. Implementation of migration for TINs to be included in purging is scheduled on Wednesday of the fourth week of December, or immediately after receipt of the migration request from SMSD-ISDS.

Before purging jobs are executed, the environment must be checked, required objects must be identified, and script statistics must be executed. A cold backup must be successfully implemented one day before the start of execution for purging jobs. Jobs and scripts, including QA’d scripts, CRON’d scripts, and other System Administrator scripts, must be suspended immediately after cold backup. The Large Rollback Segment must then be set up immediately after suspension of jobs, and purging and archiving jobs must be executed immediately after LRBS setup.

Post-Archiving and Post-Purging Requirements

After archiving and purging activities are performed, SMSD-ISDS must immediately check the results. Script statistics must be executed after purging for comparison, and a statistics report must be prepared. Dumped files must be backed up or moved to tape immediately after the status of archiving and purging activities is checked.

Temporary objects created for the purging activity must also be cleaned up. SMSD-ISDS must prepare migration requests for dropping temporary objects after reports are created and dumped files are moved. The Database Administrator must implement the migration for dropping temporary objects immediately after receipt of the migration request from SMSD-ISDS.

Procedure for Selective Data Restoration

For restoration, the NO or RDC user-requestor must fill up the Data Archiving/Purging/Restoration Request Form and route it to the System Administrator for server identification and approval. If approved, the form is forwarded to SMSD-ISDS.

For easier data retrieval in selective data restoration, the requestor may save the data to be restored in a server where enough disk space is available and inform the System Administrator of the directory where the data may be viewed, restored, or retrieved. Alternatively, the requestor may forward the media or physical tape where the data to be restored is located, but the media or physical tape must be backed up before it is forwarded.

Once the data has been restored, the concerned user must coordinate with the System Administrator, generate the report on the specific information needed or create a flat file convertible into an Excel file, and furnish the requestor a copy of the generated report.

Penalties and Risk of Non-Compliance

RMO No. 23-2004 does not prescribe taxpayer penalties, surcharge rates, compromise penalties, or interest charges. Its enforcement consequence is procedural and operational: archiving, purging, adhoc runs, and restoration are not validly processed unless the prescribed approvals, request forms, migration steps, backups, statistics reports, and cleanup activities are completed.

For taxpayers, the practical risk is evidentiary and timing-related. A business involved in an old tax case should not assume that BIR personnel can instantly retrieve archived ITS data. Counsel and accountants should build enough lead time for requests involving older taxpayer records, especially where archived data may be needed to verify a tax case, historical account, TIN-related record, or prior systems entry.

Practical Steps for Businesses and Tax Teams

First, maintain complete internal copies of tax returns, payment confirmations, registration documents, withholding tax records, assessment correspondence, and BIR filings for periods longer than the minimum three-year ITS archiving threshold mentioned in RMO No. 23-2004. While the Order concerns BIR systems, taxpayers should not rely solely on the availability of historical BIR electronic records.

Second, when handling an audit, assessment, collection dispute, refund verification, or litigation involving old records, identify early whether historical ITS data may be necessary. If the matter involves archived BIR data, the concerned BIR office may need to initiate the approved restoration procedure.

Third, tax counsel should be precise in requests involving old BIR data. The request should identify the taxpayer, TIN, taxable period, tax type, nature of the tax case, and the specific information required. RMO No. 23-2004 emphasizes structured requests, server availability, migration status, query account access, and generated reports.

Fourth, companies should treat old tax records as litigation-critical documents. The fact that BIR systems may archive or purge data after the minimum required three-year age period makes corporate document retention, tax audit readiness, and proper accounting file management even more important.

How Ablola, Saribong & Gueco Can Help

RMO No. 23-2004 is a reminder that tax compliance is not only about filing returns and paying taxes. It is also about preserving evidence, understanding BIR internal procedures, and preparing for how historical taxpayer data may be retrieved in audits, investigations, and tax disputes.

Ablola, Saribong & Gueco assists businesses, CFOs, accounting teams, and in-house counsel in BIR compliance, tax controversy management, assessment defense, document retention planning, and coordination involving historical tax records. For assistance with BIR audits, tax investigations, archived taxpayer records, or compliance procedures under RMO No. 23-2004, visit MakatiLawFirm.com.


Leave a Comment

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