Setting up a SEPA Direct Debit mandate for a new customer is one of those administrative steps that feels straightforward on the surface but carries real operational and legal weight. For installation companies managing recurring service and maintenance contracts, getting the mandate process right from the start means fewer payment delays, cleaner cash flow, and a professional experience for the customer. Done poorly, it creates compliance gaps, failed collections, and damaged trust.
This guide walks through everything involved in setting up a SEPA Direct Debit mandate for a new customer, from what the mandate actually contains to the most common setup errors that trip up even experienced teams.

What a SEPA Direct Debit mandate includes

A SEPA Direct Debit mandate is a formal authorization that gives a creditor permission to collect payments directly from a customer’s bank account. It is a legally binding document under the SEPA regulatory framework, and its contents are standardized across all participating countries within the Single Euro Payments Area.

Every valid mandate must include the customer’s full name and address, their IBAN (and BIC where required), the name and creditor identifier of the company collecting the payments, and a clear statement that the customer authorizes future debits. The mandate must also specify whether it covers a one-off collection or a recurring series of payments. For service and maintenance contracts in the installation industry, recurring mandates are the standard.

Each mandate is assigned a Unique Mandate Reference (UMR), which is used to track and identify that specific authorization throughout its lifetime. This reference appears on every transaction linked to the mandate, making it traceable for both the creditor and the customer’s bank. Without a properly formatted UMR, payment processors and banks may reject the debit instruction entirely.

Legal and compliance requirements to know first

Before collecting a single euro via direct debit, there are legal obligations that must be met. These are not optional formalities; they are enforceable requirements under the SEPA Core Direct Debit Scheme and, in some cases, under national consumer protection law.

The most critical requirement is the pre-notification rule. Creditors must notify the customer of an upcoming direct debit collection at least 14 calendar days in advance, unless a shorter notice period has been explicitly agreed upon in the contract. This notification must state the amount to be collected, the collection date, and the mandate reference. Failing to send this pre-notification on time gives the customer grounds to dispute the charge.

Mandate signatures must be properly captured and stored. A handwritten signature on paper has long been accepted, but digital signatures are increasingly the norm, provided they meet the requirements of the eIDAS Regulation for electronic signatures within the EU. Critically, the timestamp and the IP address of the signing party should be recorded as proof of authorization. This documentation is essential if a mandate is ever disputed or if a customer claims they never authorized the debit.

It is also worth noting that customers have the right to request a refund of any authorized direct debit within eight weeks of the collection date, and up to 13 months if they claim the mandate was never authorized at all. This underscores why airtight mandate documentation is not just good practice but a financial safeguard for the company.

Step-by-step setup of a SEPA mandate in your ERP

Setting up a SEPA Direct Debit mandate within an ERP system should follow a consistent process every time. Inconsistency is where errors creep in, particularly when multiple team members are creating contracts for different customers.

1. Create the customer record and verify bank details

The first step is ensuring the customer’s data in the system is complete and accurate. This means a verified IBAN, the correct legal name, and a current email address to which the mandate authorization will be sent. An invalid IBAN is one of the most common reasons direct debit collections fail, and it is far easier to catch during setup than after a failed payment run.

2. Configure the contract and billing schedule

Once the customer record is in place, the contract is created and linked to that customer. The billing frequency, contract duration, and payment amount are defined at this stage. Using reusable contract templates, where pricing and billing parameters are pre-configured, reduces manual input and ensures consistency across the team. This is especially important for larger operations where multiple people handle contract creation.

3. Send the mandate for digital authorization

The customer receives a secure link by email that takes them directly to their contract. They review the terms, draw their signature, and authorize the bank mandate, all from a single screen on any device. No account creation or password is required. The system records the exact timestamp and IP address of the signature, satisfying the legal documentation requirements discussed earlier.

4. Confirm mandate activation before the first billing run

Once the customer has signed and authorized the mandate, verify within the ERP that the mandate status has updated to active before the first scheduled billing date. Running a simulation of the billing cycle before it goes live, sometimes called a dry run, allows the team to confirm that the correct invoice amount will be generated for the correct customer on the correct date, with no surprises.

Connecting the mandate to invoices and payment runs

A signed mandate on its own does not trigger payments. It must be correctly linked to the invoicing workflow so that when the billing engine generates an invoice, it knows which mandate to use for collection.

In a well-configured system, this connection is established automatically at the point of contract creation. The mandate reference is stored against the customer’s contract, and every invoice generated under that contract inherits the mandate details. The payment service provider, such as Mollie, then uses this reference to initiate the bank debit on the scheduled collection date.

For companies managing a large portfolio of service contracts, the billing engine runs on a set schedule, often nightly, checking which contracts have reached their billing date and generating the corresponding invoices automatically. The mandate ensures that once an invoice is generated, payment collection follows without any manual intervention. This is the operational model that converts a signed contract into reliable, predictable cash flow.

It is worth confirming with the payment provider that the mandate file has been properly registered before the first collection attempt. Most providers have a brief processing window between mandate registration and the earliest permitted collection date, which must be factored into the billing schedule for new customers.

Common mistakes when setting up SEPA mandates

Even teams with experience in direct debit management make avoidable errors during mandate setup. Knowing where things typically go wrong makes it much easier to build a process that catches problems before they affect customers or cash flow.

• Incorrect or unverified IBANs. Entering a bank account number manually without validation is a frequent source of failed collections. Always use IBAN validation at the point of data entry, either through the ERP or the payment provider’s tools.
• Missing pre-notification. Sending the first debit without the required advance notice is a compliance breach. Ensure the pre-notification is built into the workflow automatically, not left as a manual step that someone might forget.
• Mandate not linked to the correct contract. In systems where mandates and contracts are managed separately, it is possible to create both without properly connecting them. Always verify the link before the first billing run.
• Using a one-off mandate for a recurring contract. A mandate must match the payment type. Using a one-off authorization for a recurring service contract means the mandate will be invalid from the second collection onward.
• No documentation of the signing event. If a customer disputes a charge and there is no record of when and how they authorized the mandate, the company has very limited grounds to defend the collection. Timestamp and IP address logging must be non-negotiable.
• Failing to handle mandate expiry. SEPA mandates expire if unused for 36 months. For customers on long-term contracts with infrequent billing cycles, tracking mandate validity is essential to avoid collection failures.

How OpusFlow automates SEPA Direct Debit mandate setup

We built the Contract Management module in OpusFlow specifically to remove the manual complexity from recurring payment workflows for installation companies. Rather than managing mandates, contracts, and invoices across separate tools, everything runs within a single connected platform.

Here is how OpusFlow handles the full mandate and billing workflow:

• Digital mandate authorization at signing. When a customer receives their contract via a secure magic link, they sign and authorize their SEPA Direct Debit mandate in the same step. Every signature is recorded with a timestamp and IP address, covering legal documentation requirements automatically.
• Automatic pre-notification compliance. OpusFlow handles the required SEPA pre-notification rules in the background, so teams never need to track notice periods manually.
• Nightly billing engine. The system checks active contracts every night, generates invoices for those that are due, and initiates payment collection via Mollie, with no manual trigger required.
• Double-billing protection. Once a contract period has been invoiced, it is permanently locked in the system. Even if a billing action is accidentally triggered again, OpusFlow will not generate a duplicate invoice for that period.
• Dry run simulation. Before going live, teams can run a full simulation of the billing cycle to verify which invoices would be generated and for which customers, with no real charges created.
• Flexible payment options. For customers who prefer not to use Direct Debit, the Invoice Transfer option keeps automated invoice generation active while allowing the customer to pay via standard bank transfer.

If your team is managing service and maintenance contracts and still handling mandate setup, billing, and payment tracking manually, the operational cost grows with every new customer added. Explore the Contract Management module and see how we can help your business move from manual invoicing to fully automated recurring revenue.

Related Articles

• How is the European home battery market changing and what does it mean for installers?
• What is the difference between a home battery and a power wall?
• How do you document a battery installation for compliance and commissioning?
• What is feed-in tariff and how does it change the battery ROI model?
• What are the common implementation challenges when adopting ERP software?