RMO No. 39-2022 updates BIR Service Desk rules, requesters, escalation channels, closure deadlines, and taxpayer system issue handling.
BIR offices, internal users, and external taxpayers dealing with system-related concerns must now route incident reports, service requests, and problem reports through the updated BIR Service Desk System framework under RMO No. 39-2022. The most immediate compliance consequence is procedural: concerns involving BIR applications, eServices, system access, connectivity, hardware, and other technical issues must be logged, tracked, escalated, resolved, and closed under the revised Service Desk process, rather than handled informally or under the older Centerpoint workflow.
What RMO No. 39-2022 Changed
RMO No. 39-2022 amended RMO No. 4-2018 on the BIR Service Desk System. The prior Service Desk System, identified as Centerpoint, had reached its optimum functionality and was already lagging in system performance and software updates. To address the need for a more reliable system for automated processes, the BIR adopted a new BIR Service Desk System intended to serve as the central repository of all logged issues and requests.
The updated system covers the creation, monitoring, maintenance, escalation, resolution, and closure of incident reports, service requests, and problem reports raised by end-users. It is designed to accommodate multiple users from BIR offices simultaneously and to apply turn-around-time handling for every workflow process so that issues and requests are channeled to the proper support group and addressed as soon as possible.
For taxpayers and businesses, the practical importance is that BIR system problems affecting eFPS, eBIRForms, eAFS, eCAR, ORUS, eONETT, eServices, tax clearance systems, electronic invoicing, tax remittance, or other BIR platforms are now processed through a more formal escalation system. This matters because delays in system support can affect filing, payment, registration, tax clearance, eCAR processing, and other time-sensitive compliance activities.
Who Is Affected by RMO No. 39-2022
RMO No. 39-2022 is addressed to all internal revenue officials, employees, and others concerned. Its main operational users are BIR Requesters, BIR employees who encounter issues, the Service Desk Group, Problem Resolution Groups, systems administrators, database administrators, security analysts, and quality analysts.
However, the issuance is also relevant to external users and taxpayers because the Customer Assistance Division is authorized to use the BIR Service Desk System to log and escalate incident reports, problem reports, and service requests of external users and taxpayers to the appropriate Problem Resolution Group. In practical terms, businesses that experience difficulty with BIR online platforms should understand that their concern may be escalated through this system by the proper BIR unit.
The taxpayers most affected are businesses that heavily rely on BIR electronic platforms, including corporate taxpayers using eFPS, taxpayers submitting AFS through eAFS, taxpayers needing eCAR or eONETT processing, employers and withholding agents using electronic filing and payment systems, importers and suppliers needing tax clearances, and companies whose compliance calendars depend on timely access to BIR systems.
Key Service Desk Roles and Workflow
RMO No. 39-2022 defines the Requester as the designated employee of an office or division who logs or creates the incident report, problem report, or service request of the user in the concerned office. A User is the employee who encounters and raises the issue to the Requester.
The Service Desk Group is composed of the Service Desk Supervisor and Analyst from the designated Service Desk site. It views, monitors, updates, and tracks the reported issue until it is resolved by the Problem Resolution Group and closed by the Requester or User. The Service Desk Group also provides initial resolution and verifies or confirms the issue with the Requester or User.
The Problem Resolution Group is the designated group or office that investigates, diagnoses, resolves, and updates application, technical, or policy issues assigned by the Service Desk Group. RMO No. 39-2022 also recognizes ticket functions such as Revert, Grab, Forward to Next Group, Transfer to Other Group, Resolve, Reprocess, Close Issue or Request, Cancel, and Merge Issue or Request.
Required Number of Requesters per BIR Office
The issuance revises the number of authorized Requesters per office or division. All National Office offices, excluding the Large Taxpayers Service, must have 1 Requester per office. Revenue Regions must have 2 Requesters per Regional Office. All divisions under a Revenue Region must have 2 Requesters per division. Revenue District Offices must have at least 3 Requesters per RDO.
For the Large Taxpayers Service, the required number is 2 Requesters for LTS. All divisions under LTS must have 2 to 4 Requesters per division. LTD-Davao must have 2 to 4 Requesters per LTD-Division, and LTD-Cebu must have 2 to 4 Requesters per LTD-Cebu.
This is a significant administrative change because it prevents bottlenecks at the office level. By assigning a required number of Requesters, the BIR intends to ensure that system issues and taxpayer-related concerns are not delayed simply because only one person can create, monitor, or close a ticket.
System Access and Required Browser
The BIR Service Desk System is accessible through the BIR intranet using the URL https://birservicedesk.bir.gov.ph:1800/
. The prescribed browsers are Google Chrome, Microsoft Edge, or Mozilla Firefox. RMO No. 39-2022 states that all incident reports, problem reports, and service requests of every office must be created electronically through the BIR Service Desk System by the officially designated Requester of the concerned office.
For search purposes, accountants and CFOs may encounter this issuance when looking for terms such as BIR Service Desk System, BIR system issue escalation, eFPS service request, BIR eCAR system problem, ORUS issue reporting, BIR eAFS technical support, and RMO No. 39-2022 Service Desk.
What Happens When the System Is Inaccessible
RMO No. 39-2022 provides a contingency procedure when the BIR Service Desk System is inaccessible or when the connectivity of the Regional or Revenue Office is down. In that case, the Requester must report the incident, problem, or service request to the Service Desk Group through phone, text, chat or messaging application, or in person, using the BIR Service Desk Request Form in hard or soft copy.
The issuance identifies Annex A1 for IT Support and Annex A2 for Application or Systems Support. Necessary attachments may include Data Correction Forms, screenshots of error messages, Certificate of ISAB, signed AUP form, and other relevant documents.
The Service Desk Group must then forward the reported issue or request, together with the necessary attachments, to the appropriate Problem Resolution Group through email. Each Service Desk site must maintain a manual logging and numbering system to track reported incidents, problems, and requests. Once the system becomes available, the Requesters must electronically log the manually reported issues based on the manually logged issues emailed by the Service Desk Group.
Service Desk Sites, Jurisdiction, and Contact Channels
RMO No. 39-2022 assigns Service Desk sites by area of jurisdiction. The Service Desk National Office covers all National Office offices excluding LTS, with hdeskno@bir.gov.ph
as the email address. The Service Desk National Office Data Center covers all offices under LTS, including LTD-Davao and LTD-Cebu, and all offices and RDOs under Revenue Regions 8A and 8B, with hdesknodc@bir.gov.ph
as the email address.
Service Desk Revenue Data Center Luzon 1 covers all offices and RDOs under Revenue Regions 1 to 4, using hdeskluzon1@bir.gov.ph
. Service Desk RDC Luzon 2 covers all offices and RDOs under Revenue Regions 5, 6, 7A, 7B, 9A, 9B, and 10, using hdeskluzon2@bir.gov.ph
. Service Desk RDC Visayas covers all offices and RDOs under Revenue Regions 11 to 14, using hdeskcebu@bir.gov.ph
. Service Desk RDC Mindanao covers all offices and RDOs under Revenue Regions 15 to 19, using hdeskmindanao@bir.gov.ph
.
For external users and taxpayers, the Customer Assistance Division is listed with contact_us@bir.gov.ph
and telephone number 8538-3200. Businesses experiencing system-related concerns should document the issue, preserve screenshots, and communicate through the appropriate BIR contact channel when their compliance deadline may be affected.
Deadlines and Closure Rules
RMO No. 39-2022 takes effect immediately. The issuance itself is dated July 6, 2022.
A key operational deadline is the closure rule for resolved issues. All resolved incident reports, problem reports, and service requests must be closed by the Service Desk Group or Requester upon confirmation with the User within 1 month from the Resolved date. If no confirmation is received after 1 month, the resolved incident report, problem report, or service request is automatically tagged Closed in the Service Desk System. For ISO Certified BIR Offices, the resolved incident report or service request must be closed according to the applicable quality plan.
Another time-sensitive rule applies to incomplete or erroneous tickets. The Service Desk Analyst or Supervisor, or CAD Agent or Supervisor, may cancel an incident report, problem report, or service request when it was erroneously created, when a duplicate record has already been logged, or when details are incomplete and the Requester does not provide an update after 2 working days.
Information and Attachment Requirements
When creating a ticket, the Requester must fill in all required fields in the system. These include the request type, priority, customer or user details, title, issue or request type, source, issue or request description, attachments when necessary, and other details for specific categories. Priority levels include Blocker, High, Medium, and Low.
The system automatically generates a unique reference number as the identifier of the logged issue. The code IR is used for Incident Report, SR for Service Request, and PR for Problem Report. Attachments supporting resolution are allowed, but the maximum file size is 4 MB per file.
The issuance also specifies additional information for certain categories. For Technical Hardware and Software, the requester must enter details such as BIR Property Number, Equipment Model, and Serial Number. For Internal Revenue Integrated System or IRIS issues, the requester must enter details such as Failure Mode, Nature of Incident, and Transaction Type.
Application and Systems Covered by the Forms
The Application or Systems Support form covers many systems that are important to businesses and taxpayers. These include eBIRForms, eFPS, Electronic Invoicing System, eServices, eAFS AFS eSubmission, eAppointment, eAccreditation and Registration System, eSales, eCAR, eDST, eLAMS, eORB, ePay, eREG, HRIS, IRIS, Integrated Tax System, ONETT Tracking System, TIN Verifier Mobile Application, BIR Service Desk System, electronic tax remittance advice, electronic tax software provider certification, tax clearance for bidding purpose and tax compliance verification certificate system, tax rulings and case management system, eSubmission or Alphalist or SLSP validation or confirmation report, Form 40 uploading, ORUS, and eONETT System.
The practical point is simple: if a BIR online system issue can affect filing, payment, registration, tax clearance, transfer tax documentation, eCAR processing, or reporting, taxpayers should keep complete proof of the issue and the communication trail. RMO No. 39-2022 formalizes how such concerns are received, categorized, escalated, and closed.
Penalties for Non-Compliance
RMO No. 39-2022 does not provide a specific monetary penalty, surcharge, interest rate, or compromise penalty for failure to use the Service Desk System. It is primarily an internal administrative and workflow issuance.
However, businesses should not treat system reporting as a mere technicality. A taxpayer that fails to document a system outage, filing issue, payment problem, or access concern may have difficulty explaining a late filing, failed submission, missed deadline, or unresolved BIR application issue. The safer approach is to preserve screenshots, reference numbers, emails, dates, times, and the names or offices contacted, especially when the system concern affects a statutory tax deadline.
Practical Steps for Businesses, CFOs, and Tax Teams
Companies should maintain an internal protocol for BIR system disruptions. When an issue arises, the accounting or tax team should immediately record the date and time, affected BIR system, transaction attempted, error message, taxpayer identification details, tax period, return type or application involved, and screenshots. The team should then contact the appropriate BIR office, Customer Assistance Division, or other available channel and request a reference number or confirmation where available.
For businesses dealing with recurring eFPS, eBIRForms, eAFS, eCAR, ORUS, eONETT, or tax clearance issues, the tax team should maintain a file of all service requests and responses. This can become important in audits, penalty abatement requests, deadline disputes, and internal reporting to management. CFOs should also ensure that tax compliance calendars build in enough lead time for electronic filing and payment, because Service Desk escalation does not automatically suspend tax deadlines unless a separate BIR issuance or lawful relief applies.
For in-house counsel and tax managers, RMO No. 39-2022 is also a reminder that tax compliance is increasingly technology-dependent. System access, user credentials, browser compatibility, attachments, and formal documentation can determine whether a tax team can prove diligence when a compliance problem occurs.
How Ablola, Saribong & Gueco Can Help
Ablola, Saribong & Gueco assists corporations, SMEs, accountants, CFOs, and in-house legal teams in managing BIR compliance, tax assessments, administrative submissions, and documentation of system-related tax filing or payment issues. When a BIR platform problem affects a deadline, tax clearance, eCAR, registration, filing, or payment obligation, businesses need more than screenshots; they need a defensible record that shows timely action and good-faith compliance.
For guidance on BIR compliance procedures, tax controversy risk, electronic filing issues, and documentation strategies under RMO No. 39-2022 and related issuances, consult Ablola, Saribong & Gueco through MakatiLawFirm.com.