Revenue Regulations No. 11-2025 and RMC 98-2026 establish a compliance framework for the Philippines’ e-invoicing mandate, with December 31, 2026, serving as a key deadline for Group 1 taxpayers. This BIR E-Invoicing Checklist provides covered businesses with a structured, actionable path toward EIS compliance, guiding finance and IT teams through essential preparation, system integration, testing, and implementation steps.
The steps are ordered by dependency: Step 1 must come before Step 2, and Steps 3–6 can run in parallel to some degree. Following this sequence ensures you do not waste time on system integration before confirming coverage, and do not go live before your PTI is approved. Each step includes typical timelines based on BIR processing norms and provider onboarding experience.
Key Takeaways
- The December 31, 2026 deadline applies to Group 1 taxpayers — large businesses, CAS/CBA users, and e-commerce platforms — under RR No. 11-2025 as amended by RR No. 26-2025.
- 7 sequential steps take a covered taxpayer from coverage confirmation to full EIS go-live — each step has specific BIR or technical deliverables that must be completed in order.
- PTI application is the step most commonly missed or delayed — it must be submitted well before the deadline to allow for BIR processing time.
- EIS certification and sandbox testing must be completed before live transmission begins — uncaught data errors in live invoices create non-compliance exposure.
- Record retention, staff training, and downtime procedure documentation must be in place before going live — compliance is not complete at the technical go-live alone.
What is the BIR EIS E-Invoicing Deadline?
The BIR Electronic Invoicing/Receipting System go-live deadline for Group 1 taxpayers is December 31, 2026, as set by RR No. 26-2025. This regulation extended the original March 14, 2026 deadline by nine-and-a-half months, providing taxpayers and the provider ecosystem additional preparation time. The BIR has not signaled a further extension, and covered businesses should plan around this date as a hard compliance line.
From January 1, 2027, any invoice issued by a Group 1 covered taxpayer without a valid BIR EIS reference number is non-compliant. Non-compliant invoices expose the issuing business to penalties of PHP 1,000 to PHP 50,000 per offence under Section 264 of the NIRC. Buyers who receive non-compliant invoices cannot use them to support VAT input tax claims — a commercial consequence that creates its own pressure for supplier compliance.
Who Must Comply With BIR E-Invoicing in 2026?
Group 1 includes three taxpayer categories, any one of which brings a business within the December 31, 2026 mandate. BIR Large Taxpayers Service registrants are automatically covered. Taxpayers with an active BIR-approved Computerized Accounting System (CAS) or Computerized Books of Accounts (CBA) registration are covered regardless of their revenue level. E-commerce businesses — those primarily conducting sales through digital platforms, online stores, or electronic channels — are covered due to the government’s focus on ensuring digital sales are captured by the tax system.
Micro taxpayers with annual gross sales at or below PHP 3 million who issue manual invoices are specifically exempt. Non-VAT registered businesses that are not large taxpayers and do not use CAS are generally not in Group 1. Businesses near these boundaries should confirm their status with their BIR RDO rather than self-assessing based on a general description of the categories.
Step 1: Confirm Whether Your Business is Covered
Before making any investment in e-invoicing infrastructure, confirm that your business is actually subject to the Group 1 mandate. This step is more important than it may seem — businesses that incorrectly assume they are covered and invest in unnecessary compliance infrastructure waste resources, while businesses that incorrectly assume they are exempt face the same penalties as those that ignored the mandate entirely.
Check your taxpayer classification: review your BIR registration records to determine whether you are registered under the Large Taxpayers Service. Review your CAS/CBA status: if you have ever submitted a CAS application to the BIR or received a CAS approval, you are almost certainly covered. Review your sales channels: if any portion of your sales is conducted through an online platform, marketplace, or digital channel, you may be covered as an e-commerce taxpayer.
If you are uncertain about any of these criteria, write formally to your Revenue District Office requesting a written confirmation of your e-invoicing coverage status. A written RDO confirmation is the strongest protection against inadvertent non-compliance or unnecessary compliance spending.
Step 2: Choose an In-House, Commercial, or ESP Solution
Three implementation models are available for covered taxpayers. The in-house model involves building a proprietary e-invoicing system and applying to the BIR for self-accreditation — this requires significant technical resources and the full BIR accreditation process. The commercial software model involves purchasing a software product from a vendor that has integrated with a BIR-accredited provider and can generate EIS-compliant invoices. The ESP (e-invoicing service provider) model involves engaging a BIR-accredited provider that connects to the EIS on your behalf.
| Model | Who It Suits | Typical Timeline | Relative Cost |
|---|---|---|---|
| In-house / Self-accreditation | Very large enterprises with dedicated IT teams and strong incentive for control | 6–12 months (including BIR accreditation) | Highest — development, infrastructure, compliance maintenance |
| Commercial software | Businesses using major ERP or billing platforms with BIR-certified modules | 2–6 weeks (if pre-built integration exists) | Medium — software licence plus integration configuration |
| ESP (service provider) | Most businesses — fastest path to compliance | 2–4 weeks for standard integrations | Medium — monthly/annual subscription plus onboarding fee |
For businesses that need to meet the December 31, 2026 deadline with limited time remaining, the ESP model is almost always the fastest and most practical path. In-house accreditation is not a realistic option within the remaining window. Commercial software with a pre-built BIR integration is viable if your specific platform has a certified module available from your ESP.
Step 3: Make Sure Your ERP or POS Produces Structured E-Invoices
Before integration with an accredited provider can succeed, your source system — ERP, billing software, or POS must be capable of generating invoice data that includes all BIR-mandated fields. Conduct a data field gap analysis: list all the fields required by the BIR EIS and check whether your current system captures each one. Common gaps include buyer TIN for B2B transactions, individual line-item descriptions rather than lump-sum amounts, VAT-exclusive amount breakdown, and unique sequential invoice numbers.
If your current system is missing mandatory fields, work with your software vendor to add them before integration with the EIS proceeds. Adding a data field to an ERP or POS is typically simpler than fixing integration-level errors after the system is connected to the BIR EIS. Addressing field gaps at the source saves significant time and effort during the testing phase.
Step 4: Apply for Your Permit to Issue (PTI) Electronic Invoice
The Permit to Issue (PTI) Electronic Invoice is the BIR’s administrative authorization for a covered taxpayer to issue e-invoices under the EIS. It is separate from EIS certification (the technical validation) and must be applied for through your BIR Revenue District Office. Do not wait until your system integration is complete to apply for the PTI — submit the application as soon as you have selected a provider and signed a contract, since BIR processing takes four to six weeks.
Required documents for PTI application: BIR Certificate of Registration (Form 2303); copy of your accredited provider’s current BIR accreditation certificate; description of the e-invoicing system specifying software platform and integration type; for CAS users, the BIR CAS approval document. Submit all documents in person to your RDO and retain a stamped copy of the submission as your application date record. Applications submitted after November 15, 2026 may not complete BIR processing before the December 31 deadline.
Step 5: Complete Your EIS Certification
EIS certification is the technical validation process that confirms your system generates and transmits e-invoice data correctly. Working with your accredited provider, submit a set of test invoices to the BIR’s sandbox environment and verify the following: all required data fields are present and correctly formatted, the EIS assigns reference numbers to valid submissions, EIS error responses (for invalid submissions) are received and handled correctly by your system, and the EIS confirmation receipt is captured and stored by your system.
Sandbox testing also gives you the opportunity to identify and fix integration issues before they affect live transactions. Common issues discovered during testing include field mapping errors (data from the wrong source field going into a BIR field), encoding problems (special characters in business names causing JSON formatting errors), and timeout handling failures (the system not retrying when the EIS connection is temporarily slow). Each of these issues is much easier to fix during testing than after go-live.
Step 6: Update ATP, Printed Invoice, and Downtime Procedures
The e-invoicing transition changes your invoicing procedures beyond just the technology. Authority to Print (ATP) for traditional printed invoice booklets is no longer the primary invoice authorization for covered taxpayers — the PTI for electronic invoices takes this role. Existing printed invoice stock may be retained for use as downtime invoices during system outages.
Develop a documented downtime procedure that specifies: what triggers the use of downtime invoices (EIS unavailability, provider outage), what format and fields the downtime invoice must include, how downtime invoices are numbered and tracked, and how the downtime data is transmitted to the EIS once the system is restored. The BIR’s rules require that downtime invoice data be submitted to the EIS within a specified period after the outage is resolved — your procedure must address this requirement explicitly.
Update all customer-facing invoice templates and billing communications to reflect the new e-invoicing format, including the position of the BIR EIS reference number on the invoice document. Customers who have been receiving your invoices in a particular format for years will need to be notified of the change, particularly if the EIS reference number changes the layout of VAT invoices they use for input tax claims.
Step 7: Set Up Record Retention and Staff Training
BIR regulations require e-invoice records to be retained for a minimum of ten years. This includes the transmitted invoice data, the EIS confirmation receipt for each transaction (which includes the EIS reference number and timestamp), and all related supporting documents. Configure your document management or accounting system to archive these records automatically, with access controls to prevent inadvertent deletion.
Staff training is the final and often overlooked step in e-invoicing compliance. Every employee involved in invoice issuance — from billing clerks and cashiers to accounts receivable managers — must understand how to use the new e-invoicing system correctly, how to handle EIS error notifications, and how to follow the downtime procedure. A compliance system that works correctly technically but is operated incorrectly by staff will still generate non-compliant invoices. Germany Advintek can support businesses with e-invoicing integration, structured invoice processing, and digital compliance workflows to help improve operational readiness and streamline invoicing processes.
Conclusion
These seven steps represent the complete compliance journey from coverage confirmation to operational go-live. Businesses that complete all seven steps before December 31, 2026 will have a compliant, documented, and operationally resilient e-invoicing process that satisfies BIR requirements. Businesses that skip steps — particularly PTI application and staff training — risk technical compliance without operational compliance.
Nexright provides guided e-invoicing compliance support across all seven steps. Our team manages the PTI application process, coordinates with accredited providers, and delivers staff training so your compliance project succeeds on time. Contact us today to begin.
Frequently Asked Questions
1. What is the earliest I can go live on the BIR EIS?
You can go live as soon as your PTI is approved, your EIS certification is complete, and your integration has passed sandbox testing. There is no restriction on going live before December 31, 2026 — early go-live is encouraged since it gives you time to resolve any operational issues before the mandatory deadline. Some businesses have chosen to go live several months before the deadline as part of a voluntary early compliance strategy.
2. Can I submit multiple months of back invoices to the EIS at once?
The BIR EIS is designed for real-time or near-real-time transmission at the time of invoice issuance, not for bulk historical uploads. Submitting months of back invoices as a catch-up exercise is technically possible but may not satisfy the near-real-time requirement for those transactions, and the BIR may view bulk historical submissions as evidence of prior non-compliance rather than compliance itself. Consult a tax advisor before attempting bulk historical submissions.
3. Does EIS certification need to be repeated if I change my ERP system?
Yes. If you make material changes to your e-invoicing system — including changing ERP platforms, changing accredited providers, or significantly upgrading your billing software — you should complete a new round of EIS certification or at minimum validate that your new system produces correctly formatted e-invoices before going live. The BIR may require a new PTI application as well, depending on the nature of the change. Notify your BIR RDO of any significant system changes.
4. Can I appoint a third party to manage my e-invoicing compliance?
Yes. Many businesses appoint their accredited ESP or a tax consulting firm to manage the compliance project on their behalf, including PTI application preparation, EIS certification coordination, and staff training. The legal responsibility for compliance remains with the taxpayer, but operational management can be fully delegated. Ensure any third-party manager has a clear scope of work and accountability for key deliverables, particularly the PTI submission deadline.
5. What happens to my existing BIR-approved invoice series numbers?
BIR-approved invoice series numbers under existing ATP authorizations remain valid for their authorized period. Under the e-invoicing transition, your e-invoices will use a sequential numbering system managed by your e-invoicing system rather than the physical booklet-based series from your ATP. Your PTI will specify the authorized invoice numbering range for your e-invoices. Maintain a clear separation between your old ATP-based series (used only for downtime) and your new EIS invoice series to avoid confusion during audits.
6. Do I need a PTI for each of my branches separately?
The PTI is issued to the registered taxpayer entity, not to individual branches. However, invoices from different branches must carry branch-specific information as required by BIR (including branch address and, in some cases, separate invoice numbering series). Confirm with your BIR RDO whether a single PTI covers all your branches or whether separate PTI applications are required for branches registered under different RDOs or under separate TIN segments.
7. What if I go live on January 2, 2027 instead of December 31, 2026?
Going live on January 2, 2027 means that every invoice you issued on January 1, 2027 and potentially portions of December 31, 2026 were non-compliant. Each of those invoices is a separate offence under Section 264 of the NIRC. While a one-day gap may seem minor, the BIR has broad discretion in how it assesses penalties, and a business that can demonstrate it was operationally ready to go live before December 31 but delayed unnecessarily has a weaker good-faith argument than one that faced a genuine technical obstacle.
