An accounting-system migration needs a clear finance acceptance decision. The new system may open correctly while customer balances, reporting categories or transaction histories remain wrong. Before go-live, management should be able to explain what moved, how it was checked and which differences are still unresolved.
A reconciliation and sign-off pack provides that evidence. The controls below are illustrative and should be adapted to the business. They cover finance-process and reporting requirements; software configuration, integration, security testing and deployment require their own implementation responsibilities.
Fix the scope and the accepted starting point
Record the entities, currencies, ledgers, reporting dimensions and periods included. Decide whether the migration carries full transaction history, open items or opening balances, and explain how older supporting records will remain accessible. Agree the cut-off date, the last permitted posting in the old system and how late transactions will be handled.
Keep an approved source snapshot: the final trial balance, relevant detailed ledgers, reconciliations and extraction details. Label its date and version so that later testing does not compare the new system with a moving source. If finance corrects the old records after extraction, log the correction and track it through the migration process.
Approve the chart-of-accounts mapping
Build a mapping from each old account to its new destination, including departments, projects or other dimensions used in management reporting. Explain where accounts are combined or split. A split may need transaction-level evidence rather than an arbitrary allocation of the closing total.
Have finance review how the mapping affects profit, assets, liabilities and reporting comparatives. Include accounts with no current balance if they are needed for history or future posting. Unmapped or duplicated codes should be investigated. A balancing journal to retained earnings or a suspense account can hide an error unless its accounting basis is understood and approved.
Reconcile totals and the detail underneath them
Start with the full trial balance and confirm that total debits and credits agree. Then compare each mapped balance and the supporting detail. Useful checks include:
- Customer and supplier totals against their control accounts, with invoice dates, due dates, credits and allocations preserved.
- Bank and cash balances against reconciliations, including outstanding items.
- Inventory quantities and values against the agreed source records.
- Fixed-asset cost, accumulated depreciation and individual asset records.
- Borrowings, payroll liabilities, taxes and intercompany balances against their schedules.
Suppose the old and new receivables reports both show RM240,000. One RM10,000 invoice could have been omitted while another was imported twice, leaving the grand total unchanged. Compare invoice identifiers and counts, review exceptions and test balances by customer. An agreed total is one check, not the whole acceptance test.
Test transactions across the cut-off
Identify which system owns each transaction stream during the change. Receipts, payments, invoices, credit notes and stock movements can otherwise be recorded twice or missed. Keep a register of transactions occurring during any posting freeze and reconcile their eventual entry.
Use representative end-to-end tests. Follow a sale through the customer account, receipt allocation and management report; follow a purchase through the supplier account and payment. Include reversals, partial settlements, foreign-currency items and other cases the business actually uses. Record expected results before testing and retain the evidence. A system change does not itself justify changing the accounting policy or recognition date.
Where e-Invoice is relevant, test that process as a separate requirement using the current official guidance. Our e-Invoice-ready accounting systems article covers the related data and exception questions.
Keep the evidence usable after migration
Test whether a reviewer can retrieve a historical transaction, its supporting document and the reconciliation explaining its balance. Exported data is of limited use if the business cannot read it after the old licence ends.
Section 245(3) of the Companies Act 2016 requires the relevant accounting records to be retained for seven years after completion of the transactions or operations concerned. Plan retention and access with the appropriate advisers, including any other applicable requirements, before retiring the old system.
Make the approval specific
The final pack should identify the tested version, approved mappings, reconciliations, test results and outstanding differences. Give each exception an amount or impact, owner, proposed remedy and target date. Define which failures prevent acceptance and who can approve any limited, conditional use. A supplier's completion notice should not substitute for management's finance review.
Repeat key reconciliations after the first live close and investigate new differences. Saifudin & Co's finance-process and technology advisory service can be discussed around these requirements. Management remains responsible for records, accounting decisions and approval; any advice and implementation work must be separately scoped.