RMO No. 39-98 requires every BIR Revenue Data Center to create an Inspection and Acceptance Committee for deliveries under procurement documents.

Revenue Data Centers must now have a formal Inspection and Acceptance Committee before deliveries under Purchase Orders, Letter Orders, Contracts, or Job Orders initiated at the Revenue Data Center are accepted. For businesses dealing with BIR technology, administrative, or operational procurement, RMO No. 39-98 matters because it places an internal acceptance control at the Revenue Data Center level, making documented inspection and acceptance part of the procurement process.

What RMO No. 39-98 Changes

RMO No. 39-98 creates an Inspection and Acceptance Committee, or IAC, in every Revenue Data Center of the Bureau of Internal Revenue. The core change is institutional: each Revenue Data Center must have a designated committee responsible for inspecting and accepting deliveries of items covered by procurement documents initiated at that Revenue Data Center.

The order is especially relevant to BIR procurement, government suppliers, technology service providers, office equipment vendors, contractors, and internal BIR units involved in requisitions. Instead of leaving acceptance of delivered goods or services to informal or ad hoc confirmation, the order requires a structured committee within each Revenue Data Center to perform the inspection and acceptance function.

The official citation is RMO No. 39-98. It was issued on May 18, 1998. The practical topic that accountants, procurement teams, and suppliers are likely to search is BIR Revenue Data Center inspection and acceptance, BIR procurement acceptance committee, Revenue Data Center deliveries, Purchase Order inspection BIR, and RMO 39-98 Inspection and Acceptance Committee.

Who Is Affected

The most directly affected offices are the BIR Revenue Data Centers, because each Revenue Data Center must have its own Inspection and Acceptance Committee. The affected internal personnel include the Quality Assurance Department, the Administrative Department, and the requisitioning unit involved in the procurement.

Businesses are affected when they supply goods, equipment, systems, services, or job order deliverables to a BIR Revenue Data Center. This may include information technology vendors, maintenance contractors, office equipment suppliers, systems support providers, administrative suppliers, and service contractors whose transactions are covered by a Purchase Order, Letter Order, Contract, or Job Order initiated at the Revenue Data Center.

For these suppliers, the key business consequence is that delivery does not end with physical turnover. The relevant Revenue Data Centerโ€™s Inspection and Acceptance Committee must inspect and accept the delivered items. Suppliers should therefore expect that the committee may check whether the delivered items match the procurement document, whether the delivery is complete, and whether the items correspond to the requirements initiated by the Revenue Data Center.

Composition of the Inspection and Acceptance Committee

RMO No. 39-98 specifies the composition of the Inspection and Acceptance Committee in every Revenue Data Center. The Chairman is the Head of the Quality Assurance Department or his duly authorized representative. The members are the Head of the Administrative Department or his duly authorized representative, and a representative of the requisitioning unit.

This composition is important because it combines three perspectives in the acceptance process. The Quality Assurance Department leads the inspection function, the Administrative Department participates from the administrative and procurement implementation side, and the requisitioning unit provides operational confirmation that the delivered items correspond to what was requested.

For suppliers and contractors, this means that acceptance may involve more than one office within the Revenue Data Center. A vendor dealing with a Revenue Data Center should not assume that acknowledgment by a single end-user is equivalent to formal acceptance. The relevant acceptance process must be routed through the Inspection and Acceptance Committee created under RMO No. 39-98.

Key Compliance Requirements and Covered Transactions

The key compliance requirement is the creation and operation of an Inspection and Acceptance Committee in every Revenue Data Center. The committee is tasked with inspection and acceptance of all deliveries of the items shown in the Purchase Order, Letter Order, Contract, or Job Order initiated at the Revenue Data Center.

The covered procurement documents identified in the issuance are specific: Purchase Order, Letter Order, Contract, and Job Order. This matters because suppliers should align their delivery documents, invoices, receipts, delivery receipts, completion reports, and turnover records with the exact procurement instrument governing the transaction.

For example, if a Revenue Data Center initiates a Purchase Order for equipment, the supplier should ensure that the items delivered correspond exactly to the items shown in that Purchase Order. If the transaction is covered by a Job Order, the supplier should be ready to demonstrate completion of the work described in that Job Order. If the transaction is covered by a Contract or Letter Order, the delivered goods or services should be traceable to the terms of that document.

The order does not provide a separate numerical threshold, peso amount, rate, or monetary limit. It also does not state a special filing deadline for private suppliers. Its operative requirement is structural and procedural: every Revenue Data Center must have an Inspection and Acceptance Committee, and the committee performs inspection and acceptance for deliveries tied to the specified procurement documents initiated at the Revenue Data Center.

Effective Date and Timing

RMO No. 39-98 was issued on May 18, 1998. The available text does not state a separate delayed effectivity date. Businesses and BIR units applying the issuance should therefore treat May 18, 1998 as the relevant issuance date and compliance reference point.

For current compliance and historical procurement review, the date is still important. If a Revenue Data Center procurement transaction is being evaluated for proper acceptance controls, RMO No. 39-98 provides the basis for checking whether an Inspection and Acceptance Committee existed and whether it participated in the inspection and acceptance of the relevant delivery.

Penalties and Risks for Non-Compliance

RMO No. 39-98 does not state a specific fine, surcharge, tax penalty, or criminal penalty for non-compliance. It is not a tax assessment issuance that imposes a new tax rate, withholding obligation, or return-filing deadline. Instead, it establishes an internal BIR procurement control mechanism for Revenue Data Centers.

Even without a stated penalty, non-compliance can have practical consequences. A supplier may face delayed acceptance, delayed payment processing, or requests for additional documentation if deliveries are not properly inspected and accepted by the committee. Internally, the absence of proper inspection and acceptance documentation may create audit, accountability, or procurement governance issues for the Revenue Data Center.

For businesses, the risk is not framed as a tax penalty but as a procurement documentation and payment risk. If the delivery cannot be matched to the Purchase Order, Letter Order, Contract, or Job Order, or if the proper committee acceptance is missing, the transaction may become harder to close administratively.

Practical Steps for Suppliers and Contractors

Businesses supplying goods or services to a BIR Revenue Data Center should first identify the governing procurement document. The supplier should determine whether the transaction is covered by a Purchase Order, Letter Order, Contract, or Job Order, because RMO No. 39-98 expressly refers to deliveries of items shown in these documents.

Second, the supplier should prepare complete delivery documentation. Delivery receipts, invoices, acceptance forms, turnover documents, warranty documents, completion reports, and technical specifications should be consistent with the procurement document. Any discrepancy in model number, quantity, scope, or description may slow down inspection and acceptance.

Third, the supplier should coordinate with the requisitioning unit but should not rely only on informal end-user confirmation. Since the committee includes a representative of the requisitioning unit, that unitโ€™s confirmation is relevant, but the formal acceptance function belongs to the Inspection and Acceptance Committee.

Fourth, businesses should maintain a procurement file for each Revenue Data Center transaction. That file should contain the Purchase Order, Letter Order, Contract, or Job Order; proof of delivery; correspondence; inspection records if furnished; and acceptance documentation. These records are useful for payment follow-up, audit inquiries, and future government procurement transactions.

Why RMO No. 39-98 Still Matters for BIR Procurement Compliance

RMO No. 39-98 is a short issuance, but it reflects an important compliance principle: government deliveries should not be accepted without a defined inspection and acceptance process. For BIR Revenue Data Centers, the order creates a committee-based safeguard involving quality assurance, administration, and the requisitioning unit.

For private businesses, the lesson is practical. When dealing with BIR Revenue Data Centers, suppliers should treat inspection and acceptance as a formal step in the procurement cycle. Proper documentation, exact compliance with the procurement document, and coordination with the appropriate Revenue Data Center personnel can help avoid disputes, payment delays, and audit concerns.

How Ablola, Saribong & Gueco Can Help

Ablola, Saribong & Gueco assists businesses, suppliers, contractors, and corporate legal departments in navigating BIR compliance, government procurement documentation, contract review, tax risk management, and regulatory correspondence. RMO No. 39-98 is a reminder that even internal BIR procedural issuances can affect how private suppliers document deliveries, secure acceptance, and protect payment claims.

If your company supplies goods or services to the BIR, deals with Revenue Data Center procurement, or needs help reviewing government contracts, acceptance documents, or BIR compliance requirements, our Makati-based tax and business law team can help. Visit MakatiLawFirm.com to consult Ablola, Saribong & Gueco on BIR compliance, procurement documentation, and Philippine tax and business law concerns.


Leave a Comment

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