RMC No. 79-2017 reiterates the 10-working-day lead time for BIR and DOF travel authority requests, with 14 working days for OP-approved entitlements.
Revenue officials and employees who need official travel authority must now treat the ten-working-day filing period as a real approval risk: travel requests submitted late, incomplete, or without proper justification may be strongly considered for disapproval. RMC No. 79-2017 matters because it reiterates a concrete administrative deadline for official travel within the Department of Finance and its bureaus and attached agencies, including the Bureau of Internal Revenue. The key compliance point is simple but strict: submit complete travel authority requests at least ten working days before departure, or at least fourteen working days before departure when the request includes entitlements requiring further approval by the Office of the President.
What RMC No. 79-2017 Changed
RMC No. 79-2017 circularizes the memorandum dated July 18, 2017 issued by Undersecretary Gil S. Beltran of the Department of Finance on the reiteration of the ten-working-day lead time requirement for requests for travel authority. The circular was issued by Commissioner Caesar R. Dulay on September 12, 2017, and was addressed to all revenue officials, employees, and others concerned.
The practical change is not a new tax rate, exemption, or taxpayer filing obligation. Rather, it reinforces an internal government compliance rule governing the timing and completeness of official travel requests. The memorandum noted a marked increase in late or incomplete travel authority requests submitted to the Department of Finance, including requests submitted only a few days before departure or even on the day of departure itself. Because of that observed practice, the circular reiterates that the existing lead time requirement must be strictly observed.
The rule being emphasized comes from Department Order No. 101-2014 dated December 10, 2014, particularly Section 5. That provision states that all applicants are strongly enjoined to observe an at least ten-working-day deadline before departure for the submission of travel applications with supporting documents. It also states that a travel application filed less than ten working days before departure will be strongly considered for disapproval.
Who Is Affected by RMC No. 79-2017
The immediate affected parties are revenue officials, BIR employees, and other personnel within the Department of Finance system who submit requests for official travel authority. The memorandum covered all heads of DOF offices, bureaus, and attached agencies, and the BIR circular directed all revenue officials, employees, and others concerned to be guided accordingly.
For private businesses, CFOs, corporate accountants, and tax practitioners, RMC No. 79-2017 does not impose a new tax payment, withholding tax duty, VAT filing rule, or documentary submission requirement. However, it remains relevant for businesses that coordinate with the BIR or DOF on activities involving official travel, inter-agency events, seminars, meetings, inspections, official representation, or government participation. Where a company expects the attendance of BIR or DOF personnel in an official capacity requiring travel authority, the lead time requirement may affect scheduling, coordination, and feasibility.
Common search phrases connected with this issuance include RMC 79-2017 travel authority, BIR travel authority ten working days, DOF travel authority request deadline, travel authority supporting documents BIR, and Office of the President approval fourteen working days. These phrases reflect the practical questions that arise when official travel is being planned close to the intended departure date.
Key Compliance Requirements and Deadlines
The central deadline under RMC No. 79-2017 is at least ten working days before the date of departure. All travel requests must be submitted to the DOF Central Records Management Division, or CRMD, within that period. The request must also be complete when filed. A late request is not merely procedurally defective; it is expressly treated as a strong ground for disapproval.
The required documentation must sufficiently spell out the destination or destinations, the duration of travel, the purpose or purposes of the trip, the entitlements involved, the sponsorship, and the justification for the necessity of the trip. This is important because the circular addresses not only late filing but also incomplete submissions. A request filed early but lacking essential details may still fail the compliance standard because the memorandum specifically referred to late or incomplete submissions as a recurring problem.
There is also a higher lead time requirement for official travel requests involving entitlements that need further approval by the Office of the President. In that situation, the travel request must be submitted to the DOF CRMD at least fourteen working days before the departure date. This fourteen-working-day rule should be treated as a separate compliance threshold, not merely a best-practice suggestion, because it accounts for the additional approval layer beyond the DOF.
Where a travel request falls short of the required lead time, it must be accompanied by a written justification addressed to the Secretary of Finance. The circular does not state that the written justification guarantees approval. It only states that such justification must accompany requests that fail to meet the lead time requirement. Therefore, officials and employees should not rely on after-the-fact explanations as a substitute for timely filing.
Penalties and Consequences for Non-Compliance
RMC No. 79-2017 identifies the operational consequence of non-compliance: failure to comply with the lead time requirement shall be considered a strong ground for disapproval. This is the key enforcement point. A travel authority request filed less than ten working days before departure, or less than fourteen working days before departure where Office of the President approval is needed for entitlements, may be denied on that basis.
The circular does not specify a monetary penalty, administrative fine, tax surcharge, interest, or compromise penalty. It also does not create taxpayer penalties. Its consequence is administrative and approval-based. For government personnel, the risk is that official travel may not be authorized. For offices coordinating the travel, the risk is disruption of official schedules, conferences, meetings, inspections, or inter-agency activities.
Practical Steps for Compliance
Government offices and personnel covered by RMC No. 79-2017 should calculate the deadline backward from the intended date of departure using working days, not calendar days. Weekends and non-working holidays should be considered carefully because they may shorten the effective preparation period. A request intended to meet the ten-working-day rule should not be filed on the last possible day if the supporting documents are still incomplete.
Before submission to the DOF CRMD, the travel file should be checked for the required information: destination, duration, purpose, entitlements, sponsorship, and justification for necessity. If any entitlement requires further approval by the Office of the President, the office should use the fourteen-working-day standard from the beginning. Treating the request as an ordinary ten-working-day submission may create an avoidable approval delay.
For businesses and private organizations coordinating with BIR or DOF personnel, the practical lesson is to build government lead time into event planning. Invitations, agendas, sponsorship details, travel details, and supporting information should be provided early enough to allow the concerned government office to comply with the ten-working-day or fourteen-working-day requirement. A last-minute invitation may be administratively difficult even when the event is important.
For internal BIR and DOF administrative teams, RMC No. 79-2017 also supports a stricter document-control process. Travel authority requests should be logged by intended departure date, checked for completeness, and escalated early if they require Secretarial attention or Office of the President approval. Late requests should include a written justification addressed to the Secretary of Finance, but the better compliance practice remains timely and complete filing.
Why This Issuance Matters for Tax and Business Compliance Planning
Although RMC No. 79-2017 is not a taxpayer-facing tax rule, it demonstrates how administrative deadlines within the BIR and DOF can affect business-facing government activity. Taxpayers, regulated entities, and professional organizations often coordinate with government officials for seminars, inspections, consultations, enforcement-related travel, or official appearances. When official travel authority is required, timing becomes a compliance issue.
For CFOs, corporate accountants, and in-house counsel, the main takeaway is to avoid assuming that government participation can be arranged on short notice. Where a project, audit-related meeting, training, or official event requires BIR or DOF attendance outside the officialβs station, the schedule should account for the ten-working-day travel authority deadline and the fourteen-working-day deadline for requests involving entitlements that require Office of the President approval.
ASG Law Can Help with BIR and DOF Compliance Coordination
Ablola, Saribong & Gueco advises businesses, regulated entities, accountants, and in-house legal teams on Philippine tax compliance, BIR procedures, government submissions, and regulatory coordination. RMC No. 79-2017 is a reminder that compliance is not limited to tax returns and payments; timing, documentation, and administrative procedure can determine whether a government-facing action proceeds smoothly.
For assistance with BIR issuances, tax compliance planning, regulatory submissions, and coordination with Philippine tax authorities, consult Ablola, Saribong & Gueco, a full-service law firm based in Makati City. Visit MakatiLawFirm.com to speak with counsel about practical, business-focused BIR compliance support.