How To Fix FZ591 - First use of SEPA mandate: run date and sequence type have been adjusted

SAP Error Message - Details

• Message type: E = Error

• Message class: FZ - Payment Transactions

• Message number: 591

• Message text: First use of SEPA mandate: run date and sequence type have been adjusted

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.

Smart SAP Assistant

• What is the cause and solution for SAP error message FZ591 - First use of SEPA mandate: run date and sequence type have been adjusted ?

  The SAP error message FZ591, which states "First use of SEPA mandate: run date and sequence type have been adjusted," typically occurs in the context of processing SEPA (Single Euro Payments Area) direct debits. This message indicates that there is an issue with the configuration or the parameters of the SEPA mandate being used for the payment run.
  Cause:
  
  First Use of Mandate: The error is triggered when a SEPA mandate is being used for the first time. The system automatically adjusts the run date and sequence type to comply with SEPA regulations.
  Sequence Type: The sequence type (e.g., "FRST" for first use, "RCUR" for recurrent, "OOFF" for one-off) may not be set correctly in the payment run.
  Run Date Adjustment: The run date may be adjusted to ensure compliance with the SEPA mandate rules, which require that the first direct debit must be initiated with a specific sequence type and within a certain timeframe.
  
  Solution:
  
  Check Mandate Status: Ensure that the SEPA mandate is correctly set up and activated in the system. Verify that the mandate is valid and has not expired.
  Review Payment Run Parameters: When creating the payment run, check the parameters being used. Ensure that the sequence type is set to "FRST" for the first use of the mandate.
  Adjust Run Date: If the run date has been adjusted, confirm that it aligns with the requirements for the first use of the mandate. The run date should be set to a date that allows for the proper processing of the direct debit.
  Consult Documentation: Refer to SAP documentation or guidelines on SEPA mandates to ensure compliance with all necessary regulations and configurations.
  Testing: If possible, conduct a test run with a different mandate or payment run parameters to see if the issue persists.
  
  Related Information:
  
  SEPA Mandate Management: Familiarize yourself with how SEPA mandates are managed within SAP, including the creation, activation, and maintenance of mandates.
  SAP Notes: Check for any relevant SAP Notes that may address this specific error or provide additional guidance on SEPA mandate processing.
  Transaction Codes: Use transaction codes like BP (Business Partner) to manage mandates or F110 for payment runs to review and adjust settings.
  Compliance: Ensure that your organization is compliant with SEPA regulations, as these can affect how mandates and direct debits are processed.
  
  If the issue persists after following these steps, it may be beneficial to consult with your SAP support team or a consultant who specializes in SAP financial processes.