Trade records and reconciliation
NinjaTrader Trading Journal
A NinjaTrader report can support a journal only if its account coverage, trade grouping and cost definitions are understood. Prepare a reconciled sample before adding manual review notes in Pineify.
Prepare a NinjaTrader Desktop report
- 1
Choose the report scope
In Control Center, select New → Trade Performance. Set the start and end dates and times, select the relevant accounts and instruments, and generate the report.
- 2
Choose what each row represents
Use Executions for individual fills or Trades for paired transactions. Keep the selected display and units with the file. Do not combine both views as though they describe additional activity.
- 3
Export and preserve the original
Right-click the generated report and select export. The current Desktop support article specifies CSV. Keep the original unchanged and work on a copy.
- 4
Compare with the brokerage statement
Check quantities, costs, open positions and missing activity before recording a sample manually. Pineify does not currently parse the exported file.
A performance report is not an official statement
NinjaTrader’s September 8, 2026 support article distinguishes server-backed NinjaTrader Brokerage/Tradovate account history from other connections that depend on the current installation’s local records. A report is not proof that every execution is present.
The article also says the displayed commission excludes NFA, routing and exchange fees. Reconcile those charges against the official live statement; a commission column alone does not establish all-in trading costs.
Keep fills, paired trades and review notes distinct
NinjaTrader’s performance guide describes scaled entries and exits as separate trades. It also warns that account-level pairing can combine executions from simultaneous strategies according to the overall account position. A strategy name alone is not a reliable allocation rule.
Keep execution IDs, quantities and position changes. Write down whether your review groups a scale-out as several closed trades or one position campaign. Apply the same convention before comparing win rates.
NinjaTrader already has Summary, Analysis and Journal displays, including notes attached to trades or executions. Use those native records as evidence. A separate journal should add a specific review process, not depend on the claim that the platform has no journal.
Convert futures price movement before subtracting costs
Fictional example in USD: two long contracts enter at 6000.00 and exit at 6001.50. Assume a 0.25-point tick and a 1.25-dollar tick value per contract. The move is six ticks, so gross P/L is 6 × 1.25 × 2 = 15.00. These are example specifications, not a contract lookup.
Assume four charged contract-sides at 0.60 each: two entries and two exits. Total costs are 2.40 and net is 12.60. Do not subtract them again from a result that is already net. Check the real contract month, multiplier, currency and statement charges before applying this method.
A generic price-difference-times-quantity calculation would give 3.00, not 15.00. If the receiving journal cannot represent the contract correctly, keep the reconciled calculation externally. This page does not add futures multiplier conversion to Pineify.
| Component | Calculation | Result (USD unless stated) |
|---|---|---|
| Price movement | 6001.50 − 6000.00 | 1.50 points |
| Ticks | 1.50 ÷ 0.25 | 6 ticks |
| Gross P/L | 6 × 1.25 × 2 | 15.00 |
| Total costs | 4 × 0.60 | 2.40 |
| Net P/L | 15.00 − 2.40 | 12.60 |
Define session labels before comparing them
For each session label, record the instrument, time zone, daylight-saving convention and start/end times. Decide whether a trade is classified by entry time, exit time or another rule. A position spanning two sessions needs an explicit policy.
Do not apply one equity-market schedule to every futures contract. Keep live, simulated and backtest observations separate. Session tags help organize a review; a small difference between groups does not establish a durable trading advantage.
Add information the execution record cannot explain
For one reconciled trade, write the setup, planned exit, reason for changing it and any unresolved statement difference. Keep the original execution evidence alongside the note rather than rewriting it to match the story.
Pineify supports manual trade records and notes. This guide does not establish automated session attribution, account synchronization, a NinjaScript-to-Pine conversion, or a guarantee about platform stability. No platform add-on is required for the manual workflow described here.
Frequently asked questions
Can Pineify import my NinjaTrader CSV?
Not currently. Import History is marked Coming Soon. Prepare and reconcile the report, then use manual entry only where Pineify can represent the instrument and costs correctly.
Does the NinjaTrader commission column include every fee?
The current Desktop support article says it excludes NFA, routing and exchange fees. Use your official statement to reconcile the full charges.
Should I export Executions or Trades?
Choose the level your review requires. Executions preserves individual fills; Trades presents paired transactions. Keep grouping consistent and do not count the two views as separate trading activity.
Does NinjaTrader already have a journal?
Yes. Its documented Journal display supports notes, including entries associated with a trade or execution. An external journal should provide additional review value.
Can I use one RTH schedule for all futures?
No. Define the relevant instrument schedule, time zone and classification rule. The page does not implement automatic session filtering or verify any specific exchange calendar.
Continue with a reconciled sample
For a manual review, use the Pineify Trading Journal after checking its current fields. For a separate spreadsheet, inspect the Excel journal template and its calculation assumptions. Neither path adds automatic broker import.
Review the general trade-import reconciliation checklist
Published by Pineify, which sells trading software. Instructions use the linked official documentation; examples are fictional reconciliation exercises. No live broker account or third-party import was used to validate this guide. A matching sample tests data handling, not future trading performance.