Mehdi Bendali Hacine
b3a77f4346
The ZATCA edi has an onboarding process which happens per journal. A private key is generated for the company and with the data from the company and journal a CSR is made to get a certificate to sign the invoices. In that process that contains multiple steps (see account_journal.py), we also have to send the compliance files which are some example (simplified or not) invoices/debit and credit notes. We have a separate folder with those files and also use them in the tests. For the onboarding, they still need to be signed however. For the sending of the customer invoices themselves, UBL 2.1 is used, but with ZATCA style adaptations. That is why we inherit from that class to be able to add those specific adaptations. This UBL needs to be signed XadeS and in this case we need to do the hash with the sign information present but with empty tags. For ZATCA invoices, as is the case with Ticketbai, the previous hash is needed for the next invoice and is stored per journal. (so we have a chain of hashes) Tests written by Simon (smdc) closes odoo/odoo#126353 X-original-commit: caf6b0f2e09e7175221894cbb6d22bd6306c4e53 Signed-off-by: Josse Colpaert <jco@odoo.com>
Odoo
Odoo is a suite of web based open source business apps.
The main Odoo Apps include an Open Source CRM, Website Builder, eCommerce, Warehouse Management, Project Management, Billing & Accounting, Point of Sale, Human Resources, Marketing, Manufacturing, ...
Odoo Apps can be used as stand-alone applications, but they also integrate seamlessly so you get a full-featured Open Source ERP when you install several Apps.
Getting started with Odoo
For a standard installation please follow the Setup instructions from the documentation.
To learn the software, we recommend the Odoo eLearning, or Scale-up, the business game. Developers can start with the developer tutorials