Evaluation of SEPA Mandates by the Payment Program
The payment program evaluates SEPA payment methods when incoming and outgoing payments are created.
Prerequisites
You classified payment methods as SEPA payment methods in Customizing for Contract Accounts Receivable and Payable under 
Business Transactions
Payments
Incoming/Outgoing Payment Creation
Define Payment Methods
. In addition, for each payment method affected, you set the SEPA Mandate
indicator in the Necessary Specifications
group box in the master record.
Note
For you to be able to classify a payment method as a SEPA payment method, you also have to set the IBAN
and Swift Code
indicators.
Features
If the payment program identifies a payment method as a SEPA payment method (for instance, in the item, master data, payment specification, or promise to pay), then the program checks if:
An IBAN is entered in the bank data of the business partner
There is an active, unlocked SEPA mandate for the IBAN for this combination of payer and payee
The reference in the SEPA mandate is suitable for the payment currently being processed
If more than one mandate qualifies, you can use event 0653 to determine which mandate is used.
If a mandate to be used for payment is already entered in the document or the contract account/contract, then the payment program checks and uses only that mandate (see Integration of SEPA Mandates in the Processes of Contract Accounts Receivable and Payable).
For payments that are processed using a SEPA payment method with a valid SEPA mandate, the system stores the GUID of the mandate that was used and additional mandate data in the header record of the payment.
In the standard system, the payment program sets the execution date for mandates used for the first time to 5 days, and for mandates used again to 2 days after the creation of the payment (local instrument code CORE
).
You can also use the local instrument code COR1
to submit the payment media (SEPA DD
) to the bank one day before the execution date.
The formats SEPA_CT
and SEPA_DD
are available for creating payment media.
The system checks the validity of a mandate based on the execution date calculated for the payment.
Note
You can set the calculated execution date at event 0062 as the alternative posting date of the clearing document. To do this, either register function module FKK_SAMPLE_0062_AUSFD
at event 0062 or implement your own logic.
Activities
For mandates that can be used for multiple payments, the system can record the number of uses. To activate this recording function, you have to specify the number of uses of a mandate that you want the payment program to record in the system. To do so, in Customizing for Contract Accounts Receivable and Payable, choose Payments
Incoming/Outgoing Payment Creation
Management of SEPA Mandates
General Settings
. Make the entry in the Number
field. If you enter this number in Customizing, then the system creates an entry for each posted payment document or payment order. This entry is stored in a management table, and you can display it later in the mandate.
In Customizing for Contract Accounts Receivable and Payable under Business Transactions
Payments
Incoming/Outgoing Payment Creation
Management of SEPA Mandates
Determine Local Instrument Code and Lead Times
, you enter the rules used by the payment program to determine the local instrument code, the lead time, and the calendar to calculate the lead time.
Recommendation
You can influence the lead times in events 0661 and 0656 (see the documentation of function modules FKK_SAMPLE_0661
and FKK_SAMPLE_0656
). The system processes event 0656 after it evaluates this Customizing activity and event 0661 before it evaluates this activity.
When you start using the Customizing settings for COR1
, we recommend that you do not perform any additional calculations for lead times in events 0661 and 0656.
