Choose a trade-focused IBKR report
The IBKR Activity Statements documentation notes that additional formats such as Excel, CSV and HTML can be downloaded within the Client Portal. IBKR also supports configurable reporting, including Flex Queries, for activity and trade-confirmation data. Portal menus and report choices can change, so use the current Client Portal documentation for your account type.
For journaling, prefer a report or Flex Query that contains executed and closed trade details for a known date range. A full Activity Statement can include positions, cash balances, fees, corporate actions, interest, dividends, deposits and withdrawals. Those are useful for account reconciliation but are not all individual closed trades. Exclude non-trade sections from the import file or leave those columns unmapped.
Understand the shape of the exported data
IBKR exports may have several sections, and a statement can represent executions, lots or transactions differently from a one-row-per-trade journal. One position may be built from multiple fills; a close may be split across executions; an asset conversion, option contract or futures instrument may use a symbol convention that differs from forex.
Edgelog’s CSV importer is a general trade mapper, not an IBKR-specific statement parser or tax-lot reconciler.
Before importing, check that each row you plan to keep has a recognizable instrument, buy/sell side, entry price, quantity and realized P&L. If your report has separate columns for proceeds, cost basis, realized P&L and commission, do not assume that proceeds are the trade result.
Map the field that actually represents the realized result you want to analyze, and preserve fees separately when the file provides them.
Import a small IBKR sample first
- In Client Portal, select a short date range and generate the trade-focused CSV/Excel report. Keep the original file private.
- Open the Edgelog CSV/Excel import flow and choose or create a separate account for the relevant IBKR portfolio.
- Upload the file and review the detected headings. Map symbol, side, entry price, size and realized P&L only when their meaning is clear.
- Inspect representative stocks, options or futures rows separately. Confirm contract quantity, multiplier assumptions and currency are not being silently confused. If the export does not carry enough information for a valid row, omit it rather than inventing a value.
- Compare Edgelog’s preview counts and net results with IBKR’s trade report for the exact same filter, dates and currency. Import only after the trade count and sample rows make sense.
Keep asset and currency boundaries clear
An IBKR account can hold several asset classes and currencies. Edgelog’s product is centered on forex and crypto journaling; other asset histories may be imported through CSV, but that does not mean every instrument-specific calculation or broker feature is supported. A contract’s unit size, multiplier, fees, currency conversion and realized P&L convention can affect the numbers.
Keep assets separated during your first test if their units differ, and verify the net P&L currency before reviewing account-level analytics.
When the activity statement is too complex
If Edgelog cannot identify the trade rows, configure a narrower IBKR Flex Query or export the relevant trade section into a clean spreadsheet with one completed trade per row. Keep a source identifier and preserve the original report so the mapping can be audited. Never delete or merge fills in a way that changes the realized result merely to make the upload pass.
If you need detailed stock-lot accounting, tax-lot matching or full portfolio reconciliation, use a tool designed for those workflows; Edgelog is a journal rather than a broker statement engine.
Read the broker CSV import overview, then use column mapping guidance or troubleshooting if the preview does not match the IBKR report.