Before importing bank transactions into ERP: a preparation checklist
Importing bank transactions requires more than establishing a connection. Decide how accounts and transaction types will be mapped, who will review exceptions and how results will be verified. This checklist supports preparation; confirm supported banks and functions for the selected product separately.
Inventory accounts and currencies
List the companies, bank accounts, currencies and corresponding ERP accounts. Separate accounts belonging to different companies at the same bank. Assign an owner and review date to the mapping register.
Map transaction types using examples
Select representative receipts, payments, charges, interest and internal transfers. Plan how unclear descriptions will be held for review instead of assigned to an incorrect account. Mask customer data before sharing examples.
Define permissions and approvals
Identify who establishes the connection, edits mappings and approves imports. Do not include passwords or bank access details in email or support messages. Verify the permission options available in the chosen product during setup.
Test duplicate scenarios
In a test environment, examine repeated downloads, retries after interrupted imports and late historical records. Confirm how records are recognised with the implementation team; do not assume all products use the same method.
Specify reconciliation criteria
Compare the bank statement with ERP results by date, account, currency, transaction count and amount. Assign responsibility and a resolution time for missing or unmatched entries. An equal grand total alone does not prove correct mapping.
Start with a controlled scope
Begin with a few accounts and a short period. Expand only after accounting and technical teams review the results. Document how to pause imports and investigate errors. Confirm bank coverage, modules, usage credits and licence terms for Online Hesap Özeti during quotation.
