General Cloud Integration Requirements
This article describes the integration requirements between source system and Clausion system. The aim of the article is to define the general technical requirements and frame for the integrations to be built to connect with Clausion system. More precise integration data content will be always planned and defined in the customer specific integration planning meeting.
Integrations to Clausion (Source system > Clausion)
This chapter describes data transfer process as well as data content and format requirements for inbound integrations to Clausion.
Data transfer process
Typically the need for data transfer from source system to Clausion is to transfer figures from certain time period to Clausion. Source system is usually accounting or ERP system. Time period for the transferred data can be for example a month or a year. The data purpose and scope measured by the number of rows will finally define, what is the time period for the data to be transferred to Clausion.
Inbound integration to Clausion can be done by data file extracted from the source system.
To be noted with the transfer file integrations: in case the integration executions need to be automated/scheduled, the source system has to provide the transfer file automatically/scheduled to a data directory, from which it can be read into Clausion.
Data content needed for the integration
File format for transfer file is .csv file with column separator "|" or ";".
The column order of the transfer file is irrelevant, as long as the decided order will remain unchanged. When transferring balance or voucher data, the data content requirements are as described below:
BALANCE AND P&L DATA FIELDS | ||
|---|---|---|
Field name (for example) |
Field description |
Mandatory Y/N |
YEAR |
Year for the data row |
YES |
MONTH |
Month for the data row |
YES |
ACCOUNT |
Account number in the source system |
YES |
AMOUNT |
Figures can be with or without plus and minus sign. Thousand separator is not needed. Decimal separator must be comma or full stop. |
YES |
DIM00 |
DIM00 code. Usually cost center or organisation unit code in the source system. |
YES |
DIM01 |
DIM01 value, if the dimension is in use |
NO |
DIM02 |
DIM02 value, if the dimension is in use |
NO |
DIM03 |
DIM03 value, if the dimension is in use |
NO |
DIM04 |
DIM04 value, if the dimension is in use |
NO |
DIM05 |
DIM05 value, if the dimension is in use |
NO |
DIM06 |
DIM06 value, if the dimension is in use |
NO |
DIM07 |
DIM07 value, if the dimension is in use |
NO |
DIM08 |
DIM08 value, if the dimension is in use |
NO |
DIM09 |
DIM09 value, if the dimension is in use |
NO |
COUNTERPART |
Counterunit's cost center/company code in the source system for eliminating internal transactions. This can be numerical only, or a code containing letters. This is needed in Clausion for internal transactions, if there is a need to eliminate them in the integration phase. |
NO |
| COMPANY | Company identifier. | YES |
In case customer has Transparent Reporting (TR) functionality in use in Clausion, the following sample data/columns can be imported into Clausion voucher data level for enabling drilling down to voucher data:
VOUCHER DATA FIELDS | ||
|---|---|---|
Field name (for example) |
Field description |
Mandatory Y/N |
VOUCHERNO |
Voucher number |
NO |
VOUCHERSERIE |
Voucher type/series |
NO |
VOUCHERDATE |
Voucher date |
NO |
SUPPLIER |
Supplier |
NO |
COMMENT |
Voucher description |
NO |
DOCID |
Parameter needed in order to drill down to invoice image. This is mandatory data, if the purpose is to drill down to invoice image and the identifying code for invoice is not available in any other fields included into data transfer. |
NO |
EXTRACOLUMN_1-n |
Additionally, other voucher data level fields can be added, that can be shown to the user in the Clausion user interface when drilling down to voucher level data. |
NO |
Integration data format requirements
The essential data format requirements for the data transfer file:
- The column separator in CSV transfer file should be vertical line '|' or semicolon ';'
- The selected column separator cannot be used in the data fields' content
- Decimal separator can be "," or "." - Clausion prefers "."
- The amount of transfer file columns need to be the same on all of the transfer file rows
- The column order needs to be the same on all of the transfer file rows
- Transfer file can contain header row for columns, but it is not mandatory.
- Preferred date format is ISO-8601
- Line change should be dos windows CRLF
Example of a voucher data transfer file (header + one data row) with separator "|":
Transfer file name
The transfer file naming will be agreed in the integration planning and definition meeting for each integration. File name should always be the same, the only parameters that can change in the file name can be month and year. Clausion suggests to name the transfer files as "SOURCE_mm_yyyy.csv", example. " ERP_10_2020.csv".
Important: The month (mm) cannot have leading zeros.
Delivering the file to Azure Storage
File can be delivered to Azure storage by using the Blob storage API or MS Storage Explorer. The latter one is used to transfer files manually. In both cases authentication is made by using SAS-token.
Note: The customer is responsible for delivering the file to the blob storage.