How To Fix SEPA_CI_LIMIT013 - IBAN and internal account ID must not be filled at the same time

SEPA_CI_LIMIT013 - Overview

• Message type: E = Error

• Message class: SEPA_CI_LIMIT - SEPA CI Limit: Messages

• Message number: 013

• Message text: IBAN and internal account ID must not be filled at the same time

Self-Explanatory Message

Since SAP believes that this specific error message is 'self-explanatory,' no more information has been given.The majority of messages in the SAP system have a message text, however this is frequently insufficient to comprehend or resolve the problem.

To make things easier, more detailed information is frequently added to describe the issue, how to fix it, and the necessary steps or configuration modifications.

Unfortunately, there isn't any extra information in this error notice.

What else can you do?

First, use our AnswerBot below to get a possible cause and solution (requires a premium subscription).

Also, review the in-depth Common Questions & Answers listed below; you could discover a solution there or be able to connect with others who have faced similar challenges.

You can also try searching the SAP support portal (support.sap.com) but you need a special user ID to access it. It is possible that an SAP support note exists that provides additional details about the mistake or even steps for fixing it.

SEPA_CI_LIMIT013 - Details

• The SAP error message SEPA_CI_LIMIT013 indicates that both the IBAN (International Bank Account Number) and the internal account ID are filled in the same context, which is not allowed. This error typically occurs in the context of SEPA (Single Euro Payments Area) transactions, where the system expects either an IBAN or an internal account ID, but not both.
  
  Cause:
  The error arises when:
  
  A user or a process attempts to create or process a payment or transaction where both the IBAN and the internal account ID fields are populated.
  The system is designed to use one identifier for the transaction, and having both leads to ambiguity.
  
  
  Solution:
  To resolve this error, you should:
  
  
  Identify the Source of the Data: Check the transaction or data entry point where the error is occurring. This could be in a payment run, a vendor master record, or a customer master record.
  
  
  Remove One of the Identifiers: 
  
  If you are using an IBAN,