SAP Knowledge Base Article - Public

3795545 - Error 'Record type 61: Amount could not be identified (data error)' in Manage Incoming Payment Files - SAP S/4HANA Cloud Public Edition

Symptom

  • During MT940 upload: error “Record type 61: Amount could not be identified (data error).” is raised in Manage Incoming Payment Files

Environment

  • Product: SAP S/4HANA Cloud Public Edition
  • Bank statement (Public Cloud)

Reproducing the Issue

  1. Import the MT940 file using Manage Incoming Payment Files
  2. Check the log
  3. Observe the error message 'Record type 61: Amount could not be identified (data error)' in the log

Cause

  • The MT940 file was not compliant: field 61 transaction code did not begin with ‘N’, ‘S’, or ‘F’, which is mandatory, leading to the parsing error.

Resolution

  1. For the MT940 error, ensure the file complies with SWIFT MT940 specifications:
  2. In field 61, the transaction code must be 4 characters and start with ‘N’, ‘S’, or ‘F’.
  3. Contact the bank to provide a corrected MT940 file that adheres to the standard, then re-upload.

Keywords

ebs processing rule, bank statement processing rules, note to payee, memo text contains, gl account derivation, external transaction type, automated rule, one-step posting, reprocess bank statement items, mt940 field 61, transaction code n s f, parsing error, record type 61 amount could not be identified, FB794 , KBA , FI-BL-PT-BA-2CL , bank statement (Public Cloud) , Problem

Product

SAP S/4HANA Cloud Public Edition all versions