SAP Knowledge Base Article - Public

2837406 - Due Date in Manage Automatic Payments for BOE Outgoing Payments

Symptom

Due date is not calculated as expected in relation to Bill of Exchange Payment Method for Supplier/Vendor Outgoing Payment

"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

Business Scenario:

Supplier Invoice 1 (Baseline Date 28.09.2019)

baseline28092019.png

Supplier Invoice 2. (Baseline Date 08.10.2019)

invoice2.png


Scenario 1

  1. Paying company code:

    Mange Your Solution -> Configure Your Solution -> Application Area: Finance -> Sub Application Area: Accounts Payable -> Step Name: Set Up Paying Company Codes for Payment Transactions (SSCUI 101001)

    payingcompanycode170.png

  2. Payment Method: Mange Your Solution -> Configure Your Solution -> Application Area: Finance -> Sub Application Area: Accounts Payable -> Up Payment Methods per Country for Payment Transactions (SSCUI 101972)

    paymentmethod.png

  3. Payment run parameters in app Manage Automatic Payment (App ID F0770)

    duedate.png

  4. Schedule Proposal

    paymentproposal.png

    The Value date shifted according to BoE due date. The Due date of the paid items is not changed
    Only one item will be paid, "next payment date" reflected.

  5. Delete Proposal: Carry out new Test.

  6. Payment run parameters in app Manage Automatic Payment

    nextduedate.png

  7. When "next payment date" shifted to 1.12.2019, both items paid irrespective of settings in paying company code.

    test2.png



Scenario 2

  1. Paying company code:

    paymingcompanycode2.png

  2. Payment Method:

    paymentmethod.png


  3. Result is the same (paid based on the "next payment date“) as in the previous cases.


Scenario 3

  1. Paying company code:
    payingcompanycode170.png

  2. Payment Method: 

    Indicator: Create a bill of Exchange Before Due Date selected:- Indicator that the bill of exchange can be created immediately. You do not have to wait until the items to be paid are due. The bill of exchange due date corresponds to the due date of the paid items.
    Use
    Creating bills of exchange as soon as possible after entering the invoices is common in countries such as France, Italy, and Spain.

    createbillexch.png

  3. Payment run parameters in app Manage Automatic Payment (App ID F0770)
    Bill of Exchange Due Date no longer present on Intial Screen.

    20.09.2019.png

  4. Application Log (Next payment date is ignored, instead the range in paying company code used)

    Errors Pymt method O in the item requires payment by b./exch. before due date and Item not due in 015 - 170 days

    Applicationlog.png

  5. Proposal: Value date according to the Invoice, but Due date of paid items according to the payment run

    proposal3.png

Exceptions: Error ID (Description): 025(Due date is too early for the bill of exchange Payment Method in question)

exceptions.png


Scenario 4


  1. Paying company code:

    paymingcompanycode2.png

  2. Payment Method

    createbillexch.png

  3. Payment run parameters in app Manage Automatic Payment

    Paymentcontrols.png


  4. Application Log (Range in Paying company code is considered and since it is empty, no payments with future value date is possible)

    logdetails.png


  5. Exceptions: Error ID (Description): 025(Due date is too early for the bill of exchange Payment Method in question)

    exceptions2.png



Summary 

  • When "Create BoE before due date" is not ticked on payment method in country, Due Date of BoE has to be entered in Manage Automatic Payments This is than updated in Value Date. Range in Paying Company Code is not reflected, but "next payment run date" in Manage Automatic Payments is reflected.

  • When "Create BoE before due date" is ticked on payment method in country, Due Date of BoE is referenced on initial Screen in Manage Automatic Payment. Instead the Due date of Invoice is used and is also updated in Value Date. Range in paying company code has to be maintained and "next payment run date" is ignored.

See Also

2842983 - BOE Multiple due dates in Manage Automatic Payment

Keywords

France, Italy, Spain BOE, Outgoing Payments, Incoming Payments, SEPA, REGUH, WEFAE, AUSFD, FZ732, FZ731, FZ720, REGUH-VALUT , KBA , FI-AP-AP-B1 , Payment transfer (w/o DE, US) , FI-AP-AP-B , Payment Progam / Payment transfer (DE, JP, US) , FI-FIO-AP , Fiori UI for Accounts Payable , FI-FIO-AR , Fiori UI for Accounts Receivable , FI-AP-AP-H , Bill of exchange , Problem

Product

SAP S/4HANA Cloud all versions