Do customers need to sign new mandates when switching payment providers?

By Jamie Fee | 2 October 2026

Usually, no. For SEPA Direct Debit, moving to a different payment service provider does not, by itself, mean every customer must sign again. An existing mandate can continue when the authorised creditor and collection scheme remain the same and the mandate stays valid. If the move changes the creditor identifier, creditor name or unique mandate reference, use the scheme’s amendment process. If it changes the legal creditor, check the law governing the customer relationship before deciding that an amendment is enough. This answer follows the mandate and amendment provisions in the EPC’s 2025 SDD Core Rulebook, version 1.2 and Clarification Paper EPC132-17, version 5.1, both dated 30 September 2026.

The useful question is: what will change on the mandate and in the collection data? Before asking customers to sign new forms, put the existing and proposed arrangements side by side. A new provider contract tells you who will process the collections; the mandate tells you whom the customer has authorised to collect.

The mandate belongs to the creditor relationship

Under section 4.1 of the Core rulebook, the mandate records the customer’s consent for the creditor to initiate collections and for the customer’s bank to act on those instructions. The creditor is the party that receives and stores that authorisation. Its payment service provider, or PSP, handles the payment side of the arrangement. Treating those roles as interchangeable can turn a straightforward provider move into the wrong mandate decision.

Start with the creditor’s legal name on the existing mandate. Then ask the receiving PSP which legal entity and creditor identifier it will put in the collection message. If those remain yours, you are assessing continuity of your existing authorisation. If the receiving arrangement uses a different legal creditor, the EPC’s clarification paper, section 2.4, says the applicable law determines what happens to the existing mandate. Where that law permits continuity without a new mandate, the rulebook’s amendment procedures apply.

This is why an assurance that “mandates are transferable” is too broad to settle the question. Ask for the proposed creditor details, scheme and amendment treatment in writing. A file export is useful, but it cannot answer a question about who the customer authorised.

Which changes need a new mandate?

Use this table to classify the move before agreeing a cutover date. The amendment rows come from PT-02.01, PT-02.02 and attribute AT-M007 in the Core rulebook, with the EPC clarification paper’s sections 2.4 and 2.10. The 2025 SDD B2B Rulebook, version 1.2, dated 30 September 2026 contains the corresponding amendment framework; its bank confirmation requirements are discussed below.

“Amendment” is not shorthand for silently overwriting a database field. PT-02.01 describes an amendment agreed between creditor and debtor; PT-02.02 requires the creditor to archive the amended mandate and send relevant amended information with the next collection. When a merger or acquisition changes the creditor’s identity, PT-02.02 expressly requires the new creditor to inform the debtor of the related amendments, for example by letter or email.

The distinction matters in a provider move involving a shared or provider-controlled creditor identifier. Do not assume that the displayed provider name is merely a processing label, or that a change in identifier necessarily means a change in legal creditor. Have the outgoing and receiving PSPs identify the creditor actually named in the mandate and collection. Then apply the appropriate row.

Preserve the identifier trail, not just the customer list

The creditor identifier and UMR connect a collection to its mandate. A useful official illustration comes from the Deutsche Bundesbank’s Creditor Identifier guidance, checked on 1 October 2026: it describes an identifier independent of an account and explains how the identifier and mandate reference together identify the authorisation. That is German issuing practice, not a promise about another country’s identifier allocation.

The EPC clarification paper’s section 2.10 gives a precise rule for changing a creditor identifier or UMR: the creditor PSP sets the amendment indicator to true in the inter-PSP collection message and includes the original value in the amendment details. If an identifier changes again later, “original” means the most recently valid value, rather than the first value ever used.

For example, suppose an existing mandate has reference SUB-104 and the receiving system needs EU-104. Assuming the mandate can legally continue, the migration record should link SUB-104 to EU-104; the next collection’s amendment data carries the former reference. If a later restructuring changes it to EU-204, the previous valid reference is then EU-104. These are illustrative references, not customer data.

Ask the receiving PSP to show you the old and new values in a sample collection file. Ask who owns the mapping and how a rejected amended collection will be handled. Section 2.15 of the clarification paper says that if a collection containing amendments is rejected, those amendments should be repeated when the collection is presented again. A rejection must not cause the receiving system to forget the transition.

A customer notice is different from a new signature

There are separate jobs here: agreeing a mandate amendment, telling the customer what changed, and notifying them of the forthcoming debit. A notice can explain a lawful continuing arrangement; sending a notice does not establish that a different creditor has acquired valid authorisation.

For the forthcoming debit, PT-04.02 sets the default pre-notification period at 14 calendar days before the due date, unless creditor and debtor agree another timeline. The notice supplies the amount and due date and may be part of an invoice or payment schedule. That is a collection-notice rule, not a universal 14-day deadline for transferring mandates between providers.

Before sending a migration notice, establish the legal creditor, the identifiers customers will see and the first collection date. Then explain those confirmed facts in ordinary language. Tell customers whether they need to take action and provide a contact route for questions. Avoid promising uninterrupted collections until the receiving PSP has accepted the data and the collection plan.

If a new mandate is required, the signing route is a separate choice. Rebeam’s article on electronically signed SEPA mandates explains the authorisation and evidence questions to resolve before choosing that route.

Check validity and scheme before moving the records

A provider move cannot revive a cancelled or expired mandate. Section 4.2 of the Core and B2B rulebooks requires cancellation when no collection has been presented under the mandate for 36 months; the calculation starts from the latest presented collection, even if it was rejected, returned or refunded. Check the presentation history rather than relying only on the last successful payment date.

Also distinguish an electronically signed mandate from the EPC’s optional bank-validated e-Mandate service. Under Annex VII, section 4.5.8, a debtor moving the debited account to another PSP must cancel the existing e-Mandate and issue a new mandate with the new debtor PSP. That concerns the customer’s bank move within that service, not simply your change of collection provider. It should not be generalised to every online signature.

B2B has another practical dependency. Its rulebook requires the debtor PSP to check mandate data before debiting, including confirmation from the debtor. The EPC clarification paper’s section 3.2 explains that missing mandate data can lead to a rejection with code MD01. If a business already collects under B2B, ask the customer’s bank whether changed creditor or mandate data require updated confirmation. An amendment at the creditor’s end and a confirmation at the debtor’s bank are different tasks.

The evidence pack to request before cutover

Ask for a pack that lets the receiving PSP trace each proposed collection back to the authorisation. The following is a practical handover checklist based on the rulebooks’ storage and amendment provisions, rather than a prescribed EPC export format.

• 
  Authorisation: the signed mandate or electronic authorisation record, scheme, signing date and current validity status.
  
• 
  Current identity: the creditor’s legal name, creditor identifier, UMR and customer account details used for collections.
  
• 
  Amendment history: previous and current values, the agreed changes, and customer communications about them.
  
• 
  Collection history: the most recent presented collection, rejected or returned items still to resolve, and the planned first collection through the receiving PSP.
  
• 
  Responsibility: who retains the original evidence, who can produce it on request, and who handles disputes concerning collections made before the move.
  

Storage is a continuing responsibility. Regulation (EU) No 260/2012, dated 14 March 2012, Article 5(3)(a)(ii) requires the payee, or a third party on its behalf, to store mandates together with subsequent modifications or cancellation. Under PSD2, Directive (EU) 2015/2366, dated 25 November 2015, Article 64, a payment is authorised only when the payer has consented, using the form agreed with their PSP. A migration needs to preserve the evidence of that consent, not merely the fields needed to submit a collection.

Use a cutover decision with named owners: the receiving PSP has accepted the mandate records; the creditor and identifiers have been checked; required amendments or new mandates are complete; customer communications and pre-notification are ready; and both providers know which collections each will submit. If any item remains unresolved, keep that cohort out of the cutover until it is resolved.

Discuss the collection arrangement before asking customers to sign again

Rebeam describes itself as a commercial payments partner. Its website states that regulated payment services are provided directly by the relevant licensed financial institution, with availability depending on the business model, customer geography, expected volumes and onboarding requirements.

Bring the existing mandate wording, creditor identifier, scheme and collection timetable to the discussion. Those documents make it possible to ask a precise question about the proposed arrangement: which details stay the same, which need amendment, and which require fresh authorisation? Rebeam’s comparison of SEPA Direct Debit and bank transfer for recurring euro payments provides the wider collection context.

Sources

• European Payments Council, 2025 SEPA Direct Debit Core Scheme Rulebook, EPC016-06, version 1.2, issued and effective 30 September 2026: sections 3.1, 4.1, 4.2, PT-02.01–02.02, PT-04.02, DS-01, AT-M001, AT-M007, AT-M008, AT-C001; Annex VII, section 4.5.8.
• European Payments Council, 2025 SEPA Direct Debit Business-to-Business Scheme Rulebook, EPC222-07, version 1.2, issued and effective 30 September 2026: mandate wording, amendment and debtor PSP confirmation provisions.
• European Payments Council, Clarification Paper on SDD Core and SDD B2B Scheme Rulebooks, EPC132-17, version 5.1, 30 September 2026: sections 2.4, 2.10, 2.15 and 3.2.
• Deutsche Bundesbank, Creditor Identifier, official guidance, undated; checked 1 October 2026.
• Regulation (EU) No 260/2012, 14 March 2012, Article 5(3)(a)(ii).
• Directive (EU) 2015/2366 (PSD2), 25 November 2015, Article 64.