3431879 - BBAN number is updated in the payment media file instead of IBAN

• BBAN number is updated in the payment media file instead of IBAN.
• Bank rejects the payment media file with the error message "Format of the account number specified is not correct. Account Number not in file profile." .

SAP S/4HANA Cloud

1. Access the app Manage Automatic Payments.
2. Execute the payment run.
3. Access the app Manage Payment Media.
4. Check whether IBAN is under the node <DbtrAcct>.
5. Instead of IBAN, BBAN is filled.

You have activated Dual Control for Sensitive Fields and IBAN is set as a sensitive field. When there is an unconfirmed change to the supplier/customer, the Valid From date for the IBAN is set to 31.12.9999. 

When the dual control for bank details is active, this is the default date. After confirmation, the date will be changed back to the creation date. This is the reason why BBAN is used instead of IBAN.

The changes need to be confirmed or rejected individually in the "Confirm Customer List (Accounting)" and/or "Confirm Supplier List (Accounting)" Apps. Kindly confirm the changes for the suppliers/customers before executing the automatic payment run.

3018771 - Sensitive field for customer/vendor

3393839 - Is it possible to Mass Confirm Multiple Customer or Supplier Sensitive Fields (Dual Control) in SAP S/4HANA Cloud?

Confirm Vendor List (Accounting), FK08, Changes for vendor & have not yet been confirmed, Message no. F2224, TIBAN, IBAN, BBAN, TIBAN_APAR, LFBK, Manage Automatic Payments, Manage Payment Media, CGI_CT, VALID_FROM, 12/31/9999, 31.12.9999, house bank, bank account number, bank key, <DbtrAcct> , KBA , FI-AP-AP-N-2CL , Master Data (Public Cloud) , FI-AP-AP-B1 , Payment transfer (w/o DE, US) , Problem