RMC No. 78-2008 clarifies that SARO is not needed to start procurement but is required before the government issues the notice of award.
Government offices, GOCCs, SUCs, LGUs, and BIR units handling procurement should not delay bidding merely because a Special Allotment Release Order has not yet been issued. RMC No. 78-2008 clarifies that procurement may begin once the activity is included in the Annual Procurement Plan, but the SARO must already be in place before the procuring entity issues the notice of award. For finance officers, BAC members, accountants, and suppliers dealing with government contracts, the critical compliance point is this: the absence of a SARO does not stop advertisement, posting, eligibility screening, or bidding, but it does stop award.
What RMC No. 78-2008 Changed
RMC No. 78-2008 published the full text of Government Procurement Policy Board Circular 02-2008 dated August 1, 2008, entitled Clarification on the Role of the Special Allotment Release Order in the Procurement Process. The clarification addresses a recurring procurement issue in government agencies: whether the Special Allotment Release Order, commonly searched as SARO procurement requirement Philippines or SARO before bidding, must be issued before a procuring entity may advertise or post an invitation to bid.
The answer is specific. Under the clarification, prior issuance of the SARO is not a pre-condition to the advertisement or posting of the invitation to apply for eligibility and to bid in public bidding. It is also not a pre-condition to the posting of the notice of procurement when the procuring entity uses alternative methods of procurement. Procurement may commence as long as the procurement activity is included in the Annual Procurement Plan of the procuring entity.
The important limitation is equally specific. Although the SARO is not required at the start of procurement, the SARO is required before issuance of the notice of award. This timing matters because the notice of award is the point at which the procuring entity must ensure that the certification on availability of funds can be properly issued by the chief accountant before any disbursement is incurred.
Who Is Affected by RMC No. 78-2008
RMC No. 78-2008 affects all Internal Revenue officials, employees, and others concerned, but the underlying GPPB Circular 02-2008 has a broader government procurement coverage. It applies to all departments, bureaus, offices, and agencies of the National Government; government-owned and/or controlled corporations, including government financial institutions; state universities and colleges; and local government units.
In practical terms, the affected parties include Bids and Awards Committees, heads of procuring entities, end-user units, budget officers, accountants, procurement officers, suppliers, contractors, consultants, and service providers participating in public procurement. Businesses selling to government should understand that a bid may validly proceed even if the SARO has not yet been issued, but they should also expect that the award cannot be made unless the required SARO is already available.
This is particularly relevant to companies that regularly join government procurement for goods, infrastructure, consulting services, technology systems, office supplies, construction, equipment, maintenance, and professional services. For these businesses, common search phrases include RMC No. 78-2008 SARO, SARO notice of award requirement, Annual Procurement Plan government bidding, GPPB Circular 02-2008, and BIR procurement SARO rule.
Key Definitions: APP, ABC, and SARO
RMC No. 78-2008 is important because it ties the procurement timetable to three defined concepts: the Annual Procurement Plan, the Approved Budget for the Contract, and the Special Allotment Release Order.
The Annual Procurement Plan, or APP, refers to the document reflecting the entirety of procurement activities to be undertaken by the procuring entity within the calendar year. It contains the name of the project or procurement, the project management office or end-user unit, the general description of the procurement, the procurement method to be adopted, the time schedule for each procurement activity, and the Approved Budget for the Contract.
The Approved Budget for the Contract, or ABC, is defined depending on the procuring entity. For national government agencies, it is the budget for the contract duly approved by the head of the procuring entity based on its APP and embodied in the agency budget as reflected in the General Appropriations Act or to be proposed in succeeding General Appropriations Acts. For GOCCs, including government financial institutions, and SUCs, it is the corporate budget for the contract approved by their governing boards pursuant to Executive Order No. 518, series of 1979, or Republic Act No. 8292. For LGUs, it is the budget approved by the Sanggunian.
The Special Allotment Release Order, or SARO, is a specific authority issued to one or more identified agencies to incur obligations not exceeding a given amount during a specified period for the purpose indicated. This definition explains why the SARO becomes critical before award: the government must have authority to incur the obligation before committing to the winning bidder.
When Procurement May Start Without a SARO
The most important rule is that procurement may commence as long as the activity is included in the Annual Procurement Plan. This means the procuring entity may proceed with the advertisement or posting of the invitation to apply for eligibility and to bid in public bidding even before the SARO is issued.
The same rule applies when alternative methods of procurement are used. The posting of the notice of procurement does not require prior SARO issuance. Therefore, for government agencies and suppliers, the compliance focus at the commencement stage is not the SARO but the inclusion of the procurement activity in the APP.
This prevents unnecessary delay in procurement while preserving fiscal control at the award stage. It also gives procuring entities a clearer sequencing rule: APP inclusion allows the procurement process to start; SARO issuance is required before the notice of award.
When the SARO Becomes Mandatory
The SARO becomes mandatory before issuance of the notice of award by the procuring entity. RMC No. 78-2008 emphasizes that the SARO must be in place at this point to ensure that the certification on availability of funds can be properly issued by the chief accountant of the procuring entity.
The circular links this requirement to Section 40, Chapter 5, Book VI of Executive Order No. 292. The practical point is that before the government makes the award, the accounting and budgetary basis for the obligation must already exist. Without the SARO, the procuring entity should not proceed to the notice of award because the required funds certification may not be properly issued.
For suppliers and contractors, this means that a completed bidding process does not automatically mean an immediate award if the SARO has not yet been issued. For government officers, it means that procurement timelines must be managed carefully so that the SARO is secured before the award stage, not after.
Compliance Requirements and Deadlines
RMC No. 78-2008 is dated November 12, 2008. The GPPB circular published through it is dated August 1, 2008. The circular does not impose a tax filing deadline, tax rate, payment deadline, or numerical threshold. Instead, it provides a procurement timing rule that government agencies must observe when handling procurements funded through allotments requiring a SARO.
The operative compliance requirements are specific. First, the procurement activity must be included in the APP before procurement commences. Second, the procuring entity may advertise or post the bidding invitation, or post the notice of procurement for alternative methods, even without a prior SARO. Third, the SARO must be issued before the notice of award. Fourth, the chief accountant must be able to properly issue the certification on availability of funds before any disbursement is incurred.
Government finance and procurement teams should therefore align procurement calendars, APP entries, budget approvals, SARO requests, and award timelines. A procurement process that starts correctly may still encounter compliance issues if the SARO is not secured before award.
Penalties and Risks for Non-Compliance
RMC No. 78-2008 does not state a specific penalty, surcharge, interest, fine, or tax consequence for non-compliance. However, the risk is practical and legal. A procuring entity that treats SARO issuance as a requirement before posting may unnecessarily delay procurement. On the other hand, a procuring entity that issues a notice of award before the SARO is in place risks proceeding without the necessary authority to incur the obligation and without proper basis for the certification on availability of funds.
For accountable officers, the compliance concern is not merely procedural. Government procurement involves budget authority, obligation, certification of funds, and disbursement controls. Issuing an award before the SARO is secured may expose the transaction to audit questions and internal accountability issues, especially if the chief accountant cannot properly certify the availability of funds.
Practical Steps for Government Units and Bidders
Government units should first confirm that each procurement activity is included in the APP before advertisement, posting, or use of alternative procurement methods. The APP should identify the project or procurement, end-user unit, general description, procurement method, activity schedule, and ABC. If the procurement is not properly reflected in the APP, the commencement of procurement may be vulnerable to challenge.
Second, procurement officers should not wait for the SARO before taking the initial procurement steps, provided the procurement is in the APP. This is the main efficiency point of RMC No. 78-2008. The rule allows the procurement process to move forward while the fiscal authority is being processed.
Third, before the notice of award is issued, the procuring entity must verify that the SARO has already been issued. This verification should be part of the award-stage checklist, together with the certification on availability of funds by the chief accountant.
Fourth, bidders should understand that SARO timing affects award, not necessarily bidding. If a government agency proceeds with posting even without a SARO, that fact alone is not inconsistent with RMC No. 78-2008. However, if the agency attempts to issue the notice of award without the SARO, suppliers should consider asking for confirmation that the funding authority and certification of availability of funds are already in place.
Why This Matters for BIR and Government Procurement Compliance
Although RMC No. 78-2008 is not a tax-rate issuance, it is still important for BIR governance, procurement compliance, public sector contracting, and businesses transacting with government. It clarifies the correct role of the SARO and prevents both premature award and unnecessary delay at the bidding stage.
The compliance message is simple but important: APP inclusion starts the procurement process; SARO issuance supports the award and obligation stage. Finance, accounting, and procurement teams should not confuse these two steps.
ASG Law Can Assist with BIR, Procurement, and Government Contract Compliance
Ablola, Saribong & Gueco advises businesses, suppliers, contractors, and regulated entities on BIR issuances, government procurement requirements, contract review, compliance risk, and documentation for transactions involving public agencies. For companies participating in government bidding or dealing with BIR-related procurement, the timing of authority, award, funding certification, and contract documentation can determine whether a transaction proceeds smoothly or becomes exposed to audit and compliance issues.
For legal guidance on RMC No. 78-2008, SARO requirements, procurement documentation, BIR compliance, and government contract risk management, consult Ablola, Saribong & Gueco through MakatiLawFirm.com.