BIR EIS e-invoicing compliance before 31 December 2026
Structured JSON invoices, digitally signed and transmitted to the BIR Electronic Invoicing System within three calendar days — built into your ERP rather than bolted on beside it.
What the EIS mandate requires
The Electronic Invoicing System is the BIR's platform for receiving invoice data directly from taxpayers' systems. Under Revenue Regulations No. 11-2025 (issued 27 February 2025, effective 14 March 2025) — with the first-group deadline extended by Revenue Regulations No. 26-2025 (issued 5 September 2025) — covered taxpayers must transmit invoice data electronically, not merely produce a digital-looking document.
The obligation rests on Sections 237 and 237-A of the National Internal Revenue Code, as amended by the CREATE MORE Act.
Who must comply by 31 December 2026
The first compliance group covers:
- Taxpayers registered with the Large Taxpayers Service (LTS)
- Taxpayers classified as large under the Ease of Paying Taxes Act — broadly, annual gross sales above ₱1 billion
- E-commerce and internet-based businesses — digital goods, digital services and platform commerce
- Taxpayers using a Computerized Accounting System (CAS), Computerized Books of Accounts (CBA), or e-invoicing software
Branches are covered as well as head offices. The fourth category is the one most often missed: if you already run a registered CAS — which many mid-sized Philippine businesses do — you are in the first group regardless of your revenue. Remaining taxpayer categories, including exporters, point-of-sale users and registered business enterprises with incentives, follow on dates the BIR has yet to announce.
Not sure which group you fall into? Classification turns on your BIR registration and your current systems, not on headcount. Send us your situation and we will tell you plainly — this is a factual question, not a sales one.
The technical requirements
| Requirement | Detail |
|---|---|
| File format | Structured JSON. XML is accepted as an internal format but not for transmission to the BIR. |
| Digital signature | Each invoice must be validated with a digital signature before transmission. |
| Transmission | System-to-system API connection between your invoicing or ERP software and the BIR EIS. Manual upload is not the compliance path. |
| Timing | Invoice data must reach the EIS within three calendar days of the transaction. |
| Data elements | A minimum set of roughly 54 fields, including seller and buyer TIN, timestamped issue date, line-item detail, VAT rate and grand total. |
Penalties for non-compliance
Failure to comply with the e-invoicing mandate carries penalties of ₱1,000 to ₱50,000 per offence under the Tax Code. The larger commercial exposure is operational: if you cannot issue a compliant invoice, you cannot bill, and collections stop. That risk is why we push clients to cut over with time for parallel running rather than in the final weeks of December.
How we deliver EIS readiness
- Scope confirmation. We establish which compliance group applies to your entity and each of its branches.
- Data readiness. The ~54 required elements are mapped against your master data. This is where most projects discover missing buyer TINs and inconsistent item descriptions — it is better to find that in month one than in December.
- Generation and signing. Business Central produces the structured JSON payload and applies the digital signature as part of the posting flow, not as a separate clerical step.
- Transmission. System-to-system connection to the EIS, with retry handling and a transmission log you can evidence during audit.
- Parallel run. Live invoices transmitted alongside your existing process until the acknowledgement rate is clean, then cutover.
EIS and CAS together
These two obligations interlock. Holding a registered CAS puts you in the first EIS group; conversely, building EIS transmission into a system that is not properly registered creates a documentation gap. We sequence CAS registration and EIS readiness as one programme inside the Business Central implementation.
This page summarises publicly available regulatory information for planning purposes. It is not tax advice. Confirm your specific obligations with your tax adviser or your Revenue District Office.
Frequently asked questions
Does the 31 December 2026 deadline apply to my business?
Is a PDF invoice sent by email enough?
How long does EIS readiness take to implement?
What are the penalties for missing the deadline?
Do we need a separate e-invoicing vendor on top of our ERP?
Find out where you stand before Q4
Tell us your BIR registration type and current systems. We will confirm which compliance group applies and what readiness actually requires for your setup.