3807497 - Future-dated bank account blocks payments and duplicate worker bank data entries ignored

Future-dated bank account record for a business partner prevents payment processing for open invoices.

Duplicate entry errors prevent employee bank data updates.

Error message:

• Worker: the id - Ignored as there are duplicate entries found.

SAP S/4HANA Cloud Public Edition

1. Navigate to the APP Maintain Business Partner.
2. Enter the business partner id.
3. Display in BP Role: Business Partner (Gen.).
4. Go to Payment Transactions / Bank Details tab.
5. Observe a bank account with Valid From a future date (for example, 01-06-2027) and Valid To 12-31-9999.
6. Attempt to process payment for open invoices for this business partner → payment is blocked/restricted.

The affected Business Partner is created and maintained by the external HR system through the SOAP API Replicate Basic Master Data for Workforce from External HR Systems, not by S/4HANA itself. Therefore the bank data at BP level is derived directly from the payload pushed by the external HR system.

Two characteristics of this API explain the behavior:

1. Full-update (full-overwrite) behavior – Each update fully replaces the existing record with the data in the latest payload. Per the official documentation: "It supports full update of the existing data with the incoming payload data. So when you trigger an update, the entire data of the existing record is replaced with the data coming from the latest payload."
2. Validity date taken from the payload – The bank account's Valid From date is taken directly from the ValidityPeriod node within WorkAgreementBankAccountInformation in the payload. S/4HANA does not generate future dates on its own; it simply accepts the validity date provided in the incoming payload.

The future-dated bank record (e.g. Valid From 06.01.2027) was therefore a reflection of the validity start date sent from the external HR system. Similarly, the "duplicate entries found" messages arise from the same data being sent in the payload rather than from a defect in S/4HANA.

This is a data-integration handling matter on the source-system side, not an error in S/4HANA.

Because the Business Partner's creation source is the SOAP API, the bank data (including deletion/correction of the future-dated record) must be maintained via the SOAP API, by re-pushing the correct payload from the source system.

To resolve and prevent recurrence, on the source-system side:

1. Validate the bank account validity start date (ValidityPeriod – StartDate) before pushing the payload, to ensure no unintended future dates are transmitted.
2. Because the API performs a full overwrite, always send the complete and correct dataset for the worker, including the intended bank validity dates, so that outdated or duplicate records are properly replaced.
3. After sending the corrected payload, verify in the Maintain Business Partner app (transaction BP) that the bank record shows the intended validity dates, and monitor the Message Monitoring app to confirm the records are no longer ignored as duplicates.

• refer to: Replicate Basic Master Data for Workforce from External HR Systems (SOAP API)

future-dated bank account, payment blocked, business partner bank details, SOAP API, full overwrite, ValidityPeriod, WorkAgreementBankAccountInformation, duplicate entries, message ignored, payroll bank data update, manage workforce, payment transactions, bank details tab, business partner, s/4hana cloud public edition , KBA , LO-MD-BP-2CL , Business Partners for Public Cloud , Problem