What is ERP (enterprise resource planning) software?

ERP software replaces the patchwork of disconnected tools — an accounting package here, an inventory spreadsheet there, a separate payroll app, a CRM no one updates — with one system where every transaction is recorded once and seen everywhere. The point is not the individual features; most standalone apps do their one job fine. The point is that the modules share a single database, so a number entered in one place is instantly correct everywhere else.

A concrete example: a salesperson confirms an order. In an ERP, that single action reserves the stock in inventory, triggers a purchase order if the item is below its reorder point, creates the sales invoice in accounting, and updates the customer's outstanding balance — all from one record, with no re-keying. Without an ERP, those four things live in four systems and someone reconciles them by hand, usually late and usually wrong.

This is why ERP is described as a single source of truth. When finance, the warehouse, the production floor, and management all read from the same data, the monthly close is faster, stock-outs and over-ordering drop, and decisions are made on current numbers instead of last month's exported reports.

These three get confused constantly, especially by smaller businesses that have outgrown one and are shopping for the next. The simplest way to tell them apart is by scope: how much of the business the software is responsible for.

Accounting software (like a standalone bookkeeping package) records money — it keeps the ledger, issues invoices, and produces financial statements. A POS (point-of-sale) system records sales at the counter and deducts stock as items are sold. An ERP contains the functions of both and connects them to purchasing, manufacturing, warehousing, and HR/payroll, so the whole operation runs on one set of numbers rather than several that have to agree.

Most Philippine businesses graduate through these in order: a POS or accounting app first, then a second and third app bolted alongside, until the cost of reconciling them — and the errors that slip through — outweighs the cost of one connected system. That tipping point, not company size in the abstract, is when ERP starts to pay for itself.

A cloud ERP runs on servers reached over the internet and is usually paid for by subscription, so the vendor handles hosting, backups, and updates, and head office sees every branch in real time. An on-premise ERP runs on servers the company owns and maintains, which gives full control of the data and keeps working during an internet outage, but puts maintenance, security, and upgrades on your own IT team.

For most Philippine companies the practical questions are not philosophical. Does it keep working when the connection at a provincial branch drops? Where does the data physically live, and does that satisfy the Data Privacy Act and any customer or PEZA requirements? And what is the real three-year cost — because per-user, per-module subscription fees on a large headcount compound quickly, while an owned system trades a higher upfront build for no recurring licence.

A growing middle option is a custom-built ERP the company owns outright — shaped to its exact workflows, BIR-compliant from day one, hosted wherever the business chooses, with no per-seat fee. That is the build-versus-buy decision larger operators increasingly weigh against an open-ended subscription.

This is where most off-the-shelf and foreign ERP products quietly fail a Philippine business. An ERP whose accounting and invoicing modules are used to keep the books and issue invoices is, in the eyes of the Bureau of Internal Revenue, a Computerized Accounting System (CAS) — and a CAS has to be registered with the BIR before it is used.

Under RMC 5-2021 and RMO 9-2021, the old Permit to Use was scrapped: a CAS is now registered by submitting the documentary requirements to your Revenue District Office, which issues an Acknowledgement Certificate (target: within three working days), followed by a post-evaluation against the BIR's system standards. An ERP that cannot produce compliant books of accounts, sequential invoice numbering, and the required system documentation cannot be registered — so it cannot legally run the business's accounting.

On top of registration, e-invoicing now applies. Under RR 11-2025 (issued 27 February 2025, implementing the CREATE MORE law), taxpayers using a CAS — along with large taxpayers and e-commerce sellers — must issue structured electronic invoices and transmit sales data to the BIR. Crucially, an ERP-generated invoice that is merely printed on paper, with no ability to report the data electronically, does not count as an electronic invoice. RR 11-2025 originally set a March 2026 deadline; a later regulation, RR 26-2025 (issued September 2025), extended it to 31 December 2026 — but compliance itself is not optional for covered taxpayers.

The lesson: in the Philippines an ERP is also a tax instrument. The finance, inventory, and manufacturing features can look identical across global vendors, yet the system still fails here if the BIR-compliance layer — CAS registration, structured invoices, EIS transmission, correct SC/PWD and VAT handling — is missing or bolted on as an afterthought.

Payroll is the same story. An ERP HR module that does not compute Philippine SSS, PhilHealth, and Pag-IBIG contributions, withholding tax, the 13th month pay, and the BIR Form 2316 to local rules is not Philippine-ready, however polished the rest of the suite looks.

What a Philippine-ready ERP must handle

• CAS registration with the BIR (Acknowledgement Certificate under RMC 5-2021 / RMO 9-2021)
• Books of accounts and financial reports in BIR-acceptable form
• Sequential, non-resettable invoice and receipt numbering
• Structured e-invoicing and sales-data transmission to the EIS where the taxpayer is covered (RR 11-2025)
• VAT, withholding (e.g. BIR Form 2307), and senior-citizen/PWD discount handling
• Payroll computing SSS, PhilHealth, Pag-IBIG, withholding tax, 13th month pay, and BIR Form 2316

ERP pricing is rarely a single sticker. Licensed suites typically charge per user, per module, per month, and then layer on an implementation project — configuration, data migration, integrations, training — that often costs several times the first year's licence. For a large headcount across multiple branches, those recurring per-seat fees keep growing with the company, indefinitely.

Off-the-shelf ERP is the right call when your processes are standard and you can adapt to the software. The calculus shifts for operators whose workflows the generic product cannot model, whose per-seat fees have ballooned, or whose BIR-compliance needs are treated as an afterthought by a global vendor. At that point the question becomes whether to keep renting a system you do not own, or build one shaped around your operation — Philippine-compliant from the first invoice, hosted where you choose, with no per-seat fee — that the company owns outright.

That build-versus-buy decision is exactly what Orkids handles for Philippine enterprises: ERP and the modules around it, built to your operation and to BIR rules, owned by you rather than rented per seat.