Skip to content
Back to Website

Broker Import

Broker Import is execution-based and built for safe partial imports with duplicate protection.

  1. Click a broker tile to open the native file picker.
  2. Select the matching broker export file.
  3. Review parsed preview rows and status badges.
  4. Keep or change the row selection.
  5. Click Import to process only selected rows.
  • Rows marked Imported are already known and cannot be selected again.
  • Select all and Clear selection apply only to importable rows.
  • Status Open means the execution currently opens or adds to a position.
  • Status Closed means the execution closes position size.
  • You can import a subset of rows in one run.
  • Already imported executions are detected and skipped.
  • Repeated imports are idempotent for known rows.
  • Matching executions can close open positions automatically.
  • interactive-brokers via Flex XML execution reports
  • scalable-capital via Transactions CSV security execution rows
  • bitpanda-fusion via trade history CSV export
  1. In Interactive Brokers -> Performance & Reports -> Flex Queries -> Trade Confirmation Flex Query
  2. Click on ”+”
  3. Apply the settings as shown in the image below
  4. Save the Flex Query and run it
  5. Select the date range -> keep format “XML”

Interactive Brokers Flex Query

After import, the app reports four counters:

  • imported_count: new trade rows created from selected executions.
  • closed_count: existing open trades that were closed by matching executions.
  • skipped_count: known executions skipped by duplicate protection.
  • failed_count: rows that could not be imported due to parsing or validation issues.

If at least one trade was imported or closed, the app returns to Trades. Otherwise, the preview is refreshed so you can review remaining rows.

If imported identifiers differ from chart symbols, map them in Settings so TradingView widgets resolve correctly without breaking reconciliation keys.

  • Make sure you selected the correct broker tile before choosing the file.
  • Verify the export type matches the broker format (for example Flex XML vs CSV).
  • Check that the file actually contains execution rows (not account summary-only exports).
  • This is expected when all executions are already known.
  • Known rows are skipped to keep imports idempotent and safe.

Existing open trades were closed automatically

Section titled “Existing open trades were closed automatically”
  • This is expected when selected executions match previously open imported positions.
  • Matching uses broker/instrument execution identity and reconciliation rules, not chart symbol text.