RMO No. 27-2018 requires the revised BIR NDA form for revenue personnel and third parties accessing BIR systems, data, or information.

BIR revenue personnel and third-party service providers who are engaged in BIR projects requiring access to BIR applications, systems, data, or information must now use the revised Non-Disclosure Agreement form under RMO No. 27-2018. The immediate compliance point is simple but important: before any person is allowed access to BIR systems or taxpayer-related information in connection with BIR work, the proper revised NDA form should be used instead of the earlier form prescribed under prior information and communication technology security policies.

What RMO No. 27-2018 Changed

RMO No. 27-2018, formally titled Revised Non-Disclosure Agreement Form, amends the Non-Disclosure Agreement form previously prescribed for use by BIR revenue personnel and third parties. The earlier NDA requirement was tied to Revenue Memorandum Order No. 50-2004, which dealt with Information and Communication Technology Security Policies. The key change is not a new tax rate, tax base, or filing deadline. Rather, it is a documentation and data-security compliance change: the BIR has revised the official NDA form that must be used when BIR personnel or third parties are given access to BIR applications, systems, data, or information.

For businesses and professional service providers, the practical impact is that confidentiality documentation for BIR projects, BIR system access, outsourced technical work, data-related undertakings, or other BIR activities should be reviewed against the revised NDA requirement. A vendor, consultant, systems integrator, information technology provider, contractor, or other third party involved in a BIR undertaking should not assume that an older NDA template remains sufficient.

Who Is Affected by the Revised BIR NDA Form

The issuance is addressed to all internal revenue officials, employees, and others concerned. It specifically covers BIR revenue personnel and third parties engaged or involved in BIR projects, undertakings, or activities requiring access to BIR applications, systems, data, or information.

This means the affected persons include internal BIR officers and employees who handle or access BIR systems and information, as well as external parties that may be brought into BIR work. The third-party category is especially important for businesses because it may include contractors, consultants, information technology vendors, software developers, systems maintenance providers, data processing vendors, project implementation partners, and other service providers who may be required to access BIR systems or data in the course of an official BIR project.

Although the issuance is internal-facing in form, it matters to private companies because BIR projects and technology-related engagements often involve external service providers. Search phrases such as BIR revised NDA form, RMO 27-2018 non-disclosure agreement, BIR third party access to systems, BIR ICT security policies, and BIR data confidentiality agreement are therefore directly relevant to businesses and vendors dealing with BIR information or system access.

Key Compliance Requirement: Use the Revised NDA Form

The central compliance requirement under RMO No. 27-2018 is the mandatory use of the revised NDA form attached as Annex A to the issuance. The revised NDA is required for BIR revenue personnel and third parties engaged or involved in BIR projects, undertakings, or activities that require access to BIR applications, systems, data, or information.

For compliance teams, the trigger is access. If a person or entity will be given access to BIR applications or systems, or to BIR data or information, the revised NDA requirement should be considered before access is granted. This is particularly relevant where the work involves digital platforms, database access, application maintenance, systems support, cybersecurity, data migration, software development, information processing, or other ICT-related activities.

For external vendors, the practical takeaway is that confidentiality undertakings should not be treated as a mere formality. Access to government tax systems and information carries heightened sensitivity because BIR systems may contain taxpayer records, internal workflows, assessment data, payment information, registration data, returns, reports, and other information that may be protected by law, regulation, policy, or contractual obligation.

Effective Date and Deadline

RMO No. 27-2018 is dated May 11, 2018 and expressly states that it takes effect immediately. No transition period, grace period, or future implementation date is stated in the issuance. For covered BIR offices, personnel, and third parties, the safest reading is that the revised NDA form should be used from the effectivity of the order for all covered projects, undertakings, and activities requiring access to BIR applications, systems, data, or information.

Because the order took effect immediately, compliance should focus on whether current templates, onboarding packets, project documentation, and access-control procedures still refer to the old NDA form. Businesses participating in BIR-related projects should confirm that the version being signed is the revised form required under RMO No. 27-2018, especially where system credentials, database access, confidential information, or taxpayer-related data will be involved.

Repeal of Inconsistent Issuances

RMO No. 27-2018 also provides that all issuances inconsistent with the order are repealed. This matters because the revised form amends the NDA form previously prescribed under RMO No. 50-2004. Where an older BIR policy, template, internal procedure, or project document conflicts with the revised NDA requirement, the revised form under RMO No. 27-2018 should control.

For corporate legal teams and in-house counsel, this makes document version control important. If a company is dealing with BIR-related work, it should avoid relying on outdated NDA templates that may have been used in prior engagements. The compliance question is not merely whether an NDA exists, but whether the correct BIR-prescribed revised NDA is being used for the relevant access.

Penalties and Consequences for Non-Compliance

RMO No. 27-2018 does not specify a monetary penalty, surcharge, interest rate, compromise penalty, or tax assessment consequence for failure to use the revised NDA form. It is not a revenue regulation imposing a tax liability. It is an internal revenue memorandum order governing the required confidentiality form for covered BIR personnel and third-party access situations.

That said, the absence of a stated tax penalty does not make the requirement optional. Failure to use the correct NDA may create compliance, administrative, contractual, procurement, project governance, and data-security issues. For third parties, it may delay onboarding, access approval, system implementation, or project acceptance. For BIR personnel and offices, it may raise internal compliance questions because the order directs the use of the revised form for covered activities.

Practical Steps for Businesses, Vendors, and Compliance Officers

Businesses that provide services to the BIR, or that participate in BIR-related projects, should first identify whether their work requires access to BIR applications, systems, data, or information. If access is required, they should confirm that the revised NDA form under RMO No. 27-2018 is part of the project documentation.

Second, companies should update internal contract checklists for government projects involving the BIR. The checklist should include review of confidentiality documentation, confirmation of the applicable BIR-prescribed NDA form, authority of signatories, coverage of personnel with actual access, and coordination with project managers before credentials or information are released.

Third, vendors should train their personnel that BIR system access is sensitive and should be limited to authorized project purposes. Even if the issuance itself focuses on the NDA form, the underlying concern is protection of BIR applications, systems, data, and information. Companies should align the NDA requirement with access controls, employee confidentiality undertakings, cybersecurity protocols, device management, document retention, and incident reporting procedures.

Finally, companies should maintain clean records showing that the appropriate NDA was executed before access was provided. This is particularly important for businesses working in ICT, software development, systems maintenance, cloud support, cybersecurity, database management, and other technical services where access logs and confidentiality obligations may later be reviewed.

Why RMO No. 27-2018 Matters for BIR Compliance

RMO No. 27-2018 is a short issuance, but it addresses a critical compliance point: taxpayer and government data must be protected through the proper confidentiality documentation. For businesses dealing with the BIR, the revised NDA form is not just an internal government template. It is part of the legal and operational framework for allowing access to BIR systems and information.

For CFOs, corporate accountants, and tax managers, the issuance is relevant when their companies work with BIR systems, support BIR projects, or engage consultants who may handle sensitive tax information. For in-house counsel, it is a reminder to check not only commercial terms, but also regulatory documentation and government-prescribed forms.

ASG Law Can Help With BIR Compliance and Government Project Documentation

Ablola, Saribong & Gueco assists businesses, service providers, contractors, and corporate legal departments in reviewing BIR compliance obligations, confidentiality documentation, tax-related contracts, regulatory risk, and government project requirements. If your company is dealing with BIR system access, tax data, third-party confidentiality obligations, or BIR-related project documentation, ASG Law can help ensure that your documents are compliant, current, and enforceable.

For assistance with BIR compliance, tax documentation, and business law advisory services in the Philippines, contact Ablola, Saribong & Gueco through MakatiLawFirm.com.


Leave a Comment

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