“EIS-ready” vs “BIR-accredited”: the difference that protects you
“BIR-accredited software” is the single most common piece of misleading marketing in Philippine e-invoicing — and it is a claim the BIR's own framework does not support. The BIR accredits taxpayers' systems, not vendors' products. Knowing the difference is how you avoid buying on a promise that cannot be true.
Key Takeaways
- No software is “BIR-accredited.” The BIR registers and certifies a taxpayer's system, not a product sold off the shelf.
- The real artifacts: a CAS Acknowledgement Certificate (registration of your system) and EIS certification of your system's ability to transmit — both attached to your registration.
- Honest vendor claims are “EIS-ready,” “CAS-registrable,” and “EOPT-compliant.” These describe capability, not a fictitious accreditation.
- Treat “BIR-accredited” as a red flag and ask the vendor to show the actual registration path instead.
Does the BIR accredit software vendors?
No. The BIR does not accredit or certify software vendors or products as blanket-compliant. It registers a taxpayer's own Computerized Accounting System — issuing an Acknowledgement Certificate — and, for the EIS, certifies that a specific taxpayer's system can transmit the required data. Both attach to the taxpayer's registration, never to a product as sold to everyone.
This is why the claim “our software is BIR-accredited” is structurally wrong: there is no BIR program that stamps a product as accredited for all buyers. What exists is a path for you, the taxpayer, to register and certify your system.
What are the real BIR artifacts?
Two things are real. First, a CAS Acknowledgement Certificate — issued when you register a computerized accounting/invoicing system (it replaced the old Permit to Use under RMC 5-2021). Second, EIS certification — the BIR's test that your system can produce the required JSON, sign it with a JSON Web Signature, and transmit via API. Both belong to your registration.
| Term | What it really is | Whose it is |
|---|---|---|
| “BIR-accredited software” | A marketing claim with no BIR program behind it | Nobody's — it does not exist |
| CAS Acknowledgement Certificate | BIR registration of a computerized system | The taxpayer who registered it |
| EIS certification | Test that a system can generate/sign/transmit to the EIS | The taxpayer's certified implementation |
| “EIS-ready” software | Honest capability claim — the system can do the above | The vendor, describing capability |
What should you ask a vendor?
Ask whether the system produces structured invoice data in the EIS format, whether it can be registered as a CAS with an Acknowledgement Certificate, and whether it can sign and transmit to the EIS when that becomes required. Those three answers tell you far more than any “accredited” badge.
- Can your system output structured invoice data in the BIR's EIS format?
- Can it be registered as a CAS, and will you support us through the Acknowledgement Certificate?
- Can it apply a JSON Web Signature and transmit via API when the EIS requires it?
- What exactly is the claim — “EIS-ready” and “CAS-registrable,” or an unsupportable “accredited”?
For the mechanics behind these questions, see CAS vs EIS, the EIS JSON / JWS format, and how to become EIS-ready. The full mandate is in the EIS compliance guide.
Frequently asked questions
No. The BIR does not accredit or certify software vendors or products as universally compliant. It registers a taxpayer's own system — issuing a CAS Acknowledgement Certificate — and certifies that a specific taxpayer's system can transmit to the EIS. Those attach to the taxpayer's registration, not to a product sold off the shelf.
“EIS-ready” means the software can produce structured invoice data in the BIR's EIS format, sign it, and be registered and connected so a taxpayer can comply. It describes capability, honestly, without claiming an accreditation that does not exist.
It is the document the BIR issues when a taxpayer registers a Computerized Accounting System (or its components). Under RMC 5-2021 it replaced the old Permit to Use and is issued within three working days of complete documents. It belongs to the taxpayer that registered the system, not to the software vendor.
Correct. The EIS certification process tests whether a taxpayer's system can generate the required JSON, apply a JSON Web Signature, and transmit via API. It certifies that taxpayer's implementation for transmission — it is not a blanket stamp that makes the vendor's product “BIR-accredited” for everyone.
Ask: can your system produce structured invoice data in the EIS format, can it be registered as a CAS (Acknowledgement Certificate), and can it sign and transmit to the EIS when required? If a vendor answers “we're BIR-accredited,” treat it as a marketing red flag and ask them to show the actual registration path.
Buy on capability, not on a badge.
NexusWorkforce is EIS-ready and CAS-registrable — structured invoices, controlled numbering, and the registration path supported end to end. No “BIR-accredited” claims, because no honest vendor can make them.
Book a demo