How To Fix 1FA800 - Use IBAN+SWIFT as offset trans.type &1 of &2 has mandate checks enabled

1FA800 - Overview

• Message type: E = Error

• Message class: 1FA - Betragskündigungen und Freibeträge

• Message number: 800

• Message text: Use IBAN+SWIFT as offset trans.type &1 of &2 has mandate checks enabled

What causes this issue?

Mandate checks have been enabled for the offsetting transaction type of
the transaction type you entered.

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?

Do one of the following:
Select a transaction type for which mandate checks have not been enabled
for the offsetting transaction type
Select the account identification method<LS> IBAN+SWIFT</> to enter
mandate details

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 1FA800 - Use IBAN+SWIFT as offset trans.type &1 of &2 has mandate checks enabled ?

  The SAP error message 1FA800 indicates that there is an issue related to the payment processing configuration, specifically concerning the use of IBAN and SWIFT codes in conjunction with mandate checks. This error typically arises when a payment transaction is being processed, and the system detects that the transaction type requires the use of IBAN and SWIFT codes, but the necessary mandate checks are not properly configured or are conflicting.
  
  Cause:
  
  Mandate Checks Enabled: The transaction type you are trying to process has mandate checks enabled, which means that the system expects to validate the payment against a mandate (authorization) that has been set up for the customer/vendor.
  Missing or Incorrect IBAN/SWIFT: The IBAN or SWIFT code may be missing or incorrectly configured in the vendor/customer master data.
  
  Configuration Issues: There may be issues in the configuration of payment methods or transaction types in the SAP system that are causing this error.
  
  
  Solution:
  
  
  Check Vendor/Customer Master