Migrating From QuickBooks to Kingdee When You Enter China

The short answer

QuickBooks is an excellent small-business accounting platform, and it is not designed to file Chinese taxes or issue Chinese invoices. When a business enters China, the platform has to change, and the change is best treated as a controlled migration rather than a data import. The parts that matter are the opening balances, the master data, the chart-of-accounts mapping, and a parallel period where the old and new processes have to agree.

Kingdee is one of the most common destinations for this migration, particularly through its small-business and mid-market product lines, because Chinese compliance is native to the product. What follows is a practical view of what the migration involves and where it usually goes wrong.

Why QuickBooks stops working at the China border

The limitation is structural rather than a matter of features. QuickBooks assumes that an invoice is a commercial document and that compliance is expressed through the accounts. In China the invoice is a tax instrument issued through state-controlled infrastructure, reconciled against the ledger and the periodic filing, and the statutory statements and annual settlement are separate outputs with their own formats.

As a result, a business using QuickBooks in China ends up with the compliance work outside the system, typically in spreadsheets and a separate invoicing tool. That is survivable at very low volume and becomes a control problem as soon as volumes rise, because the reconciliation between what the system says and what was filed is manual and depends on one person.

What has to be migrated

Migration projects go wrong when they are scoped as 'bring everything across'. What actually has to move is smaller and more specific than that.

• Opening balances, agreed to the last filed return and the prior system, not just to the trial balance.
• Chart of accounts, mapped to a Chinese statutory structure rather than translated item by item.
• Customer and supplier master data, including tax registration details, verified before import.
• Open receivables and payables, with ageing, because these carry into the first Chinese close.
• Inventory quantities and valuation, which must reconcile before production costing is relied upon.
• Fixed asset registers, where the entity holds assets and depreciation must continue consistently.

Transaction-level history is usually not required. Bringing years of it across adds cost, risk, and reconciliation work without improving compliance, and it is normally better to keep the historic detail accessible in the old system and migrate only what the new system needs to operate.

The five migration risks

These are the failure modes that recur, in rough order of how often they cause trouble.

• Opening balances that agree with the system but not with the last filing, which creates a discrepancy that follows the entity for years.
• Master data imported without verifying tax registration details, producing invoices that fail verification later.
• A chart of accounts translated rather than reconstructed for Chinese statutory reporting, which forces manual reclassification at every close.
• No parallel period, so the first live month is also the first test of the new process.
• Undefined ownership of the migration after go-live, so reconciliation between old records and new stops as soon as the project team disbands.

Chart of accounts and the statutory framework

The chart of accounts is where a migration is quietly won or lost. A translated chart — the old accounts renamed — produces a system that cannot generate statutory statements without manual intervention, because the mapping between accounts and statement lines was never designed for that framework.

The better approach is to reconstruct the chart for Chinese statutory reporting and map the historic balances into it, accepting that some accounts will merge or split. That work is unpleasant, and it is what makes every subsequent close cheap. Our guide to China statutory reporting requirements lists the outputs the chart has to support.

In-flight balances and the opening entry

The opening entry is the single most examined artefact of any migration, because it is the point at which two systems are declared to agree. Getting it right means agreeing three things at once: the closing balances in the old system, the last returns filed with the authorities, and the opening entry in the new system. Where they differ, the difference has to be explained and documented rather than absorbed.

This is also where tax registration details and the entity's registration status have to be confirmed, because the invoicing configuration depends on them and errors are far cheaper to fix before the first invoice is issued than after.

Parallel running: the discipline that prevents surprises

Running both processes for a period is the step teams are most tempted to skip and the one that most reliably prevents an unpleasant first quarter. During parallel running, both the old process and the new one produce results, and the differences are investigated and explained before the old route is retired.

For a compliance-critical flow this is worth the extra weeks. It is the only mechanism that proves the new system produces the same numbers the tax authority already holds, and proving that before cut-over is dramatically cheaper than discovering the opposite afterwards.

Choosing the target system

Kingdee is a frequent target for good reasons: its small-business and mid-market lines are built around Chinese compliance, the partner network is local, and the product range means the same vendor can support the entity as it grows. But the target should be chosen on the flows, not the brand, and the same questions apply as in any selection.

• Can an invoice be issued and reversed from the system, and does the ledger reconcile to the invoice pool automatically?
• Are statutory statements and the annual settlement supported from the books?
• Is payroll handled inside the system or deliberately outside it?
• What does a demo look like on your own chart of accounts and your own opening balances?
• Who supports this in year three, and what does that cost?

If the entity is part of a foreign group, add the reporting question before you choose. Our SAP vs Kingdee comparison covers how consolidation needs change the answer, and the foreign company ERP checklist covers the requirements in full.

Timeline shape

A migration of this kind has four phases, and each should finish before the next is relied upon.

• Phase one: document the current process, decide the target system, and confirm registration and invoicing configuration.
• Phase two: build the chart of accounts, verify master data, and agree opening balances across all three references.
• Phase three: configure and test the compliance flows, issue and reverse a test invoice, and run a statutory close on real data.
• Phase four: parallel run, reconcile differences, then retire the manual route with the controls documented.

The temptation is to compress phase two and move quickly to phase four. Resist it, because phase two is where the discrepancies that would otherwise follow the entity for years are eliminated.

Common mistakes

• Migrating transaction history rather than balances, and spending the project budget on data that will never be used.
• Translating the chart of accounts instead of reconstructing it for statutory reporting.
• Importing master data without verifying tax registration details.
• Skipping the parallel period and treating the first live month as the test.
• Treating the migration as finished at go-live, when the reconciliation ownership has to continue afterwards.

Verdict

Entering China means adopting a system built for a filing regime, and the migration is best run as a controlled project with three agreement points: opening balances, master data, and a parallel period that proves equivalence. Done that way, the migration is unremarkable. Skipped, the discrepancies it leaves behind show up at the worst possible moment, and they are much more expensive to resolve then. For entities that export as well as trade domestically, the requirements extend further — see our guide to export tax rebate in an ERP.