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 the payer's 6-digit sort code (stored on the bank account record, with optional auto-fill from the UK IBAN), 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 Lead-Time
_check_collectable enforces that a mandate is active and that no collection exceeds its optional max_amount cap. Batch validation also enforces each mandate's prenotice_days: if the requested collection date falls within the advance-notice window, validation raises a clear error preventing premature collections. Batches with a mismatched scheme are also blocked.
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: OPL-1
- Languages: English
- Author: Pokutsoft
- Dependencies: account
- Support: support@pokutsoft.com
Update date: 2026-07-02