BIR-Compliant Philippines e-Invoicing Solution
Built to support BIR e-Invoicing Philippines’ requirements for JSON invoice generation, JWS digital signing, and near real-time invoice transmission.
Why BIR e-Invoicing Matters in the Philippines
- Philippines e-Invoicing is mandated by the Bureau of Internal Revenue (BIR) under the TRAIN Law (RA 10963, Section 237-A) and implemented through the Electronic Invoicing System (EIS).
- The EIS requires covered taxpayers to issue invoices in a structured electronic (JSON) format and transmit sales data to the BIR in near real time, a simple PDF or scanned copy no longer satisfies the requirement.
- Structured invoicing improves data accuracy, lowers rejection risk, and strengthens audit readiness.
- e-Invoicing BIR compliance supports the BIR’s broader Digital Transformation (DX) program and tighter VAT/sales reporting.
Key Challenges Businesses Face
Businesses adopting e-invoicing Philippines requirements typically encounter the following challenges:
- Moving from manual, PDF, or legacy invoicing to structured JSON invoices that meet BIR field requirements.
- Integrating ERP, POS, and accounting/CAS systems with the EIS API for automated invoice generation and transmission.
- Applying valid JSON Web Signatures (JWS) and securing the Permit to Transmit (PTT) and system certification before going live.
- Adapting to the Ease of Paying Taxes (EOPT) Act reclassification, under which the Sales Invoice is now the primary document for both goods and services, while the Official Receipt serves as a supplementary document.
- Handling high transaction volumes across multiple branches without breaching BIR transmission timelines.
- Maintaining accurate and complete invoice data to minimize rejections and preserve audit-ready records throughout the statutory retention period.
Everything You Need to Know About Philippines e-Invoicing
This timeline maps every major BIR e-Invoicing Philippines regulation and deadline, from the 2017 TRAIN Law through the planned 2027 enforcement date.
| Stage / Regulation | Timeline / When | Model | Transaction Type | Format of E-Invoice | Additional Notes |
|---|---|---|---|---|---|
| TRAIN Law (RA 10963), Section 237-A | December 2017 (Effective January 2018) | Legislative Framework |
B2B
B2C B2G |
— | Required the BIR to establish the Electronic Invoicing/Receipting and Sales Reporting System (EIS). Later amended by the CREATE MORE Act (RA 12066). |
| EIS Pilot (RR 8-2022 & RR 9-2022) | 1 July 2022 | Near Real-Time Reporting (EIS) |
B2B
B2C B2G |
Structured JSON | Pilot launched for selected exporters, e-commerce businesses, and Large Taxpayer Service (LTS) entities. Invoice issued first, then sales data transmitted to BIR. |
| EIS Pilot Suspension | November 2023 – February 2025 | Pilot Suspended | — | — | BIR paused active EIS transmissions due to system maintenance and implementation challenges. |
| EOPT Act (RA 11976) & RR 7-2024 | 2024 | Document Classification |
B2B
B2C |
Sales Invoice / Official Receipt | Sales Invoice became the primary tax document, while Official Receipt became supplementary for reporting purposes. |
| RR 11-2025 (CREATE MORE Act) | Effective 14 March 2025 | Structured Reporting (EIS) |
B2B
B2C B2G |
Structured JSON (XML Supported for Issuance) | Expanded mandatory scope to large taxpayers, e-commerce businesses, and businesses using compliant invoicing software. Sales data must be transmitted within three calendar days. |
| RR 26-2025 (Deadline Extension) | 31 December 2026 | Reporting (EIS) |
B2B
B2C B2G |
Structured JSON | Compliance deadline extended to 31 December 2026. Exporters and incentive enterprises remain under a future implementation wave. |
| Cross-Border e-Invoicing (JAO No. 001-2025) | Phased Rollout from Early 2027 | Customs e-Invoicing (CEI) |
Cross-Border
|
Structured Electronic Invoice | Foreign exporters must register and submit customs invoices through the government CEI portal. Separate from the domestic EIS. |
| Wave 1 – Full Mandatory Enforcement | 1 January 2027 | Reporting (EIS) |
B2B
B2C B2G |
Structured JSON with JWS Signature | Mandatory electronic invoicing for in-scope taxpayers. Non-compliant invoices become invalid for VAT claims and are subject to statutory penalties. |
| Wave 2 – Exporters & Incentive Enterprises | TBD | EIS + ESRS |
B2B
B2C B2G |
Structured JSON | Exporters, PEZA/BOI incentive enterprises, and certain POS-based retailers will be onboarded under a future BIR regulation. |
Philippines BIR EIS e-Invoicing Process Flow
Cygnet.One connects ERP, POS, CAS, and billing systems to BIR EIS — structured JSON invoices, JWS signing, and 3-day transmission
Cygnet.One connects your ERP, POS, and billing systems to the BIR EIS generating structured JSON invoices, applying JWS signatures, and transmitting sales data in near real time through a secure, scalable architecture.
How It Works
1
Invoice Creation
Generate invoice data directly from your ERP, POS, accounting, or billing application.
2
Structure & Validation
Convert invoice data into structured JSON and validate it against BIR EIS requirements and mandatory tax fields.
3
Digital Signing & Issuance
Apply a JWS digital signature and issue the compliant invoice to the buyer.
4
Secure Transmission to BIR
Transmit signed invoice data securely to the BIR EIS and receive acknowledgment and status updates.
5
Compliance & Audit Readiness
Archive invoices, digital signatures, and acknowledgments securely to meet statutory retention and audit requirements.
Cygnet.One streamlines the complete Philippines EIS invoice lifecycle—from invoice creation and JSON validation to digital signing, secure BIR transmission, and long-term archival—ensuring regulatory compliance and operational efficiency.
Trust metrics
Organizations worldwide rely on our enterprise-grade e-Invoicing solution.
14+ global accreditations
1 scalable platform
25+ years of expertise
5 billion+ documents generated
250+ ERP integrations
1000+ enterprise clients
Our Accreditations
Cygnet.One maintains regulatory compliance and certifications across multiple jurisdictions, ensuring enterprises can adopt a trusted digital invoicing solution for global operations.
Client Logos
Sub title
PEPPOL
Certified Access Point (AP) & SMP
MoF-Approved
UAE e-Invoicing Service Provider
FTA
Accredited Tax Accounting Software Vendor
ZATCA
Compliant e-Invoice Solution
IMDA
Accredited InvoiceNow Access Point Provider (AP)
BOSA
Compliant e-Invoicing Software
HMRC
Recognised MTD VAT Software
GSTN
Authorised GST Suvidha Provider (GSP)
IRP
GSTN approved Invoice Registration Portal (IRP)
MDEC
Accredited Peppol Service Provider (SP) & PRSP
Australia
Peppol Service Provider
New Zealand
Approved Access Point Provider
ZRA
Certified Smart Invoice Software Vendor
OTA
Approved e-Invoicing service provider
DBNAlliance
Member
Resources
From Manual to Automated: Enhancing Payment Reconciliation Accuracy and Efficiency…
Cygnet Digital helped a leading multi-brand retail & manufacturing company to simplify, improve and support the complexity in documentation, and…
Overcoming e-Invoicing Implementation Challenges for Global Businesses
Learn how global businesses can overcome e-Invoicing implementation challenges, including multi-country compliance, data accuracy, and change management.
The Role of AI in Enhancing e-Invoicing Efficiency in the…
AI in e-invoicing addresses complex situations & offers predictive capabilities & benefits that enhance e-invoicing. Know more on the benefits…
Adopt a future-ready e-Invoicing solution trusted by businesses to automate workflows, meet the BIR's EIS mandate, and scale efficiently.
FAQs
The EIS is the Bureau of Internal Revenue’s platform for receiving electronic invoice and sales data. Mandated under the TRAIN Law (RA 10963, Section 237-A) and rolled out from 1 July 2022 under RR 8-2022, it requires covered taxpayers to issue structured electronic (JSON) invoices and transmit sales data to the BIR in near real time.
No. The Philippine EIS is a reporting/transmission model. The taxpayer generates the JSON invoice, signs it with a JSON Web Signature (JWS), issues it to the buyer, and transmits the sales data to the BIR. There is no government-issued clearance number or QR code that the invoice must obtain before it is valid, and it does not use a PEPPOL four-corner network.
RR 11-2025 also extended the mandate to taxpayers using Computerized Accounting Systems (CAS), Computerized Books of Accounts (CBA) with electronic invoicing, or any other invoicing software capable of generating and transmitting structured data regardless of revenue size. If your business runs any ERP, accounting, or billing software, you should verify whether this triggers your obligation under RR 11-2025.
No. The EIS requires a structured electronic invoice in JSON format. Emailing or printing a PDF does not meet the requirement, the data must be structured, signed with a JWS, and transmitted to the BIR.
Under the Ease of Paying Taxes Act (RA 11976) and RR 7-2024, the Sales Invoice became the primary document for the sale of both goods and services, and the Official Receipt was repositioned as a supplementary document. This affects which document type your system issues and transmits.
Non-compliance can trigger administrative penalties under the National Internal Revenue Code, and non-compliant invoices can be challenged putting input VAT claims and deductibility at risk and increasing audit and assessment exposure. (Confirm specific penalty amounts against current BIR issuances.)
Cygnet.One connects to SAP, Oracle NetSuite, Microsoft Dynamics, and local/custom accounting (CAS) systems, along with POS and e-commerce platforms. It maps your data into the EIS JSON format, applies JWS signing, validates against EIS rules, and transmits to the BIR with audit-ready archival.