| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 905 |
| Technical Name |
gb_direct_debit_mandate_manager |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Invoicing (account)
• Discuss (mail) |
| Lines of code | 905 |
| Technical Name |
gb_direct_debit_mandate_manager |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
Direct Debit Mandate Mana
Manage SEPA & Bacs direct debit mandates and build collection files (BYOK)
Direct debit administration is usually scattered across spreadsheets, where mandate references drift, SEPA sequence types get misapplied and building a compliant collection file is a manual chore that invites scheme rejections. UK and European businesses collecting recurring payments by direct debit lose time and cash to this every cycle. This module centralises customer mandates on gb.dd.mandate, links them to invoices, and generates ready-to-upload SEPA pain.008 and Bacs Standard 18 collection files using your own scheme credentials. No payment-institution licence is required: it produces the file, your bank does the submission.
Key Features
Central Mandate Register
Each gb.dd.mandate stores a unique UMR/Bacs DDI reference (auto-sequenced), the customer's res.partner.bank account, scheme (SEPA CORE, SEPA B2B or Bacs), signature date and creditor identifier. A draft/active/suspended/closed lifecycle on mail.thread replaces scattered spreadsheets with one tracked register.
SEPA Sequence-Type Handling
A mandate's sequence_type (FRST, RCUR, FNAL, OOFF) is stamped onto each collection, and advance_sequence_type promotes FRST to RCUR after the first successful collection. The correct SEPA sequence is always applied without manual tracking, avoiding scheme rejections.
Invoice-Driven Collection Batches
The gb.dd.batch.invoice.wizard pulls posted out_invoices due on or before a date that carry an active matching-scheme mandate and are not yet collected, creating one gb.dd.batch.line each. It turns the AR ledger into a collection run in a couple of clicks.
ISO 20022 pain.008 SEPA Export
action_generate_file builds a SEPA pain.008.001.02 XML with group header, control sum, CORE or B2B local instrument and one DrctDbtTxInf per line carrying mandate id, signature date, debtor IBAN/BIC and remittance. The output is a ready-to-upload SEPA direct debit initiation file.
Bacs Standard 18 Export
For UK collections, _build_bacs_file produces a fixed-width Bacs Standard 18 text file with sort code, account number, transaction code (first vs regular), amount in pence, mandate reference and payer name. UK businesses get a scheme-formatted collection file alongside SEPA.
Mandate Caps & Pre-Notification
_check_collectable enforces that a mandate is active and that no collection exceeds its optional max_amount cap, while prenotice_days records the advance notice the customer must receive. Batch validation also blocks lines whose mandate scheme differs from the batch.
Locked Workflow & Audit
Batches move draft, validated, file-generated, submitted and cancelled, and a submitted batch can no longer be edited via the write guard. Marking submitted stamps each line collected and advances mandate sequence types, giving a tamper-resistant collection audit trail.
BYOK Format Generator
The module is a pure file generator using the customer's own SEPA Creditor Identifier or Bacs SUN; it never connects to a bank or scheme and requires no payment-institution licence. You upload the generated file through the banking relationship you already have, keeping full control.
Use Cases
Screenshots
Collection Batches
Why Choose This Module
Direct debit admin is usually scattered across spreadsheets. This module centralises customer mandates, links them to invoices, and produces ready-to-upload SEPA and Bacs collection files — using your own scheme credentials. No payment-institution licence required: it generates the file, your bank does the submission.
Specifications
- Compatible: Odoo 18.0 / 19.0
- License: LGPL-3
- Languages: 35+
- Author: Baris Genc
- Dependencies: account
- Support: odoo@gencbaris.com
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