This release is a pre-release and may not be stable for production use.
eBill Postfinance
This module implements the exchange of electronic invoices with the Postfinance web service.
Table of contents
Installation
This module needs the Python library ebilling_postfiance which can be installed from Pypi. More information can be found at repositoryhttps://github.com/camptocamp/ebilling-postfinance.
Configuration
Create a service
First you need to be registred on ‘Postfinance eBill service <https://www.postfinance.ch/en/business/products/accounts-receivable-solutions/e-bill-invoice-issuer.html>’ To create a service go to Accounting - Configuration - Payments - Postfinance eBill Service
Configure a customer and create his contract
The contracts specific to Postfinance e-billing are located in Accounting - Customers - eBill Postfinance Contract Create a contract for a customer with his PayerId and make sure that the contract is active by being in Open state with valid start/end dates.
Set Customer Invoice Transmission Method on the customer to Postfinance.
Usage
To use this module, you need to:
Configure the service, customers and contracts as described in the CONFIGURATION section.
Create an invoice for a customer with an open Postfinance contract.
Validate the invoice, and click the Send eBill button.
Known issues / Roadmap
ToDo
Add option to import the contract subscription (csv)
Add the download of this csv from web service, but what is the endpoint ?
Nice to have
Add a link to the failed job in the chatter message.
Add an action on partner to create a ebilling contract.
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
Thierry Ducrest <thierry.ducrest@camptocamp.com>
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.
Current maintainer:
This module is part of the OCA/l10n-switzerland 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 odoo14-addon-ebill-postfinance 14.0.1.1.1.dev4
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 |
|---|---|---|---|---|
| odoo14_addon_ebill_postfinance-14.0.1.1.1.dev4-py3-none-any.whl | Python 3 | none | any | Details for odoo14_addon_ebill_postfinance-14.0.1.1.1.dev4-py3-none-any.whl |
Release files / odoo14_addon_ebill_postfinance-14.0.1.1.1.dev4-py3-none-any.whl
| Download URL | odoo14_addon_ebill_postfinance-14.0.1.1.1.dev4-py3-none-any.whl |
|---|---|
| Size | 196.9 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
54f34c3c73ce6f6c6c11be3c0528f5a018654f88625682da1343e5c97d8d2963
|
|
BLAKE2b-256 checksum How to use checksums |
50f75270bfc19cd7c749236ee27d7efbfabd7727f23dc27a9887130cac808aa2
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/5.1.1 CPython/3.12.3
|
Security for odoo14-addon-ebill-postfinance 14.0.1.1.1.dev4
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.
