Trading journal that matches your broker statement

The direct answer

A trading journal should match your broker statement, but you must verify the import before treating its P&L as authoritative. QuantLab provides supported connections and duplicate protection, while the broker statement remains the source for reconciliation. The prop firm trading journal guide explains why this matters for account rules.

Accuracy complaints are common across journal products because a missing fill or incorrect mapping can distort every summary built on top of it.

Start with complete source data

Tradovate connects through OAuth and lets you select accounts before starting a history sync. ProjectX validates a username and API key, imports selected accounts, and offers manual sync. CSV import maps broker fields and normalizes executions.

Confirm that the chosen account and date range match the statement you are comparing. A correct calculation on the wrong account is still the wrong answer.

Check executions before totals

Compare contract, side, quantity, fill price, and timing. Then compare the session result. Execution-level checks help you locate the cause instead of staring at two different totals.

QuantLab's CSV fingerprints stop a repeated file from adding the same executions again. The importer can also group nearby executions into positions. If the broker groups fills differently, compare the underlying executions before concluding that the position totals conflict.

Escalate differences in order

First check account selection and date boundaries. Next inspect missing records or field mapping. Then verify whether position grouping explains the display difference. Do not change account rules or trading behavior based on a journal until the source record is reconciled.

Once the data agrees, QuantLab can calculate maximum drawdown and evaluate a configured consistency limit. Behavior detectors and replay also depend on that same record, so reconciliation protects the rest of the review.

The journal is free during beta, with access limited to approved waitlist emails.

Keep a reconciliation note

Write down the account, source statement, and date range used for each check. Record whether the execution count and session result agreed. If you accepted a known display difference caused by grouping, explain it in one sentence.

This note prevents the same discrepancy from being investigated repeatedly. It also gives you a clean boundary for the next import. If a later total changes before that boundary, treat it as a data issue and inspect the underlying executions. Do not solve a mismatch by manually changing a summary number, because the drawdown and behavior analysis still depend on the original rows.

Recheck after changing import methods

Switching from CSV to a connection can change how executions are grouped or labeled. Use one overlapping session as a controlled comparison, but avoid leaving both copies in the journal. Compare the raw fills and identify which source will own future dates.

Once you establish that boundary, use the same reconciliation steps on each new import. Consistent checks make a later discrepancy easier to locate and keep performance conclusions tied to records you have inspected.