This module implements the exchange of electronic invoices with the SIXT Paynet infrastructure used in Switzerland.
It allows the automatic sending of invoice to customer that have registered with the service.
Table of contents
Installation
This module depends on base_ebill_payment_contract which is located on OCA/account_invoicing, so this repository must also be present on the system. This base_ebill_payment_contract module depends on account_invoice_transmit_method which will also be installed.
Configuration
Create a service
To create a service you need to be registred with SIXT Paynet service. Then the configuration of the service can be done in Accounting - Configuration - Payments - Paynet Service
Configure the customers
A customer that wants to receive his invoices through Paynet will also need to register with the service. In Odoo to enable the sending of invoices for a specific customer through Paynet, the transmit method must be set accordingly for that customer. This is done on the customer form in the tab Sales & Purchases section Sales.
Configure the contracts
The contracts specific to e-billing are located in Accounting - Customers - eBill Payment Contract Although the Paynet system allows for automatic exchange of contract registration and status changes, this automation is not yet implemented. To be active a contract needs to be in the state Open and it’s start/end dates to be valid.
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 Paynet contract.
Validate the invoice, and it will be send to the service.
Known issues / Roadmap
To Do
The B2C invoice generated is only a draft and not tested, yet.
Invoice in currency other than CHF will not be generated correctly.
Implementation of the automatic registration of contracts, is not implemented and probably not supported by the DWS
Improvements
On the contract view the list of messages for that contract could be visible.
When an error is returned by the service it should be clearer where it is located in the payload send.
In the chatter add a link to the job when it fails
Refactoring
The dependence on delivery module could be extracted in a glue module. For v14 or v15 consider refactoring on top of EDI framework
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.
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.
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.
Metadata
Release files for odoo13-addon-ebill-paynet 13.0.1.1.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 |
|---|---|---|---|---|
| odoo13_addon_ebill_paynet-13.0.1.1.0-py3-none-any.whl | Python 3 | none | any | Details for odoo13_addon_ebill_paynet-13.0.1.1.0-py3-none-any.whl |
Release files / odoo13_addon_ebill_paynet-13.0.1.1.0-py3-none-any.whl
| Download URL | odoo13_addon_ebill_paynet-13.0.1.1.0-py3-none-any.whl |
|---|---|
| Size | 80.2 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
07b8b1f5a996eb22c7515bb0a6e39a66033bb31c80e3245b9eebb7270071e061
|
|
BLAKE2b-256 checksum How to use checksums |
b26a6fcc991308d2b4a15810658f98800f2e88dba80f7dc7cc915ce900e46eca
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/4.0.0 CPython/3.8.5
|
Security for odoo13-addon-ebill-paynet 13.0.1.1.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.