Updated June 2026 · R|Trader Pro desktop

How to Export Your Trades from Rithmic R|Trader Pro (2026)

Rithmic is the data feed and clearing route under most prop firms — Apex, MyFundedFutures, Take Profit Trader, Tradeify, Bulenox, and Earn2Trade all live on it. R|Trader Pro is the bare-bones execution UI that ships with it. It's also a real journal export source: the Statements window writes a clean per-fill CSV with millisecond timestamps, broken-out commissions, and exchange + clearing fees per row — the cleanest commission detail of any retail futures platform. The trap is that one R|Trader Pro login often spans several firm-issued accounts at once, and the export will silently mix them unless you separate by account ID first. Here's the clean path.

Independent reference, not Rithmic documentation. Aurafy is not affiliated with Rithmic, LLC or with Trading Technologies. Rithmic, R|Trader, and R|Trader Pro are trademarks of Rithmic, LLC. R|Trader Pro's UI varies by build, by firm-skin (Apex Trader, TPT, Bulenox, Tradeify, MFFU, and Earn2Trade each ship slightly different branded skins of the same client), and by what your FCM enables — the exact menu wording, export-dialog layout, and column order may differ on your install. Always verify against your current build before scripting against an export. We import the standard R|Trader Pro account-statement CSV; no Rithmic API connection, no credentials shared, nothing installed in R|Trader Pro.
Why export trades Export from R|Trader Pro Statements Multi-firm on one login Column reference 3 common pitfalls Cleaning the CSV for any journal Importing into Aurafy FAQ

Why you should export your trades (even though R|Trader Pro shows P&L)

R|Trader Pro displays your fills and a running P&L tape in its position panel. So why bother with a statement export?

Bottom line: R|Trader Pro has the best raw fill-and-commission data of any retail futures platform — exchange + clearing fees broken out per row. It is not a journal. That gap is exactly where a downstream tool earns its keep.

How to export trades from the R|Trader Pro Statements window

R|Trader Pro runs on Windows (Mac users go via Parallels, CrossOver, or a Windows VM). The export path is the same across the firm-skinned builds — Apex Trader, TPT-skinned, Bulenox-skinned, MFFU-skinned, Tradeify-skinned, Earn2Trade-skinned R|Trader Pro all expose the same Statements interface from the underlying Rithmic client. Here's the clean path:

1
Open the Statements window.

From the main R|Trader Pro toolbar: Account > Statements (or the equivalent Statements button on the navigation bar in your build). On some firm-skinned builds the menu reads Reports > Statements. The window has tabs along the top — typically Open Positions, Executions (or Trades), P&L Summary, and Commission Summary. The Executions tab is the row-per-fill ledger and the one you export for a journal.

2
Filter by account, symbol, and date range.

The Statements header has filter controls for Account, Symbol, and Date Range. Pick a single account from the dropdown, not "All Accounts." If you trade multiple firms under one R|Trader Pro login (Apex + MFFU + TPT, etc.), each is a separate account ID and you want one export per account ID — see the multi-firm section below. Set the date range to your evaluation window or payout cycle. The grid updates live as you change filters.

3
Right-click in the grid → "Export to CSV" (or use the toolbar Export icon).

Most R|Trader Pro builds expose two export paths: the right-click context menu inside the grid (Export to CSV…) and the toolbar Export icon at the top of the Statements window. The right-click version respects the active tab and current filters. The toolbar version sometimes prompts for a tab and date range again — accept the same filters you set in step 2.

4
Pick CSV (not PDF) as the format.

R|Trader Pro can export Statements as PDF or CSV. PDF is fine for tax archive; for any journal import, you want CSV. If your build only shows PDF in the dropdown, the CSV button is usually a separate icon — check the toolbar before settling. Re-exporting a PDF as CSV in a downstream tool is a quality loss vs. exporting CSV directly.

5
Open the file and confirm row count + account ID.

Open the CSV (Excel, LibreOffice, or any text editor) and compare the row count against the Executions tab's total. Verify the Account column shows a single account ID — if it shows two or more, you selected "All Accounts" in step 2 and your firm rule tracking will silently get the wrong preset on the wrong rows. Re-export per account if so.

The multi-firm-on-one-login workflow — Rithmic's unique shape

This is what makes Rithmic different from Tradovate, NinjaTrader, and Sierra Chart. A single R|Trader Pro login often spans several firm-issued accounts at once — an Apex 4.0 100K eval, an MFFU Core 50K funded, a TPT PRO+ 50K, and a Tradeify Growth 100K can all be active under the same Rithmic username + password. Each one is a different account ID, comes with a different rule set, and the statement export covers all of them in one file if you don't filter.

For Aurafy users: the Rithmic import handles this for you — assign a firm + plan preset to each account ID once at import (Apex 4.0 100K, MFFU Core 50K, TPT PRO+ 50K, Tradeify Growth 100K, etc.) and Aurafy applies the correct trail / DLL / consistency math per account from that point on. A single drag-and-drop of the all-accounts CSV ends up with three independent rule trackers, one per account.

CSV column reference (Executions / Trades tab)

Column names and order vary by R|Trader Pro build and by firm-skin. These are the fields that consistently appear in the standard Executions export — verify yours and map them to whatever tool you import into.

Column (typical name)What it meansWhy it matters
Trade Date / TimeTimestamp of the fill, in the timezone configured in R|Trader Pro Settings > GeneralR|Trader Pro defaults to your PC clock's local time on most installs but some firm-skinned builds default to US/Central (Rithmic's home timezone). Verify before importing or every overnight session looks one day off
AccountThe firm-issued account ID (APEX-XXXXX, MFFNNNNN, TPTNNNNN, etc.)This is the column that decides which firm preset applies. Split the file by Account before any rule math
SymbolRithmic symbol format: root + month code + 1-digit or 2-digit year (ESM6, ESM26, NQU6, MESZ26)Rithmic's 1-digit-year format collides every decade (ESM6 means both 2016 and 2026). Most modern builds emit 2-digit years; if yours doesn't, treat the year as ambiguous and key off Trade Date
SideB / S or BUY / SELL at the fill levelSide at the fill level, not at the round-turn level — a Long round-turn shows as Buy entry fill(s) + Sell exit fill(s), not "Long" anywhere
QtyContracts in the fillFor a 5-lot entry filled in 3 pieces (2 + 2 + 1), this is 2, then 2, then 1 on three separate rows. Aggregation to round-turn happens later
Price / Fill PriceActual fill price on the exchangeRithmic does not separately report a "requested" price (R|Trader Pro is execution-only — the requested price lives in your charting platform, not here). Slippage analysis requires correlating the chart-side order against this fill price
CommissionPer-fill commission charged by the FCM (your prop firm's clearing-side commission)R|Trader Pro is the only retail futures platform that breaks this out per-fill rather than summing at the account level. Commission rates are firm-specific and can vary by program
Exchange FeePer-fill exchange fee charged by CME / CBOT / NYMEXExchange fees are flat per contract and vary by product (ES vs MES vs CL vs NQ). They are not a percentage of P&L — high-frequency strategies eat them disproportionately
Clearing FeePer-fill clearing fee (often $0.04–$0.12 per side depending on FCM)The third leg of the all-in cost stack. Sum Commission + Exchange + Clearing for true round-turn cost. Generic "$1.50/side" estimates undercount by 20–40% on most prop programs
NFA FeeNational Futures Association regulatory fee (very small — typically $0.02 per side)Present on most US-FCM-routed exports. Roll it into the all-in cost row; don't analyze separately
P&L / Net P&LGross or net per-fill P&L where Rithmic has computed itSome builds emit per-fill P&L (FIFO-matched server-side), some only emit a running net at the bottom. If yours doesn't compute round-turn P&L, you'll compute it downstream from fill price + side + qty
Order IDRithmic's internal order ID for the fill chainTwo fills with the same Order ID are partials of the same logical order — that's how you collapse a multi-fill 5-lot entry into one logical entry side. Round-turn pairing is FIFO across Order IDs within the same Account + Symbol
Quick test: open the file and filter to a single Account + single Symbol and sum (signed) Qty (BUY positive, SELL negative). The result should be zero for every day you closed flat. If it isn't, you either have open positions, your filter is wrong, or the export missed rows.

The three quiet pitfalls

Most "my Rithmic numbers don't match my journal" tickets trace back to one of these three.

1. Partial fills are each a row (and inflate your trade count)

Rithmic emits one row per fill, not one row per order. A 5-lot entry filled in three pieces and exited in two ends up as five rows in the CSV — that's one round-turn trade, not five. Naive journals (or your own Excel) that count rows as "trades" report your trade count and win rate badly wrong on any session where size or partial fills were involved.

Fix: always group fills into round-turns before counting trades. Group by Account + Symbol, sort by Trade Date/Time, walk through the fills FIFO matching Buys to Sells (or shorts to covers) until the net position returns to zero — that's one round-turn. Aurafy's Rithmic import does this automatically with FIFO matching per Account + Symbol. If you're scripting it yourself, the key invariant is: round-turn closes when cumulative signed Qty hits zero.

2. "All Accounts" exports silently mix firm presets

R|Trader Pro's Account filter defaults to "All Accounts" on most builds. Exporting with that default produces a CSV that mixes — for example — your Apex 4.0 eval, your MFFU Core funded, your TPT PRO+, and your Tradeify Growth into one file with the Account column as the only differentiator. Every downstream analysis that doesn't split by Account first applies the wrong firm rules to the wrong rows: Apex's 30% consistency to MFFU rows, MFFU's no-DLL assumption to Apex rows, TPT's phase-shifting trail mechanic to a Tradeify Growth eval. The math comes out clean and silently wrong.

Fix: in step 2 of the export, pick a specific Account from the dropdown — one export per Account is the safest workflow. If you do an "All Accounts" export, the very first step downstream must be splitting the CSV by the Account column into one file per account before any rule math runs. Aurafy handles this automatically (you tag each Account ID with its firm preset once at import) — the manual split is only needed if you're working in Excel or another generic journal.

3. R|Trader (basic) and R|Trader Pro are different — the basic version may not expose Statements export

Rithmic ships two desktop clients with confusingly similar names: R|Trader (the older, lighter-weight version) and R|Trader Pro (the modern, full-featured version with Statements, multi-account, and the full export workflow). Some FCMs default-install R|Trader on a new account; some firm-skinned builds (Apex Trader, TPT Web, MFFU's R|Trader Pro skin) only ship R|Trader Pro. If your install doesn't have a Statements window with an Executions tab, you're probably on the basic R|Trader and need to install or request R|Trader Pro through your firm.

Fix: open the application's About dialog (Help > About) and verify the build is R|Trader Pro, not R|Trader. If it's basic R|Trader, your firm's support team can install Pro free for funded traders — every Rithmic-routed prop firm we've researched (Apex, MFFU, TPT, Tradeify, Bulenox, Earn2Trade) makes R|Trader Pro available. Don't try to extract trade data from basic R|Trader for any period longer than a single day; the statement view is too limited.

Cleaning the file before import

R|Trader Pro CSVs go in cleaner than NinjaTrader's or Sierra Chart's — there's no Modify/Cancel noise, no separate Orders/Trades/Executions tabs to reconcile, and the commission columns are already broken out per row. The cleanup is mostly account-splitting and round-turn pairing:

  1. Split by Account. If the export covers more than one Account ID, split into one CSV per Account. Every subsequent step is per-account.
  2. Verify the timezone. Open the file, pick a fill you remember taking, and check the timestamp matches what you remember. R|Trader Pro's default timezone varies by build — verify before assuming local time.
  3. Pair fills into round-turns. Sort by Trade Date/Time within each Account + Symbol, walk through fills FIFO, close a round-turn each time cumulative signed Qty returns to zero. Compute the round-turn P&L from volume-weighted entry vs volume-weighted exit, signed by direction.
  4. Sum all three cost columns. All-in cost per round-turn = Commission + Exchange Fee + Clearing Fee + NFA Fee (if present), summed across all fills in the round-turn. Net round-turn P&L = Gross round-turn P&L − All-in cost.
  5. Normalize the timestamp. Convert Trade Date/Time to ISO 8601 with an explicit timezone offset (2026-06-02T13:30:00-05:00). Especially important when the export crosses DST boundaries.
  6. Map symbol to root. Add a root column derived from the symbol (ESM26ES, MESZ26MES). All cross-quarter analysis groups by root.
  7. Don't lose the raw rows. Keep the original R|Trader Pro CSV archived alongside the cleaned round-turn file. The fill-level data is what you'll need for any future slippage or partial-fill audit, and it's what your firm's compliance side may also reference if there's a payout dispute.

Or skip all of that — drop the file into Aurafy

Aurafy's Rithmic / R|Trader Pro importer reads the standard Executions CSV (single-account or all-accounts), splits by Account ID, pairs fills into round-turns using FIFO matching per Account + Symbol, sums commission + exchange + clearing + NFA fees into one all-in cost per round-turn, normalizes the timezone, maps Rithmic symbols to roots, and applies the correct firm preset per account (Apex 4.0, MFFU Core/Rapid/Pro, TPT, Tradeify Growth/Select, Bulenox Option 1/2, Earn2Trade). The trail-DD floor, consistency-rule ratio, and DLL headroom compute independently per account from there. Free tier — 1 account, 30 days of history, no card required.

Start importing free More on Aurafy + Rithmic

While you're cleaning up the data — track the rules too

Once your Rithmic trades are in a journal, a few free Aurafy tools layer prop-firm rule math on top of any trade history — no signup required:

FAQ

Does R|Trader Pro have a built-in journal so I don't need an export?

The P&L Summary and Commission Summary tabs in the Statements window give you account-level totals — gross, commissions, net — but they don't tag setups, don't compute R-multiples, don't show charts, and don't track prop-firm rules. For account-balance monitoring it's fine; for learning your edge across months, it's not enough.

What R|Trader Pro build do I need to export Statements?

Any modern R|Trader Pro build (any release in the last few years) has the Statements window with Executions / Trades / P&L Summary tabs. If your install doesn't, check Help > About — you may be on the older R|Trader (basic), not R|Trader Pro. Every firm we've researched (Apex, MFFU, TPT, Tradeify, Bulenox, Earn2Trade) makes R|Trader Pro available free for funded traders — request it through your firm support if needed.

Can I export via the Rithmic API instead of the CSV?

Yes — Rithmic's API supports execution history pulls and is what every prop-firm-side reporting dashboard uses under the hood. For one-off journal exports the CSV is the right path (no API key, no credentials shared, takes 30 seconds). For automated nightly exports into a long-term database, the API is the right answer but it's overkill for any individual trader. Aurafy and most journals import the standard CSV — not API-pulled data — so the two flows don't compete.

Why does my exported P&L not match what my prop firm's dashboard shows?

Three reasons usually. First: prop-firm dashboards apply the firm-specific commission rate (which is in the R|Trader Pro CSV — but the firm's dashboard may be using a different cached rate from your account-setup-time vs the live rate). Second: the firm dashboard may include or exclude swap/funding fees that R|Trader Pro reports separately. Third: time-of-day cutoff differences — the firm's "trading day" may end at 4:00 PM CT while Rithmic timestamps the fills in your local zone. None of these are bugs; they're reconciliation gaps you fix downstream.

What about firm-skinned R|Trader Pro — Apex Trader, TPT Trader, Bulenox Trader, MFFU Trader?

All of these are the same underlying Rithmic client with a firm-issued skin (different logo, different color scheme, sometimes a custom landing page). The Statements export path is the same across all of them. The Account column will show the firm-issued account ID, which is the same one your firm dashboard uses. If your firm-skinned build's menus look slightly different, the export is still under Account > Statements or Reports > Statements — Rithmic doesn't let skins move that menu.

Does the export include cancelled or rejected orders?

The Executions tab is fills only — Rithmic does not log cancels or rejects there. If you want order-level activity (cancels, modifies, rejects), the Orders tab in R|Trader Pro is a separate view, and it's screen-only on most builds (no CSV export). For journaling you only want fills, so this is the right shape; for bracket-discipline audits you'd watch in real-time or use your front-end platform's order log.

Can I include chart screenshots or trade notes in the export?

No. R|Trader Pro's Statements export is column data only — no screenshots, no chart annotations, no notes. If you need screenshots tied to trades, capture them outside R|Trader Pro (Aurafy's recorder is one path) and key them by entry timestamp in your journal.

What if I'm front-ending Rithmic with NinjaTrader, Sierra Chart, Quantower, or MotiveWave?

You have two valid import paths — the platform-side CSV (NinjaTrader 8's Trade Performance export, Sierra Chart's Trade Activity Log, Quantower's or MotiveWave's positions export) or the R|Trader Pro Statements CSV. Both contain the same fills. Most multi-firm traders prefer the R|Trader Pro statement because one export covers every account on the platform. Single-firm traders often find their charting platform's CSV cleaner because it has chart-side context (timeframe, setup tag if you added one). Either is fine; pick the one your downstream tool reads more cleanly. See our NinjaTrader 8 export guide and Sierra Chart export guide for the platform-side paths.

What about Topstep traders — does this apply?

No. Topstep moved off Rithmic in 2024 — Topstep funded accounts run on TopstepX (web platform) or NinjaTrader 8 with the TopstepX DLL, not on R|Trader Pro. If you're Topstep, the Tradovate export guide covers TopstepX (which uses Tradovate-style fills) and the NinjaTrader 8 export guide covers the NT8-DLL path. See our Rithmic broker page for the multi-firm-on-Rithmic-NOT-including-Topstep workflow.

Free trading journal that actually reads R|Trader Pro statements cleanly

Aurafy imports the standard R|Trader Pro Executions CSV (single-account or all-accounts), splits by Account ID, pairs fills into round-turns with FIFO matching, sums commission + exchange + clearing + NFA into one all-in cost per round-turn, normalizes the timezone, maps Rithmic symbols to roots, and applies the correct firm preset per account. Apex / MFFU / TPT / Tradeify / Bulenox / Earn2Trade rule tracking included. Free tier — 1 account, 30 days history, no card.

Start free — no card See pricing