TL;DR
"BIR-accredited POS" is shorthand for a point-of-sale system that the Bureau of Internal Revenue recognizes for issuing official invoices. In practice there are two tracks. Traditional hardware cash-register and POS machines (CRM/POS) still require a Permit to Use (PTU), applied for through the BIR eAccReg system and tied to your own Revenue District Office (RDO). Cloud and software-based sales systems are treated as a Computerized Accounting System (CAS) or component, and since RMC No. 5-2021 the BIR no longer issues a PTU for these — instead it issues an Acknowledgement Certificate (AC) within three working days of complete documents, with no pre-use demonstration but a later post-evaluation. Either way, accreditation is granted to YOU at your RDO, not bought off a shelf — so for a cloud POS each restaurant registers the system under its own TIN/RDO. A compliant system must produce system-generated, sequential, no-gaps invoice numbers, a non-resettable running grand total, Z-reading and X-reading reports, an electronic journal, and eSales-ready data. OrderEase is designed to support BIR-compliant invoicing with onboarding assistance; it is not itself BIR-accredited, and the supporting backend is still in development. Confirm every requirement with your RDO before relying on any system.
What "BIR-Accredited POS" Actually Means
Walk any restaurant trade show in Metro Manila and you will hear "BIR-accredited" used as if it were a sticker a vendor slaps on a box. It is not. In the Philippines, the right to issue official invoices is granted by the Bureau of Internal Revenue to a registered taxpayer — to you, the business — for a specific system, tied to your TIN and your Revenue District Office. There is no national list where a POS brand is permanently "accredited" and every buyer inherits that status automatically. The system has to be registered for your business, at your RDO, before you may use it to issue invoices.
That distinction matters because it changes the question you should be asking a vendor. The right question is not "Is your POS BIR-accredited?" — it is "Is your POS built to meet BIR requirements, and will you help me get it registered under my own TIN and RDO?" A system can be technically compliant and still leave you non-compliant if it never gets registered in your name. Conversely, a vendor cannot register the system for you behind the scenes and hand you a finished accreditation; the registration is inherently yours.
Two Tracks: Permit to Use vs the Acknowledgement Certificate Regime
There are two regulatory paths, and which one applies to you depends on what kind of system you run.
Hardware machines: the Permit to Use (PTU)
Cash register machines (CRM) and traditional point-of-sale machines — the standalone terminals with a fixed serial number, brand, and model — fall under the long-standing rules for sales machines (Revenue Regulations No. 11-2004 and later issuances). For these, the business applies for a Permit to Use (PTU) through the BIR eAccReg online facility before the machine is used. On approval, the RDO issues a PTU, and a decal or sticker is affixed to the machine in a place the customer can see. The business then reports sales monthly through the BIR eSales portal.
Cloud and software systems: the Acknowledgement Certificate (AC)
A cloud or software-based ordering, billing, and receipting platform is generally treated as a Computerized Accounting System (CAS) or a component of one — the BIR defines CAS components broadly to include online ordering, billing, receipting and invoicing facilities. The big change came with Revenue Memorandum Circular (RMC) No. 5-2021: for these systems the BIR no longer requires a Permit to Use. Instead, upon submission of complete documentary requirements, the RDO where the taxpayer is registered issues an Acknowledgement Certificate (AC), typically within three working days. There is no pre-use system demonstration; the BIR conducts a post-evaluation later to confirm the registered system actually meets the standards.
| Aspect | Permit to Use (PTU) | Acknowledgement Certificate (AC) |
|---|---|---|
| Typically applies to | Hardware CRM/POS machines | Cloud / software CAS or components |
| Governing basis | RR 11-2004 and related issuances | RMC No. 5-2021 |
| How you apply | BIR eAccReg online facility | Submit CAS documentary requirements to your RDO |
| Pre-use evaluation | Application reviewed before approval | No pre-use demo; post-evaluation done later |
| What you receive | Permit to Use (decal on machine) | Acknowledgement Certificate |
| Issued by | Your RDO | Your RDO (where taxpayer is registered) |
| Granted to | The registered taxpayer (you) | The registered taxpayer (you) |
| Ongoing reporting | Monthly sales via BIR eSales | Per applicable CAS / invoicing rules |
Permit to Use vs Acknowledgement Certificate — at a glance
The Compliant-POS Feature Checklist
Whichever track applies, the BIR expects the system to enforce certain controls so that sales cannot be hidden, edited away, or reset. Before you sign with any vendor, confirm the system can do all of the following — and ask to see each one demonstrated, not just described on a slide.
- System-generated invoice numbers — every official invoice carries a number the system assigns automatically, not one a cashier can type in or choose.
- Sequential and no-gaps — invoice numbers run in unbroken sequence; the system does not skip numbers or allow silent deletions that leave holes in the trail.
- Non-resettable accumulating grand total — a running total of all sales that only ever increases and cannot be zeroed out (hardware machines historically require at least a 10-digit accumulating total).
- Z-reading — an end-of-day report that closes the day's sales and is part of the audit trail.
- X-reading — an interim read of sales during the day that does not close the period.
- Electronic journal (eJournal) — a tamper-resistant electronic record of transactions retained for audit.
- eSales-ready reporting — data formatted so monthly sales can be reported to the BIR eSales portal where required.
- Required invoice face details — the system prints the BIR-mandated information on each invoice (your registered business name, TIN, address, and the prescribed invoice elements). Confirm the exact current field list with your RDO.
- No training or 'no-sale' modes that hide revenue — the system must not let staff ring sales that escape the accumulating total.
- Audit-friendly records — the ability to reprint, export, and retain records for the periods the BIR requires.
How to Get Your POS BIR-Registered
The exact documents and sequence depend on your RDO and whether you are on the hardware (PTU) or cloud/software (AC) track, but the shape of the process is consistent. Below is the typical path for getting a system registered under your business. The howTo block at the end of this article restates these steps in a structured form.
- Make sure your business itself is registered first — you need an active BIR Certificate of Registration (Form 2303) and a TIN before any system can be registered to you.
- Identify your track — hardware CRM/POS goes through eAccReg for a Permit to Use; a cloud/software receipting system goes through the CAS route for an Acknowledgement Certificate.
- Gather the documentary requirements — for the CAS/AC route this typically includes system documentation and sworn statements describing how the system works; ask your RDO for its current checklist.
- File at your RDO — submit the application and documents to the Revenue District Office where your business is registered (cloud systems: the AC is issued there, often within about three working days of complete documents).
- Receive your authorization — a PTU and decal for machines, or an Acknowledgement Certificate for a cloud/software system.
- Register for eSales and report — enroll in the BIR eSales portal and file your sales reports on the required schedule.
- Be ready for post-evaluation — for the AC route the BIR may evaluate the live system afterward, so keep your configuration and records consistent with what you registered.
Common Mistakes Restaurant Owners Make
Most compliance trouble does not come from the rules being impossible — it comes from a handful of avoidable misunderstandings.
- Assuming the vendor's accreditation covers you — a system being capable of compliance does not register it under your TIN. You still have to file at your own RDO.
- Using the system to issue invoices before registration is complete — issuing official invoices from an unregistered system is exactly the kind of gap that surfaces in an audit.
- Skipping eSales reporting — getting registered is the start, not the finish; monthly reporting where required is part of staying compliant.
- Editing the system after registration without telling the BIR — material changes to a registered system generally need to be reported; quietly reconfiguring invoicing can break your AC or PTU.
- Treating voids and discounts casually — staff deleting or re-ringing tickets to 'fix' mistakes can create gaps the BIR treats as suppressed sales.
- Buying on price alone — the cheapest terminal that cannot produce a non-resettable total or proper Z-reading is not cheap once it stalls your registration.
How a Cloud POS Handles BIR Registration
Cloud POS systems changed the practical experience of getting registered, mostly for the better. Because a cloud platform is treated as a CAS or component under RMC No. 5-2021, the heavy old pre-approval step is gone: there is no mandatory system demonstration before you can go live, and the Acknowledgement Certificate is meant to be issued within about three working days of complete documents. The BIR's evaluation moves to a post-evaluation after you are running.
The flip side is the part buyers most often miss: because the AC is issued by the RDO where the taxpayer-user is registered, every restaurant using the same cloud platform registers it separately under its own TIN and RDO. There is no single platform-wide accreditation that automatically blankets all customers. What a good cloud vendor offers instead is consistency and support — the same compliant invoicing behavior for every merchant, plus the system documentation and onboarding help you need to file your own AC cleanly.
Compliance is also only one axis of choosing a POS. Price, hardware, payment acceptance, and day-to-day workflow all matter, and a system that is compliant but painful to use every shift will cost you in other ways. For how the pieces fit on cost, see our breakdown of restaurant POS pricing in the Philippines. For reference, OrderEase plans start at ₱2,580/month for STARTER and ₱3,280/month for PRO.
Frequently Asked Questions
Q：Is there a master list of BIR-accredited POS brands I can just pick from?
A：Not in the way most owners imagine. Accreditation in practice means a system is registered for use by a specific taxpayer at that taxpayer's RDO — it is granted to your business, not permanently to a brand for everyone. The useful question is whether a POS is built to meet BIR requirements and whether the vendor will help you register it under your own TIN and RDO. Always confirm the current process with your RDO.
Q：What is the difference between a Permit to Use and an Acknowledgement Certificate?
A：A Permit to Use (PTU) is the authorization for hardware cash register and POS machines, applied for through the BIR eAccReg facility. An Acknowledgement Certificate (AC) is what the BIR issues for cloud and software systems treated as a Computerized Accounting System: since RMC No. 5-2021 these no longer need a PTU, and the RDO issues an AC — typically within three working days of complete documents — with a post-evaluation done later. Which one applies depends on the type of system you run.
Q：Do I register a cloud POS once for my whole company, or per branch?
A：Registration for a cloud system follows your taxpayer registration: the Acknowledgement Certificate is issued by the RDO where the taxpayer-user is registered. How that maps to multiple branches depends on how your business and branches are registered with the BIR, so confirm the exact branch-level requirements with your RDO. The key principle is that the registration is yours, tied to your TIN — it is not a one-time, platform-wide accreditation that covers every merchant on the software.
Q：Can I issue official invoices before my POS is registered?
A：You should not. The right to issue official invoices comes from registering the system for your business with the BIR. Issuing official invoices from a system that has not completed registration is the kind of gap that creates exposure in an audit. Get the PTU or Acknowledgement Certificate squared away first, and ask your RDO if you are unsure where you stand.
Q：Is OrderEase BIR-accredited?
A：No. OrderEase is designed to support BIR-compliant invoicing with onboarding assistance, but it is not currently BIR-accredited and the supporting invoicing backend is still in development. We will not claim otherwise. When the capability ships, the intended model is onboarding-assisted, per-merchant registration: OrderEase helps you prepare and file the documentation, and you hold the Acknowledgement Certificate under your own TIN at your own RDO. In the meantime, verify your obligations directly with the BIR.
Conclusion
"BIR-accredited POS" is real, but it is not a sticker you buy — it is a registration you complete for your own business, at your own RDO. Hardware machines run on the Permit to Use track; cloud and software systems run on the Acknowledgement Certificate track under RMC No. 5-2021, with no pre-use demo, a roughly three-working-day issuance, and a post-evaluation afterward. Whichever applies, insist that the system produces system-generated, sequential, no-gaps invoice numbers, a non-resettable grand total, Z-reading and X-reading, an electronic journal, and eSales-ready data — and that the vendor will help you register it under your TIN. Choose with compliance built in from the start, and confirm every detail with your RDO, because the BIR's word is the one that counts.