| Availability |
Odoo Online
Odoo.sh
On Premise
|
| Odoo Apps Dependencies |
•
Discuss (mail)
• Invoicing (account) |
| Lines of code | 1302 |
| Technical Name |
pay_sepa_sct_it |
| 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 | 1302 |
| Technical Name |
pay_sepa_sct_it |
| License | OPL-1 |
| Website | https://gencbaris.com/odoo_plugins/ |
| Versions | 18.0 19.0 |
SEPA Credit Transfer for Italy â CBI pain.001 Generator
Pay vendors and employees in EUR by generating ISO 20022 pain.001 files with the Italian CBI bank profile â uploaded through your own bank's CBI / remote-banking channel. No third-party gateway, no per-transaction fee.
What this app does
Create a batch of credit transfers in Odoo, validate every IBAN and BIC, then export a standards-compliant CustomerCreditTransferInitiation (pain.001) XML file. The file follows the EPC SEPA Credit Transfer Rulebook and the Italian CBI (Customer to Bank Interbank) corporate-banking profile, so it is accepted by the file-upload / remote-banking channels of Italian banks. You stay in full control: the file is generated inside your Odoo and uploaded with your own banking credentials.
Key features
Two ISO 20022 schema versions
Emit pain.001.001.09 (the 2019 message version on which the current SEPA Credit Transfer scheme is based, the default) or the legacy pain.001.001.03 CBI classic profile for an older Italian bank channel that still requires it. Choose per company or per batch.
Italian IBAN with CIN check
Every IBAN is validated with the ISO 13616 / ISO 7064 MOD-97 checksum and the Italian national CIN control character computed over ABI + CAB + account number â the same depth a domestic Italian bank applies. ABI and CAB are extracted and shown on each line.
CBI CUC and tax identifiers
Carry your CUC (Codice Univoco CBI) in the initiating party so the bank can authorise the file, and your Partita IVA or Codice Fiscale in the debtor block for reconciliation. Company tax ids are classified automatically into the correct ISO 20022 organisation / private id branch.
IBAN-only (BIC-less) transfers
SEPA is IBAN-only since February 2016. When a creditor BIC is unknown the file carries NOTPROVIDED for the creditor agent, exactly as the EPC guidelines require â accepted across the whole SEPA area, including San Marino.
Structured and free-text remittance
Use a free-text causale (RmtInf/Ustrd) or an ISO 11649 / SCOR RF creditor reference (RmtInf/Strd) so the payee reconciles your invoice automatically. Italian accents are transliterated to the SEPA character set.
Build batches from vendor bills
Select posted vendor bills and let the wizard group residual amounts per supplier, pull each supplier's bank IBAN, and fill in the remittance from the invoice reference â one click to a ready-to-send payment file.
pain.001 elements produced
| ISO 20022 element | Content |
|---|---|
| GrpHdr / MsgId, CreDtTm | Unique message id and creation timestamp |
| GrpHdr / NbOfTxs, CtrlSum | Transaction count and control sum (EUR) |
| InitgPty / Id / OrgId (CBI) | Your CUC with proprietary scheme name CBI |
| PmtInf / PmtMtd | TRF (credit transfer) |
| PmtInf / SvcLvl / Cd | SEPA service level |
| PmtInf / ChrgBr | SLEV (shared charges, SEPA-mandated) |
| PmtInf / ReqdExctnDt | Requested execution date |
| Dbtr / Id | Debtor Partita IVA (OrgId) or Codice Fiscale (PrvtId) |
| DbtrAcct / Id / IBAN | Ordering account IBAN |
| CdtTrfTxInf / Amt / InstdAmt | Amount with Ccy="EUR" |
| CdtrAgt / FinInstnId | BIC or NOTPROVIDED (IBAN-only) |
| RmtInf / Ustrd or Strd | Free-text causale or SCOR/RF reference |
How it works
- Set your ordering account IBAN, BIC, CUC and Partita IVA / Codice Fiscale in Settings.
- Create a SEPA Credit Transfer batch and add transfer lines (or build them from vendor bills).
- Validate the data â IBAN/CIN, BIC, amounts and CUC are checked.
- Generate the pain.001 file, preview it, and download it.
- Upload the file to your bank's CBI / remote-banking portal and mark the batch as sent.
Validation built in: ISO 13616 MOD-97 + Italian CIN for every IBAN, ISO 9362 BIC format and BIC-vs-IBAN country match, strictly positive amounts under the SEPA per-transaction ceiling, and an 8-character CUC. Problems are reported before the file is produced, so banks do not reject your upload.
Community-only, no external dependencies
Builds on the Odoo Community account module. No Enterprise module, no online connector and no third-party service is required â the file is produced entirely inside your Odoo and you transmit it with your own bank credentials.
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