Switching From Accounting Software to an ERP: Chart of Accounts, Opening Balances and Cut-Over

Signs the Accounting Software Is No Longer Enough

If the team keys the same data into several places every day, or a new branch cannot be consolidated into one report, the accounting software has become the bottleneck. It was built to keep the books well, not to hold stock, purchasing and sales for the whole company.

Before you migrate, be clear where the problem actually is. Some businesses do not need a full switch: a stock or sales system that posts into the existing accounting software is enough.

ERP vs accounting software: what is the difference?

Switching From Accounting Software to an ERP: What to Prepare

Migrations do not stall on installation. They stall on the legacy data and the cut-over date. Sequence the work properly and the switch happens without day-to-day operations stopping.

The first real task is migrating the chart of accounts, because an ERP wires that chart into inventory, purchasing, and sales. A chart built for accounting software was usually designed to produce financial statements and nothing else, so lifting it across unchanged tends to leave you unable to split cost by branch or by product line.

The safe approach is to cut over on a period boundary rather than mid-month, and to run the old and new systems in parallel for one cycle before switching the old one off. This is where teams get impatient, and where the trouble shows up at year-end close.

• Chart of accounts. Review it before moving and decide what dimensions to add: cost centres, branches, product lines.
• Opening balances. Every account balance at the cut-over date must reconcile against the old system's trial balance first.
• Master data. Customers, suppliers, and items, with the codes you intend to keep using.
• Open documents. Unclosed purchase orders, sales orders, receivables, and payables move across as open items.
• History. Most of it does not need to migrate. Keeping the old system read-only is usually enough for audit.
• Cut-over date. Pick the first day of a new accounting period and tell everyone in advance when to stop keying into the old system.

ERP consulting: plan the move so every figure comes across

How Do You Move a Chart of Accounts Into an ERP?

You build a mapping table from every old account to its place in the new chart, then prove the mapping with numbers. Copying the old chart across wholesale is the mistake. Charts built for accounting software tend to carry one account per branch or per product line, because the software had no other way to split the figures. In an ERP those splits belong in dimensions such as branch or cost centre, which leaves the chart itself holding only the accounts the financial statements need, and usually a good deal shorter.

Start by exporting the old chart and the trial balance for the last closed month. Design the new chart with the dimensions you want, then build the mapping, keeping each old account code in a reference field on the new account so last year's figures can still be traced.

The test uses your own numbers. Run that month's trial balance through the mapping: debits and credits must still balance, and each new account must equal the sum of the old accounts mapped to it. Many old accounts folding into one new account is harmless. One old account splitting into several accounts or branches is where care is needed, because someone has to allocate the balance by hand and keep the working.

Clean up the old system before any of this. A balance that is already wrong becomes an opening balance nobody can explain in the new system, and it is far harder to correct there than in the system that produced it.

• Suspense and clearing accounts. Resolve them to zero rather than carrying an unexplained balance across.
• Bank accounts. Reconcile to the statement up to the latest month.
• Old receivables and payables. Confirm they are genuinely outstanding and correct mistakes in the old system.
• Duplicate customers and suppliers. Merge them to one code each and fill in missing tax IDs, which tax invoices and withholding tax certificates both need.
• Item codes. Retire discontinued items and merge products that exist under more than one code.
• Dormant accounts. Close them in the old chart instead of carrying them into the new one.

What Goes Into Opening Balances, and When Should You Cut Over?

Opening balances are every account's closing balance on the day before cut-over, taken from the old system's trial balance. In an ERP a total is not enough for accounts that other modules depend on. Those need their detail, or the new system knows the balance but cannot work with it: it knows what customers owe in total, but cannot match a payment to the invoice it settles.

The best cut-over date is the first day of a new financial year. The whole year's accounts then come from one system, and last year's comparatives come from the old one, already closed. If that cannot wait, cut over on the first day of a month at the least. Thai VAT (the PP.30 return) and withholding tax are both filed monthly, so a mid-month cut-over means that month's returns have to be assembled from two systems.

If you are aiming for the start of a financial year, count backwards from it: an SME-level ERP takes around 4–6 months to implement. If the project runs late, moving the cut-over to the start of a later month is safer than going live before testing is finished.

• Inventory valuation method. Keep the one you use, whether weighted average or FIFO. If you want to change it during the move, talk to your auditor first: for tax purposes a change needs Revenue Department approval.
• Tax invoice numbering. The new system must not reissue numbers the old one has already used. Agree the new series before day one.
• Stock count. Count as close to cut-over as you can and adjust the old system to match before bringing the figures across.
• Documents that straddle the date. Decide which system owns open items such as purchase orders still awaiting delivery.

How Long Should the Old System and the ERP Run in Parallel?

At least one month-end close. Running in parallel means keying real transactions into both systems, closing the month in both, and comparing the results. If the figures agree within the criteria you set, the old system can be retired. If they do not, find the cause and run another cycle.

Parallel running has a real cost, because the accounting team does every job twice for as long as it lasts, so it should not drag on. What shortens it is agreeing the pass criteria before you start: which reports get compared, and how far apart they may be.

Once it passes, set the old system to read-only rather than deleting it, and leave most of the history there instead of migrating it. Thailand's Accounting Act requires accounts and supporting documents to be kept for at least five years from the date the accounts are closed, and an old system that still opens answers an auditor's or a Revenue officer's question directly. If the old product is a subscription you plan to cancel, export the key reports for every month before the contract ends, since access may end with it.

• Trial balance. Every account agrees once run through the mapping.
• Receivables and payables ageing. Each customer's and supplier's outstanding balance agrees.
• Stock quantity and value. Compared per warehouse, and against a physical count.
• VAT reports and the month's withholding tax. Both systems produce the same returns.
• Bank reconciliation. It can be completed entirely from the new system.

Do You Have to Replace Everything?

No. When the problem sits in one area, such as stock, multi-channel sales or job costing, keeping the accounting software for the books and adding a system for that one area, which posts its figures into accounting, is often faster and lower-risk than moving the whole company onto an ERP. Agree up front which system owns which number, or the double keying comes back.

Custom software that connects to your accounting software