Bank statement mapping is the configuration that tells an accounting, ERP or treasury system how to interpret each line on an electronic bank statement. Banks label transactions with codes, such as BAI2 type codes, SWIFT MT940 transaction types or ISO 20022 bank transaction codes in camt.053 messages, and with free-text references. Mapping rules translate those codes and patterns into actions in the enterprise resource planning (ERP) system: post bank fees to a fees account, treat card settlements as clearing entries, or send customer receipts to cash application.
Each bank, and sometimes each country, uses codes differently, so mapping tables must be built and tested for every bank connection and kept up to date when formats change. Errors are costly: a wrongly mapped code can post entries to the wrong general ledger account or leave items unmatched, which breaks automated reconciliation and pushes work back to manual queues.
Ref 1010001281