Direct debits and pull collections

A direct debit is a pull payment in which the creditor, with the prior authorisation of the debtor, instructs the creditor agent to collect funds from the debtor account through the debtor agent. The authorisation is called a mandate, and it records the debtor account, the creditor identity, the reference, and the terms under which collections may be made. Direct debits are used for utility bills, insurance premiums, loan repayments, subscriptions, and any recurring payment where the amount or the date may vary. They save the payer from remembering to pay each time, and they give the payee predictable collections. The direct debit lifecycle has three distinct phases. First, the mandate is set up, either on paper or electronically, and it is registered with the debtor bank. Second, the creditor sends a collection instruction, usually with advance notice to the debtor, and the debtor bank debits the account if funds are available and the mandate is valid. Third, if the collection is wrong, duplicate, or unauthorised, the debtor can claim a refund or an indemnity under the scheme rules. Different schemes have different refund windows, and in some schemes the refund right is immediate and unconditional, which places the risk firmly on the creditor. For a business analyst, direct debits require careful attention to mandates, notifications, and returns. A mandate that is not stored correctly, a collection that is sent without notice, or a return code that is misinterpreted can all cause customer harm and scheme fines. You must document the mandate lifecycle, the advance notice period, the collection timing, and the refund and return flows. You must also understand the difference between a direct debit, which is a scheme based pull, and a standing order, which is a payer initiated push of a fixed amount on a fixed date. They look similar to a customer, but the risk and the message flow are completely different. Follow one mandate through its life. A customer authorises their electricity supplier to collect Rs 2,300 a month by direct debit, and the mandate is registered with the customer's bank. Each month the supplier sends an advance notice five days before the collection, then collects on the due date. In June the customer cancels the mandate on the 10th, but the supplier's system does not pick up the cancellation and sends the collection on the 12th anyway. The bank debits the account, the customer complains, and the collection is refunded as unauthorised. Under the SEPA direct debit scheme, an authorised collection can be refunded within eight weeks of the debit, while an unauthorised collection can be claimed for up to thirteen months, which is why the distinction between authorised and unauthorised matters so much. A second failure is simpler. The collection arrives when the account holds only Rs 1,000, so it is returned for insufficient funds, and the supplier charges a late fee that the customer then disputes. An analyst documents the mandate as a lifecycle, not as a single setup step. The specification must cover how the mandate is created, paper or electronic, how it is stored and retrieved, how the customer cancels it, and how quickly a cancellation takes effect in the creditor's system. It must cover the advance notice period and what the notice must contain, and it must map every return code to its handling, insufficient funds, mandate cancelled, account closed, account transferred. The test pack should include a collection after cancellation, a duplicate collection, a collection for the wrong amount, and a collection against an account with insufficient funds. Each test should assert the customer communication as well as the system behaviour, because a customer who is debited without notice will complain even when the system did everything right.