Electronic Invoicing in the Philippines: What Businesses Need to Prepare For

Direct answer

The 31 December 2026 issuance deadline remains in RMC No. 98-2026 for its covered taxpayers, subject to the micro-taxpayer exception and applicable classification rules. Obtain the taxpayer’s Permit to Issue, plan EIS certification and check any ESP’s solution-specific accreditation. Issuance, provider accreditation and sales reporting are distinct requirements.

Source update: 2 November 2026. Read the coverage and exceptions below before applying the deadline to a particular business.

A deadline extension is not a project plan

Electronic invoicing requires more than an accounting-software decision.

Trace how the invoice is produced. Sales records the transaction, customer data supplies the buyer details, tax determines VAT treatment, the ERP records the sale, the invoicing system creates the document and collections records payment. The data must also be preserved in a form that meets BIR requirements.

If those records conflict, the resulting invoice may be incorrect.

Republic Act No. 12066, or the CREATE MORE Act, further developed the statutory framework for electronic invoicing and electronic sales reporting. BIR Revenue Regulations No. 11-2025 then prescribed implementation rules. RR No. 26-2025 subsequently extended the electronic-invoice compliance period for specified covered taxpayers to December 31, 2026.

Use the extension to identify and complete the work required for implementation.

First determine whether the business is covered

RR No. 26-2025 sets the issuance transition. RMC No. 98-2026, Sections III and IV(1), confirms the 31 December 2026 deadline for covered taxpayers, except those classified as micro taxpayers. Its Section IV(16) also preserves previously approved invoicing requirements after a downward reclassification; do not assume that becoming micro cancels an existing obligation.

RMC No. 98-2026, Section IV(2), separates invoice issuance under Section 237 from sales reporting under Section 237-A. Its Section IV(15) makes the Permit to Transmit dependent on the Commissioner’s notification or directive. RMC No. 110-2026, Section V(A)(2), likewise ties the services required from an ESP to the taxpayer’s applicable obligations and implementation phase. Neither distinction cancels an existing reporting obligation.

A PDF is not automatically an electronic invoice

RMC No. 98-2026, Section IV(4)–(7), requires a compliant system, structured data, electronic delivery capability and data capable of extraction, processing and transmission to the BIR. Manually prepared Word or spreadsheet invoices do not meet that standard.

A printed copy may be supplied under the circular’s conditions. The file extension alone does not establish compliance; test the underlying system and invoice data.

The real work is in the data

Start with the information that must be correct when an invoice is issued.

That ordinarily requires checking the seller's registered information, customer identity and TIN requirements, transaction date, invoice numbering, description of goods or services, VAT classification, zero-rated and exempt components when applicable, credit and debit adjustments, branch information, currency treatment, and the connection between the invoice and the accounting entry. The EOPT Act already made invoices the principal VAT sales documents and prescribed core VAT invoice information.

Check where each piece of information is stored.

For example, customer addresses may differ between sales and accounting records, or the billing platform may contain an outdated TIN. The contract and ERP may use different service-recognition points. An inherited tax code may also fail to reflect the registered activity’s treatment.

An automated system can reproduce the same inconsistency across many invoices.

Correct the tax logic and source data before relying on automation.

The implementation team should not be purely an IT team

Assign responsibilities to finance or accounting, tax, IT, sales or billing operations, and legal or compliance.

IT should verify that the system can generate, preserve, extract, secure and ultimately transmit the required information.

Tax should verify the transaction coding.

Accounting should check the invoice against the books and revenue recognition.

Operations should test whether the proposed process works during actual sales.

Legal should review the contracts, customer terms, data handling, vendor duties and liability for system failure, and check that the invoicing process reflects the transaction.

If the business uses SAP, Oracle, Microsoft, proprietary billing, POS or several systems together, establish which record supplies the authoritative invoice data and how the systems reconcile.

Resolve that question early enough to complete the work required by December 2026.

A practical 2026 readiness sequence

Use the following sequence as an implementation checklist, alongside the applicable BIR requirements.

1. Confirm coverage. Identify the taxpayer, branches, registration, classification and existing EIS obligations.
2. Map the system. Check data sources, invoice numbering, tax treatment, accounting reconciliation and electronic delivery.
3. Secure the taxpayer’s authority. RMC No. 98-2026 requires a Permit to Issue (PTI) Electronic Invoice before issuance. An existing CAS Permit to Use or Acknowledgement Certificate is not the PTI. Check branch and distinct-system coverage under Section IV(12)–(13).
4. Schedule certification. Obtain EIS certification within six months from PTI issuance under Section IV(15); failure is a ground for PTI revocation.
5. Test exceptions. Under Section IV(8) and (11), adjustments need separate referencing documents; downtime requires BIR-authorized manual invoices followed by electronic replacements referencing them when service returns.
6. Confirm reporting separately. Record the applicable directive, transmission requirements and responsibilities before rollout.

There may also be a tax benefit to implementation

RR No. 11-2025 provides an additional deduction for qualifying costs associated with setting up an electronic sales reporting system. Section 3(D) requires both electronic invoicing and electronic sales reporting. Micro and small taxpayers may qualify for an additional deduction equal to 100 percent of qualifying setup cost, while medium and large taxpayers may qualify for 50 percent, subject to the regulatory conditions. The additional deduction is available only once within the taxable year when the reporting system is completed or final payment is made.

Include any available deduction in the financial assessment, but do not choose unsuitable technology because of it.

Keep invoices, contracts, cost allocations and project records from the start so the basis for any claimed deduction can be established.

What management should ask now

For implementation in late 2026, management should be checking the following:

Which Philippine entities are covered?

Which current invoicing systems will remain in use?

Where does each mandatory invoice field come from?

Can the company reconcile electronic invoice data to the general ledger and tax returns?

What happens when the system is unavailable?

Bring the departmental answers together and resolve any inconsistency.

A late installation is one risk. Incorrect tax treatment or unreliable data repeated across large volumes of invoices may create a more substantial problem.

Test for those errors before putting the system into use.

NLF perspective

For a larger business, review coverage, transaction classification, VAT, invoice requirements, contractual responsibility and the audit trail while the system is being designed. Correcting them after configuration may require substantial additional work.

This article is general information and does not replace advice based on a taxpayer's actual registration, systems, transactions, and BIR issuances applicable at the time of implementation.

Vendor accreditation and readiness controls

The September 2026 warning is no longer the complete procurement context. RMC No. 110-2026 now regulates ESP solutions. Under Section V(A)(1), commercial deployment requires a valid BIR accreditation for the specific solution and configuration. An application or demonstration is not production authorization.

Section III excludes qualifying systems used solely by one taxpayer and its registered branches, including licensed software operated on that taxpayer’s own infrastructure. Services supplied to a separate juridical entity, including an affiliate, are treated as ESP services unless the BIR grants an exemption.

Accreditation does not replace the taxpayer’s PTI, EIS certification or other applicable system registrations. The taxpayer remains responsible for accurate invoices, records, returns and taxes. Section IX(3) provides limited transmission-failure relief only when its diligence, reporting and contingency conditions are met; correct taxes remain collectible.

Review contractual fees, data access, migration, continuity and support against RMC No. 110-2026. No vendor’s current accreditation status is asserted here.