3705406 - SDD lead times in SAP S/4HANA Cloud Public Edition

After a mandate's first use, the XML generation for RCUR transactions incorrectly adds 7 days to the posting date instead of 2.

SAP S/4HANA Public Cloud Edition

1. Utilize a mandate with CORE and FRST.
2. Generate the XML file and observe that the value date is set by adding 5 days to the posting date.
3. Utilize the same mandate again with RCUR.
4. Generate the XML file and observe that the value date is set by adding 7 days to the posting date instead of 2.

The value date is different as expected.

For an RCUR collection, the lead time for submitting a SEPA Core Direct Debit is two days for subsequent use. However, the DMEE calculates the Required Collection Date as Due Date + 7 days, which is correct. This is because any collections due before the FRST collection must take place after that initial collection has been completed.

Refer to the SAP community post SEPA Pre-notification and SDD Timelines Functionality for more insights into the SDD timelines logic.

• SEPA Pre-notification and SDD Timelines Functionality
• KBA 2844993 - BOE Due Date for Customer Incoming Payment with SEPA

SDD lead time, XML generation, Posting date, Mandate, CORE, RCUR, FRST, Public cloud, SEPA direct debit, Manage Automatic Payments, Value date. , KBA , FI-FIO-AP-2CL , Fiori UI for Accounts Payable (Public Cloud) , Problem