BIR Electronic Invoicing in the Philippines: What Businesses Need to Know Before December 31, 2026

RMC No. 98-2026 provides further practical clarification.

A compliant electronic invoice generally needs three characteristics:

1. It must originate from an appropriately registered, approved, or authorized accounting or invoicing system.
2. It must be capable of being electronically delivered or made available to the buyer.
3. The underlying transaction data must be capable of electronic extraction and processing for BIR reporting purposes.

This means the data behind the invoice matters just as much as the appearance of the invoice itself.

A PDF may be the document that the customer sees, but the invoicing software must still retain structured invoice information that computers can process.

A PDF Invoice Is Not Automatically an Electronic Invoice

One of the most important clarifications under the new rules is that merely preparing an invoice electronically does not necessarily make it a BIR-compliant electronic invoice.

Invoices manually prepared using applications such as:

• Microsoft Word
• Microsoft Excel
• Google Docs
• Google Sheets

do not automatically qualify as electronic invoices for purposes of the new requirement.

Similarly, a computerized accounting system that simply prints an invoice on paper does not automatically comply.

The system must be capable of electronically generating and issuing the invoice and maintaining structured data that can support BIR electronic reporting.

For example, a company may already use an ERP or accounting program to create invoices.

If employees print those invoices and give the paper copy to the customer, while the underlying software cannot electronically transmit or extract the required sales information, those invoices may still be treated as traditional or non-electronic invoices.

Businesses should therefore avoid assuming that an existing computerized accounting system is already compliant.

Who Must Comply by December 31, 2026?

The current mandatory phase covers the following taxpayers:

Covered taxpayers:

• Small, Medium, and Large taxpayers engaged in e-commerce or internet transactions.
• Taxpayers under the Large Taxpayers Service.
• Large Taxpayers under the Ease of Paying Taxes Act and RR No. 8-2024.
• Taxpayers using CAS, CBA with Accounting Records and electronic invoicing, or other invoicing software.

Other taxpayers:

• Micro taxpayers are exempt from the December 31, 2026 mandatory requirement.
• Other taxpayers specifically required by the Commissioner may become covered.

RMC No. 98-2026 confirms the December 31, 2026 deadline, while Micro Taxpayers are excluded from the mandatory requirement for this implementation phase.

Under RR No. 8-2024, taxpayer classification is generally based on annual gross sales:

• Micro: Below ₱3 million in annual gross sales.
• Small: ₱3 million to below ₱20 million.
• Medium: ₱20 million to below ₱1 billion.
• Large: ₱1 billion or more.

For e-commerce businesses in particular, determining the taxpayer classification should therefore be one of the first steps in evaluating whether the December deadline applies.

Businesses Will Need a Permit to Issue Electronic Invoice

Another important development under RMC No. 98-2026 is the Permit to Issue Electronic Invoice, or PTI Electronic Invoice.

A taxpayer covered by the electronic invoicing requirement must obtain the PTI before issuing electronic invoices through the particular system covered by the permit.

This is different from an existing Permit to Use or Acknowledgement Certificate for a Computerized Accounting System.

Having an approved CAS does not, by itself, automatically constitute authority to issue electronic invoices under the new framework.

The PTI application is generally filed with the taxpayer's appropriate Revenue District Office or Large Taxpayer Office.

Current guidance based on RMC No. 98-2026 provides that the BIR is expected to evaluate a complete application within 20 working days.

This means businesses should not plan to begin the process on December 31 itself.

Software configuration, internal testing, application preparation, and BIR processing all require lead time.

EIS Certification Comes After the PTI

Obtaining the PTI is not the end of the process.

After the PTI is issued, the taxpayer must obtain Electronic Invoicing and Sales Reporting System Certification, generally within six months from issuance of the PTI.

The certification is intended to verify that the taxpayer's system can properly extract, process, and eventually transmit the required sales information according to BIR technical requirements.

For businesses developing their own system, or implementing an ERP, accounting platform, or invoicing application, EIS compatibility should therefore be considered during software development rather than treated as an afterthought.

Electronic Invoicing and Electronic Sales Reporting Are Not the Same Thing

Businesses should also distinguish between electronic invoicing and electronic sales reporting.

Electronic invoicing concerns how the business generates and issues its invoice to the customer.

Electronic sales reporting concerns the transmission of structured invoice and sales information from the taxpayer's system to the BIR.

These are separate compliance requirements.

For now, affected businesses should focus on complying with the electronic invoicing rules by December 31, 2026.

Separate policies and procedures govern or will govern broader electronic sales reporting.

This distinction is particularly important when selecting software.

A business does not necessarily need to begin transmitting every invoice to the BIR simply because it starts issuing electronic invoices.

However, its system should be designed so that the underlying data can support electronic sales reporting once that requirement applies.

What Should Businesses Look for in Electronic Invoicing Software?

A business evaluating an accounting, ERP, POS, or standalone invoicing solution should focus on compliance capability rather than simply whether the software can produce a professional-looking invoice.

At minimum, businesses should evaluate whether the software can:

• Generate structured invoice data.
• Electronically issue invoices through email, web applications, customer portals, or similar channels.
• Preserve invoice numbers and transaction histories.
• Prevent previously issued invoices from simply being deleted or overwritten.
• Generate proper credit notes or adjustments.
• Accommodate multiple branches.
• Export or transform invoice data into the BIR-required structure, such as JSON.
• Maintain adequate audit trails.
• Support future integration with BIR EIS or related API requirements.
• Maintain proper transaction logs and data retention.
• Support user access controls and approval workflows.
• Handle backup and disaster recovery procedures.

The software should also have a clear procedure for system downtime.

What Happens During System Downtime?

Under RMC No. 98-2026, where an electronic invoice cannot be issued because of circumstances such as:

• system failure;
• internet disruption;
• power interruption;
• cybersecurity incidents;
• force majeure; or
• similar circumstances,

the taxpayer should use a BIR-authorized manual invoice.

Once the electronic system is restored, the manual transaction should subsequently be replaced or reflected through an electronic invoice referencing the manually issued invoice.

Businesses adopting electronic invoicing should therefore retain an authorized manual fallback process even after migrating to an electronic system.

A proper downtime procedure should include:

1. Authorization to use manual invoices.
2. Sequential control of manual invoice numbers.
3. Documentation of the reason for system downtime.
4. Recording of the affected transactions.
5. Subsequent encoding or synchronization into the electronic invoicing system.
6. Reference to the manually issued invoice.
7. Reconciliation between manual and electronic records.

Corrections Should Not Simply Overwrite the Original Invoice

Electronic invoicing also changes how businesses should think about invoice corrections.

An issued electronic invoice should not simply be edited or deleted after issuance.

Where the sales amount needs to be reduced, the adjustment should generally be supported by the appropriate Credit Note or Credit Memo.

Where an additional amount must be charged, a new electronic invoice should generally be issued.

This means accounting and invoicing software should have an immutable transaction history and a proper adjustment workflow.

A system where an administrator can silently change an already-issued invoice may create both accounting-control and BIR-compliance problems.

What Happens if the Company Has Several Branches?

Electronic invoicing should also be considered at the level of the entire taxpayer.

Where a covered taxpayer operates a head office and several branches, the electronic invoicing requirement generally extends to the head office and its branches.

RMC No. 98-2026 also addresses situations where different branches or business segments use different invoicing systems.

Different systems may require separate PTI treatment, while locations using the same approved system may be covered under the applicable PTI structure.

Companies with several branches should therefore perform a system inventory before filing their PTI application.

For example:

• The head office may use an ERP.
• A retail branch may use a POS system.
• Another branch may use a cloud invoicing application.
• An online store may use an e-commerce platform with a separate invoicing engine.

Management should determine whether these are separate invoicing systems for PTI purposes and how the resulting invoice data will be consolidated.

Be Careful With Claims of "BIR-Accredited E-Invoicing Software"

Businesses should exercise caution when software vendors advertise themselves as a "BIR-accredited Electronic Invoicing Service Provider."

As of September 14, 2026, the BIR publicly stated that it had not accredited, authorized, certified, recognized, or endorsed any entity as an official BIR e-Invoicing Service Provider, partner, representative, or solution provider for the electronic invoicing and sales reporting system.

RMC No. 98-2026 allows taxpayers to use:

• an internally developed solution;
• commercially available software; or
• services from an Electronic Invoicing Service Provider.

However, separate rules governing Electronic Invoicing Service Providers may still be issued.

Accordingly, taxpayers should distinguish between a vendor saying its product is "EIS-ready" and a vendor claiming to have been officially "BIR-accredited."

Those statements do not mean the same thing.

For now, businesses should verify the capability of the software itself and ensure that the taxpayer obtains the required BIR permits and certification.

Recommended Compliance Roadmap

With the December 31 deadline approaching, covered taxpayers should already be assessing their systems rather than waiting until year-end.

A practical implementation sequence is:

1. Determine taxpayer classification and coverage
   • Confirm whether the business is Micro, Small, Medium, or Large.
   • Determine whether it is engaged in e-commerce or internet transactions.
   • Identify whether the business is under the Large Taxpayers Service.
   • Review whether the taxpayer already uses CAS, CBA, POS, ERP, or invoicing software.
2. Inventory all invoicing systems
   • Head office.
   • Branches.
   • POS systems.
   • ERP systems.
   • Cloud accounting systems.
   • E-commerce platforms.
   • Custom invoicing applications.
3. Conduct a compliance gap analysis
   • Can the current system issue invoices electronically?
   • Is the invoice data structured?
   • Can the system export the required information?
   • Are issued invoices immutable?
   • Are credit notes and debit adjustments properly supported?
   • Is there a complete audit trail?
4. Upgrade or select an electronic invoicing solution
   • Modify the existing software if possible.
   • Replace unsupported software where necessary.
   • Ensure the selected system can support future BIR integration.
5. Prepare the PTI application
   • Gather required documents.
   • Document system architecture.
   • Identify branches and deployment locations.
   • Complete testing before application.
6. Implement downtime procedures
   • Maintain authorized manual invoices.
   • Establish reconciliation procedures.
   • Assign responsible personnel.
7. Train employees
   • Accounting.
   • Sales.
   • Cashiers.
   • IT personnel.
   • Branch personnel.
   • Internal audit or compliance teams.
8. Prepare for EIS Certification
   • Ensure required data can be extracted.
   • Validate structured invoice data.
   • Maintain system documentation.
   • Prepare for eventual BIR electronic sales reporting.

Electronic Invoicing Is Both an Accounting and IT Project

The transition should be treated as both an accounting project and an IT project.

Finance personnel need to confirm:

• invoice contents;
• tax treatment;
• VAT or percentage tax treatment;
• adjustment procedures;
• reconciliation controls;
• branch invoicing procedures;
• documentation requirements; and
• accounting entries.

The IT or software team must ensure that:

• invoice data is structured;
• records are secure;
• data is extractable;
• transaction history is preserved;
• the software has adequate access controls;
• invoices cannot be improperly altered;
• system backups exist; and
• the platform can eventually meet BIR technical requirements.

A successful electronic invoicing implementation therefore requires coordination among accounting, tax, operations, IT, and management.

The Bottom Line

RMC No. 98-2026 makes one point especially clear:

Electronic invoicing is more than replacing paper with PDF.

A compliant electronic invoicing system must be capable of creating structured invoice data, issuing invoices electronically, preserving proper transaction records, and supporting future electronic reporting to the BIR.

Covered taxpayers have until December 31, 2026 to comply with the mandatory electronic invoicing requirement.

However, the PTI application, system configuration, internal testing, employee training, and certification process mean businesses should begin preparing well ahead of that date.

For companies already using accounting software, CAS, ERP, POS, or invoicing applications, the immediate question should be:

Can our current system actually comply with RMC No. 98-2026, or does it merely generate invoices?

That distinction may determine whether the company is ready for the next phase of Philippine tax digitalization.