To efficiently update multiple subscriptions (e.g., following a general price change), first export all your subscriptions or apply filters to export a specific selection. Edit the necessary fields in the CSV file and then re-upload it.
In the subscriptions overview, use the button and upload your file.
The ID of a subscription is generated by the system and can only be used for updates, to create new subscriptions do not include the id header.
New subscriptions
Required:
mandateNumber: The mandate number to link the subscription on
amount: The recurring amount of the subscription
message: The communication to the debtor (max 140 characters, SEPA-safe characters only)
recurrence: The periodicity of the subscription (1w / 2w / 1m / 2m / 3m / 4m / 6m / 12m)
start: The start date of the subscription and first execution date (YYYY-MM-DD)
Optional:
ref: The unique reference per mandate of the subscription (recommended)
For monthly recurrences (1m, 2m, 3m, 4m, 6m, 12m), the start date's day of the month must be 28 or earlier. Day 29, 30, or 31 is rejected.
Update subscriptions
When updating existing subscriptions, a distinction is made between minor and major changes. When a change is major, a new subscription is created based on the existing one.
Required:
id: The id of the subscription (included when exporting your existing subscriptions)
recurrence: The periodicity of the subscription (1w / 2w / 1m / 2m / 3m / 4m / 6m / 12m) (major change if different from current value)
mandateNumber: The mandate number - if different from the current one, the existing subscription is cancelled and a new one is created on the passed mandate number (major change when different).
message: The communication to the debtor (minor change)
Optional:
amount: The recurring amount of the subscription (minor change)
ref: The unique reference per mandate of the subscription (minor change)
start: Change the start date of the subscription YYYY-MM-DD (major change - this will also become the next execution)
stopAfter: The number of times the subscription needs to be executed (major change when the value is lower than the current number of executions).
next: Override the calculated next run date (YYYY-MM-DD). Recalculated automatically when start changes.
Updating the subscription with a major change creates a new one. The first execution (next run) of that subscription is the start date.
Updating a **cancelled** or **closed** subscription via CSV does not modify the original — a new subscription is created from the import row, similar to "Start over".
Creating a new subscription due to a major change
When you update the subscription with a major change, the start date of the new subscription is also the next run. The last run is always cleared since you've created a new subscription.
When the start date of the subscription you updated was already in the past, then the new start date is the current date + 1 day. Except if you changed the start date to a custom one, then that is the new start.
