Commission a chart-of-accounts mapping you can verify

Explain why the existing account structure no longer works. Management may need consistent categories across entities, clearer departmental reporting or a migration into another system. Identify the actual reports and users affected. A cleaner-looking chart can still fail if it removes distinctions the business needs to retain.

Specify whether the provider will recommend a structure, map historical records, implement changes or perform all three. State the periods and systems covered. Mapping current balances alone is different from restating detailed comparatives, and the fee should reflect that difference before the project begins.

Ask for every source account to have an approved destination or a visible unresolved status. Where an account must split across destinations, define the evidence and rule used. An old mixed account may require transaction-level analysis; it cannot always be mapped accurately through a single lookup row.

Separate account changes from changes to departments, projects or other dimensions. Ask how the provider preserves information that moves out of the account code. Require management to approve decisions that alter report meaning, rather than letting the migration team infer a new reporting policy from a spreadsheet label.

Specify the totals and reports that will be compared before and after conversion. Differences should be explained by the approved mapping, documented corrections or known limitations. A balanced trial balance alone does not show that expenses reached the right categories or that historical comparisons remain meaningful.

IRS electronic-record guidance calls for complete and accessible records. Use that principle to require a retained source-to-destination bridge and readable historical exports. The company should be able to answer a later question about an old account without depending on an obsolete software subscription or the consultant's memory.

Ask how the provider will handle transactions posted during the project. Freeze an agreed source version for testing and define how later changes are brought forward. Without a controlled version, a reconciliation can appear to fail because the source kept changing while the mapping was evaluated.

Review the mapping and representative report outputs before live changes. Name who can approve account merges, renamed categories and comparative restatements. Some changes may be difficult to reverse in the chosen software; have the provider explain the actual product behavior using current documentation before proceeding.

AICPA engagement guidance recommends defined deliverables and responsibilities. For this project, include a rollback or recovery approach appropriate to the system, approved change record and issue-handling process. Do not assume that a design fee includes live implementation support or correction of unrelated historical errors.

Require a short guide explaining the approved categories, dimensions and process for requesting a new account. Have the operating accountant classify a few representative transactions and explain where uncertain cases go. The goal is consistent maintenance, not memorization of every account code.

Include access restrictions in the design review if new dimensions expose departmental information. A useful reporting redesign should preserve the company’s approved boundaries on who can inspect sensitive detail.

Retain the final mapping, reconciliation, approvals and unresolved exceptions. Identify which historical reports should be used after conversion and how they differ from earlier versions. Accept the project when the company can maintain the structure and trace the transformation, with its limitations clear to future users.