Here, you will find parameters for custom booking CSV and a sample file.
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
The CSV file below consists of five rows, each representing a different use case.
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.
row without additionalInfo, without label.
row without additionalInfo, with label.
row with additionalInfo, without label.
row with long additionalInfo, with label.
When creating your CSV file, adhere to the following guidelines.