Three checkpoints in this guide
Follow the full walkthrough in order, or jump directly to one of its main sections.
Start with the specific Apex account you traded and the specific record of executions or closed trades you can actually export. Do not start with a screenshot of a balance and ask an AI to explain your edge. The balance is a useful reconciliation target, but it cannot say whether a profitable day came from one planned trade, five partial fills, a different account, an adjustment, or a result before commissions.
There is another easy mistake: “Apex” does not identify one universal data feed. Apex describes Rithmic, Tradovate and WealthCharts as separate platform/account choices. The steps below concern an Apex account using Rithmic and a file whose structure matches a supported TSB profile. If your account is on Tradovate or WealthCharts, do not rename its export “Rithmic” and expect the right interpretation. Use the route for the actual source and account.
What each screen can prove
The Apex dashboard guide describes account-specific summaries, a trading-details view and daily P&L charts. It also says some charts update nightly. A daily chart tells you how a day ended; it does not independently reconstruct your entry, scale-out and exit. Apex's Rithmic commission guide separately explains the R Trader Performance tab's gross trade P&L, commission and net result. It is a useful check when the journal's net figure differs from the screen.
| Evidence you have | What it can answer | What it cannot establish on its own |
|---|---|---|
| Apex account dashboard | Which account/plan and day-level status are selected | Exact sequence of fills or one setup's net result |
| R Trader performance/closed-trade report | Recorded closed result and sometimes gross, commission and net | Every order state or an unreported stop/plan |
| Completed-order export | Which orders filled, cancelled or remained unfilled | That each order is one finished trading idea |
| Fill-history export | Timestamp, direction, quantity, price and account of executions | A complete position if its opening fill is outside the file |
| Journal after reconciliation | Comparable closed ideas, tags, sessions, execution changes | The firm's real-time rule state unless the exact rule and intraday evidence are also supplied |
The phrase “download your Rithmic CSV” is too vague to be useful. A file can be an orders table, a fills table or a closed-trade summary. TSB has profiles for several named variants; it does not infer the missing rows from the word Rithmic in the filename. Check the import preview's detected source and the chosen account before accepting a result.
Completed orders are not completed trades
Imagine a futures trader places a buy order for two contracts, receives one fill, cancels the remaining quantity, and later exits the one open contract in two partial fills. The first order has a “completed” life cycle, but the trading idea is not complete until the open contract has been closed. The cancel is an order event, not a P&L event. Depending on the report, a position may span multiple order numbers and multiple fills. Counting each row as a win or loss manufactures a win rate.
This is why the first preview should separate unfilled working orders from actual fills and show which fills form a closed position. A working or cancelled remainder is not another trade. A sample file can demonstrate that boundary, but your own account's quantity and result still need to match R Trader before you trust a win rate.
For your own file, check at least one obvious round trip by hand:
- Match the account identifier and the exact MNQ/NQ/ES/etc. contract, including expiry. A different expiry or another funded account is a separate history.
- Separate
Working,Cancelled,Rejectedand other nonfilled states from rows whose quantity actually filled. A submitted order with zero filled quantity is not a trade. - Order fills by their actual execution time and keep both buy/sell direction and filled quantity. A partial close should leave the correct open remainder.
- Compare the reconstructed gross result with the platform's result for that position. Then inspect fees and net once, without subtracting commissions twice.
- Look for an opening leg before the selected date range. If it is missing, the file cannot safely explain the later closing fill; expand the export window instead of guessing an entry.
Different Rithmic reports can show orders, fills or closed results, so use the report suited to your question. TSB supports specific exports, not every file called “Rithmic CSV.” If the preview cannot identify the source or a familiar trade does not reconcile, keep the original report and resolve that gap before analyzing the strategy.
Why gross P&L and your account balance differ
Apex gives a concrete Rithmic example: one NQ contract is opened and later closed, so there are two commission-charged sides. Their illustrated gross loss is $30; a total $3.98 commission makes the net loss $33.98. The durable lesson is not that every account will pay $1.99 a side forever. It is that a trade report's gross number and the account's net change are different measures, and the fee must be attributed exactly once.
The decision can reverse across a small cohort. Suppose, hypothetically, three separate one-contract NQ round trips show gross results of +$2, +$7 and −$4. If the actual statement for each of those trades confirms the same $3.98 round-trip commission used in Apex's illustration, the bridge is:
| Planned trade | Gross result | Confirmed commission in this example | Net result |
|---|---|---|---|
| First | +$2.00 | $3.98 | −$1.98 |
| Second | +$7.00 | $3.98 | +$3.02 |
| Third | −$4.00 | $3.98 | −$7.98 |
| Three-trade cohort | +$5.00 | $11.94 | −$6.94 |
Two of three gross results are positive, but only one of three net results is. That is a useful reason to inspect small winners before calling the setup profitable; it is not a performance estimate or current fee quote for any Apex account. If one trade used MNQ, scaled to two contracts, or was charged a different rate, replace this illustration with its exact source amounts. If the exported trade result is already net, do not deduct the commission again.
In a journal, first ask whether the platform's result is already net of fees. Compare one known trade's gross, commission and net with R Trader; do not subtract the same charge twice or add a cash adjustment as a fake market trade just to force the balance to match. A small discrepancy can change the verdict on a strategy built from small winners.
Apex's dashboard guide also distinguishes account types and daily trading details. Keep evaluation and PA/funded histories separate, even when the symbol and strategy are the same. Differences in account rules, size and trading days can make an aggregate equity curve look persuasive while hiding the stage that actually caused the problem. For prop-rule and payout eligibility, use the current plan's official dashboard and terms. A file of closed trades is retrospective evidence; it is not a live risk monitor and may not show the intraday high/low path relevant to a trailing threshold.
Turn normalized fills into a repeatable decision
Once the imported result reconciles, the useful question becomes narrower than “Did I make money?” Compare like with like: same contract family, similar size, account stage, session and setup. A positive morning sample on MNQ should not be casually combined with a larger NQ afternoon sample. A planned partial take-profit should be evaluated as one trading plan or as explicitly named closed pairs; either denominator is defensible if it is stated and the cash total reconciles. Without that distinction, “win rate” can improve merely because one trade was split into more rows.
Add what the platform export usually does not know: your planned risk, setup label, reason for entry, whether the exit followed the plan, and the screenshot or note that explains an exception. Then ask whether a pattern survives outliers and fees. A trader may discover that a profitable first target is regularly erased by discretionary re-entry, or that the best-looking setup depends on one unusually large winner. Those are hypotheses for the next set of trades, not proof of a future edge.
TSB AI Coach becomes valuable after the data is trustworthy. Its current architecture gives the model bounded, server-calculated observations from the selected user's trade history, with lens-specific evidence and limitations. It can contrast setups, sessions, fees, execution and data quality instead of offering generic trading advice. It is not fine-tuned into a private model by uploading one CSV. A useful prompt is: “In this Apex Rithmic account, which closed setups remain positive after recorded fees, and which specific trades drive the difference?” If the fee column or opening leg is missing, the answer should surface that limitation. Do not treat a confident sentence as a replacement for reconciling the source file.
A second, often more useful question is, “Are my small gross winners still winners after Rithmic commissions?” To answer, the selected Apex account and plan stage must be fixed; each completed idea needs its original gross result and fees once, and a working or cancelled order cannot enter the denominator. A useful analysis would show the count of gross-positive ideas that became net-negative, the total recorded fee drag and the exact trades behind that observation—if those fields are verified in the selected source. If one profile supplies only already-net P&L and the companion cash rows cannot be matched, the answer should not subtract an estimated per-side rate a second time. A current fee schedule is a hypothesis to cross-check, not a replacement for the account's charged amounts. The next action might be reviewing whether a narrowly positive setup justifies its trading costs on more comparable trades—not buying another prop challenge on the strength of an AI sentence.
If you are shopping for a program rather than analyzing your own account, the Apex review and payout-rules guide own that decision. This guide cannot tell you Apex is the best firm from your trading history alone. It can help you understand whether the account you already used produced a repeatable, properly costed result and what to test next. Check TSB's supported sources for the current file route; if your export is not recognized, keep the original and request an exact profile check rather than adjusting the CSV until the warnings disappear.
Quick answer
Can I analyze an Apex Rithmic account in a trading journal? TSB recognizes specific Apex/Rithmic export layouts, but first preview your file and reconcile one familiar position with R Trader. Exclude orders that never filled, combine partial fills into the intended position, and compare gross, commission and net before judging a setup. TSB AI Coach can review patterns in validated history; a closed-trade file cannot prove live prop-rule safety.
