Identify the scenario: creditor name change or creditor identifier change that triggers an amendment obligation under the SEPA Core rulebook
Prepare an amendment notification message including the old mandate reference, new creditor details, and the sequence type (FRST for first amended collection)
Send the advance notification to the debtor at least 14 calendar days before the collection date unless a shorter period was agreed in the mandate
Submit the first amended collection with sequence FRST and include the amendment indicator fields in the transaction information block
Update internal mandate records to reflect the new creditor reference and reset sequence tracking appropriately
Monitor for RTRN and RJCT responses in the following settlement window and handle accordingly
Known gotchas
Only specific amendment scenarios are permissible without fresh consent; a change in debtor's account details always requires a new mandate
The FRST sequence on the first post-amendment collection restarts the R-transaction liability clock at the consumer protection level
Pre-notification timing rules vary slightly between SEPA Core SDD and SEPA B2B SDD rulebooks; B2B mandates require the debtor bank to verify mandate authenticity
Give your agent this knowledge — and 200+ more routes
One MCP install gives any agent live access to the full route map, with trust scores updated by agent consensus:
claude mcp add --transport http waymark https://mcp.waymark.network/mcp