Correcting Opening Balances in Your Accounting System After Migrating Accounts
📅 DD/MM/YYYY
When migrating accounts to a new accounting system, correcting opening balances begins by establishing the migration date and retrieving an approved trial balance from the previous system. Separate general ledger balances from subsidiary details, currencies, and inventory, then reconcile each category rather than using an opening balance difference account to conceal discrepancies.
An accountant moves from old spreadsheets and files to a new system, then discovers that customer, supplier, and inventory balances do not match the figures the team relied on at the end of the previous year. The value of an accounting system during migration lies not in importing an Excel file quickly, but in preserving the reference for every balance and testing whether it can be explained and reconciled after go-live. Any subsequent adjustment must be linked to the cutoff date and an approved audit trail.
This article explains a practical, step-by-step approach to diagnosing the problem, with examples from businesses operating in Saudi Arabia. It identifies the documents needed to resolve each issue and the testing criteria to apply after any correction. The article addresses a specific accounting problem in its operational context and does not treat technology as a substitute for professional judgment or original documentation.
How Do You Start Reconciling Beginning-of-Period Balances in an Accounting System?
Start by determining the date as of which the figures must be correct and the scope of accounts, customers, or branches included in the review. Retain a copy of the initial report, then separate source records from entries and aggregations. An accounting system helps consolidate these references when permissions, accounts, and data are configured correctly, but generating a single report does not replace comparing both sides and verifying the reasons for exceptions.
Practical application: Book a practical demonstration of the resolution workflow in the accounting system
Steps to Correct Opening Balances After Accounting Data Migration
1. Establish the Accounting Data Migration Date
The accounting question here is not merely why one figure does not equal another, but why transactions are recorded in both systems on the same date. This directs attention to an unclear migration date that allows revenue and expenses to be duplicated. If an external party such as a customer, bank, or supplier is involved, obtain its evidence; if the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can be explained months after it is made.
The review requires more than a screenshot from the software. Use a cutoff record, the old trial balance, and reports from the first day of the new system. Allocate one column to the source of evidence, another to the financial impact, and a third to the reason accepted by management. Apply the following step: define the last posting time in the old system, the first posting time in the new system, and the rules for late transactions. Do not delete the original transaction to make the records look clean. Instead, use a correction process that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.
Practical example: A business selects January 1 but records New Year’s Eve sales in both systems. Case closure criterion: No transaction is duplicated after comparing the list of the last transactions in the old system with the first transactions in the new system. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Organizing General Ledger Accounts and Reconciliations
2. Approve the Source Trial Balance
The investigation starts with the warning sign the accountant encounters: the team imports figures from an unapproved report and then modifies them again. A common mistake is to jump to a correcting entry before understanding the source, because this may shift the difference to another account instead of resolving it. The suspected issue here is data exported before adjustments were approved or from the wrong financial period. Review the transaction date and the related branch or account, then ask whether the event actually occurred or was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.
Start with a single auditable file containing the final trial balance, closing entries, and the prior-year approval memorandum. First rule out differences confirmed to belong to another period or account, then approve a fixed reference copy with a version number, date, and authorized signature. Place the document numbers side by side so that each item can be followed without searching again. Do not combine multiple errors in one reconciliation line when their causes differ; a solution that cannot be explained is not a sound basis for a reliable financial close.
Practical example: An old Excel file did not include the final annual depreciation entry. Case closure criterion: Assets, liabilities, and equity match the approved source balances. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Understanding Customer and Supplier Account Statements
3. Reconcile the Chart of Accounts Before Accounting Data Migration
When reports indicate that more than one old account is transferred into a single general ledger account without a detailed breakdown, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is combining accounts of different types or reversing their debit and credit nature. Do not treat it as a conclusion before reviewing the evidence; a data entry error may coexist with a legitimate timing difference. Identify the impact on revenue, expenses, assets, and liabilities, and determine whether the result changes a total account or only its underlying detail.
Assemble the following evidence file: the old and new charts of accounts, the mapping table, and the balance for each account code. Ideally, every document should have an original number and date and be linked to the same transaction in the general ledger or system log. Then carry out the practical procedure: prepare a clear mapping with rules for accounts that have been split or merged. Record the comparison in a separate statement with columns for the amount, source date, and resolution status, and avoid personal notes that are difficult for the reviewer to understand. If a document is incomplete, keep the transaction under follow-up rather than assuming information that the relevant party has not confirmed.
Practical example: An old prepaid expenses account is transferred to general expenses in the new chart. Case closure criterion: The totals of the mapped accounts agree with the original trial balance. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Guide to Organizing Warehouses and Inventory Counts
Next step for your business: Compare system plans before moving away from manual spreadsheets
4. Customers and Open Invoices
This step becomes important when you notice that total receivables match the trial balance but the aging report is incorrect. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is the import of an aggregate balance for each customer without invoice dates or numbers; independent evidence is needed to support it. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, connect the diagnosis to the source of the transaction, the person who approved it, and its date, rather than merely to the amount of the difference.
To confirm or rule out the cause, obtain customer statements, unpaid invoices, advance payments, and due dates. Match documents by invoice or voucher number, amount, and bank or inventory reference, where available, rather than by totals alone. The appropriate procedure in this case is to transfer open-item details with their dates and link unallocated receipts. If more than one explanation emerges, test each separately and retain a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.
Practical example: A customer has a balance of SAR 20,000 spread across invoices of different ages. Case closure criterion: Customer-level details match the receivables account in the general ledger, and every invoice can be traced. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Guide to Reading Financial Reports
5. Suppliers and Advance Payments
The situation may not seem significant at first: a supplier has the correct credit balance but payments cannot be allocated to invoices. However, it reveals a potential weakness: the import of a net balance that conceals advances or reciprocal claims. As such cases accumulate, they may affect another report or a collection or disbursement decision. It is preferable to isolate questionable transactions from valid ones and define the time range and responsible party before searching through thousands of entries. Use one document with a clear number as the unit of review, then roll the result up to the total account when finished.
Do not start with a summary report without its details. The documents you need here are supplier statements, advances, credit and debit notes, and payments due. Use them to reconstruct the transaction history in chronological order, then separate open invoices, advance payments, and discounts due. Prioritize cases by material amounts, age, and transactions involving external parties. If an accounting entry is needed, link it to a document, approval, and user permission, while retaining the original entry information for subsequent tracking and review.
Practical example: One supplier has unpaid invoices and an advance for a future delivery. Case closure criterion: The detailed payables match the aggregate account while the original document is retained. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Financial Reports Required from the System
Next step for your business: Create an account to try organizing your business data
6. Bank Accounts, Cash Accounts, and Outstanding Reconciliation Items
The accounting question here is not merely why one figure does not equal another, but why the old bank balance matches while the new bank statement differs. This directs attention to the transfer of the book balance without a list of deposits and transfers pending reconciliation. If an external party such as a customer, bank, or supplier is involved, obtain its evidence; if the transaction is internal, retain the approval trail. Do not confuse an acceptable accounting explanation with an attempt to make the balance look better before submitting the report. A good correction can be explained months after it is made.
The review requires more than a screenshot from the software. Use the last bank reconciliation, bank statement, cash vouchers, and outstanding transactions. Allocate one column to the source of evidence, another to the financial impact, and a third to the reason accepted by management. Apply the following step: transfer the approved balance together with a separate register of outstanding items and their dates. Do not delete the original transaction to make the records look clean. Instead, use a correction process that makes it possible to understand what happened, taking into account the documentation, invoicing, and internal control requirements relevant to the transaction.
Practical example: A deposit in transit of SAR 9,000 was included in the last reconciliation in the old system. Case closure criterion: Old timing differences gradually clear without being recorded twice. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Sales and Purchase Accounting Details
7. Inventory Quantities and Values
The investigation starts with the warning sign the accountant encounters: the total value is transferred but item records differ from the inventory count or cost. A common mistake is to jump to a correcting entry before understanding the source, because this may shift the difference to another account instead of resolving it. The suspected issue here is incorrect unit conversions, quantities transferred without costs, or selection of the wrong warehouse. Review the transaction date and the related branch or account, then ask whether the event actually occurred or was recorded in a different place or period. This distinction shortens the investigation and prevents the error from multiplying at closing.
Start with a single auditable file containing the approved inventory count, item records, units of measure, and cost layers. First rule out differences confirmed to belong to another period or account, then test high-value items, barcodes, conversions, and valuation in detail. Place the document numbers side by side so that each item can be followed without searching again. Do not combine multiple errors in one reconciliation line when their causes differ; a solution that cannot be explained is not a sound basis for a reliable financial close.
Practical example: Fifty cartons of a fast-selling item are transferred as fifty individual units. Case closure criterion: Total item valuation equals the general ledger inventory account at cutoff. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Procurement System Functions
8. Fixed Assets and Accumulated Depreciation
When reports indicate that the total asset value agrees but individual asset data is incomplete, start by describing the difference in writing rather than merely telling management that the figures do not match. The cause worth testing is the transfer of net value alone without the asset cost, accumulated depreciation, and relevant dates. Do not treat it as a conclusion before reviewing the evidence; a data entry error may coexist with a legitimate timing difference. Identify the impact on revenue, expenses, assets, and liabilities, and determine whether the result changes a total account or only its underlying detail.
Assemble the following evidence file: the fixed asset register, acquisition cost, date available for use, and accumulated depreciation. Ideally, every document should have an original number and date and be linked to the same transaction in the general ledger or system log. Then carry out the practical procedure: prepare an individual asset record that enables future depreciation to be calculated in accordance with policy. Record the comparison in a separate statement with columns for the amount, source date, and resolution status, and avoid personal notes that are difficult for the reviewer to understand. If a document is incomplete, keep the transaction under follow-up rather than assuming information that the relevant party has not confirmed.
Practical example: Old equipment is transferred at net book value, omitting historical accumulated depreciation. Case closure criterion: The asset and its accumulated depreciation match the corresponding accounts in the trial balance. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Comparing Cloud and Traditional Accounting
Next step for your business: Request a demonstration of how to monitor controls and reports
9. Taxes and Open Periods
This step becomes important when you notice that a tax balance does not match the return or there are unposted credit or debit notes. Before changing any balance, ask how the data moved from the document to the report. The initial hypothesis is the transfer of an aggregate account without separating the period, notes, and liability; independent evidence is needed to support it. Correcting the final figure without correcting the procedure may cause the problem to recur the following month. Therefore, connect the diagnosis to the source of the transaction, the person who approved it, and its date, rather than merely to the amount of the difference.
To confirm or rule out the cause, obtain tax reports, tax returns, credit and debit notes, and reconciliation memoranda. Match documents by invoice or voucher number, amount, and bank or inventory reference, where available, rather than by totals alone. The appropriate procedure in this case is to reconcile tax balances with the relevant documents and returns before approval. If more than one explanation emerges, test each separately and retain a copy of the report before correction. Comparing the situation before and after correction helps ensure that the entry or allocation has not created an additional difference.
Practical example: A credit note issued before migration is used after the new system goes live. Case closure criterion: The effect of prior-period adjustments remains clear in the first return after migration. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: Accounting Solution Features
10. Reconcile Beginning-of-Period Balances and Run a Parallel Trial
The situation may not seem significant at first: differences are discovered after many invoices and purchases have been recorded in the new system. However, it reveals a potential weakness: a direct migration without acceptance tests or a frozen copy of the opening balances. As such cases accumulate, they may affect another report or a collection or disbursement decision. It is preferable to isolate questionable transactions from valid ones and define the time range and responsible party before searching through thousands of entries. Use one document with a clear number as the unit of review, then roll the result up to the total account when finished.
Do not start with a summary report without its details. The documents you need here are reconciliation records, trial-run reports, the discrepancy list, and permissions. Use them to reconstruct the transaction history in chronological order, then run a defined test period, then lock the opening balance file and approve a numbered correction for each discrepancy. Prioritize cases by material amounts, age, and transactions involving external parties. If an accounting entry is needed, link it to a document, approval, and user permission, while retaining the original entry information for subsequent tracking and review.
Practical example: A company runs the new system on a trial basis for a week before final approval. Case closure criterion: Each balance can be compared with the source again without affecting live transactions. Do not approve the resolution before verifying the result in the detailed report and its associated document.
For more on this stage: How to Calculate Value Added Tax
Practical Example: Reconciling Beginning-of-Period Balances After Migrating Accounts
An accountant moves from old spreadsheets and files to a new system, then discovers that customer, supplier, and inventory balances do not match the figures the team relied on at the end of the previous year. Do not assume that the first difference you identify explains all the figures. Create a working copy containing the balance or report before correction, then link it to the original document and the record of dates and users. If the review reveals two different causes, separate them into independent cases: one may require an accounting correction, while the other may be a timing difference that does not require a new entry.
Start with the highest-risk items and then complete the list in order: define the last posting time in the old system, the first posting time in the new system, and the rules for late transactions; transfer open-item details with their dates and link unallocated receipts; test high-value items, barcodes, conversions, and valuation in detail; run a defined test period, then lock the opening balance file and approve a numbered correction for each discrepancy. After each step, generate a new detailed report rather than relying on a change in the total. Have the accounting manager or reviewer sign off on the reason for the correction and its effect on the period, and assign a follow-up owner to cases that do not yet have sufficient supporting documentation.
Summary Comparison Table: Before and After Correction
| Balance | Required Test | Risk of Neglect |
|---|---|---|
| Initial observation | Transactions are recorded in both systems on the same date | Define the last posting time in the old system, the first posting time in the new system, and the rules for late transactions |
| Decisive document | Supplier statements, advances, credit and debit notes, and payments due | The detailed payables match the aggregate account while the original document is retained |
| Status after correction | Each balance can be compared with the source again without affecting live transactions | Run a defined test period, then lock the opening balance file and approve a numbered correction for each discrepancy |
Opening Balances Checklist Before Go-Live
• Define a single cutoff date and a list of accounts, branches, or suppliers included in the review.
• Retain the report and documents as they were before any amendment or posting.
• Match records at the individual transaction level, not merely at the total level.
• Classify each difference as a timing issue, a recording error, or a matter requiring professional judgment.
• Do not post a reconciliation entry without clear supporting documentation and approval from the authorized person.
• Regenerate the detailed report and entries, and document that the cause has been resolved.
• Assign an owner and review date to remaining cases, and record why they have not been closed.
• Keep a copy that can be rechecked when preparing or auditing financial statements.
Ready to Try the System?
Start your free trial or speak with the sales team to help choose the right solution.
Frequently Asked Questions
Is Entering a Balanced Opening Trial Balance Enough?
No. Customer, supplier, inventory, and asset balances must be reconciled with the aggregate accounts.
Should I Migrate All Historical Entries to the New System?
The choice depends on regulatory and operational requirements. Opening balances may be sufficient if historical records are archived at an approved cutoff date.
How Do I Handle Negative Customer Balances?
Review advances, credit and debit notes, and unallocated amounts instead of transferring them arbitrarily.
Can Opening Balance Differences Be Eliminated With a Single Entry?
Not without identifying the cause, the supporting document, and the accounting policy governing the correction.
What Test Should Be Performed Before Final Go-Live?
Generate the opening reports again and compare them with the source, reviewing a detailed sample from every material account.
Conclusion:
The success of resolving the problem is not measured by the disappearance of a single discrepancy from the screen, but by the ability to trace every transaction, understand its impact, and prevent recurrence. Use an accounting system to consolidate accounts, documents, and reports into a clear workflow, then link correction approval to a responsible person and a test. Most importantly, report results must be reproducible and verifiable. This is the difference between a figure that appears correct and accounting data that can be relied on for operations and decisions.
If you would like to test this workflow using your own business data: Start a trial of the accounting solution that suits your team
Manage Your Business with Greater Flexibility
Try Digital Business for free. Start issuing electronic invoices designed to meet ZATCA requirements in minutes.


