Setting up the dematerialization of invoices
Activating the relevant management rules
To be able to dematerialize invoices, you must activate the CHORUS application control to display the CHORUS tabs in sites and sales management objects. This control also displays dematerialization information in the modification screen of the billing address from a sales order.
The following items are optional:
- Enable the
CHORUS_ORIGINAL_OBILmanagement rule to make the main attachment required in order to generate the XML file. - Enable the
CHORUS_BA_COMPLEMapplication control to display the following tags in the XML file: CopyIndicator, Note (Contact) and StandardItemIdentification.
Creating a dematerialization code
| 1 | In the setup window, go to General setup > Sales > Dematerialization codes. |
| 2 | From the search results, click on  in the action bar. |
| 3 | In the Dematerialization setup screen, fill in the following fields (only the fields required to create a new dematerialization code): |
| Field | Description |
|---|---|
| Code | Enter the CHORUS code. |
| Label | Enter a label for the dematerialization code to identify it. |
| Storage directory |
Select Local directory in order to store CHORUS invoices in a local directory. In the Storage directory field, specify the directory in which the XML files of the CHORUS invoices will be stored. |
| 4 | Save the dematerialization code. |
This code can be used to generate dematerialized invoices.
Transferring dematerialized invoices automatically to CHORUS PRO
Akuiteo interfaces with CHORUS PRO in order to automatically transfer dematerialized invoices from the Desktop Application to the CHORUS PRO portal. This way, the user does not have to manually transfer dematerialized invoices to the CHORUS PRO portal.
Important
In order to interface with CHORUS PRO, please contact your Akuiteo project manager.
Adding the Certigna certificate to the Tomcat server
The Java Runtime Environment (JRE) has a configuration file (keystore) that includes root certificates from the different renowned certification authorities. When a connection is established to another system using https, this list of certificates is used to validate the secured connection.
Some certification authorities are not included in the file provided by default with the JRE, so they must be added manually. To interface with CHORUS PRO, the Certigna certificate must be added to certify the CHORUS connections.
Note
For SaaS customers, this certificate is added by Akuiteo.
Identifying the JRE's location
| 1 | Connect to the server that hosts the Akuiteo environment. |
| 2 | Launch the Tomcat Manager for that environment. |
| 3 | From the Java tab, take note of the location of the JRE used by Tomcat. |
Retrieving the Certigna's Racine certificate
| 1 | Go to the Certigna's website: https://www.certigna.com/autorite-crl. |
| 2 | Download the Certigna's authority certificate: certigna.der. |
Importing the certificate into the JRE's keystore
| 1 | Launch the command prompt as an administrator. |
| 2 | Launch the following command: |
"[JRE_LOCATION]\bin\keytool.exe" -import -alias "certigna" -keystore "[JRE_LOCATION]\lib\security\cacerts" -trustcacerts -file "[CERTIFICATE_LOCATION]\certigna.der" -storepass changeit
In this command, you must replace:
- [JRE_LOCATION] with the location of the JRE used by Tomcat
- [CERTIFICATE_LOCATION] with the location of the certigna.der certificate downloaded.
Example
"C:\Program Files\Java\jdk1.8.0_22\jre\bin\keytool.exe" -import -alias "certigna" -keystore "C:\Program Files\Java\jdk1.8.0_22\jre\lib\security\cacerts" -trustcacerts -file "C:\Users\XXX\Documents\certigna.der" -storepass changeit
| 3 | Restart the Tomcat server of the targeted Akuiteo environment to take into account the new certificate. |
Setting up the Administration console
The automatic transfer of dematerialized invoices is set up from the Administration Console, from the menu Third-party interfaces > Dematerialization.
Notes
For SaaS customers, the setup of the Administration console is done by Akuiteo.
Reference
The login information to CHORUS PRO must be specified from the setup of the Desktop Application to enable you to use different CHORUS PRO accounts depending on each company. For more information, refer to Setting up the login information per company.
| 1 | Fill in the following fields to configure the connection to CHORUS PRO: |
| Field | Description |
|---|---|
| Chorus Active | Check this box to activate the connection to CHORUS PRO. |
| Chorus Authentication URL |
Specify the URL to authenticate to CHORUS PRO:
|
| URL |
Specify the URL to connect to CHORUS PRO:
|
| 2 | Fill in the following fields to configure the interface between Akuiteo and CHORUS PRO: |
| Field | Description |
|---|---|
| Akuiteo user | Specify the login of the Akuiteo's technical user. |
| Akuiteo user's password | Specify the password associated with the Akuiteo login. |
| Akuiteo user's company code | Specify the code of the company used for connection. |
| Number of successive test runs in case of an error |
The number of successive test runs enables to specify, in case of an error when transferring dematerialized invoices, the number of times that Akuiteo will re-run the transfer. By default, Akuiteo performs 3 successive test runs in case of an error. |
| Time period in seconds between two successive test runs |
The time period between two successive test runs enables to specify, in seconds, the waiting period before another transfer is attempted in case of an error. By default, Akuiteo waits 10 seconds between two successive test runs |
| Maximum number of calls to Chorus per second |
Specify a maximum number of simultaneous calls to CHORUS PRO per second. By default, there is a maximum of 20 calls per second. For a test environment, the number must be set on maximum 1 call per second. |
Note
The CHORUS PRO portal has quotas for transferring dematerialized invoices:
- On the test environment: 5 queries per second with a maximum of 50,000 queries per day
- On the production environment: 20 queries per second with a maximum of 1 million queries per day
When these quotas are reached, the invoices can no longer be transferred. You should adapt the values in the Number of successive test runs in case of an error and Time period in seconds between two successive test runs fields if you regularly have errors when transferring invoices.
| 3 | Click on Save for each field that is filled in or modified to take into account the value specified. |
Setting up the PISTE APIs and the CHORUS PRO account
To interface CHORUS PRO with Akuiteo, you must have a PISTE application and connect it to your CHORUS PRO account.
Note
For a test environment, you must use the PISTE sandbox account and connect it to a CHORUS PRO qualification environment, in order to not transfer test invoices to a CHORUS production environment.
PISTE application
Each customer must set up their own PISTE application, and the following APIs must be activated:
- AIFE - Chorus Pro - Factures
- AIFE - Chorus Pro - Transverses
CHORUS PRO account
The PISTE application must be connected to the CHORUS PRO account.
Note
You can only connect one PISTE application per CHORUS PRO account. If you have already connected your CHORUS PRO account to a PISTE application, you must set up this PISTE application as indicated above.
| 1 | From the CHORUS PRO account, click on the menus EDI and API connections > Manage API connection. |
| 2 | Add a connection declaration by filling in the following information: |
| Field | Description |
|---|---|
| PISTE application name | Fill in the name of the PISTE application. |
| Status | Select Active from the drop-down list. |
| Type of use | Select User of a publisher or operator solution from the drop-down list. |
| Editor / solution | Fill in AKUITEO. |
| 3 | Validate the connection with the PISTE application. |
Setting up the login information per company
| DMF | 090175 ADMINISTRATOR SETUP CHORUS |
The specific Chorus parameters enable you to specify the login information to CHORUS PRO, and therefore to automatically transfer the dematerialized invoices generated by Akuiteo to the CHORUS PRO portal.
Reference
For more information about transferring dematerialized invoices to CHORUS PRO automatically, refer to Transferring dematerialized invoices automatically to CHORUS PRO.
The specific Chorus parameters are set up from Special parameters > Chorus.
This setup screen has several tabs: one tab for the ***** company and other tabs for each of the companies set up in Akuiteo. These different tabs enable you to use different Piste accounts depending on each user's company. Click on 
at the top right of the screen to enable the specific setup for a given company.
Important
The setup on the ***** company must not be used since each company must have a different CHORUS PRO account set up.
When dematerialized invoices are transferred to CHORUS PRO, Akuiteo checks the setup depending on each invoice's company:
- If a specific setup is enabled for the company, dematerialized invoices are automatically transferred to the CHORUS PRO portal using the specified connection parameters.
- If there is no specific setup for this company, Akuiteo uses the setup for *****.
- If the setup is not enabled, invoices are not transferred.
Click on 
at the top right of a company's tab to disable a specific setup.
Tip
To transfer the information specified on a company to another company, click on 
at the top right of the screen then select the Destination company from the help list and click on Validate. The information is emptied in the source company and is added to the destination company.
To set up the login information to CHORUS PRO, fill in the following fields from the tab of the relevant company:
| Field | Description |
|---|---|
| Piste Client ID | Specify the customer ID allowing the authentication to CHORUS PRO. This ID is retrieved from the PISTE account. |
| Piste Secret | Specify the client secret allowing the authentication to CHORUS PRO. This client secret is linked to the ID retrieved from the PISTE account. |
| Chorus Login | Specify the login from the CHORUS PRO technical account. |
| Chorus Password | Specify the password associated with the login from the CHORUS PRO technical account. |
| ID |
Specify an ID to identify the invoices transferred to CHORUS using the APIs, in order to differentiate them from the invoices transferred manually. This ID is free and is optional. |
After saving the setup screen, click on the Test button from the relevant tab to test the connection to CHORUS PRO using the saved values.
Important
The Piste Client ID and Piste Secret fields must be different between a production and a test environment.
Setting up the CheckFacturesClientChorus batch
When a dematerialized invoice is transferred automatically to CHORUS PRO, the CheckFacturesClientChorus batch enables to retrieve the CHORUS status in order to follow the progress of an invoice dematerialized from the Desktop Application. This status is stored on the invoice, in the Chorus status field of the CHORUS tab.
The status of a dematerialized invoice is no longer updated once the invoice has reached a status considered as final: A_RECYCLER or MISE_EN_PAIEMENT.
Reference
For more information about how to set up the CheckFacturesClientChorus batch, see CheckFacturesClientChorus batch.
