> For the complete documentation index, see [llms.txt](https://help.solink.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.solink.com/docs/install-connect-and-integrate/integrations/csv-formatting-guides/banking-format-guidelines.md). # Banking Format Guidelines This document defines the Banking CSV format for integrating ATM / teller transaction data into Solink. Data is delivered with CSV files. *** ## File Details When sending data for this Solink integration, please ensure you follow the file naming conventions outlined below: ### File Naming Format | **File Name breakdown** | Details | | ------------------------------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **`--banking.csv`** | \* If you are **splitting** the files out by store, use **\**. \* Can contain data for one or more stores as long as total group size is **below 50MB** | | **`-banking.csv`** | \* If **all stores are in one file**, the **\** can be omitted. \* Can contain data for one or more stores as long as file size is **below 50MB** | ### File Part details | File name part | Additional details | | ----------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **\** | **Required**unique date stamp without separators\* Formats: \* YYYYMMDD (daily drops) \* YYYYMMDDTHHmm (multiple drops per day) \* Examples: \* 20240213-banking.csv \* 20240213T1233-banking.csv | | **\** | **Optional**Unique identifier representing the physical location of your store. \* used if files contain the data for a single location. \* Identifier is tied to your configuration and should not change \* Formats: \* Any Alphanumeric character \* A-Z, a-z, 0-9 \* Examples \* A203 \* store535 | *** ## **Samples** Refer to the samples below for information on formatting CSV if you need to log banking transactions: Examples of data files from the retail industry: * [Banking Sample](https://github.com/SolinkCorp/help-centre-docs/tree/main/docs/.gitbook/assets/ba2ca65c-20260623-1001-banking.csv) *** ## File Content Formatting Refer to the table below for information on formatting your CSV file for the banking industry standard integration. | **Column Name** | **Required** | **Data Type** | **Examples** | **Purpose** | | ------------------------- | ------------ | ------------- | ----------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | **dataType** | ✱ Required | Picklist | 'teller''atm' | Indicates the data type. Any value containing "teller" (case-insensitive) is treated as a teller transaction. Any value containing "atm" (case-insensitive) is treated as an ATM transaction. | | **branchID** | ✱ Required | String | '1001' 'BR1001' | Branch unique ID. Maps to locationId internally. | | **terminalId** | ✱ Required | String | '1002' 'TS1002' | Teller station or ATM terminal unique ID. Maps to dataSourceId internally. | | **sequenceNumber** | ✱ Required | String | '10004' 'SQ1004' | Record unique ID. | | **transactionType** | ✱ Required | String | 'Deposit' 'Withdrawal' 'Inquiry' 'Check Deposit' 'Cash Back' 'Transfer' | Text description of the action taken by the teller or the customer at the ATM. | | **transactionDate** | ✱ Required | Date/Time | YYYY-MM-DDTHH:MM:SS.sss±HH:MM "2024-06-15T06:15:00.000-06:00" YYYY-MM-DDTHH:MM:SS.sssZ "2024-06-15T06:15:00.000Z" | Date/Time the transaction occurred. ISO-8601 datetime string. T is required to separate date and time. ±HH:MM represents timezone offset; Z indicates UTC. Used as both start and end time unless startTime/endTime are provided. | | **transactionAmount** | ✱ Required | Number | 23.5 11.95 | Transaction amount. Must be a plain numeric value — no currency symbols or commas. | | **transactionStatus** | Optional | Picklist | 'Success' 'Fail' | Status of the transaction. • Values containing "pass" or "success" (case-insensitive) → success • Values containing "fail" (case-insensitive) → fail • All other values → unable to process | | **employeeId** | Optional | String | '1003' 'EMP1003' | Employee unique ID. | | **employeeName** | Optional | String | 'John Smith' 'Jane S.' | The employee name. | | **accountNumberLast4** | Optional | String | '0552' '2203' | Last four digits of the customer account number. | | **cardNumberLast4** | Optional | String | '0552' '2203' | Last four digits of the ATM card number. | | **fromAccountLast4** | Optional | String | '0552' '2203' | Last four digits of the source account number (e.g., for transfers). | | **toAccountLast4** | Optional | String | '0552' '2203' | Last four digits of the destination account number (e.g., for transfers). | | **transactionTypeCode** | Optional | String | 'WD' 'DEP' 'TR' | Optional transaction type code. | | **transactionStatusCode** | Optional | String | 'SUCCESS' 'FAIL' | Optional transaction status code. | | **notes** | Optional | String | 'Customer requested receipt' | Optional free-text notes associated with the transaction. | | **startTime** | Optional | Date/Time | "2024-06-15T06:15:00.000-06:00" "2024-06-15T06:15:00.000Z" | Optional override for transaction start time. If omitted, transactionDate is used. Same ISO-8601 format as transactionDate. | | **endTime** | Optional | Date/Time | "2024-06-15T06:15:00.000-06:00" "2024-06-15T06:15:00.000Z" | Optional override for transaction end time. If omitted, transactionDate is used. Same ISO-8601 format as transactionDate. | *** ## Picklist Values Below are the Picklist Values. ### Result Field | **Value** | **Description** | | ----------- | ----------------------------------------------------------- | | **Success** | **The access attempt or operation completed successfully.** | | **Failure** | **The operation did not succeed.** | *** ### Common Issues | **Scenario** | **Description** | | --------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- | | `SequenceNumber` **Restrictions** | **SequenceNumber** field cannot contain any of the following characters:- ! ' ( ) ; : @ & = + $ , / ? % # \[ ] | | **Duplicated** `SequenceNumber` | Duplicated `SequenceNumber` values delivered on the same day will result in one of the records being overwritten. `SequenceNumber` values must be unique per day. | --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.solink.com/docs/install-connect-and-integrate/integrations/csv-formatting-guides/banking-format-guidelines.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.