Philippines BIR E-Invoicing Mandate 2026: EIS, ESRS & Compliance Guide

The Philippines is moving from paper-based invoicing to a mandatory electronic invoicing and sales reporting system, and the deadline is closer than most finance teams realize. The Bureau of Internal Revenue (BIR) requires covered businesses to issue electronic invoices and transmit sales data digitally, with full Phase 1 enforcement set for December 31, 2026. This guide breaks down what the mandate covers, who must comply, how the process works, and what businesses need to prepare before the deadline.

What Is the BIR E-Invoicing Mandate?

The BIR e-invoicing mandate is a legal requirement under the TRAIN Law (RA 10963) and the CREATE MORE Act that obligates covered taxpayers in the Philippines to generate electronic invoices and receipts, digitally sign them, and transmit sales data to the BIR through two connected systems: the Electronic Invoicing System (EIS) and the Electronic Sales Reporting System (ESRS). In short, businesses that fall within scope must stop relying solely on manual or paper invoicing and adopt a digital, auditable, government reported invoicing process.

Timeline: From TRAIN Law to the 2026 Deadline

The mandate did not appear overnight. It has developed in stages:

• RA 10963 (TRAIN Law): The legal foundation that introduced mandated e-invoicing for Large Taxpayers, exporters, and e-commerce platforms.
• 2022, EIS Pilot: RR 11-2025, together with RR 8-2022 and RR 9-2022, launched pilot testing with 100 selected Large Taxpayers.
• RR 11-2025 Regulations: Formalized expanded compliance guidelines and updated technical specifications for the rollout.
• December 31, 2026, Mandate: Phase 1 becomes fully mandatory for Large Taxpayers, e-commerce operators, and Computerized Accounting System (CAS) users.

Covered Taxpayers: Phase 1 and Phase 2

The rollout is happening in two phases, and knowing which one applies to your business determines your compliance timeline.

Phase 1 inclusions (enforceable mandate):

• Large Taxpayers Service (LTS): Taxpayers officially classified under the BIR LTS division, generally those with roughly ?1 billion or more in gross sales or revenue.
• Exporters and Importers: Businesses engaged in the export of goods or services.
• E-Commerce Operators: Digital platforms, online merchants, and digital service providers.
• CAS / CBA Users: Entities using Computerized Accounting Systems or Computerized Books of Accounts.

Phase 2 expansion scope:

• Non-LTS Medium and Enterprise Entities: Expansion to medium sized commercial taxpayers.
• All Remaining Business Taxpayers: A general nationwide rollout across regional district offices (RDOs).
• POS and CR Systems: Full integration of Point of Sale and Cash Register terminals across retail chains.

If any covered taxpayer or business activity is registered as a branch office, the Head Office and all its branch offices are also mandated to issue electronic invoices. It is not just the branch that met the threshold. A single branch triggering LTS or CAS criteria brings the entire corporate Tax Identification Number (TIN) network into scope, ensuring enterprise-wide compliance.

Mandatory exemptions included

• Micro and Small Taxpayers: Non-LTS small businesses below prescribed annual revenue thresholds, until future Phase 2 phases apply.
• Non-VAT Registered Entities: Small vendors under threshold that do not use a CAS.
• Foreign Non-Resident Vendors: Entities without a Philippine Permanent Establishment (PE) or Philippine tax registration.

EIS vs ESRS

EIS and ESRS are often mentioned together, but they serve different functions in the compliance pipeline.

In simple terms, EIS handles the structured generation, cryptographic signing, and issuance of e-invoices and e-receipts between seller and buyer. ESRS handles the near real time, post-issuance transmission of that sales data to the BIR's central database. A middleware layer typically sits between an enterprise's ERP or CAS and these two BIR APIs, translating and routing data so the two systems work together seamlessly.

Philippines E-Invoicing: Phase 1 vs Phase 2

The Philippines e-invoicing process can be understood in two stages. Phase 1 focuses on creating and delivering the electronic invoice, while Phase 2 adds BIR EIS validation, acknowledgement, and error handling.

Phase 1: Invoice Creation and Delivery

In Phase 1, the process starts with the seller's ERP or POS system. Invoice data is sent to an e-invoicing platform, which processes the electronic invoice and delivers it to the buyer.

Seller ERP/POS ? E-Invoicing Platform ? Buyer

The focus is on connecting existing business systems with an e-invoicing solution to generate and exchange invoices electronically.

Phase 2: BIR EIS Validation

Phase 2 extends the workflow by connecting the e-invoicing platform with BIR EIS (Electronic Invoicing System).

The platform prepares the invoice as structured JSON, applies the required JWS signature, and submits it to BIR EIS for validation.

E-Invoicing Platform ? JSON + JWS Signature ? BIR EIS ? Accepted / Rejected

• Accepted: An acknowledgement ID is returned and recorded for tracking.
• Rejected: The invoice moves to a technical error queue, where issues such as malformed JSON or an invalid signature can be corrected and the invoice resubmitted.
• Business/content error identified later: A credit or debit memo can be issued while referencing the original invoice.

Prepare your ERP, CAS, or POS environment for electronic invoicing with Taxilla's Philippines e-invoicing solution. Automate invoice generation, JSON and JWS processing, BIR EIS integration, acknowledgements, error handling, and compliance workflows through one connected platform.