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.

A long-form page for Accounting with sample build, case study, and pricing band is coming. Until then, scope it directly with us.

Why Cambodian SMBs migrate off QuickBooks and Peachtree

QuickBooks and Peachtree were the right tools for a different era. They fail Cambodian businesses on three specific pressure points: no native KHR currency code (QuickBooks Online is USD-only in practice), no GDT e-VAT API integration, and no multi-entity consolidation. When any one of those gaps becomes a compliance or growth bottleneck — and GDT's 2025–2026 compliance push has made all three urgent — migration becomes cheaper than workarounds.

QuickBooks Desktop and Peachtree (Sage 50) still run the books for a significant share of Phnom Penh SMBs — particularly businesses established before 2015 that grew up on Windows-desktop accounting. The software worked. Month-end closed, invoices went out, accountants managed the rest. The trouble is that the rest now includes: submitting e-VAT to GDT every month (Prakas 1033), converting KHR/USD at the NBC daily rate on each invoice date, and managing withholding tax (WHT) at three different rates depending on counterparty type. None of these are things QuickBooks or Peachtree do without manual workarounds.

The alternative is not always Odoo. The right modern system depends on entity count, transaction volume, government-contract exposure (CamInvoice mandate), and whether the business needs a custom ERP or can work within a configurable platform. The migration conversation starts with mapping what the current system actually does versus what the business actually needs — those two lists are always different, and the gap between them defines the scope.

What does an accounting system migration cover?

A full accounting migration is not a data export. It covers six distinct work streams: chart-of-accounts (COA) mapping, opening-balance migration, accounts-receivable and accounts-payable roll, fixed-asset register rebuild, historical-report strategy, and GDT compliance setup in the new system. Each has its own risks and timelines.

COA mapping is the work most firms underestimate. QuickBooks uses a flat account list; Odoo and other modern ERPs use a structured chart with account groups, tax mappings, and currency assignments. Every QuickBooks or Peachtree account needs to be mapped to its equivalent in the new system before a single transaction moves. Accounts with no clear equivalent — common for legacy miscellaneous or suspense accounts — require a decision: absorb into an existing account, create a new one, or close out the balance before migration.

Opening balances need to be reconciled to a specific cut-off date: the last closed trial balance in the old system becomes the opening entry in the new one. This is straightforward for cash and bank accounts but more complex for AR/AP ageing (open invoices carry over), fixed assets (cost and accumulated depreciation must both migrate), and KHR-denominated accounts (the KHR/USD rate at the cut-off date must be documented and defensible to a GDT auditor).

Historical reports — the invoices, journals, and trial balances from before the cut-off — typically stay in the old system as a read-only archive. Most businesses plan to keep QuickBooks or Peachtree running in archive mode for 3–5 years so accountants and auditors can pull prior-period data. This is the right approach: migrating 5+ years of historical journals into a new system is expensive and rarely used. Document the archive policy and location before closing the old system.

GDT compliance setup in the new system covers: Cambodia tax codes (VAT 10%, VAT 0%, VAT exempt, WHT 7%/14%/15%), the KH chart-of-accounts localization module (if using Odoo), NBC daily rate integration for multi-currency conversion, and — if the business is B2G — CamInvoice adapter scoping. This work runs in parallel with the migration; it cannot be left until after go-live. See /services/integration/api for the GDT and CamInvoice integration scope.

How long does an accounting system migration take?

A single-entity SMB migrating from QuickBooks to Odoo takes 8–13 weeks end-to-end. Peachtree migrations typically run 10–15 weeks because Peachtree's flat-file data is harder to extract than QuickBooks's structured export formats. Multi-entity or mid-market scope adds 4–8 weeks per additional entity.

• Week 1 — Discovery: COA audit, system access, cut-off date decision, stakeholder alignment.
• Weeks 2–3 — COA mapping: every account classified, gap decisions made, migration template signed off.
• Weeks 3–5 — New system setup: Odoo install, KH localization module, tax codes, multi-currency config, bank journals.
• Weeks 4–6 — Data migration: opening balances, open AR/AP invoices, fixed asset register, customer/vendor master (including TIN field population).
• Weeks 6–9 — Parallel run: both systems run simultaneously through one full month-end cycle. Reconcile to the riel and the cent before sign-off.
• Week 9–10 — Cutover: close old system, switch to new system as system of record, confirm GDT filing runs from new system.
• Week 10+ — GDT adapter go-live (if in scope): first live filing from new system, monitored for 30 days.

What does an accounting migration cost?

A QuickBooks → Odoo migration for a single-entity SMB (one legal entity, one accounting system, standard VAT) is typically quoted in the $4,000–$9,000 range on a fixed-scope basis. Peachtree migrations sit $1,000–$2,000 higher due to the harder data extraction. Multi-entity and mid-market projects are quoted after a paid discovery sprint.

We quote fixed scope, fixed price after a 1-week discovery engagement ($500, deducted from the project fee if you proceed). Discovery produces a COA mapping document, a data migration plan, a gap register, and a final quote. The reason for discovery-first pricing: migration cost varies sharply based on how clean the source data is. A QuickBooks file with 8 years of unreconciled suspense entries costs more to migrate than a clean file with 2 years of history — and that difference is not visible without looking.

Ongoing Odoo costs after migration: $0/year for Odoo Community (self-hosted), or Odoo Enterprise at approximately $150–$300 per user per year [TBC on current Enterprise pricing]. Hosting on a managed VPS or Odoo.sh runs $50–$200/month depending on scale. The GDT e-VAT adapter (if in scope) is a separate line item — see /services/integration/api for that pricing. The total cost of ownership over three years is typically lower than continuing to pay QuickBooks Online per-user licensing ($30–$90/user/month) while also paying a manual GDT filing clerk.

Common migration pitfalls in Cambodia

Most accounting migrations that stall or overrun do so because of predictable problems — all of them avoidable if caught in discovery.

• KHR rounding drift: QuickBooks stores amounts in USD only (or USD-primary). When those amounts are converted to KHR for GDT filings, the exchange rate used and the rounding method matter. A difference of ±1 riel per invoice line compounds across thousands of transactions into a material filing discrepancy. The migration must document the NBC rate used on each historical invoice date and use consistent rounding in the new system.
• GDT e-VAT re-do: migrating to a new accounting system resets the GDT integration. If the old system had any GDT connection (manual or automated), the new adapter must be built from scratch — it does not carry over. Plan the GDT go-live as a parallel project starting at week 1, not an afterthought at week 10.
• Multi-currency reconciliation gaps: businesses that invoiced in both KHR and USD in QuickBooks often have inconsistent exchange rates across historical invoices — different rates on the same day because someone typed a rate manually rather than pulling NBC. These inconsistencies surface during the parallel-run reconciliation. The fix is to document and accept the historical variance, then enforce NBC-rate discipline in the new system from day one.
• KH chart-of-accounts mapping errors: the Cambodia chart of accounts (installed via Odoo's KH localization module) uses account numbering that does not match QuickBooks or Peachtree defaults. Accounts mapped incorrectly produce wrong VAT return totals from the first filing. The mapping must be reviewed by an accountant with GDT filing experience, not just a technical implementer.
• TIN field gaps on customer and vendor records: GDT requires a TIN on every B2B invoice. QuickBooks does not mandate this field. When customer records migrate, TINs are frequently missing. These must be collected before go-live — not during the first GDT filing.
• Training underestimated: switching accounting systems is a change-management project as much as a technical one. Bookkeepers and accountants trained on QuickBooks or Peachtree need structured training on the new system before go-live, not a 1-hour walkthrough. Budget 2–5 days of structured training per accounting user, plus 30 days of supported use post-go-live.