RMO No. 22-99 sets BIR procedures for accepting outsourced and in-house application systems, assigning responsibility and Acceptance Certificate roles.

BIR offices, project teams, technology vendors, and internal system developers must route outsourced and in-house developed application systems through the Bureau’s designated acceptance process before the system may be formally accepted. RMO No. 22-99 matters because it identifies the office responsible for accepting these systems and fixes accountability for the personnel who sign Acceptance Certificates. For businesses dealing with BIR technology requirements, outsourced BIR application systems, in-house BIR application systems, BIR system acceptance, and BIR Acceptance Certificates, the key compliance point is simple: the system acceptance process is no longer informal or ad hoc.

What RMO No. 22-99 Changed

RMO No. 22-99 prescribes the guidelines and procedures in the acceptance of outsourced and in-house developed Application System(s) of the Bureau of Internal Revenue. The issuance does not announce a new tax rate, filing threshold, withholding tax obligation, VAT rule, or taxpayer registration requirement. Instead, it addresses a governance and systems-control issue inside the BIR: how application systems developed either by external service providers or by in-house personnel are to be accepted by the Bureau.

The most important change is the designation of a responsible office. The Systems Standard and Technology Management Division of the Information Planning and Quality Service is made responsible for the acceptance of outsourced and in-house developed applications of the Bureau. This is significant because application systems used by the BIR can affect taxpayer services, internal processing, compliance monitoring, and the reliability of official tax administration workflows. By assigning responsibility to a specific division, RMO No. 22-99 creates a clearer acceptance pathway for systems that are delivered to or developed within the Bureau.

The issuance also specifies the roles and responsibilities of designated personnel who will be responsible for the acceptance and signing of Acceptance Certificates. For tax practitioners and businesses, the key takeaway is that the BIR’s technology acceptance process is tied to identified accountable personnel and formal acceptance documentation, rather than mere delivery or operational use of an application system.

Who Is Most Affected

RMO No. 22-99 most directly affects BIR offices, BIR technology personnel, and personnel involved in information planning, quality service, systems standards, technology management, and application acceptance. It also affects vendors or contractors engaged to develop outsourced application systems for the Bureau, because their deliverables may be subject to acceptance by the designated BIR division and may require the issuance or signing of an Acceptance Certificate by authorized personnel.

In-house BIR development teams are likewise covered. The title and text of the issuance expressly include both outsourced and in-house developed application systems. This means the acceptance procedure is not limited to third-party contractors. Internal BIR-developed applications must also pass through the prescribed acceptance structure.

Ordinary taxpayers, SMEs, corporations, withholding agents, and individual taxpayers are not directly required to file a new form or pay a new tax under RMO No. 22-99. However, businesses may still be indirectly affected where a BIR application system relates to taxpayer-facing services, internal tax processing, or technology projects supporting BIR compliance administration. Corporate accountants, CFOs, and in-house counsel searching for RMO No. 22-99, BIR application system acceptance, outsourced application systems BIR, in-house developed BIR systems, or BIR Acceptance Certificate should understand that the issuance concerns the BIR’s acceptance of application systems, not a taxpayer-side tax return deadline.

Key Compliance Requirements and Deadlines

RMO No. 22-99 was issued on March 12, 1999. The issuance prescribes guidelines and procedures for accepting outsourced and in-house developed application systems of the Bureau. Based on the available text of the issuance, no separate tax payment deadline, filing deadline, registration deadline, or transitory compliance period is stated for taxpayers.

The principal compliance requirement is institutional and procedural: outsourced and in-house developed BIR application systems must be accepted through the office identified in the Order. The Systems Standard and Technology Management Division of the Information Planning and Quality Service is responsible for acceptance. The designated personnel identified under the Order are responsible for acceptance and for signing the Acceptance Certificates.

For BIR technology vendors and internal project owners, this means that project completion should not be treated as equivalent to formal acceptance unless the required acceptance process has been observed. Delivery of a software product, deployment of a system, or internal use of an application may not be enough where the applicable acceptance procedure requires review, approval, and signing by designated personnel. The Acceptance Certificate becomes important because it is the formal document evidencing acceptance by the responsible BIR personnel.

For business readers, the practical point is not to look for a new tax rate or taxpayer filing form in RMO No. 22-99. The document is about systems governance. It tells the Bureau who must accept outsourced and in-house systems and who must sign the corresponding acceptance documentation. Where a private contractor is engaged in a BIR technology project, contract managers should align deliverables, milestones, turnover requirements, and payment conditions with the BIR’s acceptance procedure and the requirement for an Acceptance Certificate.

Penalties for Non-Compliance

RMO No. 22-99, as summarized in the available issuance text, does not state a specific monetary penalty, surcharge, interest rate, compromise penalty, criminal penalty, or administrative fine for taxpayers. It does not impose a deficiency tax consequence on private businesses. It does not provide a new penalty table.

The risk of non-compliance is therefore procedural and operational rather than a taxpayer penalty in the usual sense. For BIR system projects, failure to follow the prescribed acceptance process may create problems in establishing whether an outsourced or in-house application system has been properly accepted. It may also create accountability issues if the required designated personnel did not perform or document acceptance through the appropriate Acceptance Certificate.

For contractors, vendors, and internal BIR project teams, the absence of a stated tax penalty does not mean the acceptance procedure can be ignored. Formal acceptance often determines whether a project deliverable is complete, whether accountable personnel have approved the system, and whether the system has passed the applicable institutional review. Businesses participating in public-sector technology work should therefore treat the Acceptance Certificate and the designated accepting office as central compliance items.

Practical Steps for BIR Technology Vendors and Project Teams

First, identify whether the application system is outsourced or in-house developed. RMO No. 22-99 covers both categories. A project should not be excluded from the acceptance process merely because it was developed internally, and a third-party vendor should not assume that delivery alone is enough.

Second, confirm that the Systems Standard and Technology Management Division of the Information Planning and Quality Service is involved in the acceptance process. Since the Order designates this division as responsible for acceptance, project documentation should reflect the proper routing of the application system for acceptance.

Third, identify the designated personnel responsible for acceptance and signing of the Acceptance Certificates. The issuance specifically provides that roles and responsibilities of designated personnel are specified in the Order. For project governance, the acceptance record should show that the appropriate personnel acted within their assigned roles.

Fourth, align contract milestones with formal acceptance. For outsourced systems, vendors should ensure that agreements and project timelines recognize that acceptance is not merely technical delivery. The project should contemplate acceptance by the designated BIR office and signing of the relevant Acceptance Certificate.

Fifth, maintain a clear documentary trail. Because RMO No. 22-99 centers on acceptance and Acceptance Certificates, the records should show the system submitted, the responsible office, the personnel who reviewed and accepted the system, and the certificate or documentation evidencing acceptance. This is especially important for later audit, project close-out, accountability, and payment discussions.

Why This Matters for Businesses Dealing with BIR Systems

For most taxpayers, RMO No. 22-99 will not change the amount of tax due or the date for filing a return. Its importance lies in BIR systems governance. Businesses that interact with BIR technology projects, provide software or systems support to the Bureau, or advise clients on BIR digital processes should understand that the Bureau has a defined acceptance structure for outsourced and in-house application systems.

For CFOs, accountants, and in-house counsel, the search terms that matter are RMO No. 22-99, BIR application system acceptance, outsourced application systems BIR, in-house developed BIR systems, BIR Acceptance Certificate, and Systems Standard and Technology Management Division. These phrases reflect the real subject of the issuance: acceptance authority, accountability, and formal system approval within the BIR.

How Ablola, Saribong & Gueco Can Help

Ablola, Saribong & Gueco assists businesses, technology vendors, contractors, and regulated companies in understanding BIR issuances, public-sector compliance requirements, tax administration rules, and documentation risks. For companies involved in BIR-facing systems, government technology projects, tax compliance platforms, or outsourced service arrangements, proper contract drafting and acceptance documentation can prevent disputes over deliverables, payment milestones, accountability, and regulatory compliance.

Our Makati-based tax and business law team can help review BIR-related contracts, structure acceptance and turnover provisions, assess compliance exposure, and prepare documentation aligned with Philippine tax administration requirements. For assistance with BIR compliance, tax advisory, government contracts, or business law concerns, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

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