3803640 - AP Supplier Invoice Due Date Incorrect from Wrong Baseline Date via API Payload - SAP S/4HANA Cloud Public Edition

• Accounts payable invoice due date is calculated incorrectly.
• The baseline date is determined incorrectly and does not match the expected document date–based logic from payment terms.

SAP S/4HANA Cloud Public Edition

1. Create the invoice via the Supplier Invoice (OData V2) API using POST (service: API_SUPPLIERINVOICE_PROCESS_SRV).
2. Include a </DueCalculationBaseDate> value in the payload that differs from the invoice/document date.
3. Check the baseline date and net due date on the posted invoice; they follow the payload date, resulting in an unexpected due date.

The API payload contains the field </DueCalculationBaseDate> with a value that overrides the expected baseline date from payment terms configuration; the system uses the provided payload date as the baseline date.

1. Review the payload used by the interface or middleware for the Supplier Invoice (OData V2) API.
2. Set the </DueCalculationBaseDate> in the payload to the intended baseline date that aligns with the applicable payment term logic (for example, the document date when required).

AP invoice, baseline date, due date, API_SUPPLIERINVOICE_PROCESS_SRV, payment terms, net due date, payload , KBA , FI-FIO-AP-PAY-2CL , Payment Apps (Public Cloud) , Problem