FacturationPrestationsDevis batch
The FacturationPrestationsDevis batch is used to automatically generate non-booked invoices from the services entered manually in the Services menu and then validated in the Manager module of the Web Portal.
This batch can also be used to manually start the automatic generation of invoices, from Management > Sales > Services billing. The parameters set up in the batch are used, except for some filters that can be specified directly in the start window by the user.
References
For more information about entering and validating services from the Web Portal, refer to the User Guide - Web Portal.
For more information about manually starting the generation of invoices, refer to Creating an invoice from services.

1 | Go to Tools > Setup, then open Batches > Batch creation and modification. |
A results screen opens to display the list of existing batches.
2 | In the results screen, click on |
3 | In the New Batch screen, fill in the batch's Code and Label, then select FacturationPrestationsDevis from the drop-down list of the Batch template field. |
4 | Specify the batch parameters. For details about these parameters, refer to Setting up the batch. |
5 | Save the batch. |
When the batch is started, the non-booked invoices are created from validated services. If there are multiple validated services linked to the same quotation, the different services lines are grouped in a single invoice.
The batch only processes the services that, from the batch's last execution date or from the status date specified in the parameters:
- are linked to a validated service quotation,
- have a validation date reached or exceeded,
- have a period end date reached or exceeded.
At the end of the process, a summary is sent by email to the employees specified in the managers fields of the batch setup. An email is also sent to the relevant project managers to let them know invoices are pending validation. If several draft invoices have been generated for the same project manager, the different invoices are grouped in a single email.

Code | Description | Type | Required |
---|---|---|---|
AFFAIRES_A_INCLURE
|
Codes of the projects to be included in the batch process. Each code must be separated by a semicolon. If no project code is specified, all projects are taken into account by the batch. Note This parameter is ignored when manually starting the batch from Management > Sales > Services billing so the user can define the desired filters. |
String Ex: PRO1;PRO2;PRO3 |
No |
BATCH_DEBUG_PARAMS
|
When the parameter is set to True, details about the batch parameters are displayed in the logs. | Boolean | No |
BATCH_LOG_CONSOLE
|
When the parameter is set to True, logs are displayed in the console. | Boolean | No |
BATCH_LOG_FILE
|
Name of the directory where the log file is saved. |
String Ex: |
No |
BATCH_LOG_ID
|
Log file ID. | String | No |
BATCH_LOG_LEVEL
|
Log level. |
String Ex: LOG;WARN |
No |
BATCH_MAIL
|
Email address of the logs' recipient in case of an error. |
String Ex: support@akuiteo.com |
Yes |
BATCH_MAIL_CC
|
Email address of the logs' cc recipient in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_CCI
|
Email address of the logs' bcc recipient in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_FROM
|
Email address of the logs' sender in case of an error. |
String Ex: support@akuiteo.com |
No |
BATCH_MAIL_REPLY_TO
|
Email address of the recipient if the email including logs in case of an error is answered. |
String Ex: support@akuiteo.com |
No |
BATCH_PWD
|
Password of the user who starts the batch. This password must be linked to the BATCH_USER specified. |
String Ex: TECH |
Yes |
BATCH_USER
|
Login of the user who starts the batch. |
String Ex: TECH |
Yes |
CLIENTS_A_EXCLURE
|
Codes of the customers to be excluded in the batch process. Each code must be separated by a semicolon. If no customer code is specified, all customers are taken into account by the batch. Note This parameter is ignored when manually starting the batch from Management > Sales > Services billing so the user can define the desired filters. |
String Ex: CUS1;CUS2;CUS3 |
No |
CLIENTS_A_INCLURE
|
Codes of the customers to be included in the batch process. Each code must be separated by a semicolon. If no customer code is specified, all customers are taken into account by the batch. Note This parameter is ignored when manually starting the batch from Management > Sales > Services billing so the user can define the desired filters. |
String Ex: CUS1;CUS2;CUS3 |
No |
DATE_SITUATION
|
Status date of the invoices generated during the batch process. By default, the batch's execution date is used. The batch only processes services with a date that is before or the same as the status date. |
Date Ex: 01/01/2022 |
No |
DIVISIONS_A_INCLURE
|
Codes of the divisions to be included in the batch process. Each code must be separated by a semicolon. If no division code is specified, all divisions are taken into account by the batch. Note This parameter is ignored when manually starting the batch from Management > Sales > Services billing so the user can define the desired filters. |
String Ex: DIV1;DIV2;DIV3 |
No |
ETABLISSEMENTS_A_EXCLURE
|
Codes of the entities to be included in the batch process. Each code must be separated by a semicolon. If no entity code is specified, all entities are taken into account by the batch. Note This parameter is ignored when manually starting the batch from Management > Sales > Services billing so the user can define the desired filters. |
String Ex: ENT1;ENT2;ENT3 |
No |
MAIL_RESPONSABLE
|
At the end of the process, a summary is sent by email to the employees specified in the managers fields of this parameter. The following codes can be used, separated by a semicolon: RESP_COM_AFF ; RESP_PRO ; RESP_FIN ; RESP_AFF ; RESP_COM_CLI ; RESP_COMPTE_CLI. An excel file is attached to this email and lists all the draft invoices generated by the batch. |
String Ex: RESP_COM_AFF;RESP_COMPTE_CLI |
No |
SOCIETES_A_INCLURE
|
Codes of the companies to be included in the batch process. Each code must be separated by a semicolon. If no company code is specified, all companies are taken into account by the batch. |
String Ex: COM1;COM2;COM3 |
No |