ScaleSystem Solutions in Cambodia.
Purchasing, inventory, sales, accounting and CRM on one ledger rather than four systems reconciled by hand, GDT e-VAT ready out of go-live.
- CRM
Leads, deals and pipeline in Khmer and English; KHR and USD on one deal, NBC rate stored.
- Sales
Quote → order → invoice in one flow, dual-currency, multi-tier discounts, approval workflows and GDT-ready figures.
- Inventory
Multi-warehouse stock, lot and serial tracking, barcode and QR scanning, low-stock alerts, reconciled to the unit before month-end.
- Supply Chain
Purchase orders, supplier lead times, landed cost and stock on one ledger, in KHR and USD.
- Accounting
KHR and USD books with no rounding drift, GDT e-VAT, withholding and salary tax, built for auditors here.
- ERP
One ledger for finance, sales and stock, compliance built in: GDT e-VAT ready, KHR and USD, Khmer-first screens.
- POS
A till that takes KHQR and cash, gives change in riel, and keeps selling when the connection drops.
- HR & PayrollSoon
HR and payroll for employers paying staff in KHR and USD.
What does Scale's System Solutions practice cover?
Scale's System Solutions practice builds the operational system Cambodian businesses run on (purchasing, inventory, sales, accounting, CRM, and HR & Payroll), from the ground up, on one data model. We serve single-entity SMBs through mid-market operators with multiple legal entities. We resell nothing and depend on no vendor; where a business runs a packaged system, we integrate with it.
A full deployment covers accounting and finance (GDT e-VAT ready, KHR/USD multi-currency at NBC daily rates), a CRM and sales pipeline, inventory and warehouse management, procurement, HR and payroll (leave entitlements, NSSF contribution rates, salary in KHR and USD), manufacturing (BOM, work orders, MRP), and project management. We build what the scope warrants and leave extension points for later. Whichever subset ships, the data spine these modules share is the standard every build is held to.
Cambodia-specific requirements are baked in from day one: the monthly GDT return figures scoped before development starts, KHR/USD multi-currency configured at the chart-of-accounts level, Khmer-language interfaces for factory-floor and warehouse users, NSSF and labour-law-compliant payroll, and withholding tax (WHT) rates (15%/10%/14%) each mapped to its own account. For businesses with government contracts, CamInvoice B2G e-invoicing is scoped as a parallel track. None of these are add-ons.
Custom build or packaged platform: how do we decide?
The decision follows one question: how much of your operation is genuinely your own? Where the workflow is how you compete (pricelists, routing, production, service), a custom build fits the software to the operation. Where the flows are standard and a platform you own covers them, keeping and integrating it is the honest answer. We put the recommendation in writing.
A custom build gives you a system shaped exactly to your operation: your approval chains, your pricelist rules, your warehouse flow, your Khmer-first screens for floor staff, GDT return figures and CamInvoice built in rather than bolted on. It carries no per-user licence stack, no vendor roadmap risk, and the source code is yours at go-live.
Packaged platforms (SAP Business One, Acumatica) earn their place when a business already runs one, the flows are standard, or an existing licence investment is worth preserving. None ships Cambodia compliance natively: the tax filing, currency handling, and Khmer layers have to be engineered on top. We connect to these systems for clients who own them (a bank feed, a CamInvoice adapter, a data bridge); we do not implement or resell them. Our ERP in Cambodia guide compares the options.
What is the typical ERP implementation timeline?
A single-entity SMB system build runs 16–22 weeks from signed contract to live system. A multi-entity mid-market group runs 26–40 weeks. Multi-site scope or unusually deep custom logic adds 6–12 weeks per major scope extension.
The most common cause of ERP timeline overrun in Cambodia is data quality: customer records missing TINs, inventory on-hand counts never physically verified, or a chart of accounts never cleaned up in the legacy system. Discovery surfaces these problems early and scopes them properly. A detailed timeline for each phase, including what runs in parallel, is in our ERP implementation timeline for Cambodia.
- Discovery (Weeks 1–2): requirements workshop, process mapping, module-by-module gap analysis, data migration inventory, integration scope (CamInvoice, banking, e-commerce). Output: a fixed-scope specification.
- Design (Weeks 2–5): chart of accounts, data model, workflow design per module, wireframes for every screen, architecture and API contracts.
- Build (Weeks 5–14): modules in vertical slices (accounting first, then what feeds it), Khmer and English interfaces, integration adapters (ABA/Wing, CamInvoice).
- Data migration (Weeks 8–14, parallel): COA, opening balances, customer/vendor master with TINs, inventory on-hand, fixed-asset register, open AR/AP; validated against source.
- Testing and UAT (Weeks 12–17): system test, user acceptance with your team on real scenarios, defect triage, sign-off from finance and operations.
- Training (Weeks 15–18): role-based sessions per user group (accounting, warehouse, sales, management), in Khmer for operational staff, with an assessment before go-live.
- Go-live and hypercare (Weeks 17–20): cutover from legacy, first month-end with Scale on standby, first GDT return figures from the new system checked.
How do migrations from QuickBooks, Peachtree, and spreadsheets work?
A migration from QuickBooks, Peachtree, or spreadsheets involves six distinct work streams: chart of accounts mapping, opening balances, open AR and AP roll-forward, the fixed-asset register rebuild, the historical report archive, and GDT re-setup in the new system. Each has its own timeline and risk profile.
QuickBooks migrations are the most common we handle. Its export (IIF and QBO formats) is structured enough to automate most of the extraction, but the chart of accounts, typically a flat list built over years by whoever had access, almost always needs a full remap before import. That remap is the real work. Plan 2–3 weeks for it and sign-off by your finance lead; the detail is in our QuickBooks migration guide.
Peachtree (Sage 50) migrations are harder. Its data sits in flat files (.DAT / .PTB) that can be read without the install media, but the extraction tooling is less mature than QuickBooks's, and Peachtree businesses tend to be older, with more accumulated data quality issues. Plan 2–3 additional weeks over an equivalent QuickBooks project; our Peachtree migration guide covers the extraction.
Spreadsheets are the fastest to extract and the hardest on data quality: duplicate customers under different names, SKUs that changed over time, KHR and USD in the same column with no currency flag, cost data never reconciled to a physical count. That data is audited and cleaned before import. History stays in the legacy archive in all three cases: opening balances (the last closed trial balance) migrate into the new system, prior-period journals do not. The legacy system stays available in archive mode for the ten years records must be kept.
Frequently asked questions: System Solutions
Do you build on an existing platform or from the ground up?
From the ground up, by default. Our builds are TypeScript and Node on Postgres and AWS, with the source code, schema, and configuration yours at go-live and no per-user licence fees on anything we wrote. We resell no platform and take no referral fees. Where a business owns a packaged system that fits, we integrate and extend it; discovery puts that recommendation in writing.
Can we run the system in Khmer for our operational staff?
Yes, natively. Because we write every screen ourselves, Khmer is a first-class language in the build, not a community translation pack bolted on afterwards: factory-floor, warehouse, and sales interfaces ship in Khmer and English from the first commit, including error messages and training materials. Management reporting typically runs in English where the financial terminology is better established, with Khmer available throughout.
What happens to our data if we part ways later?
You keep everything, by construction. Our builds store data in standard PostgreSQL; you hold the source code, the schema, and a data dictionary from the handover package, so any engineer or future provider can query and export every record without our involvement. There is no lock-in on data or on logic. That is the point of owning the build.
What about NSSF and Cambodian payroll compliance?
We build the payroll module for Cambodian rules: NSSF contribution rates across the occupational-risk, healthcare, and pension pillars, monthly payslips in KHR and USD, Tax on Salary under the progressive schedule, and the seniority-payment accrual for undetermined-duration contracts. The system generates NSSF declaration reports in the monthly employer-submission format. We do not file NSSF for you; the system produces accurate filings for your HR team to submit.
We have three legal entities under one holding company. Can we manage them in one system?
Yes. We model multi-entity groups on one database: each legal entity carries its own chart of accounts, VAT registration, and GDT TIN, behind a single login with per-entity access controls. Inter-company transactions create the matching entry in the counterparty entity, and consolidated financial statements pull every entity into one view. Because the data model is ours, consolidation matches your group structure exactly.
How long does post-go-live support last?
Every Scale ERP delivery includes 30 days of hypercare after go-live: daily check-ins, priority response to issues, and coverage of the first month-end close in the new system. After hypercare, we offer ongoing managed support covering system monitoring, integration maintenance, minor configuration changes, and user support. Monthly support is scoped to the modules and integration points in play.
Do you handle government-contract businesses with CamInvoice requirements?
Yes. CamInvoice (the GDDE B2G e-invoicing platform launched May 2025) is its own integration track. We scope the onboarding with GDDE and the adapter as a parallel work stream for businesses invoicing the ministries and institutions in scope; the adapter is built alongside the ERP. See how GDT e-VAT filing works and our API integration work.
What if we are not yet sure whether custom is right for us?
A short paid discovery sprint (1–2 weeks) is the right starting point. Discovery produces a build-versus-buy recommendation with rationale, a module scope document, a data migration assessment, and a clear scope boundary. If the recommendation is that your current system is sufficient (and that is sometimes the honest answer), we say so in the discovery output.