RMO No. 35-2022 standardizes BIR system downtime, restoration, and update advisories, helping taxpayers document outages affecting compliance.

Businesses that rely on BIR electronic systems should immediately treat official system advisories as compliance-critical records. RMO No. 35-2022 standardizes how the BIR announces system maintenance, system unavailability, slow or intermittent connection, restoration of service, and application software updates. For taxpayers, accountants, CFOs, and in-house counsel, the practical value is clear: when a BIR portal, application, or ICT service is unavailable, the advisory reference number, advisory code, and restoration notice may become important evidence for internal tax files, deadline monitoring, and explanations for delayed electronic transactions.

What RMO No. 35-2022 Changed

RMO No. 35-2022 prescribes standard templates for BIR system advisory and notification issuances. The standardization covers three main situations: systems, applications, and ICT infrastructure unavailability, whether planned or unplanned; restoration or availability of those systems, applications, and ICT infrastructure; and new application software features or upgrades.

The Order defines downtime as the period when an ICT infrastructure, application system, or service is unavailable, offline, or not operational. Planned downtime refers to restricted accessibility caused by upgrades, maintenance, migration, or configuration changes. Unplanned downtime refers to unexpected shutdowns or failures caused by technical problems, system-wide failures, power outages, or similar circumstances. System or infrastructure availability refers to restoration to normal state or condition after maintenance, fixes, or recovery from downtime.

The most important change is the creation of a uniform advisory system. Instead of inconsistent announcements, RMO No. 35-2022 requires official notices using prescribed templates, advisory codes, reference-number formats, approval procedures, and routing rules. This matters to taxpayers because BIR electronic services are often used for filing, payment, registration, certificates, tax clearance, and other time-sensitive compliance steps.

Who Is Affected by the New Advisory System

The Order is addressed to all revenue officials, employees, and other concerned persons, but its practical effect extends to external stakeholders who depend on BIR systems. Taxpayers using electronic BIR services, corporate accountants, tax managers, bookkeepers, withholding agents, and professionals handling online BIR transactions should pay attention to these advisories because they may explain why a system could not be accessed or why an electronic transaction could not be completed at a particular time.

Large corporations and regulated businesses with tax calendars should incorporate BIR system unavailability advisories into their compliance documentation. SMEs should also monitor these notices, especially when relying on online platforms for registration, return filing, payment confirmation, or other transactions near a deadline. Tax practitioners searching for BIR system downtime advisory, BIR system maintenance notification, BIR eServices unavailable, BIR portal restoration advisory, or RMO 35-2022 advisory codes should understand the codes and reference-number rules introduced by the Order.

Standard Templates and Advisory Codes

RMO No. 35-2022 prescribes templates and advisory codes for specific activities. Template No. 1 covers system maintenance or unavailability, whether planned or unplanned, with advisory code SU. For Revenue Data Center-specific downtime, the code is SUR. Template No. 2 covers slow or intermittent connection, with advisory code SIC. Template No. 3 covers system, application, or infrastructure availability, with advisory code SA. Template No. 4 covers application software updates or upgrades, including examples such as MS Teams, Zoom, and Chrome, with advisory code AU.

For uniformity, the Order recommends the use of Times New Roman font and font size 12. Although this formatting rule is internal to the BIR, the more important business takeaway is that advisory codes now identify the nature of the system event. A taxpayer reviewing a notice should be able to determine whether the problem involved unavailability, slow connection, restoration, or an application update.

When Advisories Must Be Issued

RMO No. 35-2022 requires an advisory or notification when reported downtime or outage cannot be resolved within the expected resolution time after it was reported, and also upon restoration of the system or service. The Order gives a specific benchmark: urgent or critical network-related issues have a resolution time of within 4 hours, or otherwise as indicated in the Service Level Agreement with managed service providers or contractors.

This 4-hour reference is significant for companies monitoring whether BIR system problems may affect tax compliance timing. It does not automatically extend deadlines, and taxpayers should not assume that a downtime advisory alone excuses late compliance. However, it gives taxpayers a more structured way to document when an outage occurred, when it was acknowledged, and when the system became available again.

Responsible Offices and Approval Flow

The responsible office depends on the type of activity. Application-related activities are handled by the concerned Project Proponent. Hardware-related activities are handled by the Data Warehousing and Systems Operations Division, or DWSOD. Network-related activities are handled by the Network Management and Technical Support Division, or NMTSD. Security-related activities are handled by the Security Management Division, or SMD.

In coordination with the Process Owner, the advisory or notification must be prepared in two copies. Only the duplicate copy is initialed and signed by the concerned officials. The original copy, without initials or signatures, is the version posted or emailed to authorized users once the duplicate copy has been signed and approved. Before posting or emailing the advisory to affected users, the NMTSD or RDC Service Desk Analyst must validate the original copy against the signed duplicate to confirm that the copies are one and the same. The signed duplicate must be filed for future reference.

Reference Number Rules Tax Teams Should Track

RMO No. 35-2022 requires the NMTSD or RDC Service Desk Analyst to assign a unique reference number to all advisories or notifications, whether for internal or external stakeholders. The standard format is yyyymm-xxxx-Advisory Code. The yyyymm portion represents the year and month the advisory was prepared. The xxxx portion is the number series, such as 0001, 0002, 0003, and so on. The advisory code is SU, SUR, SIC, SA, or AU. The number series resets to 0001 at the beginning of each year.

For localized advisories, the RDC name is indicated before the number series using a format such as mmddyyyy-RDC Name-0001-Advisory Code. The naming conventions include NODC for National Office Data Center, RDCL1 for RDC Luzon 1, RDCL2 for RDC Luzon 2, RDCVis for RDC Visayas, and RDCMin for RDC Mindanao.

The restoration advisory must generally use the same reference number as the unavailability advisory, with the advisory code changed to SA. For example, an ITS unavailability advisory with reference number 202207-00010-SU would use 202207-00010-SA once ITS becomes available. If a slow or intermittent connection advisory was issued as 202207-00020-SIC, the corresponding availability advisory would use 202207-00020-SA once the connection becomes stable.

Where one advisory covers multiple application systems that are not restored at the same time, the succeeding restored application systems use series numbers after the SA code, such as SA1 and SA2. The Order gives the example of eCAR, eReg, and eLAMS covered by one unavailability advisory. If only eCAR and eReg are restored first, the availability advisory may use SA1. When eLAMS is restored later, the next availability advisory may use SA2.

Localized Advisories and Monthly Downtime Reporting

Localized advisories for system unavailability or availability must be issued and approved by the concerned Revenue Data Center Head. These advisories must be emailed to the concerned Revenue Region or Revenue District Office generic official email account, with copies furnished to the concerned Assistant Regional Director, concerned Assistant Revenue District Officer or Officers, NMTSD, and SMD.

RMO No. 35-2022 also requires monitoring and reporting. The NMTSD or RDC Service Desk Analyst must monitor all advisories on system unavailability and remind the Process Owner or Proponent to prepare and release the availability advisory once the system or service is restored. The same Service Desk Analyst must devise an automated report, using Template 5, containing details on the frequency of system downtime, duration, date, and site. This report must be submitted to the Office of the Deputy Commissioner-ISG, copy furnished to the ISG Assistant Commissioners, every 5th working day of the following month.

Penalties and Compliance Consequences

RMO No. 35-2022 does not prescribe a specific taxpayer penalty for failing to monitor BIR system advisories. It also does not state that system downtime automatically waives penalties for late filing, late payment, or delayed submission. Taxpayers should therefore remain conservative: continue attempting timely compliance, take screenshots or records of failed access where appropriate, save the relevant BIR advisory, and match it with the corresponding restoration notice.

The compliance consequence is evidentiary and operational. A taxpayer that keeps accurate records of system unavailability, reference numbers, and restoration times will be better positioned to explain delays or support requests for consideration when a BIR system issue affected a required transaction. Conversely, a business that ignores official advisories may lose a useful contemporaneous record of system conditions affecting its compliance work.

Practical Steps for Businesses, CFOs, and Tax Teams

Tax teams should maintain an internal tracker for BIR system advisories affecting their compliance calendar. The tracker should record the date of advisory, reference number, advisory code, affected system, start of unavailability where stated, restoration advisory, and internal transactions affected. For deadline-sensitive filings or payments, the tracker should also show who attempted the transaction, what time the attempt was made, and what alternative steps were taken.

Companies should train accounting personnel to distinguish among SU, SUR, SIC, SA, and AU advisories. An SU or SUR advisory indicates unavailability. An SIC advisory indicates slow or intermittent connection. An SA advisory indicates restoration or availability. An AU advisory indicates application software updates or upgrades. This classification can help determine whether a tax compliance issue was caused by outage, unstable connectivity, restoration timing, or software change.

Businesses should also preserve both the initial downtime advisory and the corresponding availability advisory. The availability advisory is especially important because RMO No. 35-2022 ties the restoration notice to the same reference number, changing only the advisory code to SA, or SA1 and SA2 when multiple systems are restored at different times.

How ASG Law Can Help

Ablola, Saribong & Gueco advises businesses, CFOs, accounting departments, and in-house counsel on BIR compliance, tax documentation, audit readiness, and practical responses to system-related filing or payment issues. RMO No. 35-2022 is an internal BIR operations issuance, but it has real-world value for taxpayers who need reliable records when electronic tax compliance is affected by system downtime, slow connection, restoration timing, or platform updates.

For assistance in building a defensible BIR compliance file, responding to tax notices, documenting electronic filing issues, or preparing audit-ready explanations for delayed transactions, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

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