NinjaTrader 8 Trade Export Explained: Executions vs Trade Performance

Two files can come from the same platform, cover what looks like the same week and still produce different-looking records. That is the source of confusion when you export from NinjaTrader 8. The Executions tab describes individual executions; the Trade Performance Trades tab presents completed trading activity in a different form. Neither should be chosen because its total looks familiar. Start with the report your journal supports, keep the account and dates consistent, and check what each row represents. Understanding that distinction lets you investigate differences without blaming your trading, your memory or a missing decimal before checking the source.

Why NinjaTrader has more than one export

You need different views while trading and reviewing. Sometimes the question is what executed at a particular moment. Sometimes it is how a completed trade performed. Those questions require different arrangements of the same underlying activity. The existence of two exports is therefore not a contradiction. Trouble begins when you expect their rows to mean the same thing, or when you choose a report without knowing which kind of record the receiving journal is designed to read.

The documented supported path is the NinjaTrader 8 Executions tab, exporting the grid as CSV. The Trade Performance Trades tab is listed as Beta because the exported columns depend on which columns are visible. That status distinction concerns the specific file being read. It does not mean one platform screen is useful and the other is useless. It means you should check the report's contents and compatibility instead of relying on the platform name alone.

Imagine reviewing a position that you entered once, added to later and exited in several pieces. You may describe it as one trading idea. An execution view must still record the individual events that built and closed it. A performance view can present a more condensed picture of the completed activity. If you compare row counts without allowing for that difference, you can convince yourself that trades are missing when the two files are merely organising the history differently.

Before exporting, decide what you are trying to preserve. For a journal that rebuilds positions from fills, the execution detail is the raw material. For a quick review of completed results, a trade-oriented report may feel easier to read. Familiarity is not the only criterion. The export must contain the fields needed for the job that follows. A concise summary cannot always replace a fuller record when the question concerns a partial exit or a repeated execution.

Keep the report type visible in your own records. Naming every file after the platform makes it harder to remember which source produced a particular import. Distinguish Executions from Trade Performance and identify the account and period. This is especially helpful when you revisit a discrepancy weeks later. You want to answer a specific question about the original report, not reconstruct what you might have clicked while tired after the close.

You can use both views without importing both as if they were additional trades. One can be the documented source for your journal, while the other helps you inspect or compare the activity. The important boundary is knowing which file created the journal's positions. Keep that source consistent, and use other reports as checks. Otherwise, a useful second perspective can become a confusing second set of records describing the same trading decisions.

What an executions export records

An execution is an event in the life of a position. It tells you that some quantity traded at a price and time, rather than summarising what you ultimately made on the complete idea. Several executions can belong to one position. This detail is valuable when you want to see the order of entries, additions and exits. It also explains why a file containing many lines may represent fewer finished trades than the line count suggests.

Use the Executions tab and export the grid as CSV, as described in the help documentation. Keep the original file unchanged while checking it. The exact menu names beyond that documented path are not needed to understand the workflow. What matters is that you have the executions export, not a similarly named summary or a copy with important columns removed. Confirm the report before interpreting any result produced from it.

Quantities provide an important way to follow the activity. If you added to a position and reduced it gradually, compare the pieces rather than expecting one entry row and one exit row. Each execution contributes to the completed position. A missing piece may change the apparent size or leave the closing activity incomplete. Reading the sequence with quantities in mind is often more informative than staring at the total profit and trying to guess what disappeared.

Repeated executions are another useful distinction. The import skips a repeated execution rather than counting it again. That allows an export to overlap with activity already present without automatically treating the repeated record as another execution. Still inspect the preview when you bring in a wider range. Duplicate handling protects against repeated records; it does not prove that the account, dates or report type you selected were the ones you intended.

Time deserves attention alongside price and quantity. A late-session execution can fall on a different futures trading day from the calendar date you first associate with it. Sunday-evening activity belongs to Monday under the trading-day convention used here. When the same execution seems to appear on a different day, compare the timestamp and the day's boundary before changing the record. A date interpretation can create an apparent discrepancy without any execution being absent.

For a practical check, choose a position whose sequence you remember clearly. Find the initial entry, any additions, any partial exits and the final exit. Compare that history with the preview before confirming the import. You are not trying to memorise every execution in a busy week. You are testing whether the file is being read in a way that reconstructs actual positions sensibly. If the familiar example fails that test, stop and investigate the source.

What the trade performance report rolls up

The Trade Performance Trades tab gives you a trade-oriented way to review activity. That can feel closer to the journal entries you want to read at the weekend. The key difference is that a completed-trade view has already organised activity before you export it. You should therefore inspect what one row means rather than assuming it is interchangeable with an individual execution. A useful summary answers a different level of question from the events that produced it.

The Supported platforms page lists this file as Beta. Its columns depend on what you leave visible, so two exports from the same screen may not contain the same information. Before exporting, show the entry, exit, time, profit and commission columns. Those are the fields named in the documentation. A file missing a necessary column should be corrected at the source instead of repaired by guessing values after you have imported it.

Column headings matter because they tell the receiving system what each value represents. A number that looks like a profit could refer to a different measure than the one you expect. A time could describe one part of the trade rather than every execution inside it. Read the heading and the associated activity together. If you cannot tell what a row is summarising, do not rely on its apparent similarity to the journal's finished trade card.

A trade-oriented export can be convenient when the necessary fields are present and the preview is right. Its convenience should not become a reason to overlook missing detail. When you are investigating a scale-in or several partial exits, the execution history remains useful because it describes the individual events. Keep access to that original detail even if your regular review prefers a condensed view. Summary and detail work best as complementary records rather than competing truths.

Be consistent about which report supplies the imported trades. Alternating between a detailed export one day and a summary another can make it harder to diagnose an unexpected result. The question becomes not only what happened in the account, but also how different source files described it. A repeatable source simplifies that investigation. If you change your normal export, test the new report against a familiar period before making it the foundation of future reviews.

The preview is particularly important for a Beta file. Look for the expected entry, exit, time, profit and commission information on a recognisable trade. If the values are missing or surprising, return to the visible columns and the original report. Do not confirm simply because the platform name is recognised. Compatibility is about the particular data in the file, and your review will be only as dependable as the activity that file actually contains.

When the two disagree, and why

First decide whether the reports truly disagree or simply present different levels of detail. Four execution rows and one completed position are not automatically inconsistent. Compare quantities, timing and the full entry-to-exit sequence before comparing counts. If the activity can be followed from one view into the other, the difference may be an arrangement of information rather than a missing trade. This first distinction can save you from investigating a problem that is not there.

Next confirm that both reports cover the same account. Similar trading across accounts makes an accidental mismatch harder to notice. A familiar symbol and a nearby entry time can look convincing even when the rows belong to a different book. Do not compare totals until that basic identity is established. One report showing one account and another combining or selecting different activity will not become comparable just because the dates at the top look similar.

Date boundaries are the next place to look. An entry can precede the selected range while its exit falls inside it, or the final execution can arrive after an earlier export was saved. Compare the beginning and end of the period, not only the trades in the middle. The futures trading day adds another boundary to understand. A difference near the evening roll is a reason to inspect timestamps rather than immediately assigning a new date by hand.

Then examine fees. One report may be showing a gross result while the number you are comparing has commissions deducted. A difference in what is included can look like a disagreement in the trades themselves. Read the report's fields and check the statement before deciding which number should match. Avoid changing a fee setting only because doing so makes two totals meet. Agreement is meaningful when the treatment is correct, not when a convenient adjustment produces it.

If you still have a difference, isolate a single completed position. Compare the execution quantities and prices with the entry, exit and profit information shown in the trade-oriented export. Work forward from the underlying activity instead of backward from the total you wish to see. That approach helps identify whether the question concerns an omitted record, a summary interpretation or a cost. It also gives you a clear example if you need help checking the file.

Keep a short record of what you have ruled out. You might already have confirmed the account and period, but still need to check commission handling. Without that note, it is easy to repeat the same checks each time you reopen the problem. Leave unresolved activity unresolved until you can explain it. A tidy-looking total created through several uncertain changes is less useful than an honest difference with a specific next thing to investigate.

Commissions in the export versus on your statement

Commissions are not an optional detail when you assess a trading result. They change what you kept from the activity, and they can explain why a gross total looks better than the account. Start by checking whether the export actually contains commission values. The presence of a column is not enough if its entries are empty. Inspect the actual entries rather than assuming that a familiar heading means every relevant charge has been recorded in the file.

If your file includes commissions, those figures provide a starting point for checking costs. If fees are missing, the platform's fee schedule can supply them. This distinction matters when you investigate a difference. Review whether the original export contains the charges you expected and check the fees shown on the resulting trade. Do not guess how an unclear entry was interpreted; preserve the file and investigate the specific value before changing the record.

Compare the result with your statement using the same scope. A single trade's commissions should not be compared with every charge appearing over a longer period. Nor should a day's gross result be expected to equal a daily figure after costs. Suppose, as a hypothetical example, your trading result before fees is $200 and the relevant trading fees are $40. The resulting $160 figure describes the same activity after those costs, not a different set of trades.

Do not assume that a commission value in one export is a complete explanation of every charge on a statement. Read how the costs are presented and distinguish trade-related fees from other account charges. You are trying to understand what the daily trading result includes. If another cost is recorded separately, keep that distinction visible instead of forcing it into a field merely to make a comparison look tidy. A clear definition is more useful than a matching number without one.

When the gap looks exactly like the commissions you expected, use that observation as a lead. Check whether one side includes them and whether the other leaves them out. Then confirm the values and the period. A familiar-sized difference can still have another cause, especially when several errors offset each other. The safest conclusion comes from following the recorded activity and costs, not from recognising an amount and stopping the investigation at the first plausible story.

Once you establish the correct handling for your usual file, keep the process consistent. Save a note about which export you use and what its Commission column contains. Recheck that assumption if the report changes or if the preview begins showing unexpected charges. Your goal is not to think about commissions endlessly. It is to make sure they are included correctly so your attention can return to the trading habits revealed by the result after fees.

Exporting more than one account cleanly

Start by treating every account as a separate source, even when you trade the same contracts in each. The account identity tells you where an execution belongs. It is not a minor label to fix at the end. Confirm the account before exporting and again before importing. A trade placed in the wrong book can make two accounts look wrong in opposite directions, which is harder to understand than one clearly incomplete report.

Use a naming habit that distinguishes account, report and period. You do not need an elaborate filing system or a special application to do this. You need enough information to identify a file without opening several nearly identical downloads. A plain, consistent convention is easier to maintain on a tired evening than a complicated hierarchy. Choose something you can keep doing when the week is busy and the trading result is disappointing.

Do one account from export through preview before moving to the next if switching contexts leads you to mistakes. Alternatively, export all accounts first and review them in a fixed order. Neither method is inherently superior. The useful choice is the one that keeps you aware of which book is active. Avoid a routine where several unnamed files are open and you rely on remembering which one you downloaded a few minutes earlier.

Compare each account's daily result independently before looking at a combined view. A combined total can hide equal and opposite discrepancies between books. If one account is missing an execution and another contains activity that belongs elsewhere, the overall number might look less unusual than either individual record. Checking accounts separately gives you a clearer foundation. Only after they make sense should the aggregate view become the place where you assess your overall trading activity.

Similar or copied trades require particular care in your interpretation. Separate accounts can contain related activity without representing separate independent trading ideas. Keep the source records assigned correctly, then understand how your journal combines them in reports. Do not erase genuine account activity just to reduce a count that feels repetitive. There is a difference between preserving what happened in each account and deciding how to summarise repeated ideas across the accounts you review together.

At the end of the routine, make sure every account you intended to include has been checked. An account with fewer trades can be easy to overlook because nothing dramatic happened there. A quiet account still matters to the completeness of your records. Your final check can be as simple as comparing your planned account list with the files saved for the week. The point is completeness, not producing a large amount of administrative work.

Keeping your exports in order over a year

A year's records become manageable through small consistent decisions made while the files are fresh. Keep the original export, distinguish the report type and record the account and period in a way you understand. You do not need to predict every future question. You only need enough context to locate the source behind a day or position. The future version of you should not have to remember what an ambiguous filename meant months earlier.

Preserve original files separately from copies you use for inspection. A spreadsheet can be useful for reading rows, but a saved working copy is not necessarily identical to the export you received. If you later need to investigate a timestamp or identifier, the untouched source removes one layer of uncertainty. This is particularly valuable when a problem appears after several routine imports, because you can compare the current source with an earlier known file.

Use a repeatable export range while still checking its boundaries. A weekly habit can be convenient, but it must include the entries and exits needed to describe the activity you traded. Do not let the calendar label replace the actual check. If you held a position across a boundary, make sure the source contains the necessary history. Consistency makes the routine easier; attention to unusual positions keeps that routine accurate when the week is not ordinary.

Review unresolved differences before they accumulate into an unmanageable list. One unclear trade is easier to investigate while the account and session are familiar. That does not mean every problem must be solved immediately or that you should change values until nothing looks open. It means preserve the source, state the question and return to it deliberately. A brief note explaining what remains uncertain is more useful than either ignoring the gap or concealing it.

When you change the report you normally export, test the change on a familiar period. Compare the preview and daily results before building several months of records on the new habit. A difference in visible columns or report type can affect what the receiving journal sees. Testing a known period gives you a reference point. You are checking whether the new source preserves the same relevant activity, not merely whether it can be opened successfully.

The reward for this order is a review you can trust, not a beautiful archive that nobody uses. When a report says one setup performed better, you want confidence that the underlying trades and fees are complete. Tomorrow, pick one account and export the documented Executions grid. Keep the source intact, inspect a familiar position and compare the daily result. That small loop is the foundation of records that remain understandable long after this week's trading feels distant.

The short version

Executions and Trade Performance describe trading at different levels. The supported NinjaTrader 8 route is the Executions grid exported as CSV. The Trade Performance Trades export is Beta and needs the entry, exit, time, profit and commission columns visible. Check what a row represents before comparing counts or deciding that one report has lost trades.

When the numbers differ, work through account, period, execution sequence and fees in that order. Preserve the original file and keep unresolved questions visible. Your next practical step is to choose one familiar completed position and follow it from the execution export into the preview. If the activity and costs make sense there, you have a stronger starting point for checking the rest of the week.