A free day trading journal is only useful if the fills it records match what your broker actually executed. For DAS Trader Pro users, the gap shows up quickly. A single scaled-in position can produce a dozen partial executions, and a journal that collapses them incorrectly distorts average entry, realized P&L, and hold time. SpiceLog is a trading journal and analytics tool for US stock and ETF day traders, built for DAS Trader Pro users. It is our product, so weigh the comparisons below with that in mind. This guide covers how to export fills from DAS, what a free journal should and should not limit, and how to build a workflow whose numbers reconcile without a paid subscription.
Table of Contents
- Quick Takeaways
- Exporting DAS Trader Pro Fills Without Losing Partials
- What a Free Journal Has to Do for DAS Traders
- Building a Round-Trip Journal from DAS Exports
- Comparing Free Journal Options for DAS Traders
- Recording Position Size and Risk Per Trade
- Tagging Fills and Analyzing Performance by Tag
- Frequently Asked Questions
- References
Quick Takeaways
| Key Insight | Explanation |
|---|---|
| Export fills, not summaries | Use order and fill-level data from DAS Historical Reports so that partial executions survive into the journal. |
| Reconcile before you analyze | Compare journal realized P&L and commissions against the broker figure for each session. Any residual points to a specific fill problem. |
| Check what the free tier meters | Confirm whether a free plan caps trades, fills, history depth, or connections before you migrate historical data. |
| Group by flat-to-flat position | Build round trips from the fill sequence between zero and zero shares. Ticker-and-day grouping merges separate trades. |
| Record planned risk at entry | Store stop, share count, and dollar risk so that R-multiple and sizing analysis are possible later. |
| Keep tag families small | Three families (setup, exit reason, execution error) with short lists get applied consistently. Long lists do not. |
Exporting DAS Trader Pro Fills Without Losing Partials
DAS Inc. describes a Report Center in DAS Trader that includes Historical Reports covering trades, orders, prices, and logs. Those datasets are not interchangeable for journaling. Trade-level summaries are convenient, but they collapse the execution detail you need to audit a scale-in or a stop that filled in pieces.
For journaling, the order and fill layer is the useful one. A single position often involves a limit entry, two add-ons, a partial take-profit, and a stop-market exit, and each generates its own execution record. If your journal ingests only the net trade, you lose the sequence and cannot compute the true average entry against the prices you actually received.
Fields to verify before import
Confirm that the export contains execution timestamps, side (buy, sell, short, cover), quantity, price, and symbol. Check that short sales are distinguished from long exits, because a sign error inverts P&L on every short. Confirm whether commissions and fees are included or provided in a separate column, since a journal that ignores them overstates net results on high-volume days.
Timezone and session boundaries
Confirm the timezone your export uses and compare it with the timezone your journal assumes. A mismatch moves pre-market fills into the prior session and breaks daily reconciliation. Normalize timestamps once at import, and keep the raw file unchanged so you can re-run the mapping if a column turns out to be misread.
Pro tip: Export one known session from DAS first and reconcile it to the cent before you pull a full quarter. A parser problem caught on one day costs minutes to fix. The same problem found across six months of data costs far more.
What a Free Journal Has to Do for DAS Traders
Free journals usually differ from paid ones in three places: how many trades they ingest per period, how far back history reaches, and how many broker or platform connections they allow. For a day trader running dozens of round trips a week, a periodic cap is the limit that binds first. Calculate your monthly fill count rather than your trade count, because a scaled trade produces several fills and some tools meter each one.
Trade count caps and fill metering
Some journals meter by round-trip trade and others by execution. Under a fill-based meter, one scaled entry and its exits can consume several units from a single idea. Ask which unit is metered before you commit historical data. A fill-based limit penalizes the scale-in and scale-out style common in momentum trading, so it can make a free plan unusable for exactly the trades you most need to review.
Multi-broker consolidation
Many prop-firm and retail traders work across a DAS account, an evaluation account at another brokerage, and a personal account. A free tool is only worth using if it merges those sources into one ledger without double counting mirrored or transferred fills. Our approach at SpiceLog is to consolidate fills from multiple brokerages and journaling tools into a single analytics view. Traders who avoid that step usually rebuild it by hand in a spreadsheet journal template, and the maintenance cost rises with every account added.
Building a Round-Trip Journal from DAS Exports
A workable free workflow has four steps: export fills, normalize columns, group fills into round trips, and reconcile daily totals. The grouping step is where most errors originate. Group by flat-to-flat position, meaning the fill sequence from zero shares back to zero shares, rather than by ticker and day.
Matching partial fills to round trips
Consider a position where you buy 300 shares, sell 100, add 200, then sell 400. Flat-to-flat grouping produces one trade with a weighted average entry and a single exit sequence, which yields realistic hold times and win rates. Ticker-and-day grouping fails when you go flat and re-enter the same name within one session, because the two round trips merge into one row and distort both counts.
Reconciling daily totals
Sum realized P&L across your journal for each session and compare it with the broker's realized figure after commissions. A clean import should reconcile to zero. A nonzero residual usually indicates a dropped fill, a sign error on shorts, or a duplicate row from re-exporting an overlapping date range. Reconcile before you read any statistic, because every downstream metric inherits the error.
Comparing Free Journal Options for DAS Traders
There are three realistic routes for a DAS trader who wants a zero-cost journal, and each has a distinct failure mode. The table below sets them side by side. SpiceLog is our product, and the third row reflects our assessment, so verify its current terms yourself.
| Approach | Where It Works | Where It Breaks |
|---|---|---|
| Spreadsheet built from DAS CSV exports | Full control over grouping logic and no trade caps | Flat-to-flat matching and average-entry formulas must be rebuilt whenever the logic changes, and they scale poorly past a few hundred fills a month |
| Generic CSV import into a free journal | Fast setup if the tool accepts your column layout | Column mapping can drop the side or short indicator, which silently corrupts P&L |
| SpiceLog trading journal (our product) | Imports DAS Trader Pro fills and consolidates them with other sources in one view, and is free | Supports US stocks and ETFs; option and futures rows in an export are skipped |
Where spreadsheets fail
Spreadsheets fail at scale for a specific reason. The template handles layout well, but the matching logic is the hard part, and it must be correct for every edge case, including flips from long to short inside a session. If you use a template, treat it as a starting point and test it against one week of broker-reported realized P&L before trusting its output.
Generic CSV versus native DAS import
A native import keeps side, quantity, and price in the fields the parser expects. A generic CSV is more flexible, but it depends entirely on your mapping being right. A practical test is to import a single day with known outcomes and check that trade count, average entry, and net P&L match the DAS trade history. The DAS Trader Pro journal page describes the import path in more detail.
Recording Position Size and Risk Per Trade
A journal without planned risk cannot tell you whether your losses come from sizing or from trade selection. Record the intended stop, the share count, and the dollar risk at entry, then compute the R-multiple at exit. Without those fields, every trade reduces to a P&L figure, and you cannot separate execution errors from sizing errors.
Calculating share size from fixed risk
Share size equals dollar risk divided by per-share risk, where per-share risk is entry minus stop for longs and stop minus entry for shorts. Round down. If your stops are stop-market orders rather than guaranteed exits, deduct expected slippage from the per-share figure. A position size calculator automates this arithmetic, so you can set share counts before the open rather than during it.
Why R-multiple beats raw P&L for review
Dollar P&L scales with size, so a week of larger positions looks like a better week even when the decisions were identical. Expressing each result as a multiple of planned risk normalizes the review. Filter by R and by setup tag together, and you can see whether a setup carries positive expectancy independent of how aggressively you sized it.
Tagging Fills and Analyzing Performance by Tag
Tags turn a fill log into an analysis tool. For a day trader, the most useful schema has three tag families: setup, exit reason, and execution error. Keep each family short. Ten setup tags and a dozen error tags usually mean nobody applies them consistently, and inconsistent tags produce analysis that looks precise but is not.
A tag you cannot apply consistently under pressure is noise, not data.
Setup tags tied to observable conditions
Define each setup tag by an observable condition, such as a gap continuation above the prior-day high on elevated relative volume, rather than by how the trade felt. Then compare expectancy across tags, not just win rate. A 40 percent hit rate with a 2.5R average winner produces positive expectancy of 0.4R per trade. A setup that wins 65 percent of the time with 0.5R average winners is negative, at roughly minus 0.025R per trade.
Execution error tags across sources
When fills come from more than one brokerage, the same error tags must apply to every source. Tag late entries, moved stops, and averaged-down losers consistently, then track their frequency week over week. If an error follows you across accounts, the cause is in your process, not in a broker's data feed, and the trend line will show it before a single bad month does.
Pro tip: Apply tags at entry, not after the close. Tags assigned after a losing trade drift toward explanations that protect the result, and that bias corrupts the setup analysis the tags were meant to support.
Frequently Asked Questions
Is there a genuinely free day trading journal for DAS Trader Pro?
SpiceLog's trading journal is free and imports DAS Trader Pro fills alongside other sources. It supports US stocks and ETFs and skips option and futures rows in an export, so check what your history holds before migrating it. Whichever tool you use, test it against one week of broker-reported realized P&L before relying on its statistics.
Which DAS reports should I export for journaling?
Use order and fill-level data rather than summary trade reports. Summaries hide scale-ins, partial exits, and the sequence of executions, and you need that sequence to compute average entry and hold time correctly.
Why do my journal totals differ from my broker's P&L?
The usual causes are dropped fills, sign errors on short-side executions, duplicate rows from overlapping exports, and commissions handled inconsistently. Reconcile session by session to isolate the first day that diverges, then inspect the fills from that day.
How should I group partial fills into one trade?
Group flat-to-flat, meaning the fill sequence from a zero position back to a zero position. Ticker-and-day grouping merges separate round trips when you re-enter the same name within one session.
Do I need to track position size in a free journal?
Yes. Without planned risk per trade you cannot calculate R-multiple or separate sizing errors from selection errors. Calculate share counts from fixed dollar risk before entry, not after the fill.
If you have moved DAS Trader Pro fills into a free journal, tell us which export format and grouping method gave you the cleanest reconciliation.
References
- DAS Inc. overview of the DAS Trader suite, including Report Center historical reports
- Comparison of trade execution platforms for active retail traders, including DAS Trader Pro
- Trader forum discussion of DAS alternatives, charting, and day trading tools
Written by the team behind SpiceLog (https://www.spicelog.com/).
No comments:
Post a Comment