RMO No. 22-2026 and the Institutionalization of BIR Audit Reform

By: Myk Gregory L. Albao

Share this article

On August 24, 2026, the Bureau of Internal Revenue (BIR) issued Revenue Memorandum Order (RMO) No. 22-2026, prescribing the consolidated and revised policies, guidelines, and procedures for the BIR Audit Program.

RMO No. 22-2026 absorbs RMO No. 1-2026 rather than repealing it: RMO No. 1-2026 was a remedial issuance released alongside the lifting of the audit suspension, and RMO No. 22-2026 is the standing program it promised. Its “Background” section anchors the RMO on RMO No. 1-2026, as amended by RMO No. 6-2026 and clarified by RMC No. 14-2026, carrying forward reforms including the Single-Instance Audit Framework and anonymized, risk-based case selection.

To recall: the BIR suspended audit and field operations on November 24, 2025 under RMC No. 107-2025, amid scrutiny over the frequency and handling of Letters of Authority. The suspension was lifted January 27, 2026 through RMC No. 8-2026, issued with RMO No. 1-2026, later refined by RMO No. 6-2026 and RMC No. 14-2026 on March 4, 2026. RMO No. 22-2026 now completes that arc.

Below is a practical overview of the key changes and what they mean for taxpayers and their compliance functions.

At a Glance: What Taxpayers Should Note

Publication of audit selection criteria and selection codes for Mandatory and Priority Cases
Hard caps on Revenue Officer workload and express disqualifications from case assignment
Prescribed audit and review timelines, with the validity of assessments expressly insulated from breach
A signed Taxpayer’s Consent on Audit Venue/Authorized Representative as a standard audit document
A standardized Termination Letter for paid cases and cases without findings
Introduction of the Revalida, or “Audit of Auditors”

1. How RMO No. 22-2026 Relates to RMO No. 1-2026

In retrospect, this new RMO confirms that RMO No. 1-2026 was indeed drafted for a transition: staggered eLA consolidation deadlines, the wind-up of the VAT Audit Sections (VATAS) and Large Taxpayers VAT Audit Unit (LTVAU) by middle of this year, and the transfer of task force audits following the Run After Fake Transactions (RAFT) Task Force’s conclusion.

Those transitional measures have largely run their course, and RMO No. 22-2026 reflects the resulting audit structure. In particular, its treatment of the Consolidated eLA presents the move from fragmented, VAT-only audits to a comprehensive audit covering all internal revenue taxes as an accomplished shift rather than a pending implementation step.

What survives from RMO No. 1-2026 survives by reference: the Standard Checklist of Requirements, the prohibition against issuing an eLA in violation of the Single-Instance Audit Framework, and the mandatory eLA, MO, and TVN labels all remain.

RMO No. 1-2026 must, however, still be read alongside RMO No. 22-2026, since the newer RMO is not self-contained.

Practical Implications

RMO No. 1-2026 is best treated as the transition framework and RMO No. 22-2026 as the standing audit program.
BIR correspondence may be checked against the operative issuance and authority now in force.
Legacy VAT-only audits, replacement authorities, and consolidated eLAs are worth reconciling to identify the operative authority.

(See Section I on background and Section V(1)(f) on the Single-Instance Audit Framework.)

2. Mandatory Cases, Priority Cases, and Selection Codes

RMO No. 22-2026 divides audit cases into two categories and publishes the criteria and selection codes for each.

“Mandatory Cases” require audit or verification as a condition precedent to a tax clearance, refund, or credit claim, or other CIR-identified cases. eLA-covered codes include:

FRD (under-declaration by at least thirty percent, prima facie fraud);
OTT (one-time transactions);
SEOI/TPR (non-compliance with information-exchange or data-matching requests), and;
TRC (tax clearance requests where gross sales exceed Three Million Pesos (Php 3,000,000.00) or gross assets upon retirement exceed Eight Million Pesos (Php 8,000,000.00); TVN-covered refund and credit claims carry codes like VTR and VTC for VAT).

“Priority Cases” are electronically selected using risk-based criteria:

DIT (drastic sales/VAT decrease);
EIL (input taxes over seventy-five percent of output tax);
LOW (income tax due under two percent of gross sales);
LST (unaudited past five years), and;
EPA/PSA (related-party expense or income arrangements).

The approval architecture differs by category as well. “Mandatory Cases” need no prior CIR approval but require sign-off from the Regional Director or LTS Assistant Commissioner, the “Approving Authority” jointly responsible with the Head of the Investigating Office for correct classification, a sanctionable ground if wrong. “Priority Cases”, on the other hand, remain subject to centralized CIR approval upon recommendation of the Deputy Commissioner for Operations or Strategic Reforms Group.

Taxpayers enjoying tax exemptions or incentives (Selection Code INC) are expressly excluded from automatic audit; such cases are covered by an eLA only when supported by audit criteria, verifiable data, or non-compliance indicators, which is a meaningful narrowing for enterprises accustomed to treating incentive status as an audit magnet.

Practical Implications

The selection code may be used to test whether the audit’s stated basis matches the taxpayer’s filed returns and facts.
Related-party and shared-services arrangements are best viewed as express audit-risk areas, not background tax issues.
For incentive-enjoying entities, the specific data or non-compliance indicator supporting audit selection is worth identifying.

(See Section IV(2) on types of audit cases.)

3. Workload Caps, Disqualifications, and Rotation

RMO No. 1-2026 required assignment to be made on “workload balancing” and “applicable rotation rules” without defining either, and this is where RMO No. 22-2026 is useful as it supplies the numbers.

The maximum workload of a Revenue Officer (RO) is thirty (30) cases at any one time, replenished as reports or closures are submitted (but “Mandatory Cases” fall outside that count). No case may be assigned to an RO with thirty (30) or more pending priority cases, ten (10) pending mandatory cases, prescribing cases, no report for duty or clearance, ten (10) or more returned cases, cases outstanding beyond the prescribed period, or a resignation or retirement within six (6) months.

Rotation is likewise concrete: the same RO or lead RO may not audit the same taxpayer examined the immediately preceding taxable year, except in districts with four ROs or fewer, or as otherwise allowed.

Assignment stays anonymized, with the Information Systems Group decrypting only upon completion of assignment. The RMO retains a discretionary channel, however: Heads of Investigating Offices may recommend taxpayers for audit, with written justification endorsed by the Approving Authority and CIR approval. The RMO does not explain how this squares with anonymization, since a recommending office necessarily knows the taxpayer’s identity at that point; whether the channel stays exceptional or becomes routine will determine how much of the reform survives in practice.

Practical Implications

It may be useful to check whether the assigned RO or lead RO audited the same taxpayer in the immediately preceding year.
Reassignment triggers tied to RO workload, returned cases, separation, retirement, or clearance status are worth monitoring.
A non-standard assignment pattern may warrant closer authority and due-process review.

(See Section V(3) on assignment of cases.)

4. Prescribed Audit and Review Timelines

RMO No. 22-2026 fixes calendar periods for the report of investigation: 180 days for regional cases (including Office Audit Section cases) and 240 days for LTS cases, from the eLA date. A replacement eLA or eMOA on protested reinvestigation carries 90 days regionally and 120 for LTS; returned and ONETT deficiency cases carry 30 days.

Reviewing offices, however, have their own clock: 30 days from receipt of the docket for eLA and eMOA/replacement-eLA reinvestigation cases, 15 days for returned and ONETT cases. The audit period is suspended upon a request for an SDT or EOI, resuming only when the investigating RO receives the requested information. It must be noted that late reporting does not affect an assessment’s validity, without prejudice to administrative accountability, of course.

The same insulating language applies to the 15-day period for issuing the Formal Letter of Demand/Final Assessment Notice (FLD/FAN) under Revenue Regulations No. 18-2013. A delay in issuing the FLD/FAN will not, by itself, invalidate the assessment if it is still issued within the Section 203 or Section 222 prescriptive periods and the taxpayer’s due-process rights are observed. This follows our courts’ long-standing treatment of internal audit timelines as directory rather than jurisdictional. Still, an administrative issuance cannot extend the statutory prescriptive periods or cure a Section 228 due-process defect; whether due process was actually observed remains a judicial question, not one that the RMO can settle by mere characterization.

Practical Implications

Delays may be worth questioning where they affect prescription, due process, or the validity of the assessment authority.
Section 203 and Section 222 prescription dates are best computed separately from the RMO’s internal audit deadlines.
SDT and EOI requests are best diarized from issuance to receipt, since they may suspend and restart the audit clock.

(See Section V(5)(g) on report submission and Section V(6) on review timelines.)

5. Standardized Taxpayer-Facing Instruments: Consent on Venue, Escalating Notices, and Minutes of Discrepancy

Section 235 of the Tax Code permits examination of books at the taxpayer’s registered place of business or the appropriate BIR office. RMO No. 1-2026 recognized that voluminous records may make review at the BIR office impractical and gave taxpayers venue options, and that is now made official policy per RMO No. 22-2026.

The Taxpayer’s Consent on Audit Venue/Authorized Representative (Annex “B”) is served with the eLA and Checklist of Requirements. It records the taxpayer’s venue election and authorizes a named representative via special power of attorney or board/secretary’s certificate. The undertaking affirms the consent is voluntary, does not preclude a lawful audit, and stays effective until withdrawn in writing.

The venue election, however, is not absolute: once an SDT is validly issued, the option lapses and records must go to the BIR office the SDT specifies.

Document production escalates: failure to submit documents within ten (10) calendar days warrants a First Notice; another ten (10) days of non-compliance warrants a Second and Final Notice. Continued failure supports a recommendation for an SDT, and failure to comply with the SDT warrants criminal proceedings under Section 266 of the Tax Code.

The Minutes of Discussion of Details of Discrepancy is now a prescribed format, signed by the taxpayer or representative and the assigned RO and Group Supervisor, with any refusal to sign expressly noted; certified photocopies may be submitted, with originals required only for verification within the audit’s scope.

Practical Implications

The venue election and representative authorization deserve a considered decision, with documents ready before the eLA is served
The ten-day notice cycle compresses the window for producing voluminous records
Discussion of Discrepancy positions are now formally memorialized and will follow the case into protest

(See Section V(4) on service of the eLA and document submission requests.)

6. The Termination Letter, Replacement eLAs, and Consolidated eLAs

Among the more taxpayer-favorable additions is the standardized Termination Letter, prepared for paid cases and cases without findings and served on the taxpayer within a reasonable time; case custody then transfers for closure in the BIR system.

It is not, however, a final quietus: closure is without prejudice to any action arising should the returns later prove fraudulent or false, or to refund-claim findings for the same period, tracking Section 222(a)’s ten-year assessment period for fraudulent returns. Nor may a Termination Letter settle a proposed assessment unless the amount is fully supported by the RO’s audit findings.

The RMO also codifies definitions developed across RMO Nos. 1-2026, 6-2026, and RMC No. 14-2026. A “Replacement eLA” continues an audit without expanding the original scope, period, or tax types, while a “Consolidated eLA” combines two or more eLAs for the same taxpayer and taxable year into one authority under the Single-Instance Audit Framework, cancelling all prior eLAs. The Head of the Investigating Office must notify the taxpayer of any Replacement eLA, identifying the cancelled eLA by serial number and date.

A returned case keeps its eMOA if the original RO and Group Supervisor remain in the office; a Replacement eLA is required only where a different RO or Group Supervisor takes over, or the review reveals an uncovered deficiency. Whether an eMOA suffices when the same officers merely resume a case remains unsettled; taxpayers should preserve the objection where the team has changed.

Practical Implications

Termination Letters should be secured and retained in the permanent tax file
Verify each audit step’s authority against the eLA, eMOA, or Replacement eLA on record
Cancellation notices confirm which audit authority is operative; reconcile them against the docket

(See Section V(6)(e) on the Termination Letter and Section V(9) on Replacement and Consolidated eLAs.)

7. The Revalida: An Audit of the Auditors

RMO No. 22-2026 introduces a mechanism with no direct predecessor in RMO No. 1-2026, the term for which may ring a bell for lawyers and law students: the revalida.

Audit investigation reports and assessment issuances may now be subjected to a revalida, or “Audit of Auditors,” undertaken by the Tax Audit Review Division, which reviews audit findings, computations, and assessment issuances subject to CIR approval. The Performance Evaluation Division supports this through monitoring and quality assurance, including compliance with prescribed procedures and documentation. Findings are endorsed by the Deputy Commissioner for Operations Group for Regional cases, and by the Deputy Commissioners for Strategic Reforms and Legal Group for LTS and National Investigation Division cases.

Its stated purpose is quality assurance: ensuring findings are factually and legally supported, due process is observed, and assessments are free from material error. Read with the RMO’s sanctions provision, which makes improper selection, unauthorized audit, misclassification, and non-observance of procedures sanctionable, the revalida is best understood as an internal control directed at the examiner/s.

Its boundaries remain undefined, left to a separate revenue issuance. Until then, questions stay open: whether a revalida can upwardly revise an assessment already issued, how it interacts with paid, terminated, or protested cases, and whether a taxpayer gets notice or participation. A Termination Letter should not be assumed to foreclose subsequent internal review.

Practical Implications

Audit closure at the investigating office may not be the case’s final internal step
Documentation of the audit trail cuts both ways and is worth preserving on the taxpayer’s side too
The forthcoming revalida issuance warrants close monitoring

(See Section V(10) on Audit of Auditors and Section VII on administrative sanctions.)

Governance-Level Considerations

The new RMO’s cumulative effect compresses the interval between audit initiation and consequence, shifting audit risk from the conduct stage to the readiness stage.

Selection is confirmed to be system-assisted and criteria-driven, so audit exposure substantially reflects a taxpayer’s own filed returns and third-party data, well before any examiner is assigned. Document production runs on a ten-day cycle with a path to an SDT and criminal exposure under Section 266. Venue election and representative authorization must be settled at the outset, and Discussion of Discrepancy positions are memorialized in a signed instrument that follows the case.

For boards, audit committees, and senior management, that shift changes which questions matter before an eLA arrives, e.g. can the organization-taxpayer produce a complete document set within

ten days? Does the authorized BIR contact hold a current, documented mandate? Have selection-code risk indicators in the taxpayer’s filed returns and third-party data been identified, explained, and remediated where appropriate? These are governance questions before tax questions, requiring alignment among tax, finance, legal, and operating functions.

Concluding Observations

RMO No. 22-2026 consolidates into one instrument what had been distributed across four sets of previous issuances: it should be read with RMO No. 1-2026, as amended by RMO No. 6-2026 and clarified by RMC No. 14-2026, and against the assessment framework under Revenue Regulations Nos. 12-99, 18-2013, and 22-2020. Companies would be well served by reassessing audit readiness, document retention, and escalation procedures against the RMO’s compressed timelines and standardized instruments.

While the effort behind this RMO deserves recognition, we have yet to see whether implementation on the ground will follow the issuance’s design. The BIR paused field operations, reviewed its audit practices, and rebuilt the framework through published issuances rather than internal directions. By publishing selection criteria, capping workloads, requiring rotation, and introducing the revalida, the Bureau has adopted rules that constrain its own audit process as much as they guide it. After collecting Php 3.105 trillion in 2025, above the Php 2.85 trillion collected in 2024, the BIR appears to be betting that clearer procedure can strengthen voluntary compliance without relying only on audit intensity.

Ultimately, this reform will be judged not by the rules it publishes, but by the discipline with which those rules are applied. Selection criteria matter only if they truly constrain discretion; workload caps and rotation rules matter only if they are monitored; and the revalida will matter only if the forthcoming issuance gives it clear consequence.

For taxpayers, the message is clear and straightforward: under this framework, audit readiness begins before the eLA arrives, because the first audit trail is already written in the company’s own returns and data.