This release is a pre-release and may not be stable for production use.
Account Banking SEPA Credit Transfer
Module to export payment orders in SEPA XML file format.
SEPA PAIN (PAyment INitiation) is the new european standard for Customer-to-Bank payment instructions. This module implements SEPA Credit Transfer (SCT), more specifically PAIN versions 001.001.02, 001.001.03, 001.001.04 and 001.001.05. It is part of the ISO 20022 standard, available on https://www.iso20022.org.
The Implementation Guidelines for SEPA Credit Transfer published by the European Payments Council (https://www.europeanpaymentscouncil.eu) use PAIN version 001.001.03, so it’s probably the version of PAIN that you should try first.
It also includes pain.001.003.03 which is used in Germany instead of 001.001.03. You can read more about this here (only in german language): http://www.ebics.de/startseite/
Table of contents
Installation
This module depends on : * account_banking_pain_base
This module is part of the OCA/bank-payment suite.
Configuration
Create a Payment Mode dedicated to SEPA Credit Transfer.
Select the Payment Method SEPA Credit Transfer to suppliers (which is automatically created upon module installation).
Check that this payment method uses the proper version of PAIN.
Usage
In the menu Invoicing/Accounting > Payments > Payment Order, create a new payment order and select the Payment Mode dedicated to SEPA Credit Transfer that you created during the configuration step.
Bug Tracker
Bugs are tracked on GitHub Issues. In case of trouble, please check there if your issue has already been reported. If you spotted it first, help us to smash it by providing a detailed and welcomed feedback.
Do not contact contributors directly about support or help with technical issues.
Credits
Contributors
Alexis de Lattre <alexis.delattre@akretion.com>
Stéphane Bidoul <stephane.bidoul@acsone.eu>
Stefan Rijnhart
Julien Laloux
Alexandre Fayolle
Raphaël Valyi
Erwin van der Ploeg
Sandy Carter
-
Antonio Espinosa
Pedro M. Baeza
Maintainers
This module is maintained by the OCA.
OCA, or the Odoo Community Association, is a nonprofit organization whose mission is to support the collaborative development of Odoo features and promote its widespread use.
This module is part of the OCA/bank-payment project on GitHub.
You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.
1 maintainer
Metadata
1 maintainer
Release files for odoo12-addon-account-banking-sepa-credit-transfer 12.0.1.0.0.99.dev21
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| odoo12_addon_account_banking_sepa_credit_transfer-12.0.1.0.0.99.dev21-py3-none-any.whl | Python 3 | none | any | Details for odoo12_addon_account_banking_sepa_credit_transfer-12.0.1.0.0.99.dev21-py3-none-any.whl |
Release files / odoo12_addon_account_banking_sepa_credit_transfer-12.0.1.0.0.99.dev21-py3-none-any.whl
| Download URL | odoo12_addon_account_banking_sepa_credit_transfer-12.0.1.0.0.99.dev21-py3-none-any.whl |
|---|---|
| Size | 78.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
854253bbe19b7016007ed9e636bc6273fe4501113bf657066c21ca099866e841
|
|
BLAKE2b-256 checksum How to use checksums |
d30e8c5981405f7712cff9d9ce570ad42cc2d7c7035237e8dba305b457ecc516
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.1 CPython/3.8.10
|
Security for odoo12-addon-account-banking-sepa-credit-transfer 12.0.1.0.0.99.dev21
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
