The Philippines E-Invoicing Mandate under Revenue Regulations No. 11-2025 and the December 31, 2026 deadline for Group 1 taxpayers represent a significant change to BIR tax administration infrastructure. Understanding the full scope of the mandate — who it covers, what it technically requires, and how it compares to equivalent systems in other ASEAN countries — is essential for every covered business and for the advisors supporting them.
This guide provides a complete authoritative overview of the Philippines’ e-invoicing mandate: the regulatory framework, technical requirements, covered taxpayer groups, registration process, and what businesses should be doing right now to prepare. Whether you are a large enterprise already deep in implementation or an SME that has recently discovered you are covered, this article gives you the complete picture.
Key Takeaways
- The Philippines’ e-invoicing mandate is established under RR No. 11-2025, amended by RR No. 26-2025, and detailed by RMC 98-2026 — with the December 31, 2026 deadline applying to Group 1 taxpayers.
- The BIR Electronic Invoicing/Receipting System (EIS) receives real-time invoice transmissions from covered taxpayers via BIR-accredited service providers.
- Covered Group 1 taxpayers include large taxpayers, CAS/CBA users, and e-commerce businesses — micro taxpayers below PHP 3 million in annual gross sales issuing manual invoices are exempt.
- The Philippines’ model is most similar to Malaysia’s MyInvois system — both require near-real-time transmission to a government repository rather than optional or periodic reporting.
- Non-compliant taxpayers face PHP 1,000 to PHP 50,000 in fines per invoice, Oplan Kandado business closure, and criminal liability under the NIRC.
What is E-Invoicing in the Philippines?
E-invoicing in the Philippines is a government-mandated system under which covered taxpayers must issue sales invoices and official receipts in a structured electronic format that is transmitted in real time to the BIR’s Electronic Invoicing/Receipting System. It is not simply the digitization of existing paper invoices — it requires that invoice data be captured in a machine-readable structured format (JSON) and transmitted via API to the BIR at the time of issuance.
The mandate is grounded in the TRAIN Law (Republic Act No. 10963), which amended the NIRC to authorize the BIR to require electronic invoicing and receipts. Revenue Regulations No. 11-2025 operationalized this authority into a specific compliance framework, replacing the earlier pilot programme rules from 2019. RR No. 26-2025 extended the Group 1 deadline from March 14, 2026 to December 31, 2026. RMC 98-2026 issued detailed technical and operational implementation guidance.
The system operates on a continuous transaction control (CTC) model — invoice data is transmitted to the government in real time as each transaction occurs, rather than through periodic batch reporting. This model, increasingly common among ASEAN tax authorities, allows the BIR to monitor gross sales, detect underreporting, and verify VAT compliance at the transaction level rather than waiting for periodic tax return filings. Understanding BIR tax compliance requirements helps businesses prepare their invoicing systems, improve transaction reporting accuracy, and maintain compliance with applicable Philippine tax regulations.
E-Invoicing Technical Requirements: Format, API, and Data Fields
The BIR EIS accepts invoice data in JSON format transmitted via a REST API. Covered taxpayers do not access the EIS directly — they transmit data through BIR-accredited service providers that connect to the EIS on their behalf. The provider is responsible for converting the client’s invoice data into the BIR-prescribed JSON structure and ensuring reliable, timely transmission.
The EIS assigns a unique reference number to each successfully validated invoice submission. This reference number must be displayed on the invoice document provided to the buyer and is the key indicator of a compliant e-invoice. Invoices that lack this reference number — because they were not transmitted to the EIS — are non-compliant regardless of how they were generated.
| Required Data Field | Description | Applies To |
|---|---|---|
| Seller TIN | Taxpayer Identification Number of the issuing business | All invoices |
| Seller Name and Address | BIR-registered business name and address of the seller | All invoices |
| Buyer TIN (if VAT-registered) | TIN of the purchasing entity for B2B transactions | B2B transactions |
| Invoice Number | Unique sequential invoice identifier | All invoices |
| Invoice Date | Date of transaction or document issuance | All invoices |
| Description of Goods/Services | Line-item description and quantity | All invoices |
| Net Amount (VAT-exclusive) | Transaction value before VAT | VAT-registered sellers |
| VAT Amount | Output VAT computed at applicable rate | VAT-registered sellers |
| Total Amount Due | Net amount plus VAT | All invoices |
| EIS Reference Number | Assigned by the BIR EIS upon successful transmission | All invoices |
Who Must Comply by the December Deadline?
Group 1 taxpayers must comply by the December 2026 e-invoicing deadline, set for December 31, 2026. This group covers three overlapping categories: BIR Large Taxpayers Service registrants, taxpayers using BIR-registered Computerized Accounting Systems or Computerized Books of Accounts, and businesses primarily operating in e-commerce. Many businesses fall into more than one category — a large corporation that uses a CAS and sells through an online platform may fall under multiple Group 1 coverage criteria.
The PHP 3 million micro taxpayer exemption applies only to businesses with annual gross sales at or below this threshold that also issue manual (paper) invoices. A micro taxpayer that uses any form of computerized billing or accounting system, or that conducts any portion of its sales through an online channel, may be covered under a different criterion. The exemption is narrower than many small business owners assume.
Who Needs to Register for E-Invoicing in the Philippines?
All covered taxpayers must register with the BIR EIS and obtain a Permit to Issue (PTI) Electronic Invoice before they can begin issuing compliant e-invoices. The PTI application is submitted to the taxpayer’s BIR Revenue District Office and requires documentation of the taxpayer’s chosen accredited provider, technical system details, and current CAS/CBA registration status where applicable.
The EIS certification process — a technical validation conducted by the BIR or delegated to an accredited testing body — must also be completed before a taxpayer can go live. This process confirms that the taxpayer’s system (or their provider’s system) correctly generates invoice data in the prescribed format and transmits it to the EIS without errors. The BIR electronic invoice submission process should be tested thoroughly, typically in conjunction with the provider’s testing environment, to help identify integration issues and prepare for reliable invoice transmission.
Taxpayers that are already registered as CAS/CBA users with the BIR do not need to re-register their accounting system for e-invoicing purposes, but must still obtain a PTI and complete EIS certification for their specific e-invoicing setup. The PTI and the CAS/CBA registration are separate BIR authorizations.
How to Prepare for E-Invoicing in the Philippines
1. Assess Your Coverage and Deadline
Confirm whether your business falls within Group 1 and is subject to the December 31, 2026 deadline. Review your taxpayer classification, your CAS/CBA registration status, and your sales channels. If any portion of your business involves e-commerce, large taxpayer registration, or a BIR-registered CAS, you are almost certainly covered.
2. Evaluate Your Current Systems
Assess whether your current ERP, POS, or billing software can export invoice data in the structured format required by the BIR EIS. Most modern ERP systems — SAP, Oracle, Microsoft Dynamics have BIR EIS integration modules available. Older or custom-built systems may require significant development work. Identify your integration path before selecting a provider.
3. Select a BIR-Accredited Provider
Review the BIR’s official list of accredited e-invoicing service providers. Focus on providers with pre-built integrations for your specific software platform, a transparent onboarding timeline, a strong local compliance team, and a credible security posture. Request references from other Philippine businesses using the provider’s platform before contracting.
4. Apply for Your PTI
Submit your PTI application to your BIR RDO as soon as you have selected a provider. The PTI application requires your Certificate of Registration, provider accreditation details, and a description of your e-invoicing system. Allow several weeks for BIR processing and factor this into your overall implementation timeline.
5. Complete Integration and Testing
Work with your provider to integrate your billing system with the BIR EIS. Complete end-to-end testing in the BIR’s sandbox environment, verify that EIS reference numbers are correctly received and displayed on invoices, and confirm that your system handles error responses from the EIS appropriately. Document all test results as part of your compliance evidence file.
Philippines E-Invoicing vs Malaysia, Singapore, and Indonesia
The Philippines’ EIS model sits within a broader regional trend toward mandatory e-invoicing in ASEAN, but each country has implemented its own approach to mandate scope, technical requirements, and enforcement timelines. Understanding these differences matters for businesses operating across borders.
For Philippine businesses with operations in Malaysia or Indonesia, the key practical similarity is the near-real-time or pre-approval government connectivity requirement. A technology provider that already supports Malaysia’s MyInvois or Indonesia’s e-Faktur is likely to have the regional infrastructure needed to support BIR EIS integration as well. Multi-country e-invoicing platforms can significantly reduce the total cost of regional compliance compared to managing separate vendor relationships per country.
| Country | System | Model | Deadline/Status |
|---|---|---|---|
| Philippines | BIR EIS | Near-real-time CTC — invoices transmitted to BIR via accredited providers | Dec 31, 2026 (Group 1) |
| Malaysia | MyInvois (LHDN) | Near-real-time CTC — invoices submitted to LHDN portal for validation | Phased by revenue threshold — underway |
| Singapore | InvoiceNow (IRAS/IMDA) | PEPPOL-based network — voluntary for most; mandatory for government suppliers | Government suppliers mandated; others voluntary |
| Indonesia | e-Faktur (DGT) | Pre-approval model — VAT invoices require prior DGT approval before issuance | Mandatory for PKP (VAT-registered) taxpayers |
What Should I Do Before December 2026?
With less than three months remaining until the December 31, 2026 deadline, covered taxpayers that have not yet begun their compliance projects face a compressed implementation window. The critical path items — selecting a provider, completing integration, obtaining a PTI, and completing EIS certification — each take time and should be sequenced carefully.
Businesses that have already selected a provider but are mid-integration should focus on completing end-to-end testing by early December to leave time for resolving any issues before the deadline. Businesses that have not yet selected a provider should treat this as their most urgent action item. Businesses that are uncertain about their coverage status should confirm immediately with their BIR RDO — uncertainty is not a defence for non-compliance.
Conclusion
The Philippines’ e-invoicing mandate is a permanent structural change to tax administration, not a temporary initiative. Group 1 taxpayers have until December 31, 2026, and the window for orderly implementation is closing. The combination of a clear legal framework, a functioning EIS infrastructure, and a growing ecosystem of accredited providers means that the tools for compliance are available — what remains is for covered businesses to commit to the implementation and execute it before the deadline.
Nexright provides end-to-end e-invoicing compliance support for covered taxpayers — from coverage assessment through provider selection, integration support, PTI application, and ongoing compliance management. Contact our team today to start your compliance journey.
Frequently Asked Questions
1. Does the e-invoicing mandate apply to all types of sales, including cash sales to consumers?
Yes. The BIR e-invoicing mandate covers all taxable sales transactions — both B2B and B2C — made by covered taxpayers. For cash sales to consumers, the covered taxpayer must issue a BIR-compliant e-invoice (or official receipt for service transactions) and transmit it to the EIS. The buyer’s TIN field may be left blank for B2C transactions where the buyer is not a VAT-registered entity.
2. Can I issue both e-invoices and printed invoices to the same customer?
After the e-invoicing transition, the primary invoice document for covered taxpayers must be the EIS-compliant electronic invoice. A printed copy of the e-invoice — one that includes the BIR EIS reference number — may be provided to the buyer as a supplementary document. Issuing a separate printed invoice without an EIS reference number alongside a compliant e-invoice is not recommended and may create confusion during audits.
3. What is the difference between RR 11-2025, RR 26-2025, and RMC 98-2026?
RR No. 11-2025 is the primary regulation establishing the e-invoicing mandate framework. RR No. 26-2025 is an amending regulation that extended the Group 1 compliance deadline from March 14, 2026 to December 31, 2026. RMC 98-2026 is a revenue memorandum circular that provides detailed technical and operational implementation guidance, including data field specifications, API requirements, and downtime procedures. All three documents must be read together for complete compliance guidance.
4. Is e-invoicing the same as the BIR’s sales reporting requirement?
E-invoicing and electronic sales reporting are related but distinct. E-invoicing refers to the issuance and EIS transmission of individual transaction documents. Electronic sales reporting refers to the periodic submission of aggregated sales data to the BIR — a requirement that applies under the EIS framework and includes data fields beyond what appears on individual invoices. RMC 98-2026 addresses both requirements, and covered taxpayers must comply with both.
5. Can my business use different e-invoicing providers for different branches or systems?
Yes. A business with multiple branches or multiple billing systems can use different accredited providers for different parts of its operations, provided each provider connection is properly configured and each invoice includes the correct branch-level taxpayer identification information required by the BIR. However, managing multiple provider relationships increases administrative complexity and the risk of data inconsistencies across the EIS record.
6. What happens to existing BIR-registered CAS systems under e-invoicing?
CAS users are covered under Group 1 precisely because their existing computerized accounting systems should facilitate the technical integration required for e-invoicing. However, CAS registration with the BIR does not automatically make your system e-invoicing compliant — you still need to integrate with an accredited provider, obtain a PTI, and complete EIS certification. Think of CAS registration as a pre-condition for smooth e-invoicing adoption, not a substitute for it.
7. What is the PTI and do I need one even if I use an accredited provider?
The Permit to Issue (PTI) Electronic Invoice is the BIR’s formal authorization for a covered taxpayer to issue electronic invoices under the EIS framework. It is required by all covered taxpayers regardless of whether they use an accredited provider, build an in-house system, or self-accredit. The PTI application is submitted to your BIR RDO and requires documentation of your chosen provider and system setup. Without a PTI, your e-invoice issuance is not formally authorized, even if your system is technically connected to the EIS.
Source by:
Image by Gemini
