[18.0][MIG] Chorus modules

l10n_fr_chorus_account/README.rst

@@ -0,0 +1,172 @@
+==============
+L10n FR Chorus
+==============
+
+.. 
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! This file is generated by oca-gen-addon-readme !!
+   !! changes will be overwritten.                   !!
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+   !! source digest: sha256:233370d31ac780568aec5247004616ad883ec16eec023fe29f53a7adc85ccd78
+   !!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
+
+.. |badge1| image:: https://img.shields.io/badge/maturity-Beta-yellow.png
+    :target: https://odoo-community.org/page/development-status
+    :alt: Beta
+.. |badge2| image:: https://img.shields.io/badge/licence-AGPL--3-blue.png
+    :target: http://www.gnu.org/licenses/agpl-3.0-standalone.html
+    :alt: License: AGPL-3
+.. |badge3| image:: https://img.shields.io/badge/github-OCA%2Fl10n--france-lightgray.png?logo=github
+    :target: https://github.com/OCA/l10n-france/tree/18.0/l10n_fr_chorus_account
+    :alt: OCA/l10n-france
+.. |badge4| image:: https://img.shields.io/badge/weblate-Translate%20me-F47D42.png
+    :target: https://translation.odoo-community.org/projects/l10n-france-18-0/l10n-france-18-0-l10n_fr_chorus_account
+    :alt: Translate me on Weblate
+.. |badge5| image:: https://img.shields.io/badge/runboat-Try%20me-875A7B.png
+    :target: https://runboat.odoo-community.org/builds?repo=OCA/l10n-france&target_branch=18.0
+    :alt: Try me on Runboat
+
+|badge1| |badge2| |badge3| |badge4| |badge5|
+
+This is the base module for the support of `Chorus
+Pro <https://chorus-pro.gouv.fr/>`__, the electronic invoicing plateform
+of the French administration. Chorus Pro specifications are available on
+`Chorus Pro Community
+website <https://communaute-chorus-pro.finances.gouv.fr/>`__. All the
+suppliers of the French administration must send their invoices through
+Chorus Pro. To know more about Chorus and the obligation to send
+electronic invoices to the French administration, read `the dedicated
+page <https://www.economie.gouv.fr/entreprises/marches-publics-facture-electronique>`__
+on the website of the Ministry of Economic Affairs.
+
+To be able to generate an electronic invoice for Chorus, you need the
+module *l10n_fr_chorus_factur-x* or *l10n_fr_chorus_ubl*.
+
+**Table of contents**
+
+.. contents::
+   :local:
+
+Configuration
+=============
+
+On the customers that you invoice via Chorus, you must:
+
+-  enter their *SIRET* (*Accounting* tab),
+-  select *Chorus* as *Customer Invoice Transmission Method*
+   (*Accounting* tab),
+-  select the *Info Required for Chorus* to the value that you obtained
+   from Chorus (menu *Rechercher Structure Publique*),
+-  if the service is a required information for that customer in Chorus,
+   you must create the Chorus service and then create an invoicing
+   contact and select the related *Chorus Service* and make sure that
+   this contact is used as *Customer* on the invoice.
+
+If you want to use the Chorus API to easily send invoices to Chorus from
+Odoo, you must:
+
+-  edit the Odoo server configuration file and add two keys
+   *chorus_api_oauth_id* and *chorus_api_oauth_secret* that contain your
+   Oauth client ID and client secret obtained via
+   `PISTE <https://piste.gouv.fr/>`__. Don't forget to restart the Odoo
+   server after the update of its configuration file.
+-  in the menu *Accounting > Configuration > Settings*, in the section
+   *Chorus API*, enable the option *Use Chorus API*, which will add all
+   users to the *Chorus API* group. Then set the additional
+   configuration parameters for Chorus API that will be prompted on the
+   settings page.
+
+In the menu *Settings > Technical > Automation > Scheduled Actions*, you
+should also activate the 3 scheduled actions related to Chorus Pro.
+
+Usage
+=====
+
+On the customer form view of a French public administration, in the
+*Accounting* tab, set the *Customer Invoice Transmission Method* to
+*Chorus Pro*. You will then see a new section *Chorus Pro*. In this
+section, you should set the *Info required for Chorus* and, if the
+administration is *Service required*, you must create the Chorus
+services.
+
+If you enabled the Chorus API, just click on the button *Update Info
+Required for Chorus* and it will set the field *Info required for
+Chorus* and download all the Chorus services of that administration.
+
+When you try to validate a customer invoice/refund for a customer for
+which you send the invoices via Chorus Pro, it will check the value of
+the field *Info required for Chorus* and check that this invoice has an
+order reference or/and a Chorus service if required for that customer.
+
+If you enabled the Chorus API, you should see a button *Send to Chorus*
+on validated customer invoices and refunds that have a transmission
+method set to *Chorus Pro*. You can also select several customer
+invoices/refunds and do *Action > Send to Chorus Pro*.
+
+Sending an invoice via the Chorus API creates a Chorus Flow, cf menu
+*Accounting > Configuration > Chorus Pro > Chorus Flows* (it is not
+really a configuration thing... so we could argue that it should not be
+in the configuration menu !). You can click on the button *Update Flow
+Status* to refresh the status of the flow, until it reaches the status
+*IN_INTEGRE*. Then, click on the button *Get Chorus Invoice Identifiers*
+to get the technical identifiers of the invoice in Chorus (and write it
+on the invoice in Odoo) and get the status of the invoice in Chorus.
+Eventually, on the invoice, you can click on the button *Update Chorus
+Invoice Status* to refresh the *Chorus Invoice Status*. All these
+actions to refresh the status of the Chorus flows and of the invoice are
+automated via the *Scheduled Action* named *Chorus Pro Invoice Status
+Update*. So, if that scheduled action is active, you should not have to
+manually perform the actions described in this paragraph.
+
+In the list view of customer invoices, you can group by *Chorus Status*:
+that way, you get on overview of the status of all the invoices you sent
+to Chorus Pro, and you can easily spot if an invoice has been refused
+for example.
+
+Bug Tracker
+===========
+
+Bugs are tracked on `GitHub Issues <https://github.com/OCA/l10n-france/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 <https://github.com/OCA/l10n-france/issues/new?body=module:%20l10n_fr_chorus_account%0Aversion:%2018.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**>`_.
+
+Do not contact contributors directly about support or help with technical issues.
+
+Credits
+=======
+
+Authors
+-------
+
+* Akretion
+
+Contributors
+------------
+
+-  Alexis de Lattre <alexis.delattre@akretion.com>
+
+Maintainers
+-----------
+
+This module is maintained by the OCA.
+
+.. image:: https://odoo-community.org/logo.png
+   :alt: Odoo Community Association
+   :target: https://odoo-community.org
+
+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.
+
+.. |maintainer-alexis-via| image:: https://github.com/alexis-via.png?size=40px
+    :target: https://github.com/alexis-via
+    :alt: alexis-via
+
+Current `maintainer <https://odoo-community.org/page/maintainer-role>`__:
+
+|maintainer-alexis-via| 
+
+This module is part of the `OCA/l10n-france <https://github.com/OCA/l10n-france/tree/18.0/l10n_fr_chorus_account>`_ project on GitHub.
+
+You are welcome to contribute. To learn how please visit https://odoo-community.org/page/Contribute.

l10n_fr_chorus_account/__init__.py

@@ -0,0 +1,2 @@
+from . import models
+from . import wizard

l10n_fr_chorus_account/__manifest__.py

@@ -0,0 +1,34 @@
+# Copyright 2017-2022 Akretion France (http://www.akretion.com/)
+# @author: Alexis de Lattre <alexis.delattre@akretion.com>
+# License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+
+{
+    "name": "L10n FR Chorus",
+    "summary": "Generate Chorus-compliant e-invoices and transmit them "
+    "via the Chorus API",
+    "version": "18.0.1.0.0",
+    "category": "French Localization",
+    "author": "Akretion,Odoo Community Association (OCA)",
+    "maintainers": ["alexis-via"],
+    "website": "https://github.com/OCA/l10n-france",
+    "license": "AGPL-3",
+    "depends": [
+        "l10n_fr_siret_account",
+        "server_environment",
+    ],
+    "external_dependencies": {"python": ["requests_oauthlib"]},
+    "data": [
+        "security/group.xml",
+        "security/ir.model.access.csv",
+        "data/ir_cron.xml",
+        "data/mail_template.xml",
+        "wizard/account_invoice_chorus_send_view.xml",
+        "views/chorus_flow.xml",
+        "views/chorus_partner_service.xml",
+        "views/res_partner.xml",
+        "views/res_config_settings.xml",
+        "views/account_move.xml",
+    ],
+    "demo": ["demo/demo.xml"],
+    "installable": True,
+}

l10n_fr_chorus_account/data/ir_cron.xml

@@ -0,0 +1,38 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!--
+  Copyright 2017-2021 Akretion France (http://www.akretion.com/)
+  @author Alexis de Lattre <alexis.delattre@akretion.com>
+  License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+-->
+<odoo noupdate="1">
+    <record id="chorus_flow_cron" model="ir.cron">
+        <field name="name">Chorus Pro Invoice Status Update</field>
+        <field name="active" eval="False" />
+        <field name="user_id" ref="base.user_root" />
+        <field name="interval_number">1</field>
+        <field name="interval_type">days</field>
+        <field name="model_id" ref="model_chorus_flow" />
+        <field name="state">code</field>
+        <field name="code">model.chorus_cron()</field>
+    </record>
+    <record id="chorus_partner_cron" model="ir.cron">
+        <field name="name">Chorus Pro Partner Update</field>
+        <field name="active" eval="False" />
+        <field name="user_id" ref="base.user_root" />
+        <field name="interval_number">1</field>
+        <field name="interval_type">weeks</field>
+        <field name="model_id" ref="base.model_res_partner" />
+        <field name="state">code</field>
+        <field name="code">model.chorus_cron()</field>
+    </record>
+    <record id="chorus_api_expiry_reminder_cron" model="ir.cron">
+        <field name="name">Chorus Pro API Expiry Reminder Email</field>
+        <field name="active" eval="False" />
+        <field name="user_id" ref="base.user_root" />
+        <field name="interval_number">1</field>
+        <field name="interval_type">days</field>
+        <field name="model_id" ref="base.model_res_company" />
+        <field name="state">code</field>
+        <field name="code">model.chorus_api_expiry_reminder_cron()</field>
+    </record>
+</odoo>

l10n_fr_chorus_account/data/mail_template.xml

@@ -0,0 +1,36 @@
+<?xml version="1.0" encoding="utf-8" ?>
+<!--
+  Copyright 2018-2021 Akretion France (http://www.akretion.com/)
+  @author Alexis de Lattre <alexis.delattre@akretion.com>
+  License AGPL-3.0 or later (http://www.gnu.org/licenses/agpl).
+-->
+<odoo noupdate="1">
+    <record id="chorus_api_expiry_reminder_mail_template" model="mail.template">
+        <field name="name">Chorus API Expiry Reminder</field>
+        <field name="model_id" ref="base.model_res_company" />
+        <field name="auto_delete" eval="False" />
+        <field name="lang">{{ object.partner_id.lang }}</field>
+        <field name="email_from">{{ object.email or 'odoo@example.com' }}</field>
+        <field name="email_to">{{object.chorus_expiry_remind_user_list() }}</field>
+        <field
+            name="subject"
+        >[{{ object.name }}] Action needed to continue to use the Chorus Pro API</field>
+        <field name="body_html" type="html">
+            <p>The Odoo server of company <em
+                t-out="object.name"
+            >My company</em> is configured to access the Chorus Pro API. Accessing the Chorus Pro API requires a technical user login and password. The password of the technical user has an expiry date. The password of the technical user expires on <strong
+                t-out="format_date(object.fr_chorus_pwd_expiry_date) or ''"
+            >08/08/2021</strong> (in <strong
+                t-out="ctx.get('pwd_days')"
+            >7</strong> days).</p>
+
+            <p
+            >In order to continue to access the Chorus Pro API without problems, you should connect to Chorus Pro, generate a new password for the technical user and copy it in Odoo on the accounting configuration page.</p>
+
+            <p>
+-- <br />
+Automatic e-mail sent by Odoo.
+</p>
+        </field>
+    </record>
+</odoo>