ImportReleveCarteEntreprise batch
Important
The ImportReleveCarteEntreprise batch takes into account the following formats of bank statements: BRED and BNP Paribas.
The ImportReleveCarteEntreprise batch uses files from the statements provided by your bank in order to automatically generate the corresponding expenses in Akuiteo.
When the batch is started, each line of the imported files is analyzed to create the expenses in Akuiteo:
- The employee is determined using the business card specified in the employee record sheet (see Preparing employee record sheets).
- The date and the amount of the expense are retrieved directly from the bank statements.
- For the allocation, Akuiteo checks the employee's timesheet or schedule at the date of the expense.
- If there is only one project found at this date, this project is used for the expense.
- If multiple projects are found at this date or if the project is excluded in the batch parameters, the allocation will be left empty.
- For the expense type, the setup for external expense types is used to link a Merchant Category Code (MCC) with an expense report in Akuiteo (see Setting up external expense types). If external expense types are not set up or if the expense type is excluded in the batch parameters, the expense type will be left empty.
- The Business card option is checked for the new expense.

Business cards must be specified in employee record sheets. When the batch is started, the statement line is linked to the employee using the employee's business card number.
From the employee record sheet, click on Edit > Additional parameters > Business cards to access the employee's business cards.
Reference
For more information, refer to Adding business cards.

In a bank statement file, each line is associated with a MCC code. This code indicates the merchant's activity type for each transaction.
Before starting the ImportReleveCarteEntreprise batch, external expense types must be set up so the MCC codes can be linked with the relevant expense types. That way, when a bank statement line is imported, the MCC code of the line is searched for among the external expense types set up. If the external expense type is correctly set up and is associated with an expense type, this expense type is specified in the new expense.
If the MCC codes have not been set up in external expense types or if there is no associated expense types, the expense type will be left empty for the expenses created with the batch. The recipients of the batch's logs will be warned that the MCC codes could not be linked with external expense types.
External expense types are set up from the menu General setup > Expense reports > External expenditure type.
Reference
For more information, refer to External expense types.

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 ImportReleveCarteEntreprise from the drop-down list of the Batch template field. |
Note
The code must be unique for each batch, all companies combined.
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, bank statement files are analyzed and expenses are created in Akuiteo according to the specified parameters. If an error occurs for a line, the process continues for the other lines.
The expenses created with the batch are added to the latest open expense report. If the employee does not have an open expense report, a new expense report is created automatically.

Code | Description | Type | Required |
---|---|---|---|
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 to use when answering the email sent with the logs. |
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 | Yes |
BATCH_USER
|
Login of the user who starts the batch. | String | Yes |
CODES_AFFAIRES_EXCLUS
|
Codes of the projects to be excluded when searching for the allocation. Each code must be separated by a semicolon. |
String Ex: CODE1;CODE2;CODE3 |
No |
CODES_NATURES_EXCLUS
|
Codes of the expense types to be excluded when searching for the allocation. Each code must be separated by a semicolon. |
String Ex: CODE1;CODE2;CODE3 |
No |
DEBUT_NOM_DU_FICHIER
|
Root of the name used to identify the bank statement files to be imported by the batch. |
String Ex: bank-statements |
No |
FORMAT
|
Format of the bank statement files to be imported by the batch. The following formats are available:
|
List of values | Yes |
FTP_CHEMIN
|
Path to access the FTP server's directory where the bank statement files to be imported by the batch are located. |
String Ex: employee/statements |
Yes |
FTP_CHEMIN_OK
|
Path to access the FTP or SFTP server directory where the files imported from the FTP_CHEMIN will be moved. |
String Ex: employee/statements/processed |
Yes |
FTP_MODE
|
Method to connect to the FTP or SFTP server. Important Only the FTP or SFTP connection methods can be used. |
String Ex:FTP or SFTP |
No |
FTP_PASSWORD
|
Password to connect to the FTP or SFTP server . This password must be linked to the specified FTP_USER . |
String | No |
FTP_PORT
|
FTP or SFTP server port. | Number | Yes |
FTP_SERVEUR
|
Address of the FTP or SFTP server where the bank statement files to be imported by the batch are located. |
String Ex:ftp.akuiteo.com |
Yes |
FTP_USER
|
Login to connect to the FTP or SFTP server. | String | No |
SFTP_SSH_KEYSTORE
|
Important This parameter is required if SFTP is specified for Path to access the Keystore file that is protected by a password and that contains keys and certificates. |
String | No |
SFTP_SSH_KEYSTORE_PASSWORD
|
Important This parameter is required if SFTP is specified for Password to access the Keystore file. |
String | No |

The expenses created with the batch are marked as "paid with a business card" and are therefore considered as already refunded to the employee.
The NDF_CARTE_SOCIETE management rule must be active to differentiate the expenses to be paid from the ones that have already been paid.
This management rule enables to create two invoices for the supplier employee when the expense reports are billed:
- An invoice for the expenses "paid with a business card", that is already paid.
- An invoice for the other expenses to be paid.