ScaleERP systems for Cambodian businesses
One ledger for finance, sales, and stock, with the CRM on top and the buy side handled by our supply chain work, with Cambodian compliance built in rather than bolted on: GDT e-VAT ready, KHR and USD side by side, Khmer-first screens for the people who use it daily. Built from the ground up on standard modules, or connected to the platform you already run where keeping it is the cheaper answer. Fixed scope after a paid discovery: 16 to 22 weeks for a single entity, 26 to 40 for a multi-entity group.
What does an ERP actually replace in a Cambodian business?
It replaces the spreadsheets between your systems. Most Cambodian SMBs already have accounting software, a stock list, and a sales process. What they do not have is one place where those three agree. An ERP is the system where an order, the stock it consumes, the invoice it raises, and the tax that invoice owes are one record rather than four reconciled by hand at month-end.
The symptom is almost always the same. Someone in finance keeps a spreadsheet mapping the sales system to the accounting system. Someone in the warehouse keeps another mapping physical stock to whatever the system claims. Those spreadsheets are the business's real ERP, and they exist because the software underneath cannot answer a question that spans two departments.
That is the test worth applying before buying anything: name a question your business cannot answer without opening a spreadsheet. What did we actually earn on this order after landed cost. How much of that stock is committed against open orders. Which customers are past terms in KHR as opposed to USD. If those take a person and an afternoon, the gap is integration, not effort. The architecture that closes it is set out in full in how purchasing, inventory, sales and accounting run as one ledger.
Should you configure a platform or build from the ground up?
It follows one question: how much of your operation is genuinely your own? Where the workflow is how you compete (your pricing logic, your routing, your production sequence) a ground-up build fits the software to the operation instead of the reverse. Where the flows are standard and you already run a platform that mostly works, keeping it and adding the Cambodian compliance layer is often the cheaper answer.
We build systems; we do not implement or resell anyone's platform, and we take no referral fees. That is the only reason the next sentence is worth anything: if the honest answer is to keep what you already run, the recommendation will say so.
Every packaged platform sold in Cambodia needs localisation work, and how much differs: Cambodian tax setup, KHR and USD at the invoice-date rate, and a Khmer interface are worth checking on every one of them. Our ERP in Cambodia guide compares the options if you are weighing one.
A custom build carries no licence line at all. The recurring commitment is infrastructure and support, and the source code, schema, and documentation are yours at go-live. That is the honest trade: more to build, nothing to rent, and no vendor able to reprice you later.
- Workflow is the competitive edge, or the flows genuinely do not fit a package: build it, on one ledger, with the compliance in the core.
- Standard flows and no system yet: build on standard modules, fixed scope after discovery, with no per-user licence line to renew.
- Already running a platform that mostly works: keep it and add the Cambodian compliance layer rather than rebuild. Sometimes that is the honest answer, and it is the cheapest one.
What does Cambodian compliance require that global ERPs miss?
Three things, and a global ERP may ship none of them. The figures for the monthly GDT return. Dual-currency books in KHR and USD converted at the NBC daily rate on the invoice date, not at a period average. And withholding tax at three separate rates, 15% on services, royalties, and interest paid to residents, 10% on rental, 14% on payments to non-residents, each mapped to its own account.
A TIN is required on every B2B invoice, and a CRM that captures it once on the account means accounting never types it again. Most legacy systems treat that field as optional, which means it is missing on a large share of migrated customer and vendor records. Collecting them is a data project that has to finish before go-live, not during the first filing.
CamInvoice, the GDDE's B2G e-invoicing platform, is a separate and adjacent question; B2B is still voluntary with no published mandate date. Ask any vendor whether it is on the roadmap and whether it sits in the current contract or is priced separately. "It is coming soon, we will handle it" is not an answer.
The CamInvoice adapter, where one is needed, is built in parallel with the rest of the system, not after it. See how the CamInvoice integration is scoped.
How long does an ERP take, and what drives the scope?
Sixteen to twenty-two weeks for a single-entity SMB, twenty-six to forty for a multi-entity mid-market group, with each additional legal entity adding meaningfully to both. What moves those numbers is rarely the software. It is entity count, how clean the data in the outgoing system is, how many flows are genuinely non-standard, and how much of your own team's time is available.
Scale starts with a paid discovery sprint rather than a free proposal. It produces a build-versus-configure recommendation with the reasoning attached, a module scope document, a data migration assessment, and a fixed-scope quote. If the recommendation is that you do not need what you came asking for, that is what it will say.
The projects that slip in Cambodia usually slip on client-side availability rather than engineering. Discovery needs your finance and operations leads in the room. Data migration needs someone who knows why the old records look the way they do. Parallel run needs your accountants to close one month twice. That time is real and worth planning for.
For an order-of-magnitude view before you talk to anyone, the Cambodian ERP cost calculator takes module footprint, company size, and complexity and returns a range built from Cambodian project data.
Questions worth asking any ERP vendor
Do we own the system at the end?
On a Scale build, yes: source code, database schema, configuration, and a data dictionary are handed over at go-live, and the data sits in standard PostgreSQL any engineer can query. On a commercial platform you own your data but licence the software, and a licence can be repriced. Ask which one you are buying before you sign, because the two behave very differently over five years.
Does it work in Khmer, properly?
Ask to see a Khmer screen used by someone who is not in the demo. Khmer as a community translation pack layered over an English product behaves differently from Khmer treated as a first-class language in the build. Field lengths, sort order, date formats, and printed invoices are where it usually breaks.
Can we migrate off QuickBooks or Peachtree mid-year?
Yes. Year-end is the cleanest cut-off because the trial balance is closed, but mid-year migration is common. It needs an agreed cut-off date, usually the end of a completed month, and an in-year opening balance that reconciles to the old system to the cent. See the full accounting migration scope.
What happens when a tax rule or the CamInvoice specification changes?
The system is maintained, and that maintenance is part of the ongoing engagement rather than a surprise. It is worth pinning down in writing with any vendor: compliance is not a one-time build, and a fixed-scope implementation that treats it as one will come back to you the first time a rate, a form or a specification moves.
How much of our team's time will this take?
More than most proposals imply. Budget for your finance and operations leads through discovery, someone who knows the history of the old data through migration, and your accountants closing one month twice during parallel run. Vendors rarely price this because it is your cost, not theirs, but it is the single most common reason a Cambodian ERP project runs late.