If an approval process for a custom booking is enabled in the configuration, then any other employee(s) assigned to approve it must do so. The custom booking will be in the Waiting for Approval status until all necessary approvals have been made. Once all approvals are complete, the new custom booking will be initialised.
From the content menu, choose the Custom booking option.
Fill in the search details > click on the Search button.
Click on the Custom booking ID to view the custom booking details.
Make the approval decision: Reject custom booking or Approve custom booking.
Open the .
The custom booking view page is separated into different sections.
The custom booking page generally displays the following information:
Custom booking details - information about the custom booking, such as amount, transaction type, status, etc.
Related events -
Events caused by this custom booking on the closed account.
Events caused by this custom booking reversal on the closed account.
Related events section is dedicated to the closed accounts only.
Related account transactions -
Transactions caused by this custom booking on the open account.
Reversal transactions caused by this custom booking reversal on the open account.
Reversal account transactions - Transactions caused by another custom booking reversal on the open account that reversed the current custom booking on the open account.
Reversal events - Events caused by another custom booking reversal on the already closed account that reversed the current custom booking made when the account was still open.
Original transactions -
Transactions caused by another custom booking on the open account that are reversed by the current custom booking reversal on an open account.
Transactions caused by another custom booking made when the account was open are reversed by the current custom booking reversal made when the account was already closed.
Direction*
List
Select the custom booking direction:
Incoming - credit to the account,
Outgoing - debit from the account.
Transaction type*
List
Select the transaction type.
Note: only a subset of transaction types are available for custom bookings.
Transaction subtype
List
Select the transaction subtype.
Note: this field is only available when the transaction type has subtypes.
Fee type
List
This parameter fills up automatically based on the chosen Transaction type and cannot be edited.
Note: this field is available only when the chosen Transaction type is onetime fee (e.g. SETUP_FEE) or periodic fee (e.g. ACC_ADM_FEE).
Fee subtype Note: the fee subtype name is displayed.
List
Select the fee subtype. (Fee subtypes for onetime or periodic fees are categorised with labels.)
Note: If the fee subtype has a pricelist or special price, the price will automatically fill up the amount.
Negative balance allowed
Checkbox
This checkbox about negative balance allowance fills up automatically and cannot be edited.
Value date rule*
List
Select the value date rule:
Entered date - the value date will be the date that was entered as a custom booking value date.
Approval date - the value date will be the date when the custom booking is finally approved.
Value date*
Date
Select the custom booking value date. Format: DD.MM.YYYY.
Note: this field is only available when the Entered date rule is chosen.
Custom booking currency code
List
Select the currency. Note: The default value is the default currency of the account.
Available balance
Number
This field fills up automatically and shows the available account balance in the currency selected for the Custom booking currency code.
Amount, currency*
Number
Enter the custom booking amount.
Note: the currency fills up automatically with the currency selected for the Custom booking currency code.
Details*
Text
Enter custom booking details. Note: This text will be included in the customer account statement.
Additional info
Text
Enter additional info if needed. Note: This text is for internal purposes and will not be included in the customer account statement.
Fee transaction type
Text
This additional fee transaction type parameter fills up automatically and cannot be edited.
Note: this field is available only when the chosen transaction type has a related transactional fee. For example, with the base transaction CARD_TOPUP, the related fee transaction CARD_TOPUP_FEE can be posted if a pricelist or special price exists.
Fee amount, currency
Text
These parameters are filled up automatically and cannot be edited.
Note: this field is available only when the chosen transaction type has a related transactional fee and a pricelist or special price.
Apply fee
Checkbox
Select or deselect the checkbox for the applicability of the additional fee transaction.
Note: this field is available only when the chosen transaction type has a related transactional fee and a pricelist or special price.
The BackOffice interface supports the custom bookings option. Here are some example use cases where you might need to make a custom booking.
Enter a card transaction manually or reverse it.
Reverse the applied fee for the customer.
Enter some transactions like fees, compensations or chargebacks manually.
Enter interest or fee corrections.
Make write-offs before account closure.
Making resolving entries on a closed account.
Below you will find more information about:
From the content menu, choose the Custom booking option.
Click the Save button.
To upload the CSV file:
Administration > File import.
On the file import page, click the Import file button.
In the file import window, set the Import type to Custom bookings, upload the CSV file > click the Import button.
The outcome can be an error or success once you have uploaded your file with custom bookings.
Error: Should the Tuum system encounter an error in any row of your custom booking file, it will reject the entire file. The response will detail the error associated with the specific problematic row.
Success: The Tuum system has created all custom bookings in the CSV file.
The Tuum system bypasses account balance checks for custom booking file uploads. Therefore, transactions can push account balances into the negative, regardless of the negative balance allowance settings.
The Tuum system supports custom bookings on closed accounts. This functionality is needed when transactions or transaction reversals need to be registered in Tuum after the account is closed. For example, if the information about the card purchase is received after the card account is closed.
To register custom booking on a closed account, you need to complete two steps:
From the content menu, choose the Custom booking option.
Click the New custom booking in closed account button.
Fill in the custom booking details, and click Save.
After creating a new incoming custom booking on a closed account, it needs to be resolved to choose where the funds are directed:
Transferred to the internal account - to transfer funds to an internal account.
Registered a bank revenue - to register funds as a bank income.
To resolve a custom booking:
Find a custom booking on a closed account.
Open the custom booking view page > on the upper right corner, click the Resolve button.
The BackOffice will open the Custom booking resolve page > fill in the parameters > click the Resolve button. See below for more details.
Accounts > Search > Custom bookings.
Fill in the search details > click the Search button.
Click the Custom booking ID to view the details.
,
,
,
Open the .
Click the New custom booking button and fill in the .
Using the BackOffice interface, you can bulk upload the custom booking files in the comma-delimited CSV format. Find information about the CSV file here: .
,
.
the closed account in question > open the .
Only allowed transactions can be reversed. See the page for more details.
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.
