RMO No. 31-2025 sets immediate BIR rules for ICT proof-of-concept projects, including approvals, one-month POC limits, security checks, and termination risks.

ICT vendors, service providers, and BIR functional groups must now follow a controlled approval, documentation, security, and evaluation process before any technology proof-of-concept may be conducted for BIR-related products, solutions, or services. RMO No. 31-2025 matters immediately because a proposed ICT solution can no longer proceed on informal demonstrations alone: the POC must be approved, documented, security-reviewed, monitored weekly, completed within the prescribed period, and discontinued if it disrupts BIR ICT operations.

What RMO No. 31-2025 Changes

RMO No. 31-2025 prescribes the official guidelines and procedures for the conduct of Proof-of-Concept, or POC, activities involving Information and Communications Technology-related products, solutions, and services. It creates a structured process for evaluating whether a proposed ICT idea, technology, or solution can deliver its intended outcome before it is considered for possible government procurement, adoption, or implementation.

The most important change is that POC engagements must now be subject to defined controls, approvals, documentation, and monitoring. The Order expressly aims to establish adequate controls for the proper monitoring of all POC engagements and to ensure the submission and completeness of all required POC documentation before, during, and after the engagement.

For businesses that supply software, cybersecurity tools, digital tax platforms, data systems, cloud-based tools, network infrastructure, artificial intelligence tools, automation solutions, or other ICT products to government agencies, this means that technical demonstrations with the BIR must be treated as regulated engagements. The POC is not merely a sales presentation. It is an evaluated process involving functional review, technical review, vulnerability assessment, network infrastructure assessment, data protection documentation, and formal sign-offs.

Who Is Affected by RMO No. 31-2025

The Order directly applies to all revenue officials, employees, and others concerned within the BIR. Operationally, however, it is also highly relevant to ICT vendors and service providers that intend to offer, demonstrate, test, or validate ICT-related products, solutions, and services for BIR use.

RMO No. 31-2025 affects ICT vendors, service providers, software developers, system integrators, cybersecurity firms, cloud service providers, network infrastructure providers, automation providers, tax technology providers, and consultants whose proposed solutions may be subjected to a BIR proof-of-concept process.

Within the BIR, the affected actors include the Functional Manager, Technical Manager, Designated Project Manager, concerned Assistant Commissioner, concerned Deputy Commissioner, Data Protection Officer, Information Technology Planning and Standards Division, Network Management and Technical Support Division, and Security Management Division. The Order also identifies the relevant Functional Groups as including the Operations Group, Resource Management Group, Legal Group, and Large Taxpayers Service.

Key Definitions: Proof-of-Concept, ICT Vendor, and Disruptions

A Proof-of-Concept is defined as a prototype or early-stage demonstration confirming whether an idea or technology can deliver the desired outcome. This definition is important because the POC is not yet an award, procurement, or final acceptance of the proposed technology. It is an evaluation mechanism.

An ICT Vendor or Service Provider refers to a vendor that provides IT solutions and/or services to end users and organizations. A Project Manager refers to a BIR official or employee designated or assigned to ensure tracking and full completion of projects and deliverables. A Functional Manager refers to the functional owner, process owner, or project proponent who acts as overall overseer of the project and provides direction across the Bureau.

RMO No. 31-2025 also defines disruptions as unforeseen events that may hinder ICT operations or processes, including technical issues, data breaches, delays in timelines, and natural disasters. This definition is material because unresolved problems or disruptions caused by or attributed to the POC can trigger immediate termination of the POC engagement.

Approval Requirements Before a BIR ICT POC May Proceed

Functional and Technical Managers may initiate POC discussions based on determined needs or proposals and offers from ICT Vendors or Service Providers, but only upon approval of the concerned Deputy Commissioner.

For POC proposals offered by ICT Vendors or Service Providers to Functional Groups, the evaluation of POC proposals, the conduct of the POC, and the recommendation on whether to accept or reject the technical proposal must be conducted in coordination with the Information Systems Group counterpart. The purpose is to ensure that the proposal meets the relevant functional and technical requirements of the Bureau.

Once the Information Systems Group determines that a POC proposal is feasible, a Request for Proposal for the Proof-of-Concept, or RFP for POC, must be publicly announced. The RFP for POC must remain open for one month from the date of publication. Only those who successfully submit their Letter of Intent and other relevant requirements within the prescribed period will be considered for participation in the POC.

All POC activities require approval of the Deputy Commissioner of the Information Systems Group and the Deputy Commissioner of the concerned Functional Group for non-Information Systems Group initiated POC requests. This makes senior-level approval a mandatory checkpoint before the POC can proceed.

Important Deadlines and Time Limits

The most searched deadline under RMO No. 31-2025 is the one-month rule. The RFP for POC must remain open for one month from publication, giving interested ICT vendors and service providers a defined period to submit their Letter of Intent and required documents.

The second key time limit is the duration of the POC engagement itself. RMO No. 31-2025 provides that the POC duration or engagement shall not exceed one month. This means vendors should design demonstrations, technical testing, vulnerability responses, documentation, and reporting around a compressed one-month implementation window.

The third key deadline applies after completion or termination of the POC. The Designated Project Manager must prepare the POC Evaluation Summary Report for submission to the concerned Deputy Commissioner, through the concerned Assistant Commissioner, within ten working days after completion or termination of the POC.

During the conduct of the POC, the Designated Project Manager must also monitor and document the status of the POC and submit the POC Weekly Status Report every Monday. These weekly reporting obligations are important for vendors because unresolved implementation issues, security concerns, delays, and technical problems may be documented in the official evaluation record.

Required Documents and Security Controls

RMO No. 31-2025 requires several key documents and controls before and during a POC. Interested ICT vendors and service providers must submit a Letter of Intent and all relevant documents specified in the RFP for POC. The Designated Project Manager receives and reviews the Letter of Intent and POC proposal and forwards the submitted documents to the Information Technology Planning and Standards Division under the Information Systems Development and Operations Service for checking and verification as to completeness of requirements.

The POC process also requires a Non-Disclosure Agreement for POC Conduct and an Acceptable Use Policy. The Designated Project Manager must prepare and affix initials to these documents and release them to the ICT Vendor or Service Provider for signature. The Security Management Division must also affix initials on the NDA and receive a copy of the approved and signed NDA and AUP from the concerned office.

The Data Protection Officer is required to sign the NDA. The Order also requires coordination with the Security Management Division and Network Management and Technical Support Division on technical requirements, particularly vulnerability assessment and evaluation of the POC network infrastructure set-up. The Security Management Division provides assistance specifically on vulnerability assessment, while the Network Management and Technical Support Division participates in the assessment of the POC product or service against BIR requirements and assists with network infrastructure set-up.

Vendor Obligations During the POC

ICT Vendors and Service Providers must coordinate with the concerned BIR office on the conduct of the POC, POC-related meetings, and product demonstration. They must submit the Letter of Intent and POC proposal to the concerned BIR office, adjust the POC proposal as required, finalize the POC proposal, and sign the prescribed NDA and Acceptable Use Policy.

During the POC, vendors must conduct the POC based on the approved POC proposal, attend meetings coordinated by the concerned office or Project Manager, correct problems that may affect BIR ICT infrastructure, resolve issues together with the Designated Project Manager and the Information Systems Group, implement and document resolutions, and discontinue the conduct of the POC if issues are not resolved.

Vendors should note that participation in the POC does not guarantee acceptance of a bid in the actual bidding and awards process for any potential project that may result from the POC. This is an important procurement and compliance point. A successful technical demonstration may help inform evaluation, but it is not equivalent to a government contract award.

Consequences of Non-Compliance or Disruption

RMO No. 31-2025 does not impose a monetary tax penalty, surcharge, or compromise penalty on private parties. However, it provides serious operational consequences for non-compliance with POC requirements.

The most immediate consequence is termination of the POC engagement. The Order states that the conduct of the POC must not disrupt ICT operations in any way. Unresolved problems or disruptions caused by or attributed to the POC will cause the immediate termination of the POC engagement. A written notice of termination must be sent to the ICT Vendor or Service Provider and becomes effective immediately.

For ICT vendors, the practical risk is reputational, operational, and commercial. A vendor that fails to comply with documentation, security, vulnerability assessment, network infrastructure, reporting, or issue-resolution requirements may lose the opportunity to complete the POC and may receive an unfavorable evaluation. Because the POC Evaluation Summary Report is prepared after completion or termination and may be presented to the Deputy Commissioner of the Information Systems Group and the concerned Functional Group, vendors must treat the process as a formal government-facing compliance exercise.

Effective Date of RMO No. 31-2025

RMO No. 31-2025 is dated February 28, 2025 and provides that the Order takes effect immediately. Businesses and ICT vendors dealing with the BIR should therefore treat the POC rules as already in force for BIR-related technology demonstrations, pilot testing, and proposed digital solutions.

Practical Steps for ICT Vendors and BIR Technology Providers

ICT vendors should first prepare a complete POC compliance package before approaching or responding to a BIR opportunity. This should include a clear technical proposal, implementation schedule, product demonstration plan, risk controls, data protection measures, vulnerability management approach, network requirements, and proposed issue-resolution workflow.

Second, vendors should monitor the RFP for POC publication and submit the Letter of Intent and relevant requirements within the one-month publication period. Late, incomplete, or non-compliant submissions may prevent participation in the POC.

Third, vendors should design the POC around the one-month maximum duration. A BIR POC is not an open-ended pilot project. Milestones, deliverables, technical support, security testing, troubleshooting, and documentation should be ready from day one.

Fourth, vendors should be prepared for vulnerability assessment, network infrastructure assessment, NDA signing, Acceptable Use Policy compliance, and coordination with multiple BIR offices. These requirements are particularly important for solutions that touch BIR ICT infrastructure, taxpayer data, internal workflows, cybersecurity, digital tax administration, or large taxpayer systems.

Fifth, vendors should maintain a written issue log. Since weekly POC status reports are required every Monday and unresolved issues may trigger discontinuance or termination, vendors should document every issue, response, fix, and resolution. This protects both the vendor and the BIR project team during final evaluation.

Why This Matters for Businesses Dealing with BIR Digitalization

RMO No. 31-2025 signals that BIR digitalization projects, tax technology proposals, ICT modernization tools, and service provider demonstrations will be subject to more formal controls. For private businesses, this is relevant not only to technology vendors but also to companies that rely on digital tax compliance systems, electronic invoicing, taxpayer portals, reporting platforms, and BIR-facing compliance software.

As the BIR continues to modernize its systems, vendors seeking to participate in government technology opportunities must align technical capability with legal compliance, data protection, procurement discipline, and operational risk controls. A technically impressive product may still fail the process if documentation is incomplete, security risks are unresolved, or the POC disrupts BIR ICT operations.

How Ablola, Saribong & Gueco Can Help

Ablola, Saribong & Gueco advises businesses, ICT vendors, service providers, and corporate clients on BIR compliance, government-facing documentation, procurement-related risk, data privacy, cybersecurity obligations, and tax technology implementation. For vendors participating in BIR proof-of-concept activities, legal review should begin before the Letter of Intent, NDA, Acceptable Use Policy, proposal, and technical commitments are submitted.

Our team can assist in reviewing POC documentation, aligning vendor commitments with Philippine tax, procurement, data privacy, cybersecurity, and contract requirements, and preparing businesses for regulatory engagement with the BIR. For assistance with RMO No. 31-2025 compliance, BIR technology projects, or tax-related regulatory documentation, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

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