3716930 - MT940 file upload fails when tag :86: is missing after tag :61:

In 'Manage Incoming Payment Files' app import of MT940 bank statement fails with error 'External - transaction code is not specified for transaction type MT940' when consecutive :61: tags are present without an :86: tag.

"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

SAP S/4HANA Cloud Public Edition

1. Access the 'Manage Incoming Payment Files' app.
2. Click on 'Import'.
3. Choose 'Bank Statement'.
4. Select the file.
5. Observe the import failure with the above-mentioned error

The SAP-delivered MT940 format mapping requires an :86: tag to follow each :61: transaction line. This is a technical limitation of the parser, which does not support consecutive :61: tags without an :86: tag in between. This is standard system behavior.

1. Switch to the standard import of bank statement files using the CAMT.053.001.02 format instead of the MT940 format mapping.
2. If altering the file before import is feasible, introduce an empty :86: tag between consecutive :61: tags to ensure successful processing.
   For example:
   :61:2511071107D1871,99NMSC5484727456//SAP SE 
   :86:
   :61:2511071107D1783,13NMSC5484188911//SAP SE 

mt940, :86: tag, :61: transaction line, sap s/4hana cloud, bank statement imports, format mapping, parser limitation, camt.053.001.02, import failure, transaction details, sap public cloud. , KBA , FI-BL-PT-BA-2CL , bank statement (Public Cloud) , Problem