Use Bank Connectors
Introduction
Connectors provide visibility into how custodian files are handled on the platform. It helps you monitor file uploads, track processing status and initiate reprocessing if needed.
Key Terminologies
Term (A–Z) | Definition |
|---|---|
Connectors | Interactive reports showing processed, skipped or failed files, transactions, and positions. |
Failed | Files/data that encountered errors during processing. |
Processed | Files/transactions/positions successfully handled and matched. |
Processing (Reprocessing) | Conversion of custodian files (transactions & positions) to platform's internal data format. |
Reconciliation | Comparing bank data with platform data to identify discrepancies. |
Skipped | Files/data not processed due to irrelevance or invalid format but not marked as error. |
👉 New to some terms? Check out our full Platform Glossary for more.
Accessing Connectors
Go to Transactions from the main menu
Select the Connectors tab
How to Use Connectors
Use the date picker to select a specific date or range.
Reconciliation is typically done for the previous working day, so start by selecting yesterday's date in the date picker.
The page is divided into 3 main sections:
Files – Tracks file upload and processing status
Transactions – Lists transaction-level data extracted and processed
Positions – Shows position-level data for reconciliation
You’ll also see Auto-Reconciliation Checks that show match/mismatch data between bank and platform in percentages.
To access the Connectors tab, you must have:
Permission to view Bank Statistics
Access to the relevant Custodian
Read more here.
Connector Data Blocks Explained
Understanding Connector Data Blocks
Section | Example (from table) | Steps to Reconcile |
|---|---|---|
Files | All 15 files successfully processed. |
|
Transactions | 10 out of 20 transactions processed. |
|
Positions | All 40 positions processed. |
|
Field Name | Description | Sample Value |
|---|---|---|
ID | Unique identifier for the file or record | 93dd866f-1... |
File Name | Name of the source file containing data | broker2\_BCTEST\_01022025\_12012027(Mi...).xlsx |
File Time | Timestamp when the file was created or loaded | 2025.02.01 04:00:00 |
Source | Origin or platform where the file came from | broker2_BATEST |
Loaded Transactions | Number of transactions loaded from the file | 350 |
Processed | Indicates the transactions are successfully processed | - |
Error | Error message if any issues exist | (empty if no error) |
Field Name | Description | Sample Value |
|---|---|---|
SOURCEFILE | Name of the source Excel file received from the broker | broker2\_BC11111-MO-TST\_18042025 (6).xlsx |
TIME | Timestamp of the transaction (may appear as legacy date) | Sun Dec 31 19:07:45 GMT 1899 |
SYMBOL | Short code of the traded asset | CRM5 |
INSTRUMENT | Full name or identifier of the instrument | CNY-6.25\_FT |
SIDE | Direction of the trade (Buy or Sell) | Sell |
PRICE | Price per unit of the traded instrument | 12.19 |
QTYLOTS | Quantity of lots traded | 893.0 |
COMMISSION | Commission charged for the trade | 0.001\*F2\*1000 |
CURRENCY | Currency in which the trade is conducted | RUB |
BANKACCOUNT | Bank account or broker account name | BC11111-MO-TST |
TRANSACTIONID | Unique ID for the transaction | 82698cbe-f0b3-42cf-9961-fe834ebb8a87 |
PARENTTRANSACTIONID | ID of the parent transaction (if any) | (blank or another UUID) |
NEEDREPROCESS | Boolean value: if transaction needs reprocessing | false |
ERROR | Boolean value: if any error was detected | false |
SKIP | Boolean flag: if transaction should be skipped | false |
platformBANKACCOUNTID | Internal platform ID for the bank account | 63011338-3d44-49c1-9cdf-a047f4be16e5 |
platformINSTRUMENTID | Internal ID or ISIN/identifier for instrument in platform | US67066G1040.UW |
platformTRADEDATE | Trade date as recorded by the platform | 22.04.2025 |
SOURCE | Origin platform or broker of the file | broker2 |
CONNECTIONID | Internal reference for platform's connector ID | UUID |
CREATEDAT | Timestamp when this record was first added | 27.05.2025 16:23:24 |
CREATEDBY | User/platform who created the entry | platform/user name |
UPDATEDAT | Timestamp when record was last updated | 27.05.2025 16:23:26 |
UPDATEDBY | User/platform who last updated the entry | platform/user name |
This table displays data exactly as received from the custodian.
However, the platform adds a few technical fields for tracking and internal use, listed below:
Field Name | Description |
|---|---|
id | Unique identifier for the row in the platform. |
transactionId | Internal ID linking the row to a transaction object, if applicable. |
platformBankAccountId | Internal identifier for the associated bank account within the platform. |
instrumentId | Internal identifier for the financial instrument. |
newInstrumentId | Updated instrument ID in case of instrument change (e.g., after corporate actions). |
source | Indicates where the data originated (e.g., custodian name or provider). |
connectionId | Identifier for the platform’s connection to the data provider. |
skip | Indicates whether this row should be ignored during processing (true or false). |
Example: Position at the end of 2025.01.01 should match the opening on 2025.01.02, adjusted for any trades.
Need to Perform a Reconciliation Check?
From Connectors, click on the Reconciliation Check (%)
Use the table reference below when you're performing it.
Field Name | Description |
|---|---|
Bank Account | A bank account is held by a bank or custodian to manage a client’s funds and securities for investment. |
Bank Ccy | The currency in which the bank’s transactions or positions are recorded. |
Bank Instrument Name | The name or symbol of the instrument as recorded by the bank. |
Bank Pos Qty | Indicates the number of units or quantity of the instrument held, as reported by the bank. Special Cases:
|
Bank Price | The price per unit of the instrument as recorded by the bank. |
Bank Tr Qty | The number of units transacted (bought/sold) according to the bank. |
Bank Value | The total value of the instrument in the bank’s records, it depends on asset type. |
Instrument | The name or identifier of the instrument according to the platform. |
New Instrument | The updated or new identifier for the instrument that may have been changed internally. |
New Pos Qty | New position quantity after updates |
platform Ccy | The currency in which the platform records its transactions or positions. |
platform Instrument Name | The name or symbol of the instrument as recorded in the platform. |
platform Pos Prev Day Qty | The quantity of the instrument held in the platform at the close of the previous day quantity. |
platform Price | The price per unit of the instrument according to the platform. |
platform Value | The total value of the instrument in the platform, calculated as platformPosPrevDayQty * platformPrice. |
Status | A status indicator that shows whether the reconciliation for that particular instrument or transaction is accurate. |
Diff | Difference in position quantity/value between bank and platform |
platform New Positions | Adjusted positions post reconciliation |
Diff Prev Day | Difference between positions from previous day and current day |
Current Status | Indicates the current day’s reconciliation status |
Bank Name | Name of the Custodian |
platform Name | platform-recognized name |
See Guide: Using the Reconciliation feature for more.
Troubleshooting Steps
Step 1: Verify File with Back Office (BO): Before raising the issue, make sure the file is valid and present.
Navigate to Transactions > Connectors
Set the relevant date (e.g.,
23.09.2024)In the Files section, click on the “Failed” counter
Locate the relevant Bank, and click All Files
Select the failed file to:
Review the File Time
Check the File Content
Look for any empty columns, missing values, or format mismatches
Step 2: Identify Type of Failure
Failure Type | How to Recognize |
|---|---|
Incorrect Format | Column names don’t match expected layout; e.g., missing headers like |
Missing Required Fields | Fields like quantity, instrument name or price are blank or incorrectly mapped |
Duplicate or Outdated File | File already processed, but sent again; or file is from an old date |
Data Corruption | File content doesn’t load properly, often due to character encoding or upload issue |
Unmapped Instruments | Bank instrument names not linked to any platform instrument, leading to unmatched data |
Step 3: Take Action Based on the Issue
Issue Identified | Recommended Action |
|---|---|
File format is incorrect | Ask BO or custodian to resend file using the correct format/template |
Required fields are missing | Manually update missing fields if allowed, or request corrected file from custodian |
Duplicate/old file | No action needed unless it contains unique transactions; skip or delete if needed |
Corrupted upload | Retry uploading the file manually if permitted, or escalate with file copy to support |
Instrument mapping error | Check mapping in the platform’s instrument directory or raise for mapping update |
Optional: Reprocess the File
If you’ve confirmed the file structure is valid but the platform failed to process it, you may manually reprocess it.
Return to the Connectors > Files section
Locate the failed file
Use the “Reprocess” option (available for permitted users)
Check Reconciliation Check again to confirm resolution
When to Escalate
If issues persist after verification and reprocessing, escalate the issue with the following details:
Custodian/Bank Name
File name and date
File Time
Screenshot of error or “Failed” status
Copy of the raw file content (if possible)
Send these details to your platform Admin or Reluna support team for advanced troubleshooting.