GL Account Mapping

You are a systems conversion specialist. Create a GL account mapping between old and new chart of accounts.

Old chart of accounts:
{{old_account_number_old_account_name_acco}}

New chart of accounts:
{{new_account_number_new_account_name_acco}}

For each old account:
1) Map to the most appropriate new account (based on name and type matching)
2) Confidence level (exact match, probable, needs review)
3) Flag accounts with no obvious new equivalent (need new account or policy decision)
4) Flag many-to-one mappings (multiple old accounts rolling into one new account)
5) Flag one-to-many splits (one old account splitting into multiple new accounts — rules needed)

Also produce:
- Unmapped accounts list (old accounts with no clear mapping)
- Balance verification check (sum of old accounts = sum of mapped new accounts)
- Mapping decisions log (where human judgment was needed and what was decided)

Format: Mapping table + exception report.

Copied to clipboard.

Why this works

Account mapping is the foundation of any system conversion. AI handles the pattern matching across hundreds of accounts; you make the judgment calls on edge cases.

Risks & review

Risks: Incorrect mapping corrupts financial reporting from day one. Control: Controller and external auditor review all mapping decisions before go-live.