BIR EIS and e-invoicing in the Philippines

BIR e-invoicing is not simply emailing a PDF invoice. Under Revenue Regulations No. 11-2025, a covered taxpayer must do two distinct things: issue the invoice or receipt in electronic form, and transmit the underlying sales data to the Bureau of Internal Revenue's Electronic Invoicing System (EIS). The second part — the transmission — is what makes this a tax-reporting regime rather than a document-format preference.

The legal hook is Sections 237 and 237-A of the Tax Code, as amended by the Ease of Paying Taxes Act (RA 11976) and later the CREATE MORE Act (RA 12066). Section 237-A is the provision that obliges covered taxpayers to electronically report their sales to the BIR. RR 11-2025 is the implementing regulation that turns that statutory requirement into concrete obligations, formats, and dates, building on the earlier RR 8-2022 pilot.

The two obligations under RR 11-2025

• Issuance: produce invoices and receipts electronically rather than only on paper
• Transmission: send the sales data — invoices, receipts, credit and debit notes — to the EIS
• Format: structured JSON, not a scanned image or PDF
• Authenticity: each document signed with a JSON Web Signature (JWS)
• Timing: transmitted within three calendar days of the transaction

RR 11-2025 phases the obligation. The first wave — the group originally due by 14 March 2026 and now due by 31 December 2026 — covers taxpayers registered under the Large Taxpayers Service (LTS), taxpayers classified as large under the EOPT Act (RA 11976) and RR 8-2024, and sellers engaged in e-commerce or internet transactions. Within the e-commerce group, micro taxpayers are excluded, so the smallest online sellers are not pulled in by this wave.

A second wave is named in the regulation but not yet switched on: exporters of goods and services under Sections 106 and 108 of the Tax Code, Registered Business Enterprises enjoying incentives under Section 304(D), and businesses using POS systems. These become covered once the BIR confirms its system can process and securely store their data, plus any other taxpayers the Commissioner later designates. The obligation reaches them eventually — just not necessarily on the December 2026 date.

Once a covered taxpayer issues an invoice, the data does not sit in the seller's books waiting for a monthly return. It is converted to a structured JSON file, signed with a JSON Web Signature, and sent to the EIS through an API. The EIS validates the document and returns an acceptance or rejection — a per-document handshake rather than a batch upload reviewed weeks later.

The transmission window is three calendar days from the transaction, covering sales, receipts, and credit or debit notes. That short window is deliberate: it places the Philippines close to the continuous-transaction-control model used in markets like South Korea, where the tax authority sees sales in near real time. For a system architect, the practical consequences are queuing, retry, and reconciliation: the software must keep selling if the EIS is briefly unreachable, then transmit and confirm within the window, and keep a clean record of what was accepted, rejected, and resent.

This is also why a generic or foreign product so often fails here. Issuing a receipt is the easy part. Producing valid signed JSON, holding an API connection to the EIS, handling rejections, and reconciling the acknowledgements is the compliance layer — and it is the layer most off-the-shelf tools simply do not have for the Philippine regime.

E-invoicing rides on top of a registered system, and the registration rules changed before the e-invoicing push. RMC 5-2021 removed the old Permit to Use (PTU) for a Computerised Accounting System and its components. Instead of waiting on a PTU and a systems demonstration, a taxpayer now registers the system and receives an Acknowledgement Certificate — targeted within three working days of complete documents — with the old BIR Form 1900 and the demonstration dispensed with.

For a covered business this means two things travel together. The accounting or POS system must be registered with the BIR (now via the Acknowledgement Certificate route), and — where the taxpayer is in a covered wave — that same system must issue electronic documents and transmit them to the EIS. A BIR-accredited POS that cannot transmit to the EIS is only half-compliant for a covered taxpayer; e-invoicing is an additional obligation layered on registration, not a substitute for it.

What changed with RMC 5-2021

• No more Permit to Use (PTU) for CAS and related components
• An Acknowledgement Certificate is issued instead, targeted within three working days
• BIR Form 1900 and the systems demonstration were dispensed with
• Registration still applies — e-invoicing is added on top, not in place of it

RR 11-2025 was issued on 27 February 2025 with a first-wave compliance date of 14 March 2026. On 5 September 2025 the BIR issued RR 26-2025, which amended the transitory provisions and extended that date to 31 December 2026. The stated reason was the operational work covered taxpayers needed to reconfigure their systems and transition to e-invoicing.

The extension is breathing room, not a reprieve. The direction of travel — structured JSON, signed documents, near-real-time transmission, expanding coverage — is fixed by statute and prior issuances, and the second wave is already named in the regulation. A covered business that treats 31 December 2026 as a comfortable horizon rather than a build deadline risks discovering its current software cannot transmit at all. The safe reading is to design for EIS transmission now and use the extended runway to test, not to defer the question.

For a small, non-covered seller, an off-the-shelf invoicing tool is usually enough — the e-invoicing obligation may not yet reach them. The calculus changes sharply for large taxpayers and multi-branch operators who are squarely in the first wave: per-terminal and per-branch fees compound monthly, the EIS rules are non-negotiable, and many generic products cannot produce signed JSON or hold an EIS connection at all.

At that scale the question is whether to keep paying a growing subscription for a system you do not own and cannot extend to the EIS, retrofit a connector onto software that was never designed for it, or build invoicing and POS shaped around the operation — BIR-registered, EIS-ready, signing and transmitting from the first receipt, with no per-terminal fee. That build-versus-buy decision, with the December 2026 clock running, is exactly what Orkids exists to handle for Philippine enterprises.