- Before creating the mandate in SAP customer account, please always confirm which is the company code related (in case the customers is multi GBU)
- Before creating the mandate, please check if the bank account provided by the customer in the mandate is inserted in the customer master data bank details. If note, please send an email to Data Management team (datamanagement.3s-pt@solvay.com) with the bank account to be inserted and ask them to tick the "Collections authorization" field
- If customer change its bank account, we should request a new SEPA mandate to the customer with the new bank account and ask Data Management team to tick again the "Collections authorization" flag
- For customers which are not German, please check in the following link if the customer bank is adhering to the DD SEPA: (SDD CORE or SDD B2B) : https://www.ebaclearing.eu/services/step2-sdd-core/participants/
Then copy the SWIFT code and search in the link provided above. In this case customer bank is adhering to the DD SEPA, so we can proceed with the mandate creation.
If not, customer should be contacted to verify if he works with a bank account which is an adherent of SEPA.
The process in SAP starts with the sending of the Mandate form (check attachments) to the customer which should be filled and signed by them.
Before creating the mandate, the AR team should:
- confirm if the bank account. (IBAN) in SAP Masterdata is the same as in the Mandate form;
- confirm if "Collection Authorisation" tab is flagged as below:
In case that the Bank account is not the same as in the Mandate form or "Collection Authorization" tab is not flagged, the ticket should be sent to Data Management team requesting to add this new bank account in customer masterdata.
When all details are correct, we should create the SEPA mandate in SAP by using transaction FSEPA_M1 in PI1 system.
Warnings
- If for any reason, the mandate should be edited, go to transaction FSEPA_M1 with Mandate reference and click on as below:
- After the creation of the mandate, the payment method should be changed to H at Customer Masterdata Level in PI1 and in Local system (PF1/WP1) .
- The payment method in PF1 and WP1 customer masterdata should be updated according the following table:
WP1 PF1 Payment method analysis.xlsx
- Examples of SEPA mandates templates:
- If there are open invoices in customer´s account when implementing the SEPA direct debit, we should confirm with the requester (Collections or Customer Service teams) if all the open invoices should be considered to be debited by Direct Debit. If yes, the payment method should be changed to H in each invoice.
- If the change of the payment method was initiated by Collections team or AR team, we should assure that Customer Service is aware of this change. So if Collections haven't informed, AR team should send an email.









