Bank statement import fails in cash management due to missing transaction code mapping

ERP Infor CloudSuite
, , , , , , , ,
1

We’re experiencing failures with our daily bank statement import process in Cash Management. The import job runs but consistently fails when it encounters certain transaction codes from our bank’s BAI2 format files.

The error log shows ‘Transaction code mapping not found’ for codes like 165, 475, and 195. Our import job configuration seems correct, and we’ve verified the file format matches the template. The bank transaction code mapping table appears incomplete for these newer transaction types our bank recently introduced.

This is blocking our daily reconciliation process and creating a backlog of unprocessed statements. Has anyone dealt with similar transaction code mapping issues? What’s the proper way to add custom bank transaction codes to the mapping configuration?

2

We had this exact issue last year when our bank updated their transaction code structure. The problem isn’t just adding the codes - you need to ensure they’re mapped to the correct GL accounts and reconciliation rules.

Go to Cash Management Setup > Bank Transaction Codes and add entries for each missing code. Make sure to specify:

  • Transaction type (debit/credit)
  • Reconciliation behavior (auto-match or manual review)
  • Default offset account

Also check your import job’s error handling settings. Sometimes the job is configured to fail completely on any unmapped code rather than skipping and logging.

3

For wire transfers (165) and similar high-value transactions, I’d recommend manual review initially. ACH credits (475) can usually be auto-matched if you have good invoice matching rules configured.

Here’s a sample configuration entry:


BankCode=165
Type=CREDIT
Reconciliation=MANUAL_REVIEW
OffsetAccount=1100-WIRE-CLEARING

The key is understanding your bank’s specific code definitions. BAI2 codes can vary slightly between institutions.

4

I’ve seen this before. The transaction code mapping table in Cash Management needs to be updated manually for new bank codes. Check your bank’s BAI2 documentation for what those codes represent - 165 is typically wire transfers, 475 could be ACH credits. You’ll need to map them to the appropriate CloudSuite transaction types in the configuration.