The -Ber months are here: The countdown to the e-invoicing deadline on 31 December 2026

September 1 means one thing to many Filipinos: Christmas magic is already in the air. In the Philippines, the start of the –ber months is a time when Christmas songs are starting to play, malls and other establishments are adorned with lights and garlands, and the familiar excitement of the holiday countdown has begun once again. Before long, back-to-back family gatherings and gift shopping will fill calendars and Filipinos will be counting the days until year-end. But for taxpayers covered by the Bureau of Internal Revenue's (BIR) electronic invoicing (e-invoicing) rules, there is another date worth counting down to: 31 December 2026. 

As the -ber months begin, taxpayers may have another countdown on their minds. The BIR recently issued a draft Revenue Memorandum Circular (RMC) on e-invoicing and opened it for public consultation, providing a clearer picture of how the new regime may operate.  

More importantly, the draft retains the 31 December 2026 compliance deadline for covered taxpayers. With less than half of the year remaining, the focus is no longer just on whether e-invoicing is coming, but on whether businesses are prepared when the deadline arrives. 

Preparing for the deadline  

Revenue Regulations (RR) No. 11-2025 established the framework for e-invoicing and electronic sales reporting. The regulations seek to modernize invoicing by requiring covered taxpayers to issue invoices in electronic form and maintain invoice information in a structured format that can be electronically processed. Subsequently, RR No. 26-2025 amended the transitory provisions and established 31 December 2026 as the implementation deadline for identified taxpayers. 

For affected businesses, the deadline may require investments in software, process redesign, internal controls, and employee training. Early preparation may therefore be essential. 

Key updates in the Draft RMC 

1. Clear distinction between Electronic Invoicing and Electronic Sales Reporting  
RR 11-2025 discusses both concepts, but the draft RMC expressly clarifies that the obligation to issue electronic invoices is separate and distinct from the obligation to comply with electronic sales reporting. Taxpayers covered by the e-invoicing mandate will only be required to comply with electronic sales reporting upon issuance of separate implementing guidelines, unless already specifically notified by the BIR.  

This is one of the most important clarifications. It supports the position that compliance with e-invoicing by 31 December 2026 does not automatically mean immediate ESRS compliance. 

2. Non-JSON formats may continue to be used under the proposed structured data framework 
JSON (JavaScript Object Notation) is a structured data format that allows computers to store, process, exchange, and interpret information efficiently. In the context of e-invoicing, JSON is not necessarily the invoice that a customer sees. Rather, it is the digital language that organizes the information behind the invoice, allowing invoice data to be electronically extracted, validated, processed, and transmitted. Viewed this way, JSON is not the invoice itself, but the digital blueprint behind electronic invoice data. 

This distinction is important because a scanned image or PDF copy of a paper invoice should not automatically qualify as an electronic invoice. Under the draft RMC, an electronic invoice must be system-generated, issued electronically, and capable of electronic extraction and transmission. 

The draft RMC further clarifies that while taxpayers may continue using non-JSON formats, the proposed annexes of the said RMC provide additional insight into the structured data that may be required for e-invoicing. Among the notable additions are the mandatory EIS Unique ID, which is a unique identifier assigned to each document transmitted to the EIS, and prescribed invoice-correction fields, including correction indicators, correction codes, and references to previously transmitted invoices being corrected. The annexes likewise introduce standardized data fields for handling adjustments, cancellations, returns, duplications, and other correction scenarios.  

3. PTI Electronic Invoice requirement 
The draft RMC introduces and outlines the requirements for securing a Permit to Issue (PTI) Electronic Invoice. This is a major new compliance requirement. Taxpayers may already possess: Computerized Accounting System (CAS) Acknowledgment Certificate (AC), or existing Permit to Use (PTU), but will still need a separate PTI to issue electronic invoices. 

4. Other Clarifications 
The draft RMC likewise provides additional guidance on several practical aspects of electronic invoicing: 

a. QR code requirement 
Electronic invoices will be required to contain a QR Code that serves as a verification feature and must appear on both the electronic and printed versions of the invoice. This appears to be a new operational requirement that taxpayers may need to consider when configuring their invoicing systems. 

b. New rules on invoice corrections 
The draft RMC prescribes a formal framework for correcting invoices. Adjustments resulting in a decrease in the invoiced amount are generally to be made through a Credit Note, while increases in the invoiced amount generally require the issuance of a new electronic invoice. More importantly, the draft expressly provides that an original electronic invoice may not be deleted, altered, or modified once issued. 

c. Branch-wide compliance 
Taxpayers operating through branch networks should note that compliance is imposed on the taxpayer as a whole. Thus, where a taxpayer is covered by the electronic invoicing mandate, both the head office and all branch offices may be required to issue electronic invoices even if the covered activity is undertaken only by certain branches. 

d. Downtime and contingency procedures 
The draft RMC addresses system downtime scenarios. In cases of technical malfunction, internet connectivity issues, power interruptions, cybersecurity incidents, force majeure events, or similar circumstances, taxpayers may use BIR-authorized manual invoices. However, manually issued invoices must subsequently be recorded and maintained once the system is restored, and downtime does not excuse compliance with invoicing and record-keeping obligations. 

Further guidance for taxpayers 

Despite the guidance provided by the draft RMC, taxpayers may still seek clarification in several areas. 

First, the draft provides that an original electronic invoice may not be deleted, altered, or modified after issuance. A decrease in the amount would generally require a credit note, while an increase would require a new electronic invoice. 

Further clarification may be needed on incorrect sales amounts discovered in a later quarter, inaccurate buyer information, duplicate transmissions, incorrect tax treatment, cancellations, and returns, including their accounting, VAT, withholding tax, and reporting implications. 

Second, the draft allows the use of BIR-authorized manual invoices during system downtime, technical malfunction, internet failure, power interruption, cybersecurity incidents, force majeure, or similar events. 

After restoration, manually issued invoices must be recorded; and downtime is not an excuse for failure to issue invoices.  

Taxpayers may benefit from clearer guidance on documenting downtime, notification requirements, and transaction controls, particularly where the 1,000-invoice backup limit may be insufficient for high-volume businesses. While the BIR is expected to issue post-restoration reconciliation procedures, further guidance on how manual transactions will be encoded, matched with electronic records, and reported once systems are restored would also be helpful. 

Third, the draft defines Electronic Invoicing Solution Providers (ESP) but reserves their accreditation procedures for a separate issuance. 

Taxpayers may likewise benefit from clearer guidance on ESP accreditation, including documentary requirements, security and data protection standards, record retention obligations, BIR access, service-provider liability, and procedures for handling transmission errors or system failures. 

Fourth, the draft requires covered taxpayers to secure a PTI Electronic Invoice before issuing electronic invoices. It refers to a sworn statement of compliance, process flow, sample invoice, and proof of system registration.  

Taxpayers may also welcome guidance on the forms, templates, documentary requirements, and procedures for securing a PTI Electronic Invoice. 

Finally, the draft does not fully specify the penalties for non-compliance or delayed implementation. Greater clarity on the consequences of non-compliant invoices, unapproved systems, unreconciled downtime transactions, omitted information, and inaccurate transmissions would be helpful. 

A clear and legally supported penalty framework would give taxpayers greater certainty as they prepare for implementation. 

The public consultation presents a valuable opportunity to refine the draft RMC and provide greater clarity in areas where taxpayers continue to seek guidance. As the BIR evaluates comments and position papers submitted by stakeholders, many taxpayers will be hoping that the final issuance addresses practical implementation concerns and provides more detailed guidance before the full rollout of the electronic invoicing framework. 

In the meantime, the countdown to 31 December 2026 continues. Businesses should use the remaining time to assess their systems, review internal processes, identify implementation gaps, and monitor future BIR issuances that will shape the final compliance requirements. 

After all, this -ber season is about more than festive lights and holiday cheer. For covered taxpayers, it is a reminder that the countdown to compliance is already underway.

Let's Talk Tax is a weekly newspaper column of P&A Grant Thornton that aims to keep the public informed of various developments in taxation. This article is not intended to be a substitute for competent professional advice.

As published in BusinessWorld, dated 01 September 2026