How To Fix 1N513 - Mandate sender &1 is not account holder &2

SAP Error Message - Details

• Message type: E = Error

• Message class: 1N - BCA: Payment Item Dialog

• Message number: 513

• Message text: Mandate sender &1 is not account holder &2

What causes this issue?

The mandate sender entered is not the account holder &v2&

System Response

The system issues an error message and will not allow you to continue with this transaction until the error is resolved.

How to fix this error?

Enter the account holder &v2& as the mandate sender

Procedure for System Administrators

Error message extract from SAP system. Copyright SAP SE.

Smart SAP Assistant

• What is the cause and solution for SAP error message 1N513 - Mandate sender &1 is not account holder &2 ?

  The SAP error message 1N513 indicates that there is a mismatch between the mandate sender and the account holder in the context of direct debit processing. This error typically arises in the SAP system when dealing with payment processing, particularly in the area of SEPA (Single Euro Payments Area) direct debits.
  Cause:
  The error message "Mandate sender &1 is not account holder &2" suggests that the system is trying to process a direct debit mandate where the sender of the mandate (the entity that is authorized to collect the payment) does not match the account holder (the entity whose account is being debited). This can occur due to several reasons:
  
  Incorrect Configuration: The mandate may have been set up incorrectly, linking the wrong sender to the account holder.
  Data Entry Errors: There may be typographical errors in the account holder's details or the mandate sender's details.
  Changes in Account Holder: The account holder may have changed, but the mandate has not been updated accordingly.
  Multiple Mandates: There may be multiple mandates for the same account, leading to confusion in the system.
  
  Solution:
  To resolve this error, you can take the following steps:
  
  Verify Mandate Details: Check the mandate details in the SAP system to ensure that the mandate sender and account holder are correctly configured. This can usually be done in the transaction code related to mandate management (e.g., transaction code F110 for payment runs).
  Update Mandate Information: If there is a mismatch, update the mandate to reflect the correct sender and account holder. This may involve creating a new mandate if the existing one is incorrect.
  Check Customer Master Data: Ensure that the customer master data for both the mandate sender and the account holder is accurate and up-to-date.
  Consult Documentation: Review any relevant documentation or guidelines for setting up mandates in your SAP system, especially if you are working with SEPA mandates.
  Test the Changes: After making the necessary updates, perform a test run of the payment process to ensure that the error no longer occurs.
  
  Related Information:
  
  Transaction Codes: Familiarize yourself with relevant transaction codes such as F110 (Automatic Payment Transactions), FSEPA (SEPA Mandate Management), and BP (Business Partner) for managing customer data.
  SEPA Compliance: Ensure that your organization is compliant with SEPA regulations, as these can affect how mandates are processed.
  SAP Notes: Check for any SAP Notes related to this error message, as there may be patches or updates that address specific issues with mandate processing.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or refer to SAP community forums for additional assistance.