Merging duplicate general ledger accounts requires clear, contemporaneous documentation that creates an auditable trail and supports internal controls. Guidance from the U.S. Government Accountability Office and the American Institute of Certified Public Accountants stresses that the documentation should demonstrate why the merge was necessary, who authorized it, how balances were moved, and what controls were applied to prevent data loss or misstatement.
Required core documentation
The core record should include a formal rationale explaining the business reason for the merge, supported by an impact analysis that quantifies changes to opening and closing balances and any reclassifications across reporting periods. A separate document must show authorization from the appropriate finance or governance officer, and the updated chart of accounts with the duplicate accounts removed and the surviving account clearly identified. Supporting detail must include the journal entry or entries that effected the transfer, complete with narration, date stamps, preparer and reviewer signatures, and cross-references to subsidiary ledgers or control accounts. Evidence from the enterprise resource planning system such as change requests, ticket numbers, and system logs are essential to substantiate that the technical change matched the accounting action.
Evidence, testing and retention
Audit evidence should include reconciliations before and after the merge, sample transaction testing, and documentation of any adjusting entries made to align historical balances. Internal control documentation consistent with the Committee of Sponsoring Organizations of the Treadway Commission framework reinforces that segregation of duties and approvals were observed. For entities subject to the Sarbanes-Oxley Act and government auditors, retain records as required by law and audit policy, and preserve electronic logs to maintain an audit trail. Depending on jurisdiction and sector, retention requirements and acceptable formats vary, so align documentation with local regulators and auditor expectations.
Relevance, causes and consequences
Duplicate accounts often arise from decentralised chart ownership, legacy system migrations, or local accounting practices. Failure to document properly can lead to misstated financials, audit findings, weakened internal control opinions, and operational confusion across departments. In public-sector and multinational contexts, cultural practices around approvals and territorial reporting rules make rigorous, transparent documentation especially important to maintain trust and to comply with external reporting standards. Thorough documentation not only supports audits but also preserves institutional knowledge during staff turnover.