e-Mandate Service and Its ISO 20022 Messages

An e-mandate is a mandate that the debtor signs electronically, usually on the creditor website, and it is validated by the debtor bank during the signing process. Jonas Weber goes to the Stadtwerke Linden website, enters his IBAN and his name, and is redirected to his own bank, Meridian Bank Munich, to authenticate himself. He logs in with his normal online banking credentials, confirms the mandate details on the bank screen, and is redirected back to the utility website. The mandate is then created with a digital record of the authentication, and the creditor stores it as a valid mandate under the SDD scheme rules. The e-mandate flow uses ISO 20022 messages to carry the mandate information between the creditor, the debtor bank, and the service providers involved. The mandate initiation and the mandate acceptance are exchanged as pain.009 and pain.010 messages, while the mandate amendment and cancellation use pain.011 and pain.012 messages. The pain.009 carries the mandate request, including the debtor, the creditor, the account, and the collection details. The pain.010 carries the acceptance, confirming that the debtor bank has validated the mandate and that the debtor has authenticated the instruction. The debtor bank plays an active role in the e-mandate flow, and that role is what makes the electronic signature trustworthy. Meridian Bank Munich authenticates Jonas Weber, checks that the account he named belongs to him, and confirms that the mandate details match the account. It then returns a confirmation that the mandate has been accepted, and it records the mandate reference SWL-JW-2026-0417 against the account. If Jonas Weber had named an account that did not belong to him, the bank would have refused the mandate, and the utility would never have received a valid authorisation to collect. The e-mandate service also handles amendments and cancellations through the same message family, so the mandate stays current without paper forms. If Jonas Weber changes his bank account, he can amend the mandate through an online flow, and the amendment travels as a pain.011 message to the creditor and to the debtor bank. If he cancels the mandate, the cancellation travels as a pain.012 message, and the creditor must stop collecting from the next due date. The creditor must check the mandate status before each collection, because a collection sent against a cancelled mandate will be rejected by the debtor bank and may generate a complaint. Worked example with numbers: Jonas Weber goes to the Stadtwerke Linden website, enters his IBAN and his name, and is redirected to Meridian Bank Munich, which authenticates him, checks that the account belongs to him, and confirms the mandate details. The mandate is then stored under reference SWL-JW-2026-0417, and the mandate initiation travels as a pain.009 message while the acceptance travels as a pain.010 message, so that every party in the flow has a record of what was agreed. The whole signing takes under two minutes, and the customer never signs a paper form, which is why the e-mandate has replaced paper mandates for most utilities. Failure and recovery: the e-mandate fails when authentication fails, when the account does not belong to the customer, or when the mandate details are wrong. If Jonas Weber enters an IBAN that belongs to someone else, Meridian Bank refuses the mandate, because the account holder must be the debtor, and the signing stops. If the customer closes the browser before confirming, the mandate is never created, and the utility must ask the customer to start again. The recovery is a new signing flow, but the utility must not store a half completed mandate, because a mandate that was never confirmed is not a mandate at all, and a collection based on it would be unauthorised. For a business analyst, product owner or subject matter expert, the e-mandate requirement must state the messages, pain.009 for the initiation and pain.010 for the acceptance, and must state that the debtor bank authenticates the customer and checks the account. The requirement must also state how amendments and cancellations travel through the same message family, so that a mandate stays current without paper forms. The test pack must include a successful e-mandate, a failed authentication, a mandate with a wrong IBAN, and an amendment that changes the bank account, because each case exercises a different part of the flow. Source: EPC SDD Core Rulebook 2025; ISO 20022 pain.009 and pain.010; last reviewed 7 November 2026.