Revenue Memorandum Circular 98-2026 (RMC 98-2026) is the BIR’s primary technical implementation guidance for the Philippines e-invoicing mandate under RR No. 11-2025, as extended by RR No. 26-2025. BIR RMC 98-2026 Explained provides an overview of the detailed operational and technical rules that covered taxpayers must follow in practice. While RR No. 11-2025 established the mandate’s framework and RR No. 26-2025 extended the compliance deadline, RMC 98-2026 explains how businesses should implement e-invoicing requirements and manage their ongoing compliance obligations.
This article explains what RMC 98-2026 covers, which taxpayers it affects, how it relates to the earlier revenue regulations, the key implementation rules and dates it establishes, how it changes ATP and downtime rules, and what taxpayers need to do to comply with its specific requirements. It is a practical guide for finance managers, tax counsel, and compliance officers who need to understand the specific obligations that RMC 98-2026 creates.
Key Takeaways
- RMC 98-2026 is the primary technical guidance for BIR EIS implementation — it specifies the JSON data schema, mandatory data fields, API connectivity requirements, downtime procedures, and EIS certification process that RR No. 11-2025 authorized but did not detail.
- RMC 98-2026 clarifies the three Group 1 coverage criteria — Large Taxpayers, CAS/CBA users, and e-commerce taxpayers — and provides technical detail on how each criterion is assessed, addressing interpretive ambiguities in the original RR.
- The downtime rules in RMC 98-2026 specify the recovery window for retroactive EIS transmission, documentation requirements for downtime invoices, and the criteria that distinguish genuine downtime from operational non-compliance.
- RMC 98-2026 establishes the EIS certification process — the technical validation that a covered taxpayer’s integrated system produces BIR-compliant submissions — which must be completed before any covered taxpayer goes live in production.
- Covered taxpayers who have not yet reviewed RMC 98-2026 may have compliance gaps in areas like ATP surrender requirements, invoice data field completeness, and correction/cancellation procedures — areas where the RMC provides detail that RR No. 11-2025 does not.
What Is RMC 98-2026?
Revenue Memorandum Circular 98-2026 is an administrative issuance from the Bureau of Internal Revenue (BIR) that provides detailed technical and operational guidance for implementing the Electronic Invoicing/Receipting System mandated under RR No. 11-2025. BIR RMC 98-2026 e-invoicing guidance explains how covered businesses should implement existing regulatory obligations in practice. Revenue Memorandum Circulars interpret and clarify existing Revenue Regulations rather than independently creating new substantive tax obligations, helping taxpayers understand the procedures and technical requirements for e-invoicing compliance.
RMC 98-2026 was issued in response to significant taxpayer requests for technical guidance during the compliance preparation period. The revenue regulations establishing the mandate — RR No. 11-2025 and RR No. 26-2025 — provided the legal framework but left many technical implementation questions unanswered. RMC 98-2026 fills those gaps, making it effectively the operational manual for BIR e-invoicing compliance. It is the document that ERP developers, accredited providers, and taxpayer compliance teams rely on for specific technical requirements.
Which Taxpayers Are Covered by RMC 98-2026?
RMC 98-2026 applies to all taxpayers covered by the BIR e-invoicing mandate under RR No. 11-2025 — specifically to Group 1 taxpayers required to comply by December 31, 2026, and by extension to Group 2 and Group 3 taxpayers as their deadlines are established. The RMC provides authoritative technical specifications that all covered taxpayers’ systems and providers must implement, regardless of which group they fall in or when their deadline arrives.
1. Group 1 Taxpayers (Primary Audience for Current Implementation)
For Group 1 taxpayers, including Large Taxpayers, CAS/CBA-registered businesses, and e-commerce taxpayers, RMC 98-2026 provides important technical and operational guidance for EIS implementation. BIR revenue memorandum circular e-invoicing requirements cover system configurations, data specifications, and operational procedures that covered businesses must review and implement according to applicable BIR deadlines. Having a PTI and an accredited provider alone may not ensure compliance if the required technical configurations and procedures have not been properly implemented.
2. Accredited Service Providers
RMC 98-2026 applies directly to BIR-accredited e-invoicing service providers (ESPs). Providers must implement the data schema, API specifications, and validation rules in the RMC within their platforms. A provider’s system that produces submissions deviating from the RMC specification — even if the provider is BIR-accredited — does not produce compliant e-invoices. Covered taxpayers should confirm with their provider that their platform’s current implementation is compliant with the current version of RMC 98-2026 specifications.
How RMC 98-2026 Relates to RR No. 11-2025 and RR No. 26-2025
The three BIR issuances form a layered compliance framework. RR No. 11-2025 is the foundational revenue regulation that established the e-invoicing mandate: the covered taxpayer groups, the compliance timeline, the accreditation framework for ESPs, and the penalty provisions. It is the primary legal instrument of the mandate. RR No. 26-2025 amended the original deadline, extending the Group 1 compliance date from an earlier date to December 31, 2026. It also provided clarifications on the treatment of PEZA and BOI taxpayers that were not fully addressed in the original RR.
RMC 98-2026 sits below both Revenue Regulations in the hierarchy of BIR issuances and cannot override or amend their substantive provisions. Instead, it provides implementation guidance and interprets existing requirements. While the Revenue Regulations establish the legal obligation to issue e-invoices, the circular explains the required invoice formats, mandatory data fields, and transmission procedures. Understanding this distinction helps businesses address both regulatory and technical compliance obligations. For implementation timelines and regulatory updates, refer to the BIR E-Invoicing Deadline guide.
| Issuance | Type | Primary Content | Effect on Taxpayers |
|---|---|---|---|
| RR No. 11-2025 | Revenue Regulation | Mandate framework, taxpayer groups, ESP accreditation, penalties | Establishes legal obligation to comply with e-invoicing |
| RR No. 26-2025 | Revenue Regulation (Amendment) | Deadline extension to Dec 31, 2026; PEZA/BOI clarifications | Extends compliance deadline; clarifies Group 2 coverage |
| RMC 98-2026 | Revenue Memorandum Circular | JSON schema, API specs, data fields, downtime rules, EIS certification | Specifies technical and operational implementation requirements |
Key Implementation Rules from RMC 98-2026
1. JSON Data Schema Specification
RMC 98-2026 publishes the BIR’s prescribed JSON schema for e-invoice submissions, specifying exact field names, data types, formats, and validation rules. The schema distinguishes between mandatory fields required for every submission and conditional fields applicable to specific transaction types. Technical annexes provide examples of correctly formatted JSON payloads for standard VAT invoices, zero-rated invoices, credit notes, and cancellations. Taxpayer integration teams and provider development teams must implement the prescribed schema accurately rather than using approximations. For more information about regional e-invoicing solutions, visit Tuguegarao City.
2. Near-Real-Time Transmission Requirement
RMC 98-2026 clarifies the near-real-time transmission requirement: invoice data must reach the EIS at the time the invoice is issued to the buyer. The RMC acknowledges that network latency may cause transmission to occur within seconds or minutes of invoice generation, and this is acceptable. What is not acceptable is systematic batch processing — accumulating invoices during a period and submitting them in a single batch at a later time. The RMC does not specify a maximum permitted delay in seconds, but the intent is clear: transmission must be contemporaneous with invoice issuance.
3. EIS Certification Process
RMC 98-2026 establishes the EIS certification process as a prerequisite for production go-live. Certification requires the taxpayer’s accredited provider to submit a certification package — including sandbox test submission logs, data field mapping documentation, and a system description — to the BIR for validation. The BIR issues an EIS certification confirmation that the taxpayer must retain. No covered taxpayer may issue production e-invoices before EIS certification is received. The certification confirms that the specific system configuration produces BIR-compliant submissions.
Downtime Rules Under RMC 98-2026
One of the most detailed sections of RMC 98-2026 covers the downtime procedure — the specific rules for how covered taxpayers may issue manual invoices when the EIS is unavailable. The downtime rules balance the operational need for business continuity against the risk that the downtime provision becomes an avenue for systematic non-compliance.
1. Qualifying Downtime Criteria
RMC 98-2026 specifies that qualifying downtime must be: a genuine technical failure of the EIS, the accredited provider’s transmission infrastructure, or the taxpayer’s connectivity; documented at the time it occurs (not retroactively claimed); and communicated to the accredited provider when it arises. Planned downtime (scheduled maintenance by the provider) must be scheduled with advance notice and is not a basis for issuing manual invoices outside the maintenance window.
2. Retroactive Transmission Recovery Window
Manual invoices issued during approved downtime must be transmitted to the EIS within 24 hours of the system being restored. The 24-hour recovery window is firm — transmission after 24 hours is treated as a late submission. Late submissions are permissible with documentation of the downtime circumstances but may attract compliance review. The retroactive transmission uses the original invoice date, not the restoration date.
3. Downtime Documentation Requirements
For each downtime incident, the taxpayer must maintain: the start and end time of the outage, the evidence of the technical failure (error messages, provider communications, network logs), a list of all manual invoices issued during the outage, and confirmation of retroactive EIS transmission for each manual invoice. The downtime documentation must be retained as part of the e-invoicing compliance records for the full ten-year retention period.
ATP Changes Under RMC 98-2026
RMC 98-2026 clarifies changes to the ATP framework for covered taxpayers. From December 31, 2026, Group 1 taxpayers must follow applicable BIR restrictions on new ATP applications and the use of unused printed invoice booklets for covered transactions, subject to permitted downtime procedures. Businesses should also verify the prescribed surrender process and deadlines for unused booklets with their Revenue District Office (RDO) to avoid potential compliance violations. Romania Advintek supports businesses with e-invoicing integration and automated invoice processing solutions designed to streamline digital invoicing workflows, improve document management, and support applicable electronic invoicing compliance requirements.
How to Prepare Based on RMC 98-2026 Requirements
Covered taxpayers preparing for the December 31, 2026 deadline should review RMC 98-2026 against their current implementation plan in four areas: (1) confirm that their provider’s JSON schema implementation matches the current RMC specification; (2) confirm that their downtime procedure documentation meets the RMC’s specific requirements; (3) schedule the EIS certification process with their provider and confirm expected completion timing; and (4) plan the formal ATP surrender process to complete within 30 days of go-live.
Taxpayers who have not yet read RMC 98-2026 should treat it as required reading. The RMC is the operational specification for compliance — understanding it is not optional for businesses building a genuinely compliant e-invoicing implementation. The full text is available on the BIR website.
Conclusion
RMC 98-2026 is the technical backbone of Philippine e-invoicing compliance. It answers the implementation questions that RR No. 11-2025 and RR No. 26-2025 left open, providing specific, actionable technical specifications for data formats, transmission requirements, downtime procedures, ATP surrender, and EIS certification. Compliance with the revenue regulations is necessary but not sufficient — compliance with the technical requirements of RMC 98-2026 is what makes a covered taxpayer’s EIS implementation actually work as intended.
Nexright’s technical and regulatory teams have studied RMC 98-2026 in detail and implement its requirements in every client engagement. Contact us to review your current implementation against the RMC’s full requirements.
Frequently Asked Questions
1. Does RMC 98-2026 supersede any earlier BIR circulars on e-invoicing?
RMC 98-2026 supersedes any earlier BIR circulars or memoranda that addressed the same technical implementation topics. Where earlier guidance conflicts with RMC 98-2026, the RMC prevails as the more recent and specific issuance. Taxpayers who have been relying on earlier BIR circulars for technical guidance should review their implementation against the current RMC specification to confirm there are no divergences. The BIR periodically issues technical bulletins updating specific aspects of the RMC — monitor the BIR website for updates.
2. Can taxpayers request clarifications on RMC 98-2026 from the BIR?
Yes. Taxpayers with specific interpretive questions about RMC 98-2026 can submit formal requests for ruling or clarification to their BIR RDO or to the BIR’s Law and Legislative Division. For technical questions, the BIR also conducts e-invoicing information seminars and has a technical helpdesk accessible through the EIS portal. Document any verbal clarifications received from BIR personnel in writing — written BIR rulings or confirmation letters are more protective than undocumented verbal guidance.
3. Does RMC 98-2026 apply to voluntary e-invoicing adopters in Group 2 or 3?
Yes. Voluntary adopters — Group 2 or 3 taxpayers who choose to implement e-invoicing before their mandatory deadline — are subject to the same technical requirements as Group 1 mandatory adopters. The RMC’s data schema, transmission requirements, and certification process apply to all EIS participants, regardless of whether adoption is voluntary or mandatory. The compliance framework does not have a reduced technical standard for voluntary adopters.
4. What are the penalties for non-compliance specifically with RMC 98-2026 requirements?
Non-compliance with RMC 98-2026’s technical requirements is treated as non-compliance with RR No. 11-2025 for penalty purposes. Penalties are imposed under Section 264 of the NIRC: PHP 1,000 to PHP 50,000 per invoice for issuance of invoices that do not comply with BIR requirements (including the technical requirements of RMC 98-2026). Systematic or persistent violations may trigger Oplan Kandado business closure proceedings. The penalty framework treats technical non-compliance — for example, submissions missing mandatory data fields — the same as substantive non-compliance in invoice issuance.
5. Is there a published FAQ from the BIR on RMC 98-2026?
The BIR has published FAQ documents on its website addressing common questions about the e-invoicing mandate, including questions relating to RMC 98-2026’s technical requirements. These FAQs are updated periodically. Check the BIR website’s e-invoicing section for the most current FAQ publications. Industry groups and the Philippine Institute of Certified Public Accountants (PICPA) have also published guidance documents that synthesize and explain the BIR’s requirements in accessible language.
6. Has RMC 98-2026 been updated since it was first issued?
Since issuance, RMC 98-2026 has been supplemented by technical bulletins and corrigenda addressing specific implementation questions — particularly on the JSON schema specification, which has been updated to address edge cases identified during early testing. As of October 2026, the core provisions of RMC 98-2026 remain in force, but confirm with your accredited provider that their implementation reflects any post-issuance technical updates. Providers are responsible for tracking and implementing BIR technical updates to the EIS specification.
7. Where can I get the full text of RMC 98-2026?
The full text of RMC 98-2026 is available on the BIR website at bir.gov.ph under the “Issuances” section (Revenue Memorandum Circulars). The BIR website search function can locate the document by issuance number. Additionally, the BIR’s EIS portal at eis.bir.gov.ph includes a resource library with the key regulatory documents, technical specifications, and annexes relevant to e-invoicing compliance. BIR-accredited providers also maintain copies of the current regulatory requirements as part of their compliance onboarding materials.
Source by:
Image by Magnific
