Subscription billing: recurring invoices and automatic card/SEPA collection — Abonnements Pro

Dolibarr bills. Abonnements Pro collects.

Since version 24, Dolibarr generates its recurring invoices and can even send them. But it stops there: no saved payment method, no automatic debit, no failure handling, no service suspension. That gap is exactly what this module fills.

WHAT YOU SET UP IN TWO MINUTES

You create a plan: a label, a price, a billing cycle (monthly, quarterly, yearly, or n days), a VAT rate. Add a trial period, a minimum commitment or a fixed billing day if you need them.

You subscribe a customer to that plan. The module creates Dolibarr's native recurring invoice for you: not a parallel billing system, the real one your accountant already knows: and, if you want it, the contract with its service lines.

Your customer receives a link. They save a card or sign a SEPA mandate. That is all.

WHAT HAPPENS NEXT, WITHOUT YOU

On each due date Dolibarr generates the invoice. The module debits it, records the payment, and marks the invoice paid. You touch nothing.

If the debit fails, the module retries on the schedule you set: three days, one week, two weeks by default: notifies your customer, and sends a link to change card. If nothing works, it moves the subscription to past due, closes the contract services, and cancels after the delay you chose.

A card declined for insufficient funds is retried. A closed account or a revoked mandate is not: the module knows the difference, does not keep hammering, and asks for a new payment method instead. Your customer is not buried under pointless failure e-mails.

COLLECTION METHODS

Card and SEPA Direct Debit through Stripe, on the provider's hosted page: no card data ever enters your Dolibarr. Native SEPA direct debit through Dolibarr's own Direct debit module, with mandate, RUM and date, for those who already produce pain.008 files. And a manual mode, for customers who pay by transfer and only need the dunning.

WHAT YOU SEE

A dashboard with your monthly recurring revenue, the number of active, trial, past-due and suspended subscriptions, your 30-day failure rate, the week's due dates and the collections that need your attention.

On each subscription: the invoices, every collection attempt with its outcome and decline reason, the full event log, and the linked contract.

On each subscription invoice: the collection status and a button to debit right now.

MID-TERM CHANGES

Plan upgrade or downgrade with proration to the day. Pause and resume. Cancellation at period end or immediately. Any remaining minimum commitment is flagged before you cancel.

WHAT THE MODULE DOES NOT DO, AND WHY

It does not bill instead of Dolibarr. No Stripe Billing, no parallel numbering: your invoices stay Dolibarr invoices, with your numbering and your templates.

It never reverses an accounting entry on its own. A refund or a chargeback is flagged, logged and alerted: the decision stays yours.

It never records two payments for a single collection, even if a webhook is replayed ten times. And it never debits a customer whose payment method is not saved.

COMPATIBILITY AND REQUIREMENTS

Dolibarr 20 to 24, PHP 7.4 to 8.3, French and English. Developed and tested on Dolibarr 20.0.4 and 24.0.0: 257 automated assertions plus an HTTP check of thirty-four pages in both languages.

Requirement: the Invoices module. Dolibarr's « Recurring invoices » scheduled job must be enabled, it is what generates the invoices; the module checks its state and tells you on its setup page.

Optional, detected automatically: Contracts, Direct debit, Stripe Payment Links (to reuse your keys), WhatsApp Notify (to double your dunning).

WHAT THIS VERSION DOES NOT INCLUDE

GoCardless is planned for 1.1: the architecture is ready for it, but we do not ship a provider we could not validate on a test account.

The self-service customer portal is planned for 1.2, on Dolibarr's native WebPortal. Automatic posting of provider fees arrives in 1.1.

TWO YEARS OF UPDATES

Support: support@arcchester.com