Promotions

New products

  • MCP+ for Dolibarr

    MCP+ connects Claude, ChatGPT and other AI assistants straight to your Dolibarr. Just ask: Which tickets still need an answer?, Show me the unpaid invoices for Miller Ltd — and your assistant works on your real data instead of copy-paste. No extra server, no data handed to third parties: it runs in your own Dolibarr, with clear rights per connection and a full audit log.

    300.00 €
  • Guide Milestone/Jalon v 24

    User Guide for the Milestone/Jalon module, which allows products and services to be associated with or grouped under milestones, and displays the subtotal. It is possible to add comment lines without details such as VAT, price, etc., as well as to force page breaks in commercial proposals, customer orders, customer invoices, supplier invoices, and supplier orders.

    FREE

EasySepa - SEPA enhancement suite for Dolibarr

mp23914d20260827133607

New

Extensible SEPA enhancement suite for Dolibarr with two available features: consolidate all of a customer's invoices into one SEPA charge, and collect each invoice on its own due date (multiple PmtInf blocks in the XML). Coming next: XSD validation, pain.008.001.08 support, returns reconciliation and SEPA dashboard. Each feature toggles independently.

99.00 €
Excl. tax

  • Author EasySoft Tech SL
  • Module version 1.1.3
  • Release date 08/27/2026
  • Access to download and updates 2 years
  • How to contact support info@easysoft.es
  • Compatibility Dolibarr V15+   -   PHP7.0 - 8.3
  • Last update 09/06/2026 04:12 PM

More info...

EasySoft Tech - Solutions that drive your business forward
 

Group SEPA charges and collect on each invoice's due date

EasySepa is the enhancement suite for SEPA direct debits and credit transfers in Dolibarr: two features you can enable per remittance to cut bank fees and align collections with the reality of each invoice.

1
charge per customer, not per invoice
2
features combinable per remittance
PmtInf
per due date (ISO 20022)
V15–V23
PHP 7.0–8.3

The problem it solves

When you generate a SEPA remittance in Dolibarr, every invoice becomes an independent charge with a single common execution date for the whole batch. That clutters your customers' bank statements, multiplies bank fees and shifts collections away from the date your customer is actually ready to pay.

What you run into What it costs you
A customer with 5 pending invoices receives 5 direct debits on the same day An upset customer, 5 bank fees and a complaint email for each invoice
All invoices are charged on one common date although their due dates are staggered Collections too early or too late: rejects due to insufficient funds and unpredictable cash flow
The SEPA XML is built without control over how transactions are grouped Manual XML editing, format risks and administration time for a routine task

Your customer sees one line. Your bank charges one fee. And your collections land on the right day.

SEPA SUITE FOR DOLIBARR

Two improvements you enable on every remittance

Since version 1.1.3, creating a SEPA file shows a native dialog with two independent, combinable options: group all invoices of the same customer into a single charge (with the total amount and the references separated by commas in the XML) and use each invoice's due date as the collection date (generating multiple PmtInf blocks, the canonical ISO 20022 pattern accepted by every European bank). The database keeps per-invoice granularity, so standard Dolibarr reconciliation, payment marking and reject handling keep working as always.

How it looks in your Dolibarr

The full cycle: invoices prepared for direct debit, the options dialog when creating the remittance and the remittance generated with its SEPA file.

EasySepa module configuration page in Dolibarr
Module configuration page
SEPA remittance options dialog with the two enhancements
Options dialog: group by customer and collect on the due date
SEPA remittance created with its file ready for the bank
The remittance is recorded with its downloadable XML file

What's included

One charge per customer
All pending invoices of a customer are consolidated into a single transaction with the total amount. IBAN, BIC and creditor identifier are resolved automatically.
Collection on the due date
Each charge is scheduled for its invoice's due date. Past-due invoices are moved to the next business day and you're told how many were adjusted.
Traceability preserved
The database keeps one row per invoice: Dolibarr bank reconciliation, payment marking and reject handling keep working normally.
ISO 20022 & multi-company
pain.008 / pain.001 files built with the digitick/sepa-xml library: automatic escaping, evolving schema support and per-entity independence. Interface in 8 languages.

What it's used for

  • Companies collecting many recurring direct debits that want customers to see a single charge per period.
  • Teams with invoices at staggered due dates that need to collect each one on its exact date.
  • Businesses paying suppliers by credit transfer that want to consolidate payments for the same creditor.
  • Accountants tired of reconciling bank returns against remittances full of duplicated lines.

Getting started

1
Unzip the module into custom/easysepa/ and activate it together with the direct debit and transfer modules.
2
Define the company bank account with its IBAN, BIC and ICS, and your customers' RIB, as in the standard SEPA flow.
3
Prepare the direct debit requests from the Domiciliations tab of each invoice (Prepare Direct Debit).
4
Create the SEPA remittance: the dialog lets you enable customer grouping and due dates, and the file is generated ready for the bank.

Requirements

Dolibarr V15 to V23
PHP 7.0 to 8.3
Database MySQL 5.7+ · MariaDB 10.2+ · PostgreSQL 10+
License GNU General Public License v3.0 · 730 days of update access

Before you buy

Can I adapt it to my case?
Yes. It is distributed under GNU GPL v3: you receive the full source code and can read, modify and adapt it without asking permission.
How can I test it without risking my data?
Install it on a test copy of your Dolibarr and generate a remittance without sending it to the bank: the file stays in the remittance folder for you to validate.
What if it doesn't fit my setup?
Write to info@easysoft.es before buying and we'll look at it together. We prefer to tell you it doesn't fit than to sell you something that doesn't work.
What happens after the 730 days?
The module keeps working: nothing is deactivated or lost. What is renewed is access to new versions, improvements and email support during the update window.

Active maintenance

EasySepa evolves as a suite: pre-send XSD validation, pain.008.001.08 schema support (EPC 2025), recurring remittances, return reconciliation or the Spanish Cuaderno 19.14 are on the roadmap. Each piece is released as an optional, activatable feature without breaking what you already have.

24
modules published on Dolistore
GPLv3
full source code
8
interface languages
730
days of updates

Does it fit what you need?

Tell us about your case and we'll tell you if EasySepa suits it — and if it doesn't, we'll tell you that too.

info@easysoft.es www.easysoft.es



If you think this module is a fork of another one (published after the first one) or violates some terms or conditions of use (for users or vendors), you can make a report at dolistore@dolibarr.org