You want to collect rent payments by direct debit in future. The paying person agrees and their IBAN is available. Before you submit the first amount, however, the process needs a complete foundation: who collects, which mandate applies, what is announced and how is a failed booking handled?
Clarify payment claim and collection method separately
First determine the contractually and arithmetically clarified amount with its due date. A collection possibility does not automatically legitimise a disputed additional item. Which change of the previous payment method must be appropriately agreed is checked against the specific tenancy agreement.
Also clarify the person who actually pays and holds the account. A stored IBAN does not replace the required authorisation. The Bundesbank describes the SEPA mandate as consent to the collection and an instruction to the payer’s payment service provider. For consumer payments the core scheme must be distinguished from the business-to-business scheme. [MANDAT]
Make the arrangement with your own bank concrete
Discuss with your bank which collection agreement, identification, mandate evidences and submission channels apply in your case. This article does not set up a payment service and does not provide an original mandate. The conditions of a particular German or Austrian bank are not derived from a general SEPA statement.
Our editorial recommendation: assign a clear internal identifier, the actual scope and the current status to each collection authorisation. If details change, the necessary evidence is clarified. An old file is not used as an unexamined suitable authorisation for a different collecting person without verification.
Coordinate announcement and submission
The Bundesbank states the exact amount and the due date for the pre-notification. In principle a lead time of at least 14 calendar days is envisaged unless another period has been agreed with the payer; the concrete implementation depends on the collection agreement. [VORAB]
Therefore plan back from the actual collection date. Which information is sent when by which agreed channel to the paying side? If the amount changes it must remain clear which announcement belongs to the new collection. That is more than internally changing a number in the accounts table.
Run the process on paper first
Use an explicitly fictitious monthly case: clarified rent amount, appropriate authorisation, intended announcement, submission and subsequent feedback. Mark who is responsible for each step. An internal trial run is not a real test debit and does not require any movement on the tenant’s account.
Pay particular attention to duplicate channels. If a transfer has previously been initiated and at the same time the first direct debit is planned, the transition month must be clearly coordinated. The mere desire for automatic payment must not accidentally lead to two uncoordinated payment requests.
Fictitious case: A feedback goes unnoticed
Sofia submits the agreed amount and immediately records it as finally paid. Later a return debit appears, which is not taken into account in her monthly overview. On the next reconciliation the bank balance and the rent account contradict each other.
She therefore keeps submission, actual booking and later feedback separate. In the event of an error it is clarified, based on the banking rules and the specific reason, which next step is appropriate. A feedback is not simply ignored nor is the same process blindly resubmitted.
Your finished process links authorisation, announcement and traceable booking. It also contains a responsible return channel for questions and errors. The direct debit thus simplifies organisation without replacing the verification of the actual rent claim and the current payment status.