System Solutions in Cambodia.
Stand up the modules your operation actually runs on, purchasing, inventory, sales, and accounting on one ledger rather than four systems reconciled by hand. Fixed scope, fixed price, GDT e-VAT ready out of go-live. We map your processes, configure or build the system, migrate data from QuickBooks, Peachtree, or spreadsheets, and ship in 8–15 weeks for an SMB module migration, 16–22 for a full single-entity ERP, 26–40 for a multi-entity group. Khmer + English UI, audit-traceable from day one.
- CRM
Leads, contacts, deals, pipeline, activity timeline. Khmer + English fields, multi-currency deal tracking, mobile access for sales reps in the field. Configurable workflows for B2B, distribution, and project-based sales.
- Sales
Quote → order → invoice in one flow, with dual-currency pricing, multi-tier discounts, approval workflows, and direct GDT filing. Built for the way Cambodian distributors actually quote and reconcile.
- Inventory
Multi-warehouse stock, lot + serial tracking, barcode + QR for shop-floor scanning, low-stock alerts, and provincial-warehouse-aware reordering. Reconciles to the unit before month-end.
- Supply Chain
Purchase orders, supplier lead times, landed cost and stock on one ledger for Cambodian importers and distributors. We map the buy side to the books: PO to goods receipt to landed cost to the VAT line, in KHR and USD at the NBC daily rate. ERP owns the ledger end to end; this is the buy side that feeds it.
- Accounting
Cambodian chart of accounts, KHR + USD dual-currency books with no rounding drift, GDT e-VAT, withholding tax, salary tax, and monthly e-filing. Built for auditors here, not adapted from a US template.
- ERP
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, KHR and USD side by side, Khmer-first screens for the people who use it daily. Configured on a platform where the flows are standard, built from the ground up where they are not. Fixed scope after a paid discovery: 16 to 22 weeks for a single entity, 26 to 40 for a multi-entity group.
- POS
A till that takes KHQR and cash, prices in USD and gives change in riel, and keeps selling when the connection drops. Supplied, installed and supported by the team that built it, with the owner's phone getting every sale as it happens. Starts at $12.99 a month. Two weeks free, cancel any time. Twelve months for the price of ten. Counter hardware and on-site setup are quoted separately.
- HR & PayrollSoon
Scale HR launch tie-in placeholder. Copy lands in P0c alongside the SaaS launch.
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 on spreadsheets through mid-market operators with multiple legal entities and government-contract obligations. We resell nothing and depend on no vendor; where a business runs a packaged system, we integrate with it, and every build is scoped to Cambodian regulatory and operational reality.
Most Cambodian operators hit the same wall at some point: the business outgrew its original tools. QuickBooks or a local accounting package handled the early years. Then GDT compliance tightened, inventory got complex, or the team grew past the point where a shared spreadsheet was safe. The question is not whether to modernise; it is which platform, which modules, and in which order.
The module landscape for a full ERP deployment covers: accounting and finance (GDT e-VAT ready, KHR/USD multi-currency at NBC daily rates), CRM and sales pipeline, inventory and warehouse management, procurement, HR and payroll (local leave entitlements, NSSF contribution rates, salary in KHR and USD), manufacturing (BOM, work orders, MRP for factories and light manufacturers), and project management for service businesses. Not every business needs every module. We implement what the scope warrants and leave clean extension points for what comes later. Whichever subset ships, the modules sit on one record rather than beside each other: the data spine these modules share is the standard every System Solutions build is held to.
How we build: TypeScript and Node (Python where it fits), Postgres as the primary data store, AWS infrastructure: boring, durable technology your own engineers can inherit. Every screen is written for the people who will use it, Khmer and English from the first commit, and the source code, configuration, and schema are yours at go-live. There are no per-user licence fees on logic we built for you, and no vendor whose roadmap your operation depends on. Where a business already owns a packaged platform and it genuinely fits, we integrate and extend it rather than forcing a rebuild. We are vendor-independent and take no referral fees, so that advice costs us nothing to give honestly.
Every Scale System Solutions engagement is fixed-price after a scoped discovery. We do not run open-ended time-and-materials ERP projects; they consistently overrun. Discovery produces a module specification, a data migration plan, a training plan, and a fixed quote. The scope is then locked and delivered. Variations are quoted as change orders, not absorbed into a vague ongoing retainer.
Cambodia-specific requirements are baked in from day one, not added as an afterthought. That means GDT e-VAT API integration 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%) mapped to the correct GDT TVET codes. For businesses with government contracts, CamInvoice B2G e-invoicing is scoped as a parallel track. None of these are add-ons; they are part of the standard Cambodia ERP configuration.
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 the way you compete (pricing, routing, production, service), a ground-up custom build fits the software to the operation. Where the flows are standard and a platform the business already owns covers them, keeping and integrating it is the honest answer. We are vendor-independent, take no referral fees, and put the recommendation in writing either way.
A custom build gives you a system shaped exactly to your operation: your approval chains, your pricing logic, your warehouse flow, your Khmer-first screens for floor staff, GDT e-VAT and CamInvoice wired natively rather than bolted on. It carries no per-user licence stack, no vendor roadmap risk, and the source code is yours at go-live. The trade is a higher upfront build cost and a paid discovery to scope it properly, which is why the discovery output includes the honest comparison, not just the build quote.
Packaged platforms (Odoo, SAP Business One, Acumatica and similar) earn their place when a business already runs one, when the flows are genuinely standard, or when an existing licence investment is worth preserving. None of them ships Cambodia compliance natively: the tax filing, currency handling, and Khmer layers all have to be engineered on top regardless. We integrate with and extend these systems for clients who own them; we do not resell them, and our revenue never depends on which way the recommendation goes.
For a market comparison of the packaged options including pricing and timelines, see our Odoo vs SAP Business One vs Acumatica comparison.
What is the typical ERP implementation timeline?
A single-entity SMB system build runs 12–18 weeks from signed contract to live system. Mid-market scope runs 18–28 weeks. Multi-entity, multi-site, 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 that have not been physically verified, or chart-of-accounts structures that were never cleaned up in the legacy system. Discovery surfaces these problems early and prices them correctly. A detailed timeline for each phase, including what can run 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 (GDT, banking, e-commerce). Output: a fixed-scope specification document that becomes the project's contract boundary.
- Design (Weeks 2–5): Chart of accounts design, data model decisions, workflow design for each module, UX wireframes for every screen, architecture design and API contract definition.
- Build (Weeks 5–14): Module development in vertical slices (accounting first, then the modules that feed it), Khmer + English interfaces, integration adapters (GDT, ABA/Wing, CamInvoice). For clients on an existing platform: configuration and extension instead of ground-up build.
- Data Migration (Weeks 8–14, parallel): COA migration, opening-balance import, customer/vendor master (with TIN fields populated), inventory on-hand, fixed asset register, open AR/AP invoices. Run extraction from legacy system; validate against source.
- Testing + UAT (Weeks 12–17): System test on full configuration. User acceptance testing with your team on real scenarios. Defect triage and fix. Sign-off from your finance lead and operational owner.
- Training (Weeks 15–18): Role-based training for each user group (accounting, warehouse, sales, management). Khmer-language training for operational staff. Post-training assessment before go-live approval.
- Go-live + Hypercare (Weeks 17–20): Cutover from legacy system. First month-end in new system with Scale on standby. GDT first filing from new system monitored.
What does System Solutions cost in Cambodia?
SMB system implementations (single entity, standard modules: accounting, CRM, inventory, sales) typically run $8,000–$30,000 all-in on a fixed-scope basis. Mid-market projects (multiple entities, deeper custom logic, GDT and banking integrations) run $30,000–$80,000. Full ground-up custom builds are quoted after a paid discovery sprint and generally start above $40,000.
The wide range reflects scope differences, not margin variability. The core determinants of ERP cost are: number of modules in scope, volume and cleanliness of data to migrate, number of integrations required (each GDT, banking, or e-commerce integration adds $2,500–$8,000), level of customisation required, training burden (number of users, language requirements), and whether the business has internal IT capacity to support the system post-go-live or needs a managed support arrangement.
We quote fixed scope, fixed price after a paid discovery sprint. Discovery runs 1–2 weeks and costs $800–$1,500 (deducted from the project fee if you proceed). The output is a module specification, a data migration plan, and a final fixed quote with a scope boundary that is clear to both sides. Open-ended T&M ERP projects consistently overrun; we do not offer them.
Ongoing costs after go-live: a custom build carries zero licence cost. The recurring line is infrastructure and support only. Hosting on managed cloud runs $80–$250/month depending on scale. The GDT e-VAT adapter runs $150–$300/month in hosting and monitoring. HR & Payroll (if NSSF filings are also automated) adds approximately $100/month in managed service if you want Scale to handle the monthly submission on your behalf. Businesses staying on a commercial platform additionally carry that vendor's per-user licence fees.
For a Cambodia-specific ERP cost breakdown with a self-service estimate tool, see the Cambodia ERP cost calculator.
How do migrations from QuickBooks, Peachtree, and spreadsheets work?
A migration from QuickBooks, Peachtree, or a spreadsheet-based system involves six distinct work streams: chart-of-accounts mapping, opening-balance migration, open AR/AP roll-forward, fixed-asset register rebuild, historical-report archiving, and GDT compliance re-setup in the new system. Each has its own timeline and risk profile.
QuickBooks migrations are the most common we handle. QuickBooks's data export is structured enough (IIF and QBO formats) to automate most of the extraction, but the resulting chart of accounts (typically a flat list built over years by whoever had QuickBooks access) almost always requires a full remap before it can be imported into a modern ERP. That remap is the real work; the technical extraction is not. Plan 2–3 weeks for COA mapping and sign-off by your finance lead.
Peachtree (Sage 50) migrations are harder. Peachtree's data is stored 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. Peachtree migrations typically run $1,000–$2,000 more than equivalent QuickBooks projects and take 2–3 additional weeks.
Spreadsheet migrations are the fastest in terms of technical extraction (you already have a flat file) but the hardest in terms of data quality. Businesses that have run operations on Excel for years typically have inconsistencies: duplicate customers under different names, inventory SKUs that changed over time, KHR and USD amounts in the same column with no currency flag, and cost data that was never reconciled to physical stock counts. The migration process must audit and clean this data before import; that work cannot be accelerated by throwing more developers at it.
In all three cases, the migration does not bring historical transaction detail into the new system. Opening balances (the last closed trial balance from the legacy system) migrate; prior-period journals stay in the legacy system as a read-only archive. This is the correct approach: migrating 5+ years of historical journals into a new ERP is expensive, rarely accessed, and introduces reconciliation complexity that is not worth the cost. The legacy system stays live in archive mode for 5–7 years to satisfy Cambodia's 7-year record-retention requirement.
For the QuickBooks migration specifically, see our QuickBooks to Odoo migration guide. For Peachtree, see our Peachtree migration guide.
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 (durable, mainstream technology your own engineers can inherit), with the source code, schema, and configuration yours at go-live and no per-user licence fees on anything we wrote. We do not resell any platform or take referral fees. Where a business already owns a packaged system that genuinely fits, we integrate with and extend it instead of forcing a rebuild; that recommendation comes out of the paid discovery, 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 (customers, invoices, transactions, inventory) 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 format required for monthly employer submissions. We do not file NSSF on your behalf; we build the system that 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 (loans, shared-services invoices, management fees) automatically create the corresponding entry in the counterparty entity, and consolidated financial statements pull from all entities into one reporting view. Because the data model is ours, the consolidation logic matches your group structure exactly instead of approximating it through an add-on.
How long does post-go-live support last?
Every Scale ERP delivery includes 30 days of hypercare support 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 retainers on a monthly basis, covering system monitoring, GDT adapter maintenance, minor configuration changes, and user support. Retainer pricing depends on the number of modules and integration points in scope.
Do you handle government-contract businesses with CamInvoice requirements?
Yes. CamInvoice (the GDDE B2G e-invoicing platform launched May 2025) is a separate integration track from the GDT e-VAT adapter. We scope CamInvoice registration and adapter development as a parallel work stream in ERP projects for businesses that sell to government entities. Registration takes 2–4 weeks via a GDDE-approved provider; the adapter development runs alongside ERP configuration. See how GDT e-VAT filing works and our API integration work for the full scope.
What if we are not yet sure whether custom is right for us?
A paid discovery sprint ($800–$1,500, 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 fixed-price quote. The discovery fee is deducted from the project fee if you proceed. If the recommendation is that your current system with a GDT adapter is sufficient (and that is sometimes the honest answer), we say so in the discovery output.