Set migrated SEPA-mandates to sequence type RCUR

[Former Member]

Hi,

I need to make sure migrated SEPA mandates don't get rejected by the bank. 

I am assuming migrated mandates get sequence type FRST automatically if I don't fill the Usage fields in the template.
And I am assuming they get sequence type RCUR if I fill the 6 fields for First Use Date and Last Use Date with dummy data in the migration template.
I plan to use dummy data [01.01.2019; BKPF; 3710 9999999999 2019; 01.01.2019; BKPF; 3710 9999999999 2019] for the last six fields in the template.

Can the community confirm that this is the normal way to migrate SEPA mandates (with dummy usage data)?

[Sandeep_Kumar · Accepted solution]

Hi,

Are you referring to payment types ( 1 for one time and N for recurring)? You can maintain these settings in the migration template.

Best,

Sandeep

[Former Member · Accepted solution]

I am referring to mandates with payment type N. For these mandates the bank expects to receive a sequence code in the payment file, such as FRST, RCUR, FNAL or OOFF.