eBill Paynet
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.
Create a service
In the standart are 2 service provider (Paynet, Invocloud -> stand 2023 both down) deposited. You can expand the provider by installing an expansion from another provider like io_market. To create a service you need to be registred with the provider. Then the configuration of the service can be done in Accounting - Configuration - Payments - Paynet Service.
- Service Provider: you can chose one of the installed provider
- Credentials are all necessary information to connect with the provider
- Under invoice you can tick the box to add the page from "Print QR-Bill" in the sending invoice (default is not added)
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.
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
Credits
Authors
- Camptocamp SA
Contributors
- Jamotion <info@jamotion.ch>
- Thierry Ducrest <thierry.ducrest@camptocamp.com>
- Trobz:
- Dung Tran <dungtd@trobz.com>
Other credits
The migration of this module from 13.0 to 14.0 as financially supported by Camptocamp
To Do
- Completely separate old code for the old providers, so we have a good example
- Expand the invoice part so that the user can customize the layout
- Add possiblity on the e-bill to extend all possible extension (e.g. invisible information on invoice)
Change Logs
- remodeled ebill paynet is now flexibler and is more open to expand with other providers
- Added expands qr-code data and ebill informations
- Added ebill paynet io market modul