No products
* Prices may vary depending on your country.
* An additional contribution can be added at the time of payment.
New products
Fully customizable PDF template for Dolibarr 24 proposals: logo, colors, margins, columns and address blocks, no code needed. Cover and presentation pages before the proposal, terms and PDF appendices merged with a continuous footer, barcodes and QR codes, online signature by the customer on the right page.
Dolibarr tells you how many items you have. It does not tell you where they are, which batch expires first, in which order to walk the warehouse, or what must be ordered today to be delivered on time.
mp23914d20260827133607
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.
|
|
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–V24
PHP 7.0–8.3
|
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.
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.
The full cycle: invoices prepared for direct debit, the options dialog when creating the remittance and the remittance generated with its SEPA file.
| Dolibarr | V15 to V24 |
| 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 |
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
|
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