Skip to main content

How to Choose an EIS-Compliant POS or Sales Data Transmission System

Choosing a point-of-sale or accounting system for BIR e-invoicing is not just a matter of buying “BIR-accredited” software off a vendor’s slide deck. A system that satisfies Revenue Memorandum Order (RMO) No. 24-2023 accreditation for invoice-issuing machines can still fail Electronic Invoicing System (EIS) readiness, because EIS layers extra, separate requirements — JSON-format sales-data transmission, a passed connectivity test, and a Permit to Transmit (PTT) — on top of basic accreditation.

Handle Your Other BIR Filings FREE →

What does “BIR-accredited” actually cover, and what does it leave out? #

“BIR-accredited” usually means only that a cash register machine, POS system, or invoicing software has a Certificate of Accreditation under RMO No. 24-2023 — proof it can issue a compliant invoice or receipt. That accreditation says nothing about whether the same system can package that transaction’s data into the BIR’s required electronic format and transmit it to the Electronic Invoicing System (EIS); that is a separate, later step.

RMO No. 24-2023 spells out which machines and software the accreditation rule applies to:

“[The Order] shall cover all types of sales machines and/or software generating invoices/receipts that are used in business to record sales transactions, which shall include the following: Cash Register Machine (CRM); POS System — Bundled POS (both hardware and software) and POS Software; e-Invoicing or e-Receipting System/Software used under a Subscription-Based Agreement; and all other similar sales machines/software that will generate printed invoices/receipts.”

That scope, as summarized in Ablola, Saribong & Gueco Law’s coverage of RMO No. 24-2023, is about issuing a compliant document. It does not by itself confirm the system can meet the additional, EIS-specific transmission requirements below — a gap worth checking before you sign a multi-year POS contract on the strength of an “accredited” label alone.

Accreditation, registration, or both — which track applies to your system? #

Which BIR paperwork a system needs depends on whether it is a bundled POS/cash register machine or a Computerized Accounting System (CAS), and the two tracks are not interchangeable. A vendor selling you a bundled POS or CRM goes through accreditation; a vendor selling you accounting or invoicing software that plugs into your existing books goes through a separate, simplified registration route.

System typeGoverning issuanceWhat you receiveWhere it’s processed
Cash Register Machine (CRM)RMO No. 24-2023Certificate of AccreditationEnhanced eAccReg System
Bundled POS (hardware + software) or POS softwareRMO No. 24-2023Certificate of AccreditationEnhanced eAccReg System
e-Invoicing/e-Receipting software under a subscription agreementRMO No. 24-2023Certificate of AccreditationEnhanced eAccReg System
Computerized Accounting System (CAS) / computerized books of accountsRMC No. 5-2021Acknowledgement CertificateRelevant BIR office (Revenue District Office / LTS)

For the CAS registration process in detail, see The BIR CAS Acknowledgment Certificate Process Under RMC No. 5-2021. Whichever track your vendor’s system falls under, RMO No. 24-2023 also specifies that registration in the Enhanced eAccReg System must happen before the machine or software is put into use, and that BIR offices may not charge a fee for accreditation or registration.

What must the system do specifically to transmit to EIS, not just issue invoices? #

A system ready for EIS transmission needs a defined set of technical features beyond invoice printing, because it is the machine — not the accountant — that has to prove to the BIR that each sale’s data reached EIS intact and on time. Based on the BIR’s published technical and accreditation requirements, the checklist a buyer should walk through with any vendor includes:

  • Non-resettable, accumulated grand-total sales tracking — the running total cannot be zeroed out or rolled back.
  • Tamper-evident design and activity logs (electronic journal), with data retention typically expected for several years.
  • Sequential invoice/receipt numbering, with any reprint clearly marked as a reprint rather than a new transaction.
  • X-reading and Z-reading capability for daily and cumulative sales reports.
  • Sales-data output in JSON format, digitally signed, rather than a scanned image or PDF of the printed invoice.
  • A passed EIS Connectivity Test — a recorded, successful “handshake” between the system and the BIR’s EIS Portal.
  • A Standard Audit File for Tax (SAF-T) export capability, so the system can produce a standardized file for a BIR audit on request.
  • An issued Permit to Transmit (PTT) before the system sends any production (live) sales data to EIS.

Ask a prospective vendor to show, not just claim, each of these — a signed contract that says “EIS-ready” is not the same as a demonstrated connectivity test result.

The obligation to electronically report sales data, which this whole accreditation-and-certification chain exists to satisfy, traces to a single statutory provision — Section 237-A of the National Internal Revenue Code, inserted by the TRAIN Law. Reading the actual text matters because it names exactly which taxpayers the mandate reaches and on what trigger, rather than leaving that to inference from BIR press materials.

“Within five (5) years from the effectivity of this Act and upon establishment of a system capable of storing and processing the required data, the Bureau shall require taxpayers engaged in the export of goods and services, and taxpayers under the jurisdiction of the Large Taxpayers Service to electronically report their sales data to the Bureau through the use of electronic point of sale systems, subject to rules and regulations to be issued by the Secretary of Finance as recommended by the Commissioner of Internal Revenue.”

— Section 237-A, National Internal Revenue Code, as inserted by Republic Act No. 10963 (the TRAIN Law). Revenue Regulations No. 8-2022 (implementing this provision) and Revenue Regulations No. 11-2025 (implementing later CREATE MORE Act amendments under RA No. 12066) are what turned this statutory mandate into the accreditation, connectivity-test, and Permit to Transmit process described above. For the fuller picture of who this covers and the current compliance date, see What Is the BIR Electronic Invoicing System (EIS) and Which Taxpayers Must Comply? and RR No. 26-2025: BIR Extends E-Invoicing Compliance Deadline to December 31, 2026.

A worked example: comparing two POS vendors before signing #

A 15-branch quick-service restaurant chain, classified under the BIR’s Large Taxpayers Service, is renewing its POS contract in late 2026 ahead of its EIS deadline. Its outgoing system, accredited years earlier, still passes muster for printing receipts but was never built for EIS. Two vendor proposals come in:

Evaluation pointVendor A (legacy upgrade)Vendor B (EIS-native)
Certificate of Accreditation under RMO No. 24-2023Held, but for the old hardware onlyHeld for the new bundled POS
Sales-data output formatCSV export, manually convertedNative JSON, digitally signed
EIS Connectivity Test resultNot yet attemptedProvided as part of onboarding
Permit to Transmit supportVendor leaves this to the clientVendor manages the application with the client
Non-resettable grand total / tamper logAdd-on module, extra costBuilt in
SAF-T exportNot availableAvailable

On paper, both vendors can point to “BIR accreditation.” Only Vendor B’s proposal closes the gap between accreditation and actual EIS transmission readiness — the chain’s finance team flags Vendor A’s proposal as needing a documented remediation plan (JSON conversion, a scheduled connectivity test, and someone assigned to file the PTT application) before it can be treated as EIS-compliant, not just accredited.

How does a system actually get from accreditation to a live Permit to Transmit? #

Accreditation is the starting point, not the finish line — a covered taxpayer’s system still has to clear certification and a permit before it can transmit live sales data to the BIR. The general sequence, drawn from the BIR’s published EIS onboarding process, runs:

  1. Register the underlying system — accreditation (RMO No. 24-2023) for a POS/CRM, or an Acknowledgement Certificate (RMC No. 5-2021) for a CAS.
  2. Build or configure the Sales Data Transmission System to the BIR’s Standard API Guidelines so it can output JSON-format sales data.
  3. Enroll in the EIS Certification Portal and submit the system for EIS Certification (EIS CERT), including proof of a successful connectivity test.
  4. Apply for the Permit to Transmit (PTT) once certification confirms the system meets the technical requirements.
  5. Begin production transmission to EIS only after the PTT is issued — not before, and not on a system still mid-certification.

Skipping straight from “the vendor says it’s EIS-ready” to live transmission, without documentation for each of these steps, leaves a business unable to prove compliance if the BIR asks.

Frequently asked questions #

Is BIR accreditation of my POS machine the same as EIS compliance? #

No. Accreditation under Revenue Memorandum Order No. 24-2023 confirms your cash register machine, POS, or e-invoicing software meets baseline invoice-generation and tamper-proofing rules. Electronic Invoicing System (EIS) compliance is a separate, additional step: the same system must also pass a BIR EIS Connectivity Test, transmit sales data in the prescribed JSON format, and hold a Permit to Transmit before it can send live data to the BIR.

Do I need to accredit my system if I use a Computerized Accounting System (CAS) instead of a POS? #

The paperwork differs. A CAS, or its components such as computerized books of accounts, goes through the simplified registration process under Revenue Memorandum Circular No. 5-2021 and receives an Acknowledgement Certificate rather than a Certificate of Accreditation. A bundled POS or cash register machine still goes through accreditation under RMO No. 24-2023. Either route, if your business is covered by the e-invoicing mandate, still needs the separate EIS Connectivity Test and Permit to Transmit on top of that base registration.

How much does BIR accreditation of a POS or CRM cost? #

Nothing charged by the BIR itself. RMO No. 24-2023 directs that accreditation and registration of covered sales machines and software through the Enhanced eAccReg System is free of charge, and prohibits any Revenue Region, Large Taxpayers Office, or Revenue District Office from collecting a fee for it. A vendor may still charge you for the software, hardware, or implementation work needed to meet the requirements.

What happens if I keep using a POS that was accredited before EIS but was never updated for e-invoicing? #

An older accreditation under a prior BIR order does not automatically carry EIS readiness. If your business falls into a category with an active e-invoicing deadline, that POS or CAS still needs to add JSON-format sales-data transmission, pass the EIS Connectivity Test, and obtain a Permit to Transmit before that deadline — otherwise you are only accredited for invoice issuance, not for the electronic sales-data transmission the law separately requires.

Can I switch POS vendors mid-year without losing my BIR accreditation? #

You register the new machine or software on its own merits — accreditation and registration follow the specific hardware/software combination, not the taxpayer generally. Moving vendors means the new system needs its own Certificate of Accreditation (or Acknowledgement Certificate, for a CAS), its own registration in the Enhanced eAccReg System before use, and, if you are EIS-covered, its own connectivity test and Permit to Transmit — plan the cutover so the old and new systems don’t both go live without registration.

Summary #

An EIS-compliant POS, CRM, or CAS purchase decision has to clear two separate bars: baseline accreditation or registration (RMO No. 24-2023 for POS/CRM systems, RMC No. 5-2021 for a CAS) and EIS-specific technical readiness — JSON sales-data output, a passed connectivity test, and an issued Permit to Transmit — required by Section 237-A of the NIRC and its implementing regulations. Before renewing or signing a POS contract, ask the vendor to demonstrate each checklist item rather than accept “BIR-accredited” as proof of e-invoicing readiness on its own, and keep the accreditation certificate, connectivity test result, and PTT on file as your evidence of compliance.