<h1 class="title">L10n FR Chorus</h1> <p><a class="reference external" href="https://odoo-community.org/page/development-status"><img alt="Beta" src="https://img.shields.io/badge/maturity-Beta-yellow.png" /></a> <a class="reference external" href="http://www.gnu.org/licenses/agpl-3.0-standalone.html"><img alt="License: AGPL-3" src="https://img.shields.io/badge/licence-AGPL--3-blue.png" /></a> <a class="reference external" href="https://github.com/OCA/l10n-france/tree/15.0/l10n_fr_chorus_account"><img alt="OCA/l10n-france" src="https://img.shields.io/badge/github-OCA%2Fl10n--france-lightgray.png?logo=github" /></a> <a class="reference external" href="https://translation.odoo-community.org/projects/l10n-france-15-0/l10n-france-15-0-l10n_fr_chorus_account"><img alt="Translate me on Weblate" src="https://img.shields.io/badge/weblate-Translate%20me-F47D42.png" /></a> <a class="reference external" href="https://runbot.odoo-community.org/runbot/121/15.0"><img alt="Try me on Runbot" src="https://img.shields.io/badge/runbot-Try%20me-875A7B.png" /></a></p> <p>This is the base module for the support of <a class="reference external" href="https://chorus-pro.gouv.fr/">Chorus Pro</a>, the electronic invoicing plateform of the French administration. Chorus Pro specifications are available on <a class="reference external" href="https://communaute-chorus-pro.finances.gouv.fr/">Chorus Pro Community website</a>. 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 <a class="reference external" href="https://www.economie.gouv.fr/entreprises/marches-publics-facture-electronique">the dedicated page</a> on the website of the Ministry of Economic Affairs.</p> <p>To be able to generate an electronic invoice for Chorus, you need the module <em>l10n_fr_chorus_factur-x</em> or <em>l10n_fr_chorus_ubl</em>.</p> <p><strong>Table of contents</strong></p> <div class="contents local topic" id="contents"> <ul class="simple"> <li><a class="reference internal" href="#configuration" id="id1">Configuration</a></li> <li><a class="reference internal" href="#usage" id="id2">Usage</a></li> <li><a class="reference internal" href="#bug-tracker" id="id3">Bug Tracker</a></li> <li><a class="reference internal" href="#credits" id="id4">Credits</a><ul> <li><a class="reference internal" href="#authors" id="id5">Authors</a></li> <li><a class="reference internal" href="#contributors" id="id6">Contributors</a></li> <li><a class="reference internal" href="#maintainers" id="id7">Maintainers</a></li> </ul> </li> </ul> </div> <a name="configuration"></a> <h2><a class="toc-backref" href="#id1">Configuration</a></h2> <p>On the customers that you invoice via Chorus, you must:</p> <ul class="simple"> <li>enter their <em>SIRET</em> (<em>Accounting</em> tab),</li> <li>select <em>Chorus</em> as <em>Customer Invoice Transmission Method</em> (<em>Accounting</em> tab),</li> <li>select the <em>Info Required for Chorus</em> to the value that you obtained from Chorus (menu <em>Rechercher Structure Publique</em>),</li> <li>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 <em>Chorus Service</em> and make sure that this contact is used as <em>Customer</em> on the invoice.</li> </ul> <p>If you want to use the Chorus API to easily send invoices to Chorus from Odoo, you must:</p> <ul class="simple"> <li>edit the Odoo server configuration file and add two keys <em>chorus_api_oauth_id</em> and <em>chorus_api_oauth_secret</em> that contain your Oauth client ID and client secret obtained via <a class="reference external" href="https://developer.aife.economie.gouv.fr/">PISTE</a>. Don't forget to restart the Odoo server after the update of its configuration file.</li> <li>in the menu <em>Accounting &gt; Configuration &gt; Settings</em>, in the section <em>Chorus API</em>, enable the option <em>Use Chorus API</em>, which will add all users to the <em>Chorus API</em> group. Then set the additional configuration parameters for Chorus API that will be prompted on the settings page.</li> </ul> <p>In the menu <em>Settings &gt; Technical &gt; Automation &gt; Scheduled Actions</em>, you should also activate the 3 scheduled actions related to Chorus Pro.</p> <a name="usage"></a> <h2><a class="toc-backref" href="#id2">Usage</a></h2> <p>On the customer form view of a French public administration, in the <em>Accounting</em> tab, set the <em>Customer Invoice Transmission Method</em> to <em>Chorus Pro</em>. You will then see a new section <em>Chorus Pro</em>. In this section, you should set the <em>Info required for Chorus</em> and, if the administration is <em>Service required</em>, you must create the Chorus services.</p> <p>If you enabled the Chorus API, just click on the button <em>Update Info Required for Chorus</em> and it will set the field <em>Info required for Chorus</em> and download all the Chorus services of that administration.</p> <p>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 <em>Info required for Chorus</em> and check that this invoice has an order reference or/and a Chorus service if required for that customer.</p> <p>If you enabled the Chorus API, you should see a button <em>Send to Chorus</em> on validated customer invoices and refunds that have a transmission method set to <em>Chorus Pro</em>. You can also select several customer invoices/refunds and do <em>Action &gt; Send to Chorus Pro</em>.</p> <p>Sending an invoice via the Chorus API creates a Chorus Flow, cf menu <em>Accounting &gt; Configuration &gt; Chorus Pro &gt; Chorus Flows</em> (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 <em>Update Flow Status</em> to refresh the status of the flow, until it reaches the status <em>IN_INTEGRE</em>. Then, click on the button <em>Get Chorus Invoice Identifiers</em> 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 <em>Update Chorus Invoice Status</em> to refresh the <em>Chorus Invoice Status</em>. All these actions to refresh the status of the Chorus flows and of the invoice are automated via the <em>Scheduled Action</em> named <em>Chorus Pro Invoice Status Update</em>. So, if that scheduled action is active, you should not have to manually perform the actions described in this paragraph.</p> <p>In the list view of customer invoices, you can group by <em>Chorus Status</em>: 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.</p> <a name="bug-tracker"></a> <h2><a class="toc-backref" href="#id3">Bug Tracker</a></h2> <p>Bugs are tracked on <a class="reference external" href="https://github.com/OCA/l10n-france/issues">GitHub Issues</a>. 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 <a class="reference external" href="https://github.com/OCA/l10n-france/issues/new?body=module:%20l10n_fr_chorus_account%0Aversion:%2015.0%0A%0A**Steps%20to%20reproduce**%0A-%20...%0A%0A**Current%20behavior**%0A%0A**Expected%20behavior**">feedback</a>.</p> <p>Do not contact contributors directly about support or help with technical issues.</p> <a name="credits"></a> <h2><a class="toc-backref" href="#id4">Credits</a></h2> <a name="authors"></a> <h3><a class="toc-backref" href="#id5">Authors</a></h3> <ul class="simple"> <li>Akretion</li> </ul> <a name="contributors"></a> <h3><a class="toc-backref" href="#id6">Contributors</a></h3> <ul class="simple"> <li>Alexis de Lattre &lt;<a class="reference external" href="mailto:alexis.delattre&#64;akretion.com">alexis.delattre&#64;akretion.com</a>&gt;</li> </ul> <a name="maintainers"></a> <h3><a class="toc-backref" href="#id7">Maintainers</a></h3> <p>This module is maintained by the OCA.</p> <a class="reference external image-reference" href="https://odoo-community.org"><img alt="Odoo Community Association" src="https://odoo-community.org/logo.png" /></a> <p>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.</p> <p>Current <a class="reference external" href="https://odoo-community.org/page/maintainer-role">maintainer</a>:</p> <p><a class="reference external" href="https://github.com/alexis-via"><img alt="alexis-via" src="https://github.com/alexis-via.png?size=40px" /></a></p> <p>This module is part of the <a class="reference external" href="https://github.com/OCA/l10n-france/tree/15.0/l10n_fr_chorus_account">OCA/l10n-france</a> project on GitHub.</p> <p>You are welcome to contribute. To learn how please visit <a class="reference external" href="https://odoo-community.org/page/Contribute">https://odoo-community.org/page/Contribute</a>.</p>