Swiss Payment slip known as ESR/BVR
This addon allows you to print the ESR/BVR report Using Qweb report.
The ESR/BVR is grenerated as an image and is availabe in a fields of the l10n_ch.payment_slip Model.
This module will also allow you to import v11 files provided by financial institute into a bank statement
This module also adds transaction_ref field on entries in order to manage reconciliation in multi payment context (unique reference needed on account.move.line). Many BVR can now be printed from on invoice for each payment terms.
Configuration
You can adjust the print out of ESR/BVR, which depend on each printer, for every company in the “BVR Data” tab.
This is especialy useful when using pre-printed paper. Options also allow you to print the ESR/BVR in background when using white paper and printing customer address in the page header.
By default address format on ESR/BVR is %(street)sn%(street2)sn%(zip)s %(city)s This can be change by setting System parameter bvr.address.format
Usage
The ESR/BVR is created each time an invoice is validated. To modify it you have to cancel it and reconfirm the invoice.
To import v11, use the wizard provided in bank statement.
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 smash it by providing detailed and welcomed feedback.
Credits
Contributors
Nicolas Bessi <nicolas.bessi@camptocamp.com>
Vincent Renaville <vincent.renaville@camptocamp.com>
Yannick Vaucher <yannick.vaucher@camptocamp.com>
Romain Deheele <romain.deheele@camptocamp.com>
Thomas Winteler <info@win-soft.com>
Joël Grand-Guillaume <joel.grandguillaume@camptocamp.com>
Guewen Baconnier <guewen.baconnier@camptocamp.com>
Alex Comba <alex.comba@agilebg.com>
Lorenzo Battistini <lorenzo.battistini@agilebg.com>
Paul Catinean <paulcatinean@gmail.com>
Paulius Sladkevičius <paulius@hbee.eu>
David Coninckx <dco@open-net.ch>
Akim Juillerat <akim.juillerat@camptocamp.com>
Simone Orsi <simone.orsi@camptocamp.com>
Financial contributors
Hasa SA, Open Net SA, Prisme Solutions Informatique SA, Quod SA
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-payment-slip 10.0.1.1.6
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_payment_slip-10.0.1.1.6-py2-none-any.whl | Python 2 | none | any | Details for odoo10_addon_l10n_ch_payment_slip-10.0.1.1.6-py2-none-any.whl |
Release files / odoo10_addon_l10n_ch_payment_slip-10.0.1.1.6-py2-none-any.whl
| Download URL | odoo10_addon_l10n_ch_payment_slip-10.0.1.1.6-py2-none-any.whl |
|---|---|
| Size | 1.1 MB |
| Tags | Python 2 |
|
SHA-256 checksum How to use checksums |
8aab5ffb674747a0b6a3f8fe06b96e31cd7cdbf38fce13546f8b4758ea1eb8bf
|
|
BLAKE2b-256 checksum How to use checksums |
a92a0a91ec3779816bcca2619c6b9c6c3c16a6a371a65f8752ecfb769b322471
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/1.11.0 pkginfo/1.4.2 requests/2.19.1 setuptools/30.4.0 requests-toolbelt/0.8.0 tqdm/4.24.0 CPython/3.5.3
|
Security for odoo10-addon-l10n-ch-payment-slip 10.0.1.1.6
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.
