Electronic invoice in Philippines

The Complete Guide to the Philippines’ E-Invoicing Mandate: Navigating BIR’s EIS, structured JSON reporting, and the phased rollout defined by taxpayer category.

Select a country

Overview

The Philippine model is supplier-generated electronic invoicing plus centralised post-issuance sales reporting. The seller creates the invoice in its own system and gives it to the buyer; the data goes to the Bureau of Internal Revenue (BIR) separately. There is no clearance: BIR does not approve an invoice before delivery and issues no code without which a document cannot be used.

The single most important thing to understand is that two obligations have been pulled apart in time. Revenue Regulations No. 26-2025 set the deadline for issuing structured e-invoices at 31 December 2026. But mass data transmission through the Electronic Sales Reporting System requires a separate Revenue Regulation, to be issued once BIR's system is confirmed ready. Scope is also not defined by transaction type — it is defined by what kind of taxpayer you are.

3 calendar days

the transmission deadline for taxpayers already connected to the EIS

EIS CERT + PTT

two permits, obtained by the taxpayer — never by its software provider

10 years

retention — with the first five in hard copy

Timeline

Four years of regulation, a pilot that stayed small, and a deadline that has already moved once.

Already in force

2022

RR No. 8-2022 creates the EIS

The Electronic Invoicing/Receipting System initially covered exporters of goods and services, e-commerce taxpayers and those under the Large Taxpayers Service — with e-invoice issuance, registration of the generating system and transmission of sales data. In practice it stayed a pilot: BIR's annual report recorded 63 pilot taxpayers using the EIS as at 31 December 2024.

2025

RR No. 11-2025 redefines the electronic invoice

An e-invoice is a system-generated document containing structured data, extractable automatically, ready for electronic transmission to BIR and produced by a registered or accredited accounting or invoicing system. It may be given to the buyer as a PDF by email, through an app or another electronic interface, and later printed — but a scan of a paper document is not an e-invoice.

2 June 2025

VAT on non-resident digital services

A separate regime for foreign digital service providers took effect, with registration, reverse charge on B2B purchases and prescribed invoice content. It should not be confused with the domestic EIS — see Export, imports and digital services.

Still ahead

31 December 2026

Structured e-invoice issuance for the named categories

RR No. 26-2025 extended this deadline — taxpayers in scope were originally required to comply from March 2026. Non-structured formats such as PDF alone will no longer count as e-invoices for those covered.

No date set

Mass ESRS data transmission

RR No. 26-2025 expressly provides that mandatory transmission through the Electronic Sales Reporting System will be introduced by separate Revenue Regulations once BIR's system is ready — including for taxpayers already bound by the 2026 issuance deadline.

The single biggest open question in the Philippines is that future ESRS regulation. No separate Revenue Regulation setting a general launch date and final technical specification has appeared in the BIR publications reviewed, and BIR was still describing e-invoicing implementation, system integration and data privacy as matters of ongoing work and consultation. Its publication — with the final schema, API, reporting deadlines and onboarding process — could materially change the technical assessment of this country.

Who is in scope

This is where the Philippines differs most from a European mandate. The obligation attaches to the kind of seller you are — size, activity and the system you use — not to the type of transaction.

Must issue structured e-invoices by 31 December 2026

—Taxpayers carrying out e-commerce or other internet transactions and classified as Small, Medium or Large. Micro Taxpayers are exempt

—Taxpayers under the jurisdiction of the Large Taxpayers Service

—Taxpayers classified as Large under the Ease of Paying Taxes Act and RR No. 8-2024

—Users of a Computerized Accounting System (CAS), Computerized Books of Accounts with electronic invoicing, or other invoicing software

Awaiting a separate regulation

These categories come in only once BIR has built a system able to store and process the transmitted data, and has issued dedicated Revenue Regulations:

—Exporters of goods and services

—Registered Business Enterprises using tax incentives

—Taxpayers using POS systems

—Other categories designated by the Commissioner of Internal Revenue

The overlap is what catches companies out. A business in a "later" category — an exporter, say — may already be covered on another ground: because it is a Large Taxpayer, or because it uses qualifying invoicing software. The earlier obligation wins. Assess the client against all four current criteria before concluding it has until a future regulation.

The reporting model

In CTC terms the Philippines is supplier-generated e-invoice plus centralised post-issuance sales reporting. What it is not is worth stating precisely, because the country is routinely misfiled.

Not clearance — the invoice needs no prior BIR approval before it goes to the buyer, and there is no mandatory clearance code

Not Peppol four-corner or five-corner — no two certified Access Points are required between seller and buyer

Transmission runs from the seller's own system directly to BIR, not through an intermediary network

What connecting to the EIS involves

01 Hold a system that generates registered electronic invoices

02 Build a Sales Data Transmission System against the standard API Guidelines

03 Complete enrollment, then obtain the EIS Certification (EIS CERT) and the Permit to Transmit (PTT)

04 Transmit data to the EIS as encrypted JSON over the API

Two different timing regimes

Current EIS participantsReal-time or near-real-time transmission, with a maximum of three calendar days from the transaction date

New RR 26-2025 categoriesThe e-invoice issuance deadline applies, but the universal transmission deadline and interface still have to be set by the separate ESRS regulation

Do not apply the three-day rule to every taxpayer facing the 2026 deadline. It binds those already operating under RR No. 8-2022 with a Permit to Transmit — a much narrower group.

B2G

There is no separate nationwide B2G requirement — no obligation that invoices to government be sent in a defined structured format, through Peppol, or via a dedicated clearance portal.

PhilGEPS is the single electronic government procurement portal and is intended to cover the process from procurement planning through to payment. But the procurement rules require suppliers to issue invoices that comply with BIR requirements; they set no separate national B2G XML standard. PhilGEPS is not an equivalent of a Peppol Access Point or a European clearance portal.

The practical rule is simple: a supplier to government applies the same BIR rules as for B2B and B2C. If it falls into a category that must issue structured e-invoices by 31 December 2026, that applies to its invoices to public buyers too.

B2B and B2C

There is no single date after which every Philippine business must issue a structured e-invoice to every other business. Until 31 December 2026 the transition is compulsory for the designated seller categories only; Micro Taxpayers are generally exempt, though they may adopt e-invoicing voluntarily. The same category logic governs B2C: medium and large e-commerce and internet sellers are in the first wave, physical shops using only POS and not otherwise covered come in later under a separate regulation.

The ordinary invoicing rules continue regardless

—A VAT-registered seller must issue a registered invoice on every sale, whatever the amount

—For other taxpayers the base threshold is PHP 500 — but an invoice must still be issued below it if the buyer asks

—Small sales may be aggregated into an invoice at the end of the day

One structural change worth noting for anyone mapping document types: after the Ease of Paying Taxes reform, the ordinary Official Receipt is no longer the primary evidence of a sale — the Invoice is.

Formats and PDF

The Philippine system is not based on EN 16931. BIR's regulations establish no correspondence with the European semantic invoice model, and neither Peppol BIS Billing 3.0, European UBL 2.1 nor UN/CEFACT CII is a mandatory national format. The operative format for current EIS participants is BIR's own JSON over the API.

The PDF position here is unusually nuanced and easy to get wrong in both directions. A PDF may legitimately be how the e-invoice reaches the buyer — by email, through an app or another electronic interface, and it may then be printed. What a PDF cannot be is the source: the document must be system-generated with structured data that can be extracted automatically and transmitted to BIR. A scan of a paper document is not an e-invoice, and for covered taxpayers a non-structured PDF alone will no longer count as one.

So the design rule for a platform is: generate structured data, render a PDF from it, and never let the PDF become the record of truth.

Peppol in the Philippines

Peppol is not government infrastructure in the Philippines. There is no Peppol Authority, no mandatory Peppol channel and no national electronic address scheme comparable to 0208 in Belgium or 9930 in Germany.

Parties may of course use Peppol voluntarily for commercial exchange; the identifier is then agreed with the Access Point under the permitted OpenPeppol schemes. It will not be an official identifier of the Philippine e-invoicing mandate, and Peppol delivery discharges no BIR obligation.

Export, imports and digital services

Exports

Exporters are one of the categories awaiting a separate regulation, unless already covered on another ground. For export transactions a document titled Commercial Invoice is acceptable provided it carries the required tax data. ViDA does not apply — there is no intra-EU category in Philippine tax law, no 2030 date for Philippine companies and no obligation to route cross-border invoice data through European reporting infrastructure.

Buying digital services from abroad

A separate VAT regime applies to non-resident digital service providers (NRDSP) and should not be mixed up with the domestic EIS. Since 2 June 2025, foreign NRDSPs must register with BIR; on a B2B purchase the Philippine business applies reverse charge, withholding and remitting 12% VAT.

—The foreign supplier's invoice must show the date, a transaction reference number, identification of the buyer including the TIN for B2B, a description of the transaction and the total amount

—No XML invoice form is prescribed for an NRDSP, and a local representative is not mandatory for registration

—For input VAT on such a B2B purchase, the key document is the filed BIR Form No. 1600-VT — not a structured e-invoice that has passed through the EIS

A different system entirely: the customs invoicing scheme

The Philippines is also developing a Cross-border Electronic Invoicing System under Administrative Order No. 23. It must not be confused with BIR's tax EIS. It concerns imported goods, pre-border technical verification, the fight against undervaluation and misdeclaration, and information sharing between customs and other agencies, with cross-border invoice data provided to government agencies in real time. Coverage is phased — agricultural goods, then goods with health and safety risks, then others.

Its accreditation regime applies to Testing, Inspection and Certification Companies — with requirements including existing branches in the Philippines, ISO/IEC 17020 or 17065, financial security and separate government accreditation. Those requirements do not apply to Peppol Access Points or ordinary e-invoicing software providers. AO No. 23 originally aimed at full implementation within two years; the Department of Finance is still publishing accreditation procedures, and no confirmation of a universal production go-live for all imported goods was found.

Permits and accreditation

There is no Philippine Peppol Access Point accreditation, because there is neither a Peppol Authority nor a mandatory Peppol channel. But there is a different layer of national regulation that a foreign provider can easily miss.

RMC No. 72-2025 requires developers, dealers, suppliers and pseudo-suppliers of sales machines and software to obtain or renew a Certificate of Accreditation under the RMO No. 24-2023 procedure, and the invoices and records their systems generate must comply with BIR rules. A foreign provider may need no "AP licence" — but its product can fall within BIR's requirements for sales and invoicing software suppliers if Philippine taxpayers use it commercially to issue official invoices.

Can a foreign provider onboard Philippine clients?

For voluntary Peppol exchange, potentially yes — OpenPeppol allows organisations from countries without a national authority to participate. For tax compliance, Peppol certification alone is not enough. The provider must ensure the invoice carries the mandatory Philippine tax fields, that the system is registered or accredited where required, that the taxpayer holds the appropriate permission to use the system, that an EIS connection is backed by the taxpayer's EIS CERT and PTT, and that data is transmitted to BIR in the national API and format.

RR No. 8-2022 puts the obligation to obtain the EIS CERT and PTT on the taxpayer, regardless of its arrangements with a software provider. You cannot hold these on a client's behalf, and a proposal that implies otherwise is wrong.

Local presence

The e-invoicing rules reviewed contain no requirement to hold a Philippine Peppol Access Point, an official electronic mailbox, a state delivery mailbox, or a local representative specifically for e-invoicing. For an NRDSP a local representative is expressly not mandatory, although a foreign supplier may voluntarily appoint a Philippine service provider for registration, filings and notices — a separate digital-services VAT rule, not an e-invoicing one.

What a solution has to cover

—BIR registration of the CAS, CBA, POS or invoicing system

—Sequential invoice numbering, the TIN and branch code

—An immutable audit trail and structured data storage

—API transmission capability, with EIS CERT and PTT for the current EIS model

—Compliance with the software provider accreditation requirements

—PDF rendering that does not displace the structured original

—Credit and debit adjustments, and correct treatment of VAT, VAT-exempt and zero-rated sales

Archiving

Books of accounts and other accounting records must be preserved for ten years, counted from the day following the filing deadline for the return — or from the date of filing where filed late — for the taxable year in which the last entry was made.

The two-stage rule

First 5 yearsHard copies of the books of accounts, including subsidiary books and other accounting records, must be retained

Years 6 to 10The taxpayer may retain only an electronic copy of the hard copy in an electronic storage system

This is the detail most European archive designs miss: a fully paperless Philippine archive is not compliant for the first five years, however good the electronic storage.

One relief is worth knowing. Taxpayers duly authorised to use the EIS — whether through the web-based facility or by API transmission — are not required to submit printed copies of the invoices or receipts they issue. That removes a submission burden; it does not remove the preservation rules above.

Penalties

Failure to issue a proper invoice

Failing to issue a proper invoice, or issuing instead a document treated only as a supplementary document, can attract a fine of PHP 1,000 to PHP 50,000 and imprisonment of two to four years. RR No. 11-2025 refers breaches of electronic invoicing and sales reporting to Sections 264 and 264-A of the Tax Code.

Failure to transmit data

For a taxpayer already legally obliged to transmit, Section 264-A provides a penalty for each day of the violation of the higher of:

—0.1% of annual net income as shown in the audited financial statements for the second preceding year

—PHP 10,000 per day

If the aggregate violation exceeds 180 days within a taxable year, permanent closure of the business is possible. An exception applies for force majeure and causes beyond the taxpayer's control.

This sanction should only apply where the transmission obligation has already taken effect for that particular taxpayer. For the future expanded ESRS a separate Revenue Regulation is still required — so a per-day penalty cannot yet attach to a taxpayer who is only inside the 2026 issuance deadline.

Input VAT

An e-invoice is not the only basis for input VAT across the economy. The Tax Code requires input VAT to be supported by a VAT invoice issued in accordance with Section 113 — it does not say that invoice must have passed clearance or travelled through Peppol. Electronic form becomes mandatory for a particular seller only once its own deadline arrives; outside the covered categories, registered manual, loose-leaf, CAS or POS invoices continue to be used.

The fields that actually protect the buyer's credit

—The sale amount and the VAT amount

—The registered names and TINs of both seller and buyer

—A description of the goods or the nature of the services

—The transaction date

Other defects in an invoice may expose the seller to liability without necessarily destroying the buyer's right to input VAT, provided those key data are present. What is legally decisive is a proper VAT invoice — not whether it was a PDF, an XML, a Peppol document or something that passed tax clearance.

How we help

The Philippines should not be built as an ordinary European Access Point. It needs its own localisation:

Philippine invoice fields, TIN and branch structure, with sequential numbering

Structured data generation with a separate PDF rendering that never becomes the original

The current BIR EIS JSON and API for taxpayers already connected

Architecture ready for the future ESRS, whose format may still change

Support through BIR registration, software accreditation, and the client's own EIS CERT and PTT

Separate logic for exports, zero-rated sales and NRDSP digital services

Connection by API, SFTP and CSV, with ERP and IDoc source data

Frequently asked questions

Is e-invoicing mandatory in the Philippines?

For named categories, and by 31 December 2026. RR No. 26-2025 extended that deadline — the original requirement was to comply from March 2026. It covers Small, Medium and Large e-commerce and internet taxpayers, those under the Large Taxpayers Service, Large taxpayers under the Ease of Paying Taxes Act, and users of CAS, CBA with electronic invoicing or other invoicing software. Micro Taxpayers are generally exempt. This is not a universal B2B mandate defined by transaction type.

Does the invoice need BIR approval before I send it?

No. The Philippines is not a clearance country: the seller generates the invoice in its own system, gives it to the buyer, and the data goes to BIR separately. There is no mandatory clearance code without which a document cannot be issued, and no Peppol four- or five-corner arrangement — transmission runs from the seller's system directly to BIR. Taxpayers already connected under RR No. 8-2022 with a Permit to Transmit must send within three calendar days of the transaction.

When does the data reporting obligation start for me?

That is the open question. RR No. 26-2025 expressly provides that mandatory transmission through the Electronic Sales Reporting System will be introduced by a separate Revenue Regulation once BIR's system is ready — including for taxpayers already bound by the 2026 issuance deadline. No such regulation setting a general date and final technical specification has appeared in the BIR publications reviewed. Until it does, the three-day rule binds only existing EIS participants.

Can I send the invoice to the buyer as a PDF?

Yes as a delivery method, no as a source. Under RR No. 11-2025 the e-invoice may reach the buyer as a PDF by email, through an app or another electronic interface, and be printed afterwards. But it must be system-generated with structured data that can be extracted automatically and transmitted to BIR. A scan of a paper document is not an e-invoice, and for covered taxpayers a non-structured PDF alone will no longer qualify. Generate structured data, render the PDF from it, and keep the structured record as the original.

Can my software provider hold the EIS permits for me?

No. RR No. 8-2022 places the EIS Certification and the Permit to Transmit on the taxpayer, regardless of its arrangements with a software provider. Connecting to the EIS also requires a system generating registered electronic invoices, a Sales Data Transmission System built to the standard API Guidelines, and enrollment. Separately, note that RMC No. 72-2025 requires developers, dealers and suppliers of sales machines and software to hold a Certificate of Accreditation — which can reach a foreign provider whose product Philippine taxpayers use to issue official invoices.

Is there a B2G mandate or a government portal?

No separate nationwide B2G requirement exists — no mandated structured format, no Peppol route and no dedicated clearance portal for invoices to government. PhilGEPS is the single electronic procurement portal covering planning through payment, and the procurement rules require BIR-compliant invoices, but they set no national B2G XML standard. PhilGEPS is not a Peppol Access Point or a European-style clearance portal. A government supplier simply applies the same BIR rules as everywhere else.

How long must records be kept?

Ten years, counted from the day after the filing deadline for the return — or from the date of filing if filed late — for the taxable year in which the last entry was made. Crucially it is a two-stage rule: hard copies of the books of accounts, subsidiary books and other accounting records must be kept for the first five years, after which an electronic copy of the hard copy in an electronic storage system suffices. A fully paperless archive is therefore not compliant for years one to five.

What is the customs cross-border invoicing system?

A completely different scheme, under Administrative Order No. 23, and it must not be confused with BIR's tax EIS. It covers imported goods, pre-border technical verification, tackling undervaluation and misdeclaration, and real-time sharing of cross-border invoice data between customs and other agencies, phased across agricultural goods, then health and safety risk goods, then others. Its accreditation applies to Testing, Inspection and Certification Companies — requiring existing Philippine branches, ISO/IEC 17020 or 17065 and financial security — and none of that reaches Peppol Access Points or e-invoicing software providers.

Summary

The Philippines is a reporting country, not a clearance country, and its mandate is defined by taxpayer category rather than transaction type. Named categories must issue structured e-invoices by 31 December 2026 — a deadline already extended once from March 2026 — while Micro Taxpayers stay outside it and several groups, including exporters and POS users, await a separate regulation.

The system rests on BIR's own JSON API rather than any international standard. EN 16931, Peppol BIS Billing, UBL and CII play no part, there is no Peppol Authority and no national address scheme. What does bind is registration of the invoicing system, the taxpayer's own EIS CERT and Permit to Transmit, and potentially software supplier accreditation for the provider.

The honest assessment is that one document could change all of this. The separate ESRS Revenue Regulation — with its final schema, API, reporting deadlines and onboarding process — has not been published. Build the structured-data layer now and keep the transmission layer replaceable; and remember the five-year hard-copy rule, which no amount of good electronic archiving substitutes for.

Resources

BIR Electronic Invoice System (EIS) The production portal — enrollment, the web issuance facility and the API transmission environment BIR EIS Certification portal Where the EIS CERT is obtained — the step before the Permit to Transmit, and the taxpayer's own responsibility BIR Revenue Regulations Where RR 11-2025 and 26-2025 sit — and where the awaited ESRS regulation will appear Revenue Regulations No. 8-2022 (PDF) The founding EIS rules — the source of the EIS CERT, the Permit to Transmit and the three-day transmission deadline Revenue Regulations No. 17-2013 — preservation of books of accounts The ten-year retention rule and the five-year hard-copy requirement, in the judiciary e-library Bureau of Internal Revenue Revenue issuances, eServices and the registration systems behind CAS, CBA and POS approval

Need support with e-invoicing compliance?

As a certified Peppol Access Point we provide solutions for sending and receiving electronic invoices securely across Europe — including format conversion, validation and integration with national systems.

Start your free trial