Skip to main content
Co-Mate

Philippines · BIR EIS

Philippines BIR E-Invoicing (EIS) Integration

Connect your ERP, billing or POS system to the BIR Electronic Invoicing System. We map your sales data, build secure JSON transmission and support the BIR testing and certification process.

Who must comply with Philippines e-invoicing?

Section 237-A of the Philippine Tax Code, introduced by the TRAIN Law, requires electronic invoicing and electronic reporting of sales data to the BIR for specific taxpayer groups. Coverage started with:

  • Taxpayers engaged in the export of goods and services.
  • Taxpayers engaged in e-commerce.
  • Taxpayers under the jurisdiction of the Large Taxpayers Service.

The BIR onboards covered taxpayers in phases, and later legislation (including the Ease of Paying Taxes Act) updated invoicing rules. Confirm current coverage and timelines with the BIR's latest regulations.

How does the BIR Electronic Invoicing System work?

BIR EIS sales data transmission flow with Co-Mate's connector: Your ERP / POS → Co-Mate connector → BIR EIS → Logs & status → BuyerYour ERP / POSE-invoice issuedCo-Mate connectorJSON · sign · sendBIR EISReceive & acknowledgeLogs & statusStored in your systemBuyerReceives invoice
BIR EIS sales data transmission flow with Co-Mate's connector

The EIS is primarily an electronic invoicing and sales data reporting system. Your system issues the invoice to the buyer and transmits the invoice and sales data to the BIR EIS, which acknowledges receipt. Unlike a strict clearance model, the invoice is not held back waiting for approval, but transmission must be complete, accurate and timely.

Before production, the taxpayer's system goes through registration, testing and certification steps defined by the BIR.

What are the BIR EIS technical requirements?

  • Structured JSON payloads following the EIS data specification.
  • Security: signing and encryption of transmissions and secure credential management.
  • Identifiers: seller TIN, branch codes and registered system details.
  • Tax data: VATable, zero-rated and exempt sales breakdown, discounts and totals.
  • Acknowledgements and logs retained as proof of transmission.

How does Co-Mate connect your ERP or POS to the BIR EIS?

We add a transmission service beside your ERP or POS. It collects issued invoices, builds and signs the EIS payloads, sends them through the BIR API, records acknowledgements and alerts your team about failures. One service can handle multiple branches and source systems, with a dashboard showing what was sent and what still needs attention.

Which ERPs and billing systems do we support for Philippines?

  • SAP Business One
  • Microsoft Dynamics 365
  • Oracle NetSuite
  • Odoo
  • ERPNext
  • Zoho Books
  • Tally
  • QuickBooks
  • Xero
  • Sage
  • Custom PHP / .NET / Java
  • POS systems

Don't see yours? If it stores invoices in a database or exposes an API, export or webhook, we can connect it. See all ERP e-invoicing integrations.

Implementation steps

A predictable path from first call to live, monitored e-invoicing.

  1. 1

    Coverage check

    Confirm whether you are covered by current BIR EIS requirements or regulations (large taxpayers, exporters, e-commerce) and your onboarding status.

  2. 2

    Sales data mapping

    Map invoice and sales data from your ERP or POS to the EIS data structure, including TIN, branch codes and VAT breakdowns.

  3. 3

    Transmission build

    Build JSON generation, signing and secure transmission to the BIR EIS API, plus acknowledgement handling and logs.

  4. 4

    Certification testing

    Support the BIR testing and certification process for your system, with documented test cases and evidence.

  5. 5

    Go-live

    Switch on production transmission per branch or system with monitoring and a rollback plan.

  6. 6

    Ongoing compliance

    Monitor transmissions, resend failures and update the connector when BIR revises its specifications.

Common Philippines e-invoicing challenges and how we handle them

ChallengeWhy it mattersHow we handle it
Many branches and POS terminalsEach source needs consistent data and registration details.Central transmission service with per-branch configuration and monitoring.
Certification evidenceTesting steps need documented scenarios and results.Prepared test plans and logs that map to BIR requirements.
Network or API failuresUnsent data creates compliance gaps.Durable queues, retries and alerts for anything not acknowledged.
Shift from receipts to invoicesRecent rule changes altered invoicing documents and terminology.Document templates and data fields updated with your tax adviser's guidance.

Philippines e-invoicing FAQ

What is the BIR Electronic Invoicing System (EIS)?

Who must use the BIR EIS?

What format does the EIS use?

Does my ERP or POS need BIR certification?

Can you integrate SAP, NetSuite, Odoo or a custom POS with the EIS?

Is Co-Mate accredited by the BIR?

Official sources

Last reviewed:

E-invoicing rules, timelines and technical specifications change often. This page summarises the official guidance as we understood it on the review date. Always confirm obligations and dates with the tax authority or your tax adviser before acting. Co-Mate provides integration engineering, not tax or legal advice.

Make your ERP Philippines e-invoicing ready without replacing it.

A 30-minute call with an engineer, not a salesperson. You get a clear scope, a fixed-price proposal and an honest view of what to change and what to keep.