| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1427 |
| Technical Name |
pay_sepa_sct_fr |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1427 |
| Technical Name |
pay_sepa_sct_fr |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
SEPA Credit Transfer for France
Generate ISO 20022 pain.001 credit-transfer files for French banks â clé RIB validation, ISO 11649 RF references, category purpose codes and BIC-less / IBAN-only support. No third-party gateway, your data never leaves Odoo.
What this module does
This app turns vendor bills, payroll runs or any list of beneficiaries into a fully-formed SEPA Credit Transfer pain.001 XML file, built to the EPC SEPA Credit Transfer Rulebook and the French banking community (CFONB) profile. You upload the file to your own bank's online-banking or EBICS channel â the module transmits nothing to any external service, so there is no per-transaction fee and your payment data stays inside your database.
It produces, from the same data, the current pain.001.001.09 (2019 message version on which the current SEPA Credit Transfer scheme is based, the default) and the legacy pain.001.001.03 schema for an older French e-banking channel that still requires it.
French-specific features
Clé RIB validation
Every French IBAN carries a two-digit RIB key (clé RIB) that a bank re-derives from the code banque, code guichet and account number. The module computes it with the official Banque de France control (89·banque + 15·guichet + 3·compte mod 97) and rejects an account whose key is inconsistent â a problem the plain IBAN checksum does not catch.
ISO 11649 RF reference
Generate a structured RF creditor reference from an
invoice number with one click. The two ISO 7064 MOD-97 check
digits are computed for you, the reference is emitted in
RmtInf/Strd/CdtrRefInf with code SCOR, and your
supplier reconciles the payment automatically.
Category purpose
Tag a batch with an ISO 20022 category purpose code
(SALA salaries, SUPP supplier, TREA treasury, TAXS taxes,
PENS pensions and more) so the receiving bank applies the
correct handling. The code is placed in
PmtTpInf/CtgyPurp/Cd.
IBAN-only / BIC-less
SEPA has been IBAN-only since February 2016. When no BIC is
known the file carries NOTPROVIDED for the agent,
exactly as French banks expect. For a recognised French bank
code the head-office BIC is filled in automatically.
Feature overview
| Output format | ISO 20022 pain.001.001.03 and pain.001.001.09 (CustomerCreditTransferInitiation), UTF-8 XML. |
| IBAN validation | ISO 13616 length + ISO 7064 MOD-97 check for all SEPA countries, plus French overseas (DOM/TOM) territories. |
| Clé RIB | Banque de France RIB-key control on every French IBAN, with the standard letter-to-digit table. |
| BIC | ISO 9362 validation, IBAN/BIC country match, automatic head-office BIC from the French bank code (optional â IBAN-only stays valid). |
| Remittance | Unstructured free text or ISO 11649 RF structured creditor reference (SCOR), within the SEPA character set. |
| Category purpose | SALA, SUPP, PENS, TREA, TAXS, GOVT, DIVI, INTC, TRAD, OTHR. |
| Charge bearer | SLEV (service-level, mandatory for SEPA). |
| Build from bills | Wizard turns selected posted vendor bills into a ready batch, grouping amounts due per payee and optionally deriving an RF reference per supplier. |
| Workflow | Draft â Generated â Sent, with chatter audit trail, in-app file preview and one-click download. |
| Compatibility | Odoo 18 and Odoo 19, Community-only dependencies (account, base, mail). |
How it works
- Set your ordering account IBAN, initiating party and default schema version in Settings â SEPA Credit Transfer FR.
- Create a credit-transfer batch and add transfers, or use the Build from Bills wizard on your posted vendor bills.
- Click Validate Data to surface any IBAN, clé RIB, BIC or RF-reference issue before producing the file.
- Click Generate pain.001, review the preview, and Download the XML.
- Upload the file to your bank's online-banking or EBICS channel and mark the batch as Sent.
Boundary & disclosure
This module is a file generator. It builds the SEPA pain.001 payment file for you to upload through your own bank using your own banking credentials (BYOK). It is not a payment service provider, does not connect to any bank API, and never transmits your payment data to a third party. Final execution is always performed by your bank.
Screenshots
Credit Transfers
Build From Bills
Odoo Proprietary License v1.0 This software and associated files (the "Software") may only be used (executed, modified, executed after modifications) if you have purchased a valid license from the authors, typically via Odoo Apps, or if you have received a written agreement from the authors of the Software (see the COPYRIGHT file). You may develop Odoo modules that use the Software as a library (typically by depending on it, importing it and using its resources), but without copying any source code or material from the Software. You may distribute those modules under the license of your choice, provided that this license is compatible with the terms of the Odoo Proprietary License (For example: LGPL, MIT, or proprietary licenses similar to this one). It is forbidden to publish, distribute, sublicense, or sell copies of the Software or modified copies of the Software. The above copyright notice and this permission notice must be included in all copies or substantial portions of the Software. THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Please log in to comment on this module