TradingView CSV Reconciliation for NQ and MNQ

A TradingView strategy CSV should let you explain the report one closed trade at a time. If the spreadsheet total disagrees, first check what each row represents, which trades are included, and whether you are comparing the same metric.

This guide builds a reconciliation worksheet for simulated strategy results. Every trade, price, fee, balance and outcome in the worked examples is hypothetical. None represents AORDS performance, a broker statement or an expected return.

1. Save the report and export as one evidence set

Download the trade list and save the corresponding report before changing settings. TradingView supports CSV export; its support page explains that exports from different report tabs contain different information. Interface labels can vary, so identify the trades export rather than relying only on a familiar button name. TradingView export instructions.

Give the files a shared run name. Add a settings note containing:

• Strategy version and inputs; exact exchange symbol and contract or continuous series.

• Timeframe, chart type, session, displayed timezone and timestamp convention.

• Test start and end, export time, and whether Deep Backtesting was enabled.

• Initial capital, account currency, sizing rules, commissions and slippage.

• Calculation and execution settings, historical bar detail, and any trade filters.

Check that the report column is for all trades if your worksheet includes both directions. Compare the earliest and latest included records, especially trades crossing a date boundary. Do not silently choose entry date in one file and exit date in another.

Also check coverage. As of October 8, 2026, TradingView documents retention of individual data for the latest 9,000 trades under the default testing range. This can restrict CSV contents without restricting Metrics totals. A different testing range enables Deep Backtesting and retains individual data for all trades. Document any coverage mismatch before expecting equal totals. TradingView trade-list documentation.

2. Separate event rows from realized results

Open the raw CSV without editing it. Inspect several complete trades in both the file and report. Map the actual headers to trade identity, entry or exit type, time, price, quantity, currency P&L and cumulative P&L.

If the export has paired entry and exit rows with the same trade result repeated, summing both copies doubles the outcome. Keep the raw rows, but include the realized result once in your calculation layer. An exit-row filter may work for that layout; verify it against the report before applying it throughout.

Do not blindly delete duplicate trade numbers. An identifier may group multiple records, and partial exits require their own quantity allocation. Create a stable worksheet key using the run, reported trade identity and relevant exit details. Check uniqueness at the level of the closed record you are reconciling.

TradingView defines Net PnL as the sum of closed-trade results, excluding open positions. That is the appropriate target for a realized-results ledger. Keep open P&L separately, and never sum a cumulative column as if each value were a new gain. TradingView Net PnL definition.

3. Copy this reconciliation worksheet

Use one calculation row per reported closed trade or closed portion, with links back to its raw records. Keep these field groups together:

1. Identity: run name, report trade number, worksheet key, entry signal, exit signal and direction.

2. Timing: original timestamps, normalized timestamps, entry time, exit time and date-filter decision.

3. Exposure: entry price, exit price, closed quantity, instrument point value and P&L currency.

4. Accounting: reconstructed price P&L, allocated commission, exported net P&L and explained difference.

5. Controls: inclusion flag, cumulative realized P&L, duplicate warning and source-row references.

For a long position, reconstruct price P&L as exit minus entry, multiplied by point value and closed quantity. Reverse the price difference for a short. CME explains the equivalent tick calculation: ticks moved multiplied by tick value and contract count. CME futures P&L explanation.

Use the filled quantity, not a default input or the largest position seen during the trade. If account and instrument currencies differ, resolve the report's conversion method before comparing cash amounts. Retain precision until the final display, and inspect decimal separators and negative-number formats during import.

4. Work through a hypothetical partial-exit ledger

MNQ has a $2 multiplier per index point and a minimum outright tick of 0.25 points, worth $0.50 per contract. CME MNQ specifications. See also our NQ and MNQ contract-size guide.

For this hypothetical ledger, assume USD accounting, no slippage and a $1 commission per contract per side. These fees are invented. Start flat, buy three MNQ contracts at 20,000, and close them in separate portions:

• Hypothetical portion A: sell one at 20,010. Price P&L is $20. Allocate $1 entry commission and $1 exit commission. Net result: +$18.

• Hypothetical portion B: sell two at 19,990. Price P&L is −$40. Allocate $2 entry commission and $2 exit commission. Net result: −$44.

• Hypothetical trade C: after becoming flat, sell one at 20,020 and buy it back at 20,000. Price P&L is $40, less $2 commission. Net result: +$38.

The hypothetical ledger totals $20 before commissions and $12 afterward: $18 − $44 + $38. Closed quantities reconcile with the quantities opened, and total allocated commission is $8. If each net result appeared on both an entry row and an exit row, summing every copy would incorrectly produce $24.

TradingView supports partial exits with specified quantities. Preserve the report's closed-record granularity when checking trade counts; grouping portions into a personal “setup” changes the unit being counted. TradingView partial-exit documentation.

5. Reconcile totals before interpreting statistics

Check included closed-record count, total net P&L and the final cumulative realized amount. Then compare winning and losing totals. TradingView's Gross profit and Gross loss use positive and negative net trade outcomes, with configured commissions already reflected. Do not subtract those commissions again. Gross profit; Gross loss.

For the hypothetical three-record ledger, positive net outcomes total $56 and the losing magnitude is $44. The resulting profit factor is approximately 1.27. Aggregating the two long portions into one setup changes the grouping and its statistics. Read our win rate, expectancy and profit-factor guide before comparing differently grouped samples.

Why drawdown may still differ

With hypothetical starting capital of $10,000, this ledger ends successive closed records at $10,018, $9,974 and $10,012. Its maximum closed-record drawdown is $44. Entry and exit records alone cannot establish the worst movement while positions remained open.

TradingView's intrabar drawdown uses adverse price movement during open positions and its documented reference-equity calculation. A closed-result worksheet lacks that path information. Compare named definitions before calling the difference an error. TradingView intrabar drawdown; closed-trade versus intraday drawdown.

6. Resolve the first mismatch

Sort by closing sequence and locate the earliest unexplained difference. Check its inclusion, quantity, price, commission and currency before inspecting later totals. Record the cause and rerun the same checks after correcting the worksheet.

A reconciled export establishes accounting consistency. For the separate question of execution, use our backtest-versus-live testing guide. Keep unresolved discrepancies visible rather than adjusting numbers until they agree.

Futures trading involves substantial risk of loss. This article is educational and does not provide personalized investment advice. Simulated results do not guarantee future performance.