This guide details the Bank Transaction Codes used in Jiko's statements, bank statements and brokerage statements. These codes need to be configured in the systems that import and process these statements.
Integration Options
Jiko offers the following integration options for connecting with your Treasury Management System (TMS):
Import both Bank Statements and Brokerage Statements into the Cash Management product of your TMS, into separate bank accounts.
Alternatively, import Bank Statements into the Cash Management product of your TMS and T-bill Transactions into the Financial Transactions product. A cusip-level position summary can also be imported into Financial Transactions to reconcile reported quantities against the quantity derived from separately imported buy/sell trades.
Bank Transaction Codes
BTCs used in camt.053 Bank Statements
The table below lists the types of bank transactions reported by Jiko and how they are represented in bank statements.
BTCs used in camt.053 Brokerage Statements
Jiko provides brokerage statements detailing T-bill holdings, with the opening and closing values of the holdings, to import them as the balances of a bank account. Bank transactions are also reported and categorized as described below, to explain the net change from the opening to the closing value:
Additions: new funds deposited into the brokerage account.
Subtractions: funds withdrawn from the brokerage account.
Gains/Losses from T-bills held in the account.
Fees charged and deducted from the brokerage account.
It is accordingly necessary to configure Bank Transaction Codes representing this activity in the systems that import and process these statements.
Alternatively, you can directly import the T-bill buy and sell transactions into your system, using Jiko’s reporting named “Trade Report”: this method allows your system to automatically calculate the opening and closing values, as well as other relevant data like gains and losses.
Kyriba Integration Options
This section is specific to the import of camt.053 bank statements in Kyriba. Irrespective of the bank that reported bank statements. Kyriba offers to represent Bank Transaction Codes in two ways at integration time, depending on format parameter “CONCATENATEDOMN”.
Illustration for a wire credit, reported in camt.053 statements through Domain PMNT, Family RCDT, Subfamily DMCT:
Illustration when format parameter CONCATENATEDOMN is not used:
