| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Sign (sign)
• Invoicing (account) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2406 |
| Technical Name |
sign_sepa_mandate |
| License | OPL-1 |
| Website | https://www.alwinen.de |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Sign (sign)
• Invoicing (account) • Discuss (mail) |
| Community Apps Dependencies | Show |
| Lines of code | 2406 |
| Technical Name |
sign_sepa_mandate |
| License | OPL-1 |
| Website | https://www.alwinen.de |
Sign SEPA Direct Debit Mandates Online — Right Inside Odoo
Send. Sign. Validate. Activate. Zero paper, zero IBAN typos, zero waiting on your AR team.
A native Odoo Sign extension built for SEPA mandates
Stop chasing customers for signed PDFs and stop re-typing IBANs by hand. This module turns every SEPA Direct Debit Mandate into a fully digital workflow that runs inside the Accounting app:
- One-click Request Signature: a new button on the mandate form opens the right template in the customer's own language.
- Sign on any device: customers receive a personal signing link — based on the powerful Odoo Sign app.
- IBAN validation built-in: the signed IBAN is checked before it ever touches your database.
- Automatic writeback: the validated IBAN is saved to the mandate record.
- Auto-activate: the mandate flips from Draft to Active once the customer has signed. No human in the loop.
Editing the SEPA Direct Debit Mandate sign template
Customer signing the SEPA Direct Debit Mandate
SEPA Direct Debit Mandate after signing
Settings for the SEPA Direct Debit Mandate sign template
Powerful Features Out of the Box
1. One-Click Request Signature
Right where you already work: a primary "Request Signature" button is added to every draft SDD mandate. It opens the standard Odoo Sign wizard pre-filled with the correct template, the correct signer, and a back-reference to the mandate.
2. Automatic Language Selection
Speak your customer's language: the template is chosen from
partner.lang. English and German templates ship pre-configured, and you can map any
additional language to your own template — with safe fallback to English.
3. Built-in IBAN Validation
Catch typos before they hit production: the IBAN field is bound to a dedicated sign item type with IBAN-format validation. Invalid IBANs are rejected at signing time, not after the next direct-debit batch fails.
4. Automatic IBAN Writeback
No double data entry: the validated IBAN is written back to
mandate.partner_bank_id.acc_number. If the mandate has no bank record yet, Odoo
creates one on the customer in the right company — a chatter message records the change.
5. Auto-Activate After Signature
From request to active in one round-trip: enable the per-company option and a signed mandate with a valid IBAN goes straight to the Active state — no accountant in the loop, no validation queue.
6. Full Visibility & Audit Trail
Never lose track: a "Signatures" stat button shows every request linked to the mandate, the "SEPA Signed" search filter lists all completed mandates, and chatter records every state change end-to-end.
How it works — in 4 steps
|
1
|
Step 1 — Click Request Signature on the mandate
Open any draft SDD mandate and hit the new Request Signature button.
The module picks the template that matches |
|
2
|
Step 2 — The customer signs from any deviceThe native Odoo Sign email goes out. The customer fills in the IBAN, draws a signature on the touchscreen or mouse, and confirms. No Odoo account required. |
|
3
|
Step 3 — Odoo validates & writes the IBAN backThe IBAN will be validated and written back to the mandate record. A chatter message is posted on the mandate as a clean audit trail. |
|
✔
|
Step 4 — Mandate auto-activates & you can debitThe mandate moves from Draft to Active automatically once the customer has signed. Direct-debit payment batches can pick it up on the very next run. |
Frequently Asked Questions
Is an e-signature legally binding for a SEPA mandate?
Inside the EU, the eIDAS regulation recognises electronic signatures as legally binding. Combined with the audit trail produced by Odoo Sign (timestamp, signer identity, IP, full document hash) the signed mandate carries the same probative value as a hand-signed PDF for direct-debit purposes. Always confirm requirements with your bank and your local compliance officer.
What happens if the customer enters an invalid IBAN?
The IBAN sign item is bound to a dedicated type with IBAN-format validation. The customer cannot submit the form until the IBAN passes the format check, so your mandate database never receives garbage values.
What if the customer already had IBAN in Odoo?
If the mandate already has IBAN, the signed IBAN updates it through the standard writeback path. If the mandate has no bank record yet, the module creates a fresh one on the customer in the right company and links it to the mandate automatically — a chatter message records exactly what happened.
Can I disable the auto-activation?
Yes. The Auto-activate after signature switch lives on the company. With the toggle off, the mandate stays in Draft after signature and your accountant validates it manually — useful when you want a review by your accountant.
Can I add my own template (Italian, French, Spanish…)?
Absolutely. Create a sign template with your own localised PDF, and add a new row mapping the language to your template in the settings. Customers in that language will automatically receive your template from then on.
Does it work with Odoo's multi-company feature?
Yes. Both the template mapping and the auto-activate switch are company-dependent. Each branch of your group runs with its own SEPA-compliant document, its own creditor identifier, and its own activation policy.
Support & Contact
Questions, customisation requests, or help configuring the SEPA workflow for your country — get in touch and we'll be happy to help.
Email Support:
info@alwinen.de
Developed by Alwinen GmbH
Professional Odoo Solutions for European Businesses
https://www.alwinen.de
Copyright © Alwinen GmbH | Licensed under the Odoo Proprietary License v1.0
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module