BECLM File Format

Overview

 If you want to import your data in bulk, you must define the file format during your onboarding process. This format must then be consistent for all future imports you perform on BeCLM.

 If it changes, you must contact Support to make the necessary adjustments.

 The detailed procedure for creating a compatible file format for BeCLM can be found below.

This includes all the data fields that can be processed by our software, whether mandatory or optional, to ensure the BeCLM algorithm processes your data to a high standard. 

Detailed Procedure

Information about the expected file format:

•  Standard CSV

• Delimiter: ; (semicolon)

• Encoding: UTF-8

• The first line corresponds to the header containing the name of each column. The name of the column isn’t used in the processing; only the order defined in your configuration file matters.

•  

It is essential to:

• Strictly follow the CSV file formatting guidelines

• Ensure the unique identifier for individuals and/or legal entities are accurate

• Maintain the exact column order for every import 

Definitions:

Below is a list of headers that you can include in your CSV file format.

Failure to comply with the specified rules may result in import errors in BeCLM.

·       Unique ID:

The unique ID must remain the same between files uploaded - Otherwise, the system will consider it to be two different person and will “struck off” the risk file of the person it can no longer find and “create” a new file (to characterise manually).

·       Civility:

Accepted values: MR / MRS / SOC. The value SOC can be used to distinguish between individuals and legal entities. Alternatively, the absence of a first name may be used to identify a legal entity.

·       Nationality:

Alphanumeric – no normalization. This check is performed by comparing the submitted value against values found in control sources.

·       Date of Birth:

The date must be in format: dd/mm/yyyy

·       SIREN:

A 9-digit number – duplicates are not allowed. This value is required to retrieve data from SIREN/BODACC/RNE APIs.

File structure:

 Please see the list of available import fields below.

 Caution: The file structure (column choices and sorting) must not be changed after implementation in production. If any modifications are required, please contact our support team.