LSV and Postfinance Direct Debit file generator
Features:
LSV file generation
Postfinance Direct Debit file generation
Invoice freeing. You can “free” an invoice that is in a direct debit order. This is because you have sometimes to generate 2 direct debit order for the same invoice (i.e. if debit fails the first time).
Installation
To install this module, you need to have the module account_banking_sepa_direct_debit found in OCA/bank-payment repository.
Configuration
- For LSV file generation, don’t forget :
To set your LSV identifier in your beneficiary bank account.
To set your BVR identifier in your beneficiary bank account if you want to use BVR references.
To setup a payment mode with payment type “LSV Direct Debit”
That each partner which is concerned by LSV has to have a valid bank account with a valid mandate..
- For postfinance DD file generation, don’t forget :
To set your Postfinance DD identifier in your beneficiary BVR account.
To setup a payment mode with payment type “Postfinance Direct Debit”
That each partner which is concerned by Postfinance DD has to have a valid BV account with a valid mandate.
Usage
Create some invoices for partners with well configured bank accounts.
Create a Direct Debit order with a payment mode having LSV/DD payment type.
Make sure that due dates are in the valid range if you chose “Due date” as preferred execution date.
Press “Confirm payments”
Press “Make payments”. This will launch the LSV/DD file generation wizard.
Download the generated file and press “Validate”. If you need to download the file again, you can access the generated file with the “Generated Direct Debit Files” menu.
For further information, please visit:
Known issues / Roadmap
- Currently, only BVR reference usage is implemented (using l10n_ch_payment_slip
module) for LSV refernece. IPI usage is not implemented yet, this way an error occurs if no BVR ref are set in invoices.
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 smashing it by providing a detailed and welcomed feedback.
Credits
Contributors
Cyril Sester <cyril.sester@outlook.com>
Steve Ferry <steve.ferry1992@gmail.com>
Carlos Serra-Toro <carlos.serra@braintec-group.com>
Maintainer
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.
To contribute to this module, please visit http://odoo-community.org.
1 maintainer
Metadata
1 maintainer
Release files for odoo10-addon-l10n-ch-lsv-dd 10.0.1.0.0
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 |
|---|---|---|---|---|
| odoo10_addon_l10n_ch_lsv_dd-10.0.1.0.0-py2-none-any.whl | Python 2 | none | any | Details for odoo10_addon_l10n_ch_lsv_dd-10.0.1.0.0-py2-none-any.whl |
Release files / odoo10_addon_l10n_ch_lsv_dd-10.0.1.0.0-py2-none-any.whl
| Download URL | odoo10_addon_l10n_ch_lsv_dd-10.0.1.0.0-py2-none-any.whl |
|---|---|
| Size | 56.3 kB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
d743844d5ee522a3431f07cad2775ebf8a3e9b435cc469395bdeb95a1d3af970
|
|
BLAKE2b-256 checksum How to use checksums |
95daa8ef1957da3d6235247e88acb76aed04fbbcdb6b1b7ab827148bb4d7a126
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
Security for odoo10-addon-l10n-ch-lsv-dd 10.0.1.0.0
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.
