SimpleTradeLog 1.1.1

What’s new: direct IBKR Flex synchronization

Connect a read-only Interactive Brokers Flex Query once, then bring new stock executions into your local trading journal without exporting a file for every review.

Released September 2026

A faster route from execution to review

SimpleTradeLog still supports Interactive Brokers .tlg trade logs and activity statement .csv files. Version 1.1.1 adds another option: a direct, read-only connection to the IBKR Flex Web Service.

The connection retrieves supported stock executions, including quantities, prices, commissions, symbols, and execution times. It does not place orders, change the brokerage account, or request live market data.

What the new connection does

The setup is designed to be understandable on day one and dependable when you return weeks later.

Guided IBKR setup

The Broker connection screen explains how to create an execution-level Trade Confirmation Flex Query, enable the Flex Web Service, and enter the Query ID and token.

Test before importing

Preview the masked account, available date range, new executions, duplicates, and unsupported rows before saving the connection.

Secure local credentials

The Flex token is encrypted with the operating system’s secure storage and is excluded from exported SimpleTradeLog backups.

Manual and automatic sync

Use Sync now at any time. SimpleTradeLog also checks whether a synchronization is due when the desktop app opens.

How repeat synchronization works

You do not create a new query every week or month. SimpleTradeLog reuses the saved Query ID and token until IBKR expires or revokes the token.

  1. 1
    First connection
    Request up to 365 days and import supported stock executions that are not already in the journal.
  2. 2
    One week later
    Request approximately 14 days: the elapsed week plus a seven-day safety overlap.
  3. 3
    One month later
    Request approximately 37 days. Existing IBKR execution identifiers are ignored automatically.
SimpleTradeLog executions table with symbols, trade times, quantities, prices, and fees
Flex-synchronized executions appear in the same local execution history as supported file imports.

What stays the same

The connection is an additional workflow, not a forced migration.

CapabilityVersion 1.1.1 behavior
File importsIBKR .tlg and supported activity statement .csv imports remain available.
Trade storageImported and synchronized executions stay in the local SQLite database on the computer.
Existing journalsThe database upgrades automatically by adding optional source fields; existing executions are not rewritten.
DisconnectingRemoving the IBKR connection keeps executions that were already synchronized.
Trading accessThe Flex connection is read-only and cannot submit, modify, or cancel orders.

Continue exploring SimpleTradeLog

Read the Interactive Brokers trading journal guide, follow the existing IBKR statement import workflow, review the product documentation, or see pricing.

Questions about IBKR Flex sync

Practical details for upgrading and maintaining the connection.

Will version 1.1.1 keep my existing trades?

Yes. The local database migration adds optional source fields without deleting or rewriting existing executions.

Do I need a new Flex Query for every sync?

No. SimpleTradeLog reuses the same saved Query ID and token until the token expires or is revoked.

Can I still import an IBKR file?

Yes. Direct Flex synchronization and supported TLG or activity statement CSV imports can be used alongside each other.

Can SimpleTradeLog trade through this connection?

No. The Flex connection retrieves reporting data only and cannot place, modify, or cancel Interactive Brokers orders.

Spend less time moving execution files

Connect IBKR Flex or keep your existing file-import workflow, then review net P&L, costs, calendar results, and trading statistics.

Download for WindowsMac (Apple Silicon)Mac (Intel)