Nexus Journal Guide
Nexus Journal Broker Import Compatibility
Broker support is not one binary feature. File parsing, live connection flows, historical synchronization, charge handling, market coverage, and deduplication differ by provider. This page documents those distinctions so traders can choose the correct source and verify the result.
Reviewed 2026-07-15 by Nexus Journal product team.
File and connection coverage
Zerodha, Dhan, Upstox, Angel One, Groww, FYERS, and mStock have both file-import and connection-oriented implementation paths. Kotak is primarily connection/API-oriented in the current provider structure, while ICICI and Motilal Oswal are file-import focused.
StockyMind supports multiple spreadsheet generations and backup JSON where recognized. Nexus formats support journal re-import workflows. IBKR supports dedicated CSV-style and trade-confirmation PDF parsing, with commission and fee fields mapped into the US workflow.
Market and cost boundaries
Dhan includes India and US data paths, including US symbol identity resolution from broker data. IBKR is treated as a US-market provider. Indian workflows use tax and charge categories where the source provides them, while US workflows keep commissions and fees separate from Indian tax terminology.
A supported trade import does not guarantee that every broker report supplies every charge, tax, order identifier, or lifecycle field. Missing source granularity remains a limitation of the resulting analysis.
Deduplication and reconciliation
The import pipeline uses broker and exchange identifiers where available, plus normalized signatures and cross-broker logic. Upstox preserves trade identifiers across daily sync and historical backfill; Dhan ledger and tax paths retain overlap metadata to reduce replay and double-counting risk.
After any import, compare date range, record count, symbols, quantities, gross P&L, and known charges with the official source. A successful parser message is not a substitute for reconciliation.
Compatibility changes over time
Broker exports and APIs can change without notice. A renamed header, new report layout, expired token, changed pagination rule, or missing segment can affect an otherwise supported workflow.
Keep the original report, use the most specific supported importer, and report a changed format with a redacted sample that preserves headers and structure.