RMO No. 36-2022 sets the process for donating ICT systems to the BIR, including LOI, proposal, privacy review, testing, donation, and approval rules.
Businesses, technology providers, software developers, and systems integrators that intend to donate ICT systems or software solutions to the Bureau of Internal Revenue must now follow a formal acceptance process before any development work or engagement begins. RMO No. 36-2022 requires a signed Letter of Intent, a detailed technical proposal, prior endorsement by the concerned BIR offices, legal documentation, privacy assessment, acceptance testing, migration procedures, and a Deed of Donation before the system may be accepted and recorded by the BIR.
What RMO No. 36-2022 Changed
RMO No. 36-2022 prescribes the guidelines and procedures for the acceptance of Information and Communications Technology systems or solutions donated by a third party developer or provider to the BIR. The issuance applies to donated application systems, software, ICT solutions, and related components that are turned over to the BIR through a Memorandum of Agreement, Memorandum of Understanding, and Deed of Donation.
The key change is that a donation of an ICT system to the BIR is not treated as a simple voluntary turnover. It must undergo a structured review process involving the concerned Process Owner, the Information Systems Group Project Manager, the Legal Service, Administrative Service, Property Division, Accounting Division, and, where applicable, the Office of the Commissioner. The system must satisfy functional, technical, data privacy, security, interoperability, documentation, acceptance testing, migration, and property-recording requirements.
For private developers, the practical consequence is clear: no engagement should begin based only on a verbal understanding, informal request, or goodwill proposal. The third party developer must tender a signed Letter of Intent addressed to the Commissioner of Internal Revenue, through the Deputy Commissioner of the concerned Process Owner, signifying the intention to develop a system at no cost to the BIR.
Who Is Affected
RMO No. 36-2022 primarily affects third party developers, software companies, IT service providers, consultants, systems integrators, and entities proposing to donate tax-related or administrative ICT systems to the BIR. It is also relevant to corporations, industry associations, development partners, and public-private initiatives that may offer digital tools, platforms, or application systems intended for BIR use.
The issuance also matters to taxpayers and businesses indirectly. Where private sector-developed systems are intended to support BIR operations, tax administration, taxpayer services, reporting, or internal processing, the system cannot be implemented unless it passes the BIR’s required procedures. CFOs, tax managers, and corporate compliance teams searching for terms such as BIR ICT donation rules, donated application system BIR, RMO 36-2022 software donation, BIR third party developer requirements, or BIR Deed of Donation ICT system should understand that this issuance governs the official route for such donations.
Required Letter of Intent and Technical Proposal
The process begins with the submission of a signed Letter of Intent and a technical proposal. The technical proposal must include a brief introduction, purpose or objective, functional scope, technical diagram, technical specifications and requirements, and a work plan containing key activities and timelines.
The technical specifications must cover relevant hardware, software, security components, and other technical requirements. This is important because the BIR will not accept an ICT system based only on business usefulness. The proposal must also be reviewed for technical feasibility, compatibility with BIR operations, data privacy, security, and interoperability, if necessary.
The Letter of Intent and technical proposal are assigned to the concerned Process Owner by the Deputy Commissioner of the Process Owner. The Process Owner then coordinates with the Information Systems Group Project Manager to evaluate whether the proposal meets the BIR’s functional and technical requirements.
Documents Required Before the Engagement Starts
Before the third party developer starts work or engagement, the developer must submit a draft Memorandum of Agreement or Memorandum of Understanding, a signed Non-Disclosure Agreement, and a signed Acceptable Use Policy. The MOA or MOU must state that the application system or solution and its components will be donated to the BIR.
This requirement is significant for IT contractors and donors because it separates a true donation from an outsourced development arrangement. The BIR must be able to confirm that ownership of the system and its relevant components will be turned over to the government, and that confidentiality, acceptable use, privacy, security, and documentation obligations are in place before work begins.
One-Year Development Limit and Change Request Requirement
RMO No. 36-2022 provides that the application system development duration or engagement must not exceed one year. Failure to deliver on the agreed target date is a ground to terminate or suspend the MOA or MOU.
The issuance also requires progress reporting. The Information Systems Group Project Manager must submit progress reports to the Assistant Commissioner and Deputy Commissioner concerned. Any change to the approved scope or timelines must be discussed and documented through a Change Request. This means developers should maintain a disciplined project management record, because delays, scope changes, and technical changes must be formally documented.
Privacy Impact Assessment, Walkthrough, Testing, and Migration
Data privacy is built into the process. The BIR Data Privacy Committee’s Privacy Impact Assessment Team must conduct a Privacy Impact Assessment at the start of the project using the prescribed template. This ensures that privacy protection is considered throughout the development lifecycle of the system or program.
Before acceptance testing, a system walkthrough must be conducted. A briefing or demonstration of the new application system must also be completed before implementation. The developed application system or solution must then undergo acceptance testing under the procedures in RMO No. 24-2003, which covers testing and acceptance of in-house developed and outsourced application systems.
Migration of the new application system or solution must follow ISG Memorandum Order No. 2-2016 on processing and implementation of migration requests. The third party developer must also perform migration and deployment activities in coordination with the Information Systems Group Project Manager and must ensure that key personnel are available after deployment to production to fix or troubleshoot issues.
Donation, Ownership, and Accounting Requirements
Because the system is a donation, the developer must submit system and technical documentation, including source code, configuration, and other relevant documentation. These final project documents become the property of the BIR. The Process Owner and Information Systems Group Project Manager must ensure that final copies are turned over to the BIR.
A separate Deed of Donation must be submitted for the developed application system or solution following the procedures under RMO No. 15-2020. The Process Owner must forward the Deed of Donation and its attachments for review and recommendation. The Legal Service reviews the MOA or MOU and the Deed of Donation. If the terms are legally proper and in order, it recommends approval and acceptance.
The approval level depends on the value of the donated IT-related system or solution. For cost value of ₱12 million and below, the Deputy Commissioner for the Information Systems Group signs and approves the Deed of Donation. For cost value above ₱12 million, the Commissioner of Internal Revenue signs and approves the Deed of Donation. If the value is above ₱12 million, the Deputy Commissioner for the Information Systems Group affixes initials.
The Property Division must receive the original copy of the certificate or proof of ownership, the authenticated copy of the duly notarized Deed of Donation, and the authenticated copy of the Delivery Receipt or List of Deliverables. The Accounting Division must receive the authenticated copy of the duly notarized Deed of Donation and record the cost of the donated assets or application system. The cost to be capitalized is the fair value or declared value stated in the Deed of Donation or other relevant donor-submitted documents, including directly attributable costs.
Penalties and Consequences for Non-Compliance
RMO No. 36-2022 does not prescribe a monetary penalty against a third party developer for non-compliance. However, it provides operational consequences. The most direct consequence is that failure to deliver on the agreed target date is a ground to terminate or suspend the MOA or MOU. In addition, without the required Letter of Intent, technical proposal, NDA, Acceptable Use Policy, MOA or MOU, Privacy Impact Assessment, acceptance testing, migration compliance, documentation turnover, Deed of Donation, and property-accounting requirements, the BIR has no basis to formally accept and record the donated ICT system.
Practical Steps for Developers and Donors
Any company proposing an ICT donation to the BIR should prepare the transaction as a regulated government-facing technology project, not merely as a corporate social responsibility initiative. The developer should first prepare a signed Letter of Intent addressed to the Commissioner of Internal Revenue through the proper Deputy Commissioner. It should then prepare a technical proposal containing the required introduction, objectives, functional scope, diagram, technical specifications, security components, and work plan.
Before any work begins, the developer should be ready to sign the NDA and Acceptable Use Policy, agree on the MOA or MOU, document the donation undertaking, and coordinate closely with the Process Owner and Information Systems Group Project Manager. The project calendar must observe the one-year development limit and should include allowance for privacy assessment, walkthrough, user acceptance testing, migration, documentation turnover, Deed of Donation processing, notarization, property recording, and accounting recognition.
Developers should also prepare complete technical documentation from the start. Source code, configurations, technical records, delivery receipts, list of deliverables, and certificate or proof of ownership are not afterthoughts. Under RMO No. 36-2022, they are part of the BIR’s acceptance and property-recording process.
Effective Date
RMO No. 36-2022 is dated July 29, 2022 and takes effect immediately. It supersedes all issuances or portions of issuances inconsistent with it. For any ongoing or proposed ICT donation to the BIR, the safest approach is to align the documentation, approvals, testing, donation, and turnover process with RMO No. 36-2022 before implementation.
How Ablola, Saribong & Gueco Can Help
Ablola, Saribong & Gueco advises businesses, software providers, regulated entities, and corporate donors on BIR compliance, technology contracts, government-facing documentation, data privacy, donation instruments, and tax administration issues. For companies planning to donate ICT systems, enter into MOAs or MOUs with government agencies, or structure technology projects involving the BIR, early legal review can prevent rejected proposals, ownership disputes, privacy gaps, and documentation defects.
For assistance with BIR compliance, ICT donation documentation, tax technology projects, or corporate legal review, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.