thinkorswim Trading Journal: Account Statement, Multi-Leg, and the Schwab Migration

thinkorswim ships with a Monitor tab that has solid analytics for "how am I doing today / this week / this month" — daily P&L, position-level Greeks for options, basic per-symbol stats. Tax-time reports are good. As a quick scoreboard, it works.

Where it falls short for active journaling:

• No setup-level analytics. You can't tag a trade as "Globex PDC Long" or "Iron Condor IVR50+" and see efficacy stats per setup. Without setup tagging, you can't separate strategies that work from ones you keep doing out of habit.
• No per-trade journal entries. There's no place to write "what was I thinking?" alongside the trade — no notes, no mood, no lessons learned. Trade data without context is incomplete data.
• No R-multiple tracking. TOS shows P&L; it doesn't show whether a trade was a quality trade given the risk taken. R-multiple is the unit that separates quality from luck.
• No multi-leg position grouping in analytics. Combo orders execute as multi-leg in TOS but the position-level analytics don't cleanly separate "my iron condors" from "my naked short puts."
• No AI review. TOS analytics are static — they tell you what happened, not what behavioral patterns are emerging or what to focus on next.

TOS's primary export is the Account Statement — a CSV (or sometimes plain-text) file containing every transaction in your account over a chosen date range. This is the file your journal needs.

Step-by-step export

1. Open the desktop thinkorswim platform (the export feature is more complete on desktop than mobile/web).
2. Click the Monitor tab.
3. Click Account Statement on the left sidebar.
4. Set your date range. For first-time journaling, pull as far back as your account allows (often 2+ years). For ongoing journaling, weekly or monthly is typical.
5. Click the gear icon → Export to file.
6. Choose CSV format. Save somewhere you'll find it.

What's in the file

The Account Statement contains multiple sections — trade history, money movement (deposits/withdrawals), dividends, interest. The trade history section is what your journal needs. A good importer ignores the other sections automatically; less-good importers either fail or pollute your trade list with non-trade events.

For most TOS users, the recommended setup is: drop a backfill Account Statement covering all the history you care about, then export weekly going forward. ~5 minutes initial setup; ~30 seconds per weekly refresh.

1. Create a TradersForge account (free tier covers 50 trades/month for testing; Tracker tier from $9/mo unlocks unlimited trades and AI trade reviews).
2. Navigate to Import & Connect in the sidebar.
3. Drop the Account Statement CSV onto the import area. The thinkorswim adapter is auto-detected — no manual format selection.
4. TradersForge parses the trade history section, ignores money movement and dividends, and groups multi-leg combo orders into single positions automatically.
5. Review the imported trade list. Multi-leg structures (iron condors, verticals, etc.) appear as single positions with the structure type tagged.
6. For ongoing journaling, export a fresh Account Statement weekly and drop it in. TradersForge dedupes — only new trades since the last import get added.

Options journaling lives or dies on multi-leg grouping. An iron condor is FOUR fills (sell call, buy call, sell put, buy put) but ONE strategic position. If your journal shows the four fills as four separate trades, your per-strategy analytics are useless — you can't answer "what's my win rate on iron condors?"

How TOS combo orders work

When you submit an iron condor as a single combo ticket in TOS, all four legs share an order ID and get filled together. This is the GOOD case for journaling — the legs are linkable.

How TradersForge groups them

On import, fills sharing an order ID (or executed within a short window for orders that don't expose order IDs) get grouped into one position. The position is auto-tagged with the inferred structure type — iron condor, vertical credit spread, butterfly, calendar, diagonal, jade lizard, etc. — based on leg count, expiries, and strike layout.

What if you legged in manually?

If you built an iron condor by submitting each leg separately (instead of as a combo ticket), TOS sees them as four unrelated orders. TradersForge can still group them post-import via a manual link operation — or you can leave them as separate trades and tag each with a shared "iron condor" setup tag. The latter loses position-level analytics but keeps individual leg detail.

Setup tag (most undertracked field)

For every trade, tag the setup that generated it: "ORB Long," "Liquidity Sweep Reversal," "Iron Condor IVR40+," "Wheel on QQQ," etc. Then run win-rate and avg-R queries per setup. Almost every trader discovers that 2-3 setups account for ~80% of their profit, and the rest are net losers they keep taking out of habit.

IV rank at entry (options-specific)

For options trades, log IV rank at entry. Per-IV-bucket expectancy reveals patterns like "my iron condors only work above IVR 40" or "my long calls lose money above IVR 50." TOS doesn't track this in journal-friendly form, so it's a manual tag — but it's the single most valuable field for options journaling.

Daily journal entry

A few minutes of writing per session about: pre-market plan, what you actually did vs the plan, mood / sleep / focus, key lesson, focus for tomorrow. The correlation between "followed plan = yes" days and green days is overwhelming for most traders.

Per-trade emotional state

Confident, nervous, FOMO, disciplined, revenge, calm. Patterns surface fast — most traders find their FOMO trades are net losers, and disciplined trades produce the bulk of profit.

Account Statement includes non-trade events

Dividends, ACH transfers, interest payments, corporate actions — all in the same file as trades. A good adapter ignores them; a generic CSV importer can pollute your trade list. Verify your imported trade count against TOS's own count to confirm.

Time zones in the export

TOS Account Statement timestamps are in your platform-configured timezone, not UTC. If imported into a journal that assumes UTC, your trades end up at the wrong time. TradersForge detects and converts based on your user-preference timezone.

Assignment events

A short put that gets assigned at expiration shows up as an option close + a stock open — two separate transaction lines. Most journals handle the option close fine; some lose track of the resulting stock position. TradersForge tags the assignment relationship so the strategy lifecycle is preserved.

Futures fills mixed in

If you trade futures alongside stocks/options in TOS, those fills come through the same Account Statement. R-multiple uses the correct contract multiplier per asset class automatically. No separate import needed.