SAP Knowledge Base Article - Public

2844993 - BOE Due Date for Customer Incoming Payment with SEPA

Symptom

SEPA Bill of Exchange Payment method in app Manage Automatic Payment for Incoming Payment of Customer Invoice due date logic

 "Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."

Environment

S/4 HANA CLOUD

Resolution

Scenario - SEPA mandates with Create BOE before Due Date 

  1. Three customer invoices on the same customer but on three different partner bank details with three different SEPA mandates

    App Manage Customer Line Items (App ID F0711)

    managecustomerlineitemsboe.png

  2.  App Maintain Business Partner (App ID BP)

    maintainbusinesspartner.png


  3. App Display SEPA Mandates (App ID App ID FSEPA_M3)

    SEPA mandate for B2B DD with recurring payment

    B2BDD.png


    SEPA manadate for CORE DD with recurring payments

    COREDD.png


    SEPA mandate for CORE DD with One-Time payment

    onetimemandate.png



  4.  According to F1 Help following rules apply to value date calculation:

    f1help.png


  5.  Payment Method: Create bill/exch. before due date selected - (This means  that the due date of the BoE is the invoice's due date) and SEPA Mandate Required
    Mange Your Solution -> Configure Your Solution -> Application Area: Finance -> Sub Application Area: Accounts Payable -> Up Payment Methods per Country for Payment Transactions (SSCUI 101972)

    sepadd.png


  6.  In App Manage Automatic Payments BoE due date set up for 15.11.2019

    duedateparameter.png


    Due dates are now as follows:
     
    PAYMENTPROPOSAL.png


  7. Calander

    CALANDER.png


The option:'Create BOE before the due date' in payment method setting which means that the due date of BoE is the invoice’s due date.
If the due date fall in on the weekend, the next working day is the due date of the BoE

SEPA DD due date is calculated on top of it:

If the Boe’s due date is on the first usage date of SEPA Mandate, it will move on to the next working date(ITS04), The subsequent date is later than the first usage date.

If the Boe's due date > the first usage date in SEPA mandate,  the Boe's due date is the final due date in payment document, without considering the leading time.

SEPA CORE Direct Debit: First time use of a mandate and one-off : 5 days lead time, bank collection date is 5 working day +  Creation date= value date. Subsequent use of the mandate : 2 days lead time, bank collection date is 2 working day + Creation date= value date

SEPA B2B Direct Debit: First time use of a mandate and Subsequent use of the mandate, or One-off : 1 days lead time, bank collection date is 1 working day + Creation date = value date

Once the payment is executed, the Mandates are updated accordingly

 

Scenario - SEPA Mandate not required on the Payment method in country level


  1. Payment Method At Country Level


    SEPAMANDATEREQUIRED.png
     
  2.  In App Manage Automatic Payments BoE due date set up for 15.11.2019

    paymentresult.png

Due date of all items is on 15.11.2019, so there is no change


Scenario  - Subsequent usage must later than the first usage

  1. In Manage Customer Line Items (App ID F0711) 2 customer invoices due

    managecusotmerlineitems.png

  2. Payment Method: Create bill/exch. before due date selected - (This means that the due date of the BoE is the invoice's due date) and SEPA Mandate Required
    Mange Your Solution -> Configure Your Solution -> Application Area: Finance -> Sub Application Area: Accounts Payable -> Up Payment Methods per Country for Payment Transactions (SSCUI 101972)

    sepadd.png
  3. In Create SEPA Mandates (App ID FSEPA_M1) B2B Mandate selected

    B2BMandate.png
  4. In App Manage Automatic Payments (App ID F0770) For Invoice 1, in the Parmeters the Due Date (the due date of the bill of exchange to be issued is specified) is set as 10.12.2019 (10th of December 2019)

  5. In the Payment created the Due date is shown as 10.12.2019 (10th of December 2019)

    duedate1payment.png
  6. In App Manage Automatic Payments (App ID F0770) For Invoice 2, in the Parmeters the Due Date (the due date of the bill of exchange to be issued is specified) is set as 20.11.2019 (20th of November 2019)

    duedate2.png

  7. In the Payment created the Due date is shown as 11.12.2019 (11th of December 2019)

    duedate2payment.png



  8. The First Usage can be seen in the SEPA Mandate. See App Display SEPA Mandates (App ID FSEPA_M3).  Enter Mandate Reference (The mandate Reference can be obained from in the Manage Automatic Payments app from the Payment Line Item.)
  9. Select Usage tab

    firstusage.png
     

 

Subsequent usage must later than the first usage, this is why on the second payment run the due date was update to 11.12.2019 (11th of December 2019)


 

 

See Also

2844089 - BOE Due Date for Customer Incoming Payment

2842983 - BOE Multiple due dates in Manage Automatic Payment

Keywords

F0770, BOE, DUE DATE, ITALY, SPAIN, FRANCE, 1WQ, J59, BKX,J60, SEPA, SDD, B2B, Mandate, H, CORE, B2B, , KBA , FI-FIO-AR , Fiori UI for Accounts Receivable , FI-FIO-AP , Fiori UI for Accounts Payable , FI-AR-AR-H , Bill of exchange , Problem

Product

SAP S/4HANA Cloud all versions