# EazLink Philippines > EazLink connects existing ERP, POS, CAS, ecommerce and branch systems to Philippine electronic invoicing and BIR EIS workflows. It is integration middleware, not accounting software. ## Primary pages - [Home](https://ph.eazlink.net/): Service definition and positioning. - [Solution](https://ph.eazlink.net/solution/): Integration, status, recovery and audit proof. - [Coverage](https://ph.eazlink.net/coverage/): Supported ERP, POS, CAS and custom-system paths. - [Partners](https://ph.eazlink.net/partners/): Partner-led and white-label delivery. - [Insights](https://ph.eazlink.net/insights/): All Philippine BIR EIS answer pages. - [Contact](https://ph.eazlink.net/start/): Integration fit check. ## Priority answer pages - [What is BIR EIS integration middleware?](https://ph.eazlink.net/insights/bir-eis-integration-middleware/): BIR EIS integration middleware receives invoice data from the system that already runs the business, checks and maps that data, manages transmission, and returns a usable status. It does not replace the ERP, POS, CAS or ecommerce platform. It keeps BIR-specific logic out of those core systems. - [Who must issue electronic invoices in the Philippines by December 31, 2026?](https://ph.eazlink.net/insights/who-must-issue-electronic-invoices-philippines-2026/): RR 26-2025 gives four named groups until December 31, 2026: covered ecommerce taxpayers except micro taxpayers, taxpayers under the Large Taxpayers Service, taxpayers classified as large under the cited rules, and users of CAS, CBA with accounting records and other invoicing software. POS users and some other groups are described separately and should not be assumed to share that date without checking later BIR regulations. - [RR 11-2025 vs RR 26-2025: what changed for electronic invoicing?](https://ph.eazlink.net/insights/rr-11-2025-vs-rr-26-2025/): RR 11-2025 defines electronic invoices, electronic invoicing, electronic sales reporting and the taxpayer groups in scope. RR 26-2025 amends the transitory provisions and gives specified groups until December 31, 2026 for electronic invoice issuance. It does not erase the definitions or the rest of the operating framework in RR 11-2025. - [Are POS users required to issue electronic invoices by December 31, 2026?](https://ph.eazlink.net/insights/are-pos-users-covered-by-bir-eis-2026/): POS users are named in RR 26-2025, but not in the four groups expressly given the December 31, 2026 electronic invoice issuance deadline. The POS provision is tied to the establishment of a BIR system capable of storing and processing the data and to separate regulations. A POS user may still fall into another covered group, so classification must be checked taxpayer by taxpayer. - [Do ecommerce sellers need electronic invoices in the Philippines?](https://ph.eazlink.net/insights/ecommerce-sellers-electronic-invoices-philippines/): RR 26-2025 includes small, medium and large taxpayers engaged in ecommerce or internet transactions among the groups given until December 31, 2026 for electronic invoice issuance. It states that micro taxpayers are exempted from that listed group. Sellers should confirm their classification, activities and any other basis that may put them in scope. - [CAS vs BIR EIS: what is the difference?](https://ph.eazlink.net/insights/cas-vs-bir-eis-philippines/): A Computerized Accounting System records the company's accounting transactions and may generate invoices. BIR EIS is the government-side electronic invoicing and sales reporting environment. A CAS does not become EIS-ready simply because it prints an invoice. The system needs structured, extractable data and the applicable transmission, testing and permission workflow. - [BIR EIS Certification and Permit to Transmit: A Taxpayer Guide](https://ph.eazlink.net/insights/bir-eis-certification-vs-permit-to-transmit/): A Philippine e-invoicing project can involve a Permit to Issue, BIR EIS Certification and a Permit to Transmit. Each serves a different purpose. The taxpayer applies for its own permissions and remains responsible for compliance. A software provider can help with system design, data mapping, tests and evidence, but it cannot replace the taxpayer in the BIR process. - [How does BIR EIS system-to-system API integration work?](https://ph.eazlink.net/insights/bir-eis-api-system-to-system/): In a system-to-system design, the invoice-producing system sends structured data to an integration layer, which applies the current BIR mapping and submits through the approved interface. The integration stores the response and returns a status to the source system. Registration, certification, credentials and production permission sit around that technical flow. - [What should developers prepare for BIR EIS JSON and JWS testing?](https://ph.eazlink.net/insights/bir-eis-json-jws-technical-readiness/): Developers should prepare a stable invoice data model, representative JSON payloads, a controlled signing boundary where required by the current technical specification, secure credential handling, repeatable tests and complete response logs. Do not guess algorithms, headers or certificate rules from an old example. Use the technical documents issued for the taxpayer's current BIR certification environment. - [Is a PDF invoice an electronic invoice under RR 11-2025?](https://ph.eazlink.net/insights/structured-electronic-invoice-vs-pdf-philippines/): A system-generated invoice may be delivered electronically, including as a PDF attachment or through an application, but RR 11-2025 also requires structured invoice data that can be extracted and readily transmitted. A photo or scanned copy of a paper invoice is expressly not an electronic invoice. A PDF by itself does not prove that the underlying structured data exists. - [BIR EIS portal vs system-to-system API: which approach fits?](https://ph.eazlink.net/insights/bir-eis-portal-vs-system-to-system/): A portal is useful for official registration, certification, reference and tasks that the BIR exposes through its web interface. System-to-system integration moves structured invoice data from the business system through an approved API or transmission path. Companies with recurring volume, many branches or several source systems usually need automation, but the official portals still remain part of onboarding and operations. - [Does BIR EIS work offline, and what happens during API downtime?](https://ph.eazlink.net/insights/bir-eis-offline-api-downtime/): A BIR API cannot receive a transaction while the connection or service is unavailable. A business can design local capture, queuing and controlled recovery around that interruption, subject to the rules that apply to its invoice process. The queue must preserve the source transaction, distinguish timeout from rejection and prevent a retry from creating a duplicate. ## Official basis and editorial method - Regulatory pages distinguish electronic invoice issuance from electronic sales reporting and link the applicable BIR source beside the answer. - Content is reviewed against current BIR regulations and portals; it is implementation guidance, not tax or legal advice. - [Full answer-page reference](https://ph.eazlink.net/llms-full.txt) - [Machine-readable FAQ](https://ph.eazlink.net/ai/faq.json) - [Service definition](https://ph.eazlink.net/ai/service.json) Last updated: 2026-09-06