BIR EIS Portal: Features, Requirements, and Best Practices

The BIR EIS portal is where covered businesses in the Philippines transmit their sales data electronically to the tax authority. This article will help you know more about what the portal does, who must use it, and the steps to get certified and compliant.

Key Takeaways

• 31st December 2026 is the e-invoicing deadline in the Philippines for the specified taxpayers, as per the BIR RR No. 11-2025 and 26-2025.
• The EIS is the BIR's platform for receiving and storing electronic invoice data.
• You need EIS Certification and a Permit to Transmit before you can send anything.
• Invoices must be in JSON format, signed with a JSON Web Signature (JWS), and transmitted within three calendar days.
• Only taxpayers the BIR has mandated or notified can register.

What is the BIR EIS Portal?

The BIR EIS portal is the Electronic Invoicing System run by the Bureau of Internal Revenue for receiving, processing and storing electronic sales data. Instead of filing paper summaries, covered taxpayers transmit their invoice data straight to the BIR through the portal.

It works alongside your own invoicing system. Your software generates the invoice as structured data, signs it, and sends it to the EIS. The BIR validates that data, and only invoices it accepts become part of the official record. Those accepted invoices are what support VAT credits and expense claims down the line.

The main portal sits at eis.bir.gov.ph, while the certification process runs through a separate site, eis-cert.bir.gov.ph.

Who Needs to Use the BIR EIS Portal?

The mandate doesn't cover everyone at once. It targets specific groups, rolled out in stages under RR 11-2025 and RR 26-2025.

If your business has branches, every office is in scope once any one qualifies, the head office included. You can't certify one location and leave the rest.

Smaller businesses, such as micro taxpayers outside these groups, aren't mandated yet. Many still prepare early, since the net tends to widen over time.

Key Features of the BIR EIS Portal

The portal does more than just receive files. Its main functions are:

• Sales data reporting:  invoices are transmitted through the API, which returns an acknowledgement almost instantly, though you have up to three calendar days to send each one
• Validation: each file is checked, and an acknowledgement is returned on acceptance
• Digital records: accepted invoices form part of the BIR's official archive
• Audit support: the stored data gives the BIR a verifiable trail
• API integration:  your ERP or accounting system connects directly for automatic transmission

There's also a manual route where smaller taxpayers can encode or upload invoices through the portal itself, rather than building a full API connection. For most covered businesses, though, API integration is the practical choice, since the volumes make manual entry unworkable.

BIR EIS Portal Requirements

Getting onto the EIS is a process, not a single sign-up. Here's what it takes.

Documents: You'll need your BIR Certificate of Registration, VAT registration details, valid TIN, and business permits. Corporations also provide a Board Resolution or Secretary's Certificate, while individuals may need a Special Power of Attorney for their representative.

Format: Invoices must be generated in a structured format, with JSON as the BIR's primary requirement. XML is also recognised under RR 11-2025. What doesn't qualify as an e-invoice is a PDF, a Word file or a scanned image. Every invoice also carries at least 20 mandatory data fields and must be signed with a JSON Web Signature (JWS), which is what lets the BIR confirm the data hasn't been tampered with.

EIS Certification: You apply through the certification portal, submitting your documents and declaring your invoicing system. The BIR reviews everything and may run testing before issuing your EIS Certificate. Note that certification is granted on a per-server basis. If you run more than one system at once, such as a CAS alongside a CRM or POS, or a branch operating on its own separate server, each server must be authenticated individually.

Permit to Transmit: Certification alone isn't enough. You then apply for a Permit to Transmit (PTT), which is what actually authorises you to send data. Reporting begins following PTT approval.

A common misunderstanding is worth clearing up. Holding CAS accreditation does not mean you're EIS-compliant. They're separate systems, and you apply for EIS Certification and the PTT regardless of what your software provider has done.

Best Practices for BIR EIS Compliance

A few habits keep your compliance clean once you're live.

• Test end-to-end before the deadline. Run invoice generation, data mapping, JSON validation and transmission as a full workflow, and fix exceptions early.
• Watch the three-day window. Sales data must be received by the EIS within 3 calendar days of the transaction. 
• Keep your evidence handy. Retain the original JSON, the signature files, BIR acknowledgements and your error logs. The BIR expects a retrievable archive during audits.
• Align your branches. If you run several, make sure each uses the certified system and follows the same process.
• Brief your team in detail. Finance, IT and accounting all touch this workflow. Everyone should know who generates, signs, transmits and reconciles.

How ClearTax Helps Businesses Comply with BIR EIS

Managing JSON schemas, digital signatures, and a three-day clock by hand is where most compliance slips happen. ClearTax connects your existing ERP or accounting system to the EIS, converts your invoice data into the BIR's required JSON format, and applies the digital signature automatically.

It validates each invoice against the schema before transmission, so errors surface early rather than after rejection. It transmits within the deadline, captures the BIR acknowledgement, and keeps the retrievable archive that the audit rules demand. Your team runs the business while the compliance runs itself.