System Solutions in Cambodia.

Stand up the modules your operation actually runs on — 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–14 weeks for SMB, 16–24 for mid-market. Khmer + English UI, KHR + USD books, audit-traceable from day one.

What does Scale's System Solutions practice cover?

Scale's System Solutions practice implements and integrates ERP, CRM, sales, inventory, accounting, and HR & Payroll platforms for Cambodian businesses — from single-entity SMBs running on spreadsheets to mid-market operators with multiple legal entities and government-contract obligations. We work across Odoo, SAP Business One, Acumatica, and bespoke custom ERP builds, with every deployment scoped to Cambodian regulatory and operational reality from the start.

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.

Platform choice is a real decision with real trade-offs. Odoo Community is zero per-user licensing, open-source, extensible in Python, and has a Khmer-language interface module — the right baseline for most Cambodian SMBs. Odoo Enterprise adds payroll, consolidated reporting, and a signed service agreement with Odoo SA. SAP Business One is the right tool for mid-market businesses that run complex multi-currency treasury, have Big-4 auditors, or operate in regulated industries that expect a named SAP partner on the engagement letter. Acumatica suits distribution, construction, and light manufacturing businesses that need strong project accounting and field mobility. Custom ERP makes sense when the business has genuinely unique operational logic — manufacturing process, pricing engine, or regulatory exposure — that a configurable platform cannot represent without destructive workarounds.

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 (7%/14%/15%) 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.

How do we choose between Odoo, SAP Business One, and Acumatica?

The right platform depends on five factors: entity count and consolidation needs, transaction volume, audit and reporting requirements, operational domain (distribution vs. service vs. manufacturing), and total cost of ownership over three years — not sticker price alone.

Odoo is the right answer for the majority of Cambodian SMBs. Zero per-user licensing (Community), a growing Khmer localisation module, an active local partner network, and a configurable module set that covers the full ERP scope. The downside: Odoo's financial reporting module is less sophisticated than SAP B1's, and the implementation quality varies widely depending on the partner. We implement Odoo to product-grade standards — typed configuration, automated tests on custom modules, and a handover package that lets your team own the system after go-live.

SAP Business One is the right answer when: the business has a Big-4 audit requirement, runs multi-entity treasury across currencies, needs consolidated financial statements to IFRS standard, or operates in an industry (finance, insurance, large manufacturing) where SAP on the engagement letter matters. SAP B1 is more expensive per user and requires a certified SAP partner — Scale holds SAP B1 implementation experience and works with accredited channel partners for licences. The implementation timeline is longer and the change-management burden is higher; it is the correct trade-off for the businesses that need it.

Acumatica suits distribution, construction, and project-based professional services businesses. Its strength is project accounting — tracking costs, billing, and margin against individual projects rather than aggregate departments. It also handles field mobility well (technician apps, field service modules) and is cloud-native. Cambodian businesses in construction, engineering, or multi-site retail distribution who have hit the ceiling of Odoo's project module should evaluate Acumatica seriously.

Custom ERP is the right answer when the business has proprietary operational logic — a unique pricing model, a government-mandated data format that no commercial ERP handles, or a manufacturing process so specific that adapting a configurable platform would require more custom code than building from scratch. This is rarer than clients expect; most 'we need custom' requests turn out to be solvable with Odoo or SAP B1 configuration. But when it is genuinely the right answer, we build in TypeScript and Node, with Postgres as the primary data store, AWS infrastructure, and source code handed to the client at go-live.

For a full Cambodia-specific platform comparison including pricing, implementation timelines, and fit-by-industry, see our guide at /insights/odoo-vs-sap-b1-vs-acumatica-cambodia.

What is the typical ERP implementation timeline?

A single-entity SMB ERP implementation on Odoo runs 12–18 weeks from signed contract to live system. SAP Business One for a mid-market business runs 18–28 weeks. Multi-entity, multi-site, or heavily customised projects add 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 at /insights/erp-implementation-timeline-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 custom screens. For custom ERP: architecture design and API contract definition.
• Configuration / Build (Weeks 5–14): Odoo install, KH localisation, module configuration, custom-module development (if scoped), integration adapters (GDT, ABA/Wing, CamInvoice). For SAP B1: instance setup, add-on configuration, B1if middleware.
• 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 ERP implementations (single entity, Odoo, standard modules: accounting, CRM, inventory, sales) typically run $8,000–$30,000 all-in on a fixed-scope basis. Mid-market projects (multiple entities, SAP B1, custom modules, GDT and banking integrations) run $30,000–$80,000. Custom ERP 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: Odoo Community is zero licensing cost; Odoo Enterprise is approximately $150–$300 per user per year. Hosting on a managed VPS runs $80–$250/month depending on scale. The GDT e-VAT adapter runs $150–$300/month in hosting and monitoring. HR & Payroll module — 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.

For a Cambodia-specific ERP cost breakdown with a self-service estimate tool, see /insights/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 /insights/quickbooks-to-odoo-cambodia. For Peachtree, see /insights/peachtree-migration-cambodia.

What is our GDT e-VAT integration approach?

GDT e-VAT integration connects your ERP or accounting system directly to Cambodia's General Department of Taxation API, eliminating the manual re-entry that most Cambodian accountants do today. Every invoice confirmed in your system triggers an automated submission to GDT with the correct KHR conversion, WHT codes, and TIN data — no spreadsheet, no manual upload, no deadline stress on the 19th of the month.

The GDT API has been live since approximately 2019 and accepts invoice-level VAT declaration data. It is a REST API authenticated with a GDT-issued credential tied to your TIN. The adapter we build reads confirmed invoices from your ERP (Odoo, SAP B1, QuickBooks Online, or custom systems), converts any USD amounts to KHR at the NBC daily rate on the invoice date, maps your internal tax codes to GDT's TVET code table, and submits with retry logic and full audit logging.

The adjacent platform is CamInvoice — GDDE's B2G e-invoicing network, launched May 2025. If your business sells to government entities or state-owned enterprises, CamInvoice issuer registration and integration is a separate track that runs alongside the GDT adapter. CamInvoice registration takes 2–4 weeks via a GDDE-approved service provider; start it on day one of the project, not after the adapter is built.

Common pitfalls: KHR rounding drift (GDT requires round-riel amounts, no decimals — the adapter must match GDT's rounding exactly, not your ERP's default), WHT misclassification (GDT TVET codes do not map 1:1 to QuickBooks or Odoo WHT categories), TRN gaps on customer records (GDT requires buyer TIN on every B2B invoice — blank-TRN invoices must be routed to a manual queue, not suppressed), and hardcoded NBC rates (the adapter must pull NBC's published daily rate, not use a static approximation).

For full GDT e-VAT integration scope and pricing, see /services/integration/api and /insights/gdt-e-vat-explained.