Mappings

Account and column mappings. Changes take effect only through approved change requests.

Account mapping

Every legacy account and where it lands in the new chart of accounts. Type and subtype compatibility is checked for each pair.

In effect: approved version 1 (127 accounts).

Showing 1 of 127 legacy accounts that need attention
Legacy account	Current target	Compatibility	Suggestion	New target	Rationale
1205 Allowance for Doubtful AccountsContra asset	1200 Accounts ReceivableAccounts receivable	target exists oktype oksubtype conflict	1210 Name match 0.75	New target for 1205	Rationale for 1205

View-only in public demo

Re-pointing a legacy account at a different target is a change request the implementation lead and the customer controller both approve, after which a fresh run re-checks every number it touches.

Column mappings

How each export's columns are read into canonical fields. One approved set per dataset.

account_mapping_v2.csv (Account mapping)
ledgerpro_ap_aging_20251231.csv (Ap aging)
ledgerpro_ap_aging_20260630.csv (Ap aging)
ledgerpro_ar_aging_20251231.csv (Ar aging)
ledgerpro_ar_aging_20260630.csv (Ar aging)
firstcascade_4471_statement.csv (Bank transactions)
ledgerpro_bills.csv (Bills)
ledgerpro_customers.csv (Customers)
firstcascade_fx_eurusd.csv (Fx rates)
ledgerpro_gl_detail_2026H1.csv

Account mapping versions

Version 1 approved 127 accountschange request