Nexus Journal Guide
US Trading Journal with IBKR Import
Nexus Journal supports US-market journaling through an IBKR-focused workflow. The app adapts labels, currency display, fees, charts, and analytics so US trades are reviewed separately from Indian tax and broker assumptions.
Reviewed 2026-07-15 by Nexus Journal product team.
IBKR import workflow
IBKR reports can be imported into the journal workflow so traders can review executions, symbols, quantities, prices, commissions, fees, and realized performance.
The US workflow is intentionally separated from Indian broker workflows to reduce data mixing and market-specific interpretation errors.
Fees instead of Indian taxes
In US mode, Nexus presents costs as commissions and fees rather than Indian tax labels such as STT or stamp duty.
That keeps gross P&L, net P&L, fee impact, drawdown, and performance review aligned with the market being traded.
Same professional review layer
US trades still benefit from Nexus features such as portfolio analytics, chart review, notes, profit giveback, drawdown, risk metrics, real-time price context, and theme tracking.
The result is one review system for serious trading behavior across markets.
IBKR CSV and trade-confirmation PDF support
The IBKR provider parses structured rows containing symbol, date and time, side, quantity, trade price, trade value or proceeds, commission, fee, currency, and account identity where present. It also extracts supported landscape Trade Confirmation Report PDFs.
The PDF parser carries header-column positions across pages and keeps order summary rows while excluding exchange-level partial-fill detail rows to avoid counting the same order twice.
IBKR fee and reconciliation boundaries
IBKR commissions and fees are stored as US-market costs rather than mapped to Indian STT or stamp-duty labels. The source currency is retained where the report supplies it.
Compare symbols, timestamps, quantities, prices, proceeds, commission, fees, and account ID with the official report. PDF layout changes and reports without the expected summary structure can require a different source export.