This guide details the structure and data of Jiko's end-of-day bank statement export file exported to the ISO camt.053 format (version 8).

Bank Structure and Data

Jiko provides bank statements in the ISO 20022 camt.053 version 08 format. The following table details the data mapping for the main fields within this format.

GroupHeader <GrpHdr>

Definition: Common information for the message.

Camt.053 field	Field type	Mapping with the Jiko data
→ MessageIdentification <MsgId>	Text (35c)	Definition: Point to point reference, as assigned by the account servicing institution, and sent to the account owner or the party authorised to receive the message, to unambiguously identify the message. Usage: The account servicing institution has to make sure that MessageIdentification is unique per account owner for a pre-agreed period. Mapping: “Jiko” followed by the reporting format, and a time stamp formatted as `YYYYMMDD-HHMMSS`. Using the character “-” as a separator. Example: `JIKO-CAMT053V8-20250829-030201`
→ CreationDateTime <CreDtTm>	Date/Time	Definition: Date and time at which the message was created. Mapping: Write the system date and time. Example: `2025-08-29T03:02:01`

Statement <Stmt>

Reports on booked entries and balances for a cash account.

Camt.053 field	Field type	Mapping with the Jiko data
→ Identification <Id>	Text (35c)	Definition: Unique identification, as assigned by the account servicer, to unambiguously identify the account statement. This identifier helps: Distinguish between multiple statements for the same account. Track statements for auditing, reconciliation, and reference purposes. Automate the processing of statements by financial systems. Mapping: Dynamically generated UUID for each new statement export, without the “-” character to make it fit to 35c. Note: as a result, relaunching the export on the same day and with the same filtering parameters will present a new Id value. Example: `1dadfc19a50740eaa67bf2aecb6a1a8f`
→ CreationDateTime <CreDtTm>	DateTime	Definition: Date and time at which the statement was created. Mapping: System date and time. Example: `2025-08-29T03:02:01`
→ FromToDate <FrToDt>	-
→→ FromDateTime <FrDtTm>	Date	Definition: Date and time at which the period starts. Mapping: Start date set in the reporting filter. Where the time is always set to 00:00:00 to represent the start of the day. Example: `2025-08-28T00:00:00`
→→ ToDateTime <ToDtTm>	Date	Definition: Date and time at which the period ends. Mapping: End date set in the reporting filter. Where the time is always set to 23:59:59 to represent the end of the day. Example: `2025-08-28T23:59:59`

→ Account <Acct>

Definition: Unambiguous identification of the account to which credit and debit entries are made.

Camt.053 field	Field type	Mapping with the Jiko data
→→ Identification <Id>	-
→→→ Other <Othr>	-
→→→→ Identification <Id>	Text (35c)	Definition: Unique and unambiguous identification for the account between the account owner and the account servicer. Mapping: “id” of the pocket without character "-" so as to match the max field length of 35 characters of the camt standard. Example: if the "id" of a pocket is `a81bc81b-deal-4e5d-abff-90865d1e13b1` then the account identifier in the statement is `a81bc81bdeal4e5dabff90865d1e13b1`
→→ Type <Tp>	-
→→→ Code <Cd>		Definition: Specifies the nature, or use of the account. Mapping: Fixed value “SVGS” (Savings Account).
→→ Currency <Ccy>	Text (3c)	Definition: Identification of the currency in which the account is held. Mapping: “USD”.
→→ Name <Nm>	Text (70c)	Definition: Name of the account, as assigned by the account servicing institution, in agreement with the account owner in order to provide an additional means of identification of the account. Mapping: “pocket_name” of the pocket. Example: “Settlement - Outgoing”.
→→ Owner <Ownr>	Text	Definition: Party that legally owns the account.
→→→ Name <Nm>	Text (70c)	Definition: Name by which a party is known and which is usually used to identify that party. Mapping: Customer name. Example: "Woods, Washington and Martin".
→→→ Identification <Id>	-	Definition: Unique and unambiguous identification of a party.
→→→→ OrganisationIdentification <OrgId>	-
→→→→→ Other <Othr>	-
→→→→→→ Identification <Id>	-	Definition: Identification assigned by an institution. Mapping: Jiko’s identification number of the customer. Example: “345979486”.
→→→→→→ SchemeName <SchmeNm>	-	Definition: Name of the identification scheme.
→→→→→→→ Code <Cd>	Text (4c)	Definition: Name of the identification scheme, in a coded form as published in an external list. Mapping: Type used for the identification number of the customer. Example: “TIN”.
→→→ CountryOfResidence <CtryOfRes>	Text (2c)	Definition: Country in which a person resides (the place of a person's home). In the case of a company, it is the country from which the affairs of that company are directed. Mapping: Country code of the address of the customer. Example: “US”.
→→→ ContactDetails <CtctDtls>		Definition: Set of elements used to indicate how to contact the party.
→→→→ EmailAddress <EmailAdr>	Text (2048)	Definition: Address for electronic mail (e-mail). Mapping: Customer’s email address.
→→ Servicer <Svcr>	-	Definition: Party that manages the account on behalf of the account owner, that is manages the registration and booking of entries on the account, calculates balances on the account and provides information about the account.
→→→ FinancialInstitution Identification <FinInstnId>	-	Definition: Unique and unambiguous identification of an internationally recognized or proprietary identification scheme.
→→→→ Name <Nm>	Text (140c)	Definition: Name by which an agent is known and which is usually used to identify that agent. Mapping: fixed value “Jiko”.

→ Balance <Bal>

Definition: Set of elements used to define the balance as a numerical representation of the net increases and decreases in an account at a specific point in time.

Note: Two balance records are generated: one to represent the opening balance and one for the closing balance, differentiated by field Type <Tp>.

Camt.053 field	Field type	Mapping with the Jiko data
→→ Type <Tp>	-
→→→ CodeOrProprietary <CdOrPrtry>	-
→→→→ Code <Cd>	Text (4c)	Definition: Balance type, in a coded format. Mapping: “OPBD" (Opening Booked Balance).
→→ Amount <Amt>	Amount	Definition: Amount of money of the cash balance. Mapping: Opening balance of the account on the selected statement Start date. Example: `<Amt Ccy="USD">0.00</Amt>`
→→ CreditDebitIndicator <CdtDbtInd>	Text (4c)	Definition: Indicates whether the balance is a credit or a debit balance. Usage: A zero balance is considered to be a credit balance. Mapping: If Opening balance < 0 then “DBIT” If Opening balance >= 0 then “CRDT” Example: if the opening balance = 0 then “CRDT”.
→→ Date <Dt>	Date	Definition: Indicates the date of the balance. Mapping: Selected statement Start date. Example: “2025-08-28”.
→→ Type <Tp>	-
→→→ CodeOrProprietary <CdOrPrtry>	-
→→→→ Code <Cd>	Text (4c)	Definition: Balance type, in a coded format. Mapping: “CLBD" (Closing Booked Balance).
→→ Amount <Amt>	Amount	Definition: Amount of money of the cash balance. Mapping: Closing balance of the account on the selected statement End date. Example: `<Amt Ccy="USD">0.00</Amt>`
→→ CreditDebitIndicator <CdtDbtInd>	Text (4c)	Definition: Indicates whether the balance is a credit or a debit balance. Usage: A zero balance is considered to be a credit balance. Mapping: If Closing balance < 0 then “DBIT” If Closing balance >= 0 then “CRDT” Example: if the closing balance = 0 then “CRDT”.
→→ Date <Dt>	Date	Definition: Indicates the date of the balance. Mapping: Selected statement End date. Example: “2025-08-28”.

→ Transaction Information (Ntry)

Definition: Specify an entry in the statement. Usage: At least one reference must be provided to identify the entry and its underlying transaction(s).

Camt.053 field	Field type	Mapping with the Jiko data
→→ EntryReference <NtryRef>	Text (35c)	Definition: Unique reference for the entry. Mapping: Incoming: ACH credit: “individual_identification_number” Wire credit: “reference_number” On_US credit: “description” Sweep credit: write fixed text “Sweep” Outgoing: Wire debit: “reference_number” On_US debit: “description” Sweep debit: write fixed text “Sweep”
→→ Amount <Amt>	Amount	Definition: Amount of money in the cash entry. Mapping: “amount_value” and “amount_currency” of the bank transaction. Notes: credits are represented with a positive amount, debits are represented with a positive amount too and differentiated through field CreditDebitIndicator <CdtDbtInd>. Example: an “amount_value” of USD 123456 in Jiko is represented as `<Amt Ccy="USD">1234.56</Amt>`.
→→ CreditDebitIndicator <CdtDbtInd>	Enum	Definition: Indicates whether the entry is a credit or a debit entry. Mapping: If the transaction is a debit (decreases the balance) then “DBIT”. If the direction is a credit (increases the balance) then “CRDT”. Example: “CRDT”.
→→ Status <Sts>	Text	Definition: Status of an entry on the books of the account servicer. Mapping: Fixed value “BOOK”.
→→ BookingDate <BookgDt>	Date	Definition: Date and time when an entry is posted to an account on the account servicer's books. Usage: Booking date is the expected booking date, unless the status is booked, in which case it is the actual booking date. Mapping: “time_settled” date of the bank transaction. Without any time. Example: “2025-08-28”.
→→ ValueDate <ValDt>	Date	Definition: Date and time at which assets become available to the account owner in case of a credit entry, or cease to be available to the account owner in case of a debit entry. Mapping: “time_settled” date of the bank transaction. Without any time. Example: “2025-08-28”.
→→ AccountServicerReference <AcctSvcrRef>	Text (35)	Definition: Unique reference as assigned by the account servicing institution to unambiguously identify the entry. Mapping: Bank transaction's "id" without the hyphen (-) separator character. This adjustment ensures the string complies with the camt length requirement of 35 characters. Example: if the original “id” value is `d96f413e-8ec2-44aa-972c-7e96b7388956` then it is written as `d96f413e8ec244aa972c7e96b7388956`.
→→ BankTransactionCode <BkTxCd>	-	Definition: Set of elements used to fully identify the type of underlying transaction resulting in an entry.
→→→ Domain <Domn>	-	Definition: Set of elements used to provide the domain, the family and the sub-family of the bank transaction code, in a structured and hierarchical format. Usage: If a specific family or sub-family code cannot be provided, the generic family code defined for the domain or the generic sub-family code defined for the family should be provided.
→→→→ Code <Cd>	Text (4c)	Definition: Specifies the business area of the underlying transaction. Mapping: See Bank Transaction Codes section below. Example: “DOMN”.
→→→ Family <Fmly>	-	Definition: Specifies the family and the sub-family of the bank transaction code, within a specific domain, in a structured and hierarchical format.
→→→→ Code <Cd>	Text (4c)	Definition: Specifies the family within a domain. Mapping: See Bank Transaction Codes section below. Example: “PMNT”.
→→→→ SubFamilyCode <SubFmlyCd>	Text (4c)	Definition: Specifies the sub-product family within a specific family. Mapping: See Bank Transaction Codes section below. Example: “ICDT”.
→→ EntryDetails <NtryDtls>	-	Definition: Provides details on the entry.
→→→ TransactionDetails <TxDtls>	-	Definition: Provides information on the underlying transaction(s).
→→→→ References <Refs>	-	Definition: Provides the identification of the underlying transaction.
→→→→→ EndToEndIdentification <EndToEndId>	Text (35c)	Definition: Unique identification, as assigned by the initiating party, to unambiguously identify the transaction. Mapping: Same value as in field EntryReference `<NtryRef>`.
→→→→→ AccountServicerReference <AcctSvcrRef>	Text (35)	Definition: Unique identification, as assigned by a sending party, to unambiguously identify the payment information group within the message. Mapping: Same value as in field AccountServicerReference `<AcctSvcrRef>` under field Transaction Information `<Ntry>`.
→→→→→ UETR <UETR>	Text (36c)	Definition: Universally unique identifier to provide an end-to-end reference of a payment transaction. Mapping: “id” of the bank transaction. Example: `604c3b7c-111a-4659-9dcb-b36a905f2b4d`
→→→→ RelatedParties <RltdPties>	-
→→→→→ Debtor <Dbtr>	-	Definition: Party that owes an amount of money to the (ultimate) creditor.
→→→→→→ Party <Pty>	-	Definition: Identification of a person or an organization.
→→→→→→→ Name <Nm>	Text (140c)	Definition: Name by which a party is known and which is usually used to identify that party. Mapping: The mapping depends on the direction and type of the bank transaction: Incoming ACH credit: “company_name” WIRE credit: “counterparty_name” On_US credit: "counterparty_name" SWEEP credit: write text “From my Jiko portfolio at Jiko Securities Inc.” Outgoing ACH debit: “name” of the customer WIRE debit: “name” of the customer On_US debit: “name” of the customer FEE debit: “name” of the customer SWEEP debit: write text “From my Jiko bank account at Jiko Bank”
→→→→→ Creditor <Cdtr>	-	Definition: Party to which an amount of money is due.
→→→→→→ Party <Pty>	-	Definition: Identification of a person or an organisation.
→→→→→→→ Name <Nm>	Text (140c)	Definition: Name by which a party is known and which is usually used to identify that party. Mapping: Incoming ACH credit: “name” of the customer WIRE credit: “name” of the customer On_US credit: “name” of the customer SWEEP credit: “To my Jiko bank account at Jiko Bank” Outgoing ACH debit: “company_name” of the bank transaction WIRE debit: <to be confirmed based on how incoming files are mapped to Jiko’s db fields> On_US debit: "counterparty_name" FEE debit: write “Jiko”. SWEEP debit: write text “To my Jiko portfolio at Jiko Securities Inc.”
→→→→→ UltimateCreditor <UltmtCdtr>
→→→→→→ Party <Pty>	-	Definition: Identification of a person or an organisation.
→→→→→→→ Name <Nm>	Text (140c)	Definition: Name by which a party is known and which is usually used to identify that party. Mapping: Incoming ACH: “name” of the customer Outgoing ACH: “company_name” of the bank transaction
→→ RemittanceInformation <RmtInf>	-	Definition: Structured information that enables the matching, that is reconciliation, of a payment with the items that
→→→ Unstructured <Ustrd>	Text (140c)	Definition: Information supplied to enable the matching/reconciliation of an entry with the items that the payment is intended to settle, such as commercial invoices in an accounts' receivable system, in an unstructured form. Mapping: “remittance_information” of the bank transaction. Example: “Invoice 123”.

Bank Transaction Codes

The table below lists the types of bank transactions reported by Jiko and how they are represented in bank statements.

Export Bank Statements to the camt.053.001.08 format