GoCardless SEPA Direct Debit for Odoo

At its core the module adds a proper GoCardless mandate lifecycle to Odoo. We introduce a dedicated gocardless.mandate model (models.Model) linked one-to-many from res.partner, with fields for scheme, mandate reference, status and the GoCardless customer/bank-account IDs. Compute fields using @api.depends roll up each customer's active-mandate state and outstanding collection totals so your finance team sees everything on the partner form. Mandates are created either through a hosted GoCardless authorisation flow (Billing Request Flow) surfaced from the customer portal, or set up by your team from a mandate wizard — the customer authorises once, and every future invoice can be collected against it.

Collection is wired into the documents you already use. When an account.move (customer invoice) is confirmed for a partner with an active mandate, the module can create a GoCardless payment for the balance due, respecting scheme-specific charge dates and advance-notice rules. For subscription and recurring revenue, it hooks into your billing cadence (Odoo subscriptions or a scheduled ir.cron sweep) to batch-create collections on the correct dates. One-off "collect now" actions are available directly from the invoice via a server action / button for ad-hoc charges.

The hard part of direct debit is what happens after you submit — and that is exactly what we automate. A secured, signature-verified webhook controller (JSON-RPC style HTTP endpoint) ingests GoCardless events (payment confirmed, paid_out, failed, charged_back, mandate cancelled/expired) and reconciles them against the originating Odoo payment. Confirmed collections post an account.payment and reconcile it to the invoice; payouts can be matched to your bank statement lines to close the loop end-to-end. Failed and charged-back payments are flagged, the invoice is re-opened, and a configurable retry policy (with backoff and a max-attempt cap) re-presents the collection or escalates to your dunning process — so a bounced debit never silently slips through.

Everything is built to Odoo standards: strict ir.model.access.csv plus record rules so only Accounting/Finance roles can view mandates and trigger collections, QWeb-ready mandate confirmation documents, clean OWL/XML views with status ribbons, and a settings page holding your GoCardless access token and webhook secret. It runs on Community and Enterprise, uses the official GoCardless API, and — because it is written natively — coexists cleanly with your existing accounting localisation and payment providers.

Because this is a bespoke build, we scope it to your schemes, currencies, subscription model and reconciliation workflow before we write a line of code. Typical delivery is 2–4 weeks. You receive the full module source, a sandbox-verified deployment, documentation and a support window — no black boxes, no per-transaction lock-in beyond GoCardless's own published fees.