RMO No. 26-2021 requires the revised NDA form for BIR personnel and third parties accessing BIR systems, applications, data, or information.

Access to BIR applications, systems, data, and information now requires use of the revised Non-Disclosure Agreement form under RMO No. 26-2021, effective immediately. This matters most to BIR revenue personnel, contractors, vendors, consultants, technology service providers, and other third parties engaged in BIR projects because access to sensitive tax systems and taxpayer information must now be documented using the revised NDA form prescribed by the Bureau.

What RMO No. 26-2021 Changed

RMO No. 26-2021 amended the Non-Disclosure Agreement form previously prescribed for use by BIR revenue personnel and third parties under Revenue Memorandum Order No. 15-2014, which covered the Revised Information and Communications Technology Security Policy. The key change is not a new tax rate, tax base, or filing deadline. Instead, it is a documentation and information-security requirement: the revised NDA form in Annex A must be used and accomplished when BIR personnel or third parties are involved in work requiring access to BIR applications, systems, data, or information.

For businesses dealing with BIR technology projects, outsourced support arrangements, systems implementation, data processing, document handling, digitization, systems maintenance, consultancy, or other undertakings involving BIR information, the practical takeaway is straightforward: access to BIR systems or information should not be treated as an informal operational matter. It must be supported by the prescribed confidentiality documentation.

The issuance is particularly relevant for searches such as RMO 26-2021 revised NDA form, BIR non-disclosure agreement form, BIR ICT security policy NDA, third party access to BIR systems, and confidentiality agreement for BIR projects. These are the issues that matter to companies and service providers when they are onboarding personnel, vendors, or consultants for work touching BIR systems or taxpayer-related data.

Who Is Affected by RMO No. 26-2021

RMO No. 26-2021 is addressed to all internal revenue officials, employees, and others concerned. The policy directive specifically covers BIR revenue personnel and third parties engaged or involved in BIR projects, undertakings, and activities requiring access to BIR applications or systems, or to BIR data or information.

This means the issuance affects not only BIR employees but also outside persons and entities that may be given access in connection with official BIR work. These may include IT contractors, software developers, systems integrators, cybersecurity providers, data migration specialists, records management providers, consultants, and other project participants whose work requires them to view, handle, transmit, process, maintain, or otherwise access BIR systems or information.

For private businesses, the significance is indirect but important. A company that contracts with, supports, or supplies services to the BIR may be required to ensure that its representatives comply with the revised NDA requirement before they are allowed to participate in covered work. Corporate compliance officers, legal departments, and project managers should assume that any engagement involving BIR applications, systems, or data will require confidentiality documentation aligned with RMO No. 26-2021.

Key Compliance Requirement: Use the Revised NDA Form

The central compliance requirement is the use of the revised Non-Disclosure Agreement form. RMO No. 26-2021 states that the revised NDA shall be used by BIR revenue personnel and third parties engaged or involved in BIR projects, undertakings, or activities requiring access to BIR applications, systems, data, or information.

The issuance does not create a monetary threshold, transaction-value threshold, revenue threshold, or taxpayer classification requirement. Its trigger is access. If the person or entity will have access to BIR applications, systems, data, or information in connection with a BIR project, undertaking, or activity, the revised NDA form becomes relevant.

For compliance teams, the important operational question is therefore not whether the person is an employee or an independent contractor. The better question is whether the person will be engaged in a BIR-related project or activity that requires access to BIR systems or information. If the answer is yes, the revised NDA form should be part of the access-control and onboarding process.

Effective Date and Immediate Action Required

RMO No. 26-2021 took effect immediately. The issuance is dated August 9, 2021, and its effectivity clause states that the Order shall take effect immediately. This means there is no grace period stated in the issuance and no later compliance date stated for covered personnel or third parties.

Because the effectivity is immediate, covered BIR offices and project stakeholders should not continue using forms or procedures inconsistent with the revised NDA requirement. Any internal workflow for granting access to BIR applications, systems, data, or information should be checked against the revised form requirement under RMO No. 26-2021.

For third-party service providers, the practical step is to prepare for NDA execution as a condition to access. Companies should coordinate with their BIR counterpart, project owner, or contracting office to confirm the applicable form, the required signatories, and whether all personnel who will access BIR systems or information must separately accomplish the NDA.

Repeal of Inconsistent Issuances

RMO No. 26-2021 contains a repealing clause stating that all issuances inconsistent with the Order are repealed. This is important for compliance because older internal references, templates, onboarding checklists, or project documentation may no longer be sufficient if they conflict with the revised NDA form requirement.

In practical terms, BIR offices, contractors, and project administrators should avoid relying on older NDA templates merely because they were used in previous engagements. Where a project involves access to BIR applications, systems, data, or information, the controlling requirement is the revised NDA form prescribed by RMO No. 26-2021.

Penalties for Non-Compliance

RMO No. 26-2021 does not state a specific fine, surcharge, imprisonment penalty, or administrative penalty for failure to use the revised NDA form. It also does not prescribe a tax deficiency consequence, assessment consequence, or withholding tax consequence. Its focus is on confidentiality documentation and information-security compliance.

However, the absence of a specific penalty in the issuance should not be read as permission to ignore the requirement. In actual operations, failure to accomplish the proper NDA may delay or prevent access to BIR applications, systems, data, or information. It may also create compliance, contractual, administrative, and data governance issues for personnel or service providers involved in BIR projects.

For businesses, the risk is especially practical: a vendor or consultant that cannot satisfy the required confidentiality documentation may be unable to proceed with a BIR-related project. For personnel, failure to comply may affect authorization to access sensitive systems or information.

Practical Steps for Businesses, Contractors, and Compliance Teams

First, identify whether your company or personnel are engaged in any BIR project, undertaking, or activity involving access to BIR applications, systems, data, or information. The revised NDA requirement is triggered by access, not by company size, industry, revenue, or tax classification.

Second, review existing project onboarding documents. If your current checklist still refers to prior NDA templates or general confidentiality undertakings, update the process to align with RMO No. 26-2021. Do not assume that a generic corporate NDA will satisfy the requirement where the BIR-prescribed revised NDA form is required.

Third, require project managers to map who will actually access BIR applications, systems, data, or information. Access may be direct, such as logging into a BIR system, or operational, such as handling data or information in connection with a BIR project. Each person or entity with covered access should be reviewed for NDA compliance.

Fourth, coordinate with the BIR office or project counterpart before deployment. This helps avoid delays caused by missing confidentiality documentation, incomplete forms, or uncertainty over who must sign.

Finally, keep an internal record of NDA compliance. For regulated projects, system access, data handling, and confidentiality obligations should be documented as part of the company’s legal and compliance file.

How Ablola, Saribong & Gueco Can Help

RMO No. 26-2021 is a short issuance, but it has practical consequences for companies and third-party providers working with BIR systems, data, and information. Businesses should treat the revised NDA requirement as part of their tax compliance, data privacy, cybersecurity, procurement, and government contracting controls.

Ablola, Saribong & Gueco advises companies, contractors, and regulated entities on BIR compliance, confidentiality obligations, government project documentation, tax-related data handling, and legal risk management. For assistance in reviewing BIR project documentation, confidentiality undertakings, or compliance procedures under RMO No. 26-2021, visit MakatiLawFirm.com.

Reference:

RMO No. 26-2021 Prescribes the …


Leave a Comment

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