Change the remitter name (payer name / 振込元の依頼人名) only for a specific supplier

[Linh_NguyenThiThao]

We have a requirement to change the remitter name (payer name / 振込元の依頼人名) only for a specific supplier in SAP S/4HANA Cloud Public Edition.

As far as we understand:

The remitter name is configured only at Company Code × Payment Method level via SSCUI 101044 – Set Up Payment Methods per Company Code.

We cannot find any SSCUI, Cloud BAdI, or Custom Logic that allows overriding the remitter name at vendor level.

Payment Medium Cloud BAdIs seem to allow only adding reference fields or changing file names, but not modifying the remitter/payer name in the payment file.

My questions:

1. Is there any supported way in SAP S/4HANA Cloud Public Edition to override the remitter name for a specific supplier (vendor-specific)?

2. If not, is creating a dedicated payment method (with a different remitter name) and assigning it only to that supplier considered the recommended workaround?

3. Has anyone implemented a similar requirement, or is this fully restricted due to Public Cloud limitations?

Any insights, confirmation, or SAP official references would be greatly appreciated.

[Chris1973 · Accepted solution]

Good day @Linh_NguyenThiThao 

Thank you for your question.

Have a look at the following reference.

https://help.sap.com/docs/SAP_S4HANA_CLOUD/9d271749cf1148058b9acd9e0d8bf02a/158e8b6aefb8430d89d28960...

https://help.sap.com/docs/SAP_S4HANA_CLOUD/164aaa06151b4106b7bc163efe97902a/ed166f63a4de44afab81168b...

Answer to question 1:

No. There is no supported BAdI, SSCUI or configuration in public cloud that allows you to override the remitter name at the vendor level. These restrictions are in place due to the clean-core principle.

Answer to question 2:

Yes, that is the recommended workaround. You basically create a new Payment Method through SSCUI 101044, set a custom remitter name for that method and assign the new payment method only to the specific vendor in their master data. You can achieve isolating the remitter name for that supplier.

Answer to question 3:

Yes, it is a public cloud limitation. I have had a few instances, especially Japan related use cases and the recommendation is to make use of a multiple payment method.

In summary, the reason why the public cloud does not allow you to enhance the remitter dynamically through Payment Medium Cloud BAdIs is because:

1. Firstly, the system populates the payer field during proposal and this is based on a hard-coded logic.
2. Secondly, public cloud BAdIs such as Payment Medium tend to add fields, while Payment Mediums allow file name change within limited file-level.

Best regards

Chris

[OwenLiu · Accepted solution]

We’ve marked the answer as the accepted solution to assist you. If you have more questions, you can un-accept it whenever needed.