Custom booking CSV file

Here, you will find parameters for custom booking CSV and a sample file.

Parameters with description

Row title
Description

accountId

An existing account technical identifier in Tuum.

Note: custom bookings should be permitted on the account.

transactionTypeCode

The transaction type, including the fee or transaction with the fee where custom bookings are allowed. For more details, see annex.

Note: the transaction direction is automatically derived from the transaction type.

valueDateRule

The following options are available:

  • APPROVAL_DATE - the value date will be the date when the custom booking is finally approved.

  • ENTERED_DATE - the value date will be the date that was entered as a custom booking value date.

valueDate

The value date; format: yyyy-mm-dd.

  • Mandatory if ENTERED_DATE;

  • Must be empty (“,,”) if APPROVAL_DATE.

Note: It cannot be in the future or before the allowed value date min date.

amount

Custom booking amount; must be positive.

currencyCode

Custom booking currency; must be allowed currency.

applyFee

The following options are available:

  • TRUE,

  • FALSE.

details

A textual description.

additionalInfo

Additional info not visible to the customer. Not mandatory

Note: If additionalInfo is empty then comma (“,”) must be still added to the file as field delimiter.

label

Label value posted with PERIODICAL or ONETIME fee to specify fee type at a more detailed level. Not mandatory

Note: If label value is empty then comma (“,”) must be still added to the file as last field delimiter

Sample CSV file

The CSV file below consists of five rows, each representing a different use case.

  1. row is the file header, which consists of the list of the parameter names. It is mandatory to have this row first in the file.

  2. row without additionalInfo, without label.

  3. row without additionalInfo, with label.

  4. row with additionalInfo, without label.

  5. row with long additionalInfo, with label.

accountId,transactionTypeCode,valueDateRule,valueDate,amount,currencyCode,applyFee,details,additionalInfo,label
ID-7479,CAMP2ACC,APPROVAL_DATE,,2000.01,EUR,TRUE,Text to account statement 0,,
ID-7479,SETUP_FEE,APPROVAL_DATE,,2001.01,EUR,TRUE,Text to account statement 1,,SETUP_VIBAN
ID-7479,CAMP2ACC,APPROVAL_DATE,,2002.01,EUR,TRUE,Text to account statement 2,Internal comment 2,
ID-7472,SETUP_FEE,ENTERED_DATE,2028-01-16,2003.01,EUR,TRUE,Text to account statement 3,Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. Internal comment 3 very long. END,SETUP_VIBAN

File upload guidelines

When creating your CSV file, adhere to the following guidelines.

  • Only include up to 1000 rows in the CSV file.

  • Avoid adding quotation marks around any text.

  • Ensure there are no commas inserted within the details or additionalInfo fields.

  • Use a unique name for each file you upload.

Last updated

Was this helpful?