Demo accounts and live accounts may look identical on the user interface, yet they generate different categories of paperwork. A demo simulates execution against modeled prices; a live account produces legally and financially meaningful tickets, balances, and tax-relevant history. Learners who treat the two journals as interchangeable sometimes discover reconciliation gaps when they switch. This article compares record-keeping differences in a calm, checklist tone. It does not argue that one mode is morally superior; it argues that filing systems should match the mode.
What a Demo Ticket Represents
A demo fill is a platform record of a simulated transaction. No counterparty has taken the other side in the banking sense. No funds move. The ticket number helps support staff diagnose software behavior. Timestamps still matter for studying session habits, but they do not create brokerage confirmations usable in court or with tax authorities unless your jurisdiction explicitly states otherwise—which is uncommon.
Demo prices typically derive from live feeds with a delay or from aggregated streams. During releases, demo slippage rules may differ from live books. A learner who archives demo results as if they were live fills overstates evidential value. Label folders clearly: DEMO followed by platform name and month.
Reset Balances and Fresh Starts
Many demos allow balance resets or fresh virtual capital. Each reset breaks the continuity of an equity curve. If you export CSV history, note reset dates in a cover sheet. Otherwise year-to-date return calculations become meaningless. Live accounts do not offer casual resets; drawdowns remain in the statement chain.
Some firms close inactive demos. Export before vacation. Live dormancy rules differ and may include fees stated in client agreements.
What a Live Ticket Represents
A live fill is part of a customer account relationship. It should appear on daily statements, monthly summaries, and annual tax packets where applicable. Ticket details include execution price, commission, swap or financing if held overnight, and account currency. These fields feed reconciliation between platform history, email confirmations, and back-office PDFs.
- Live exports should be archived in read-only storage after download.
- Ticket IDs should match between web report and terminal journal.
- Discrepancies trigger support tickets with attachments, not silent edits to personal spreadsheets.
Regulators in several regions require transaction reporting from brokers; the retail trader’s copy is still the first line of personal defense in disputes.
Spread, Swap, and Financing Columns
Demo swap tables may mirror live formulas or simplify them. Weekend triple-swap conventions, holiday accruals, and dividend adjustments on contracts for difference can differ subtly. A journal that tracks carry costs must cite which account type produced the numbers. Mixing demo swap accrual with live notional yields false carry attribution.
Commission models also diverge. Raw spread demos may hide commission add-ons present live. When comparing round-trip cost, build two column headers in the ledger rather than one blended average.
Order Types and Partial Fills
Live limit orders can partially fill across multiple micro tickets. Demos sometimes fill instantly at full size. Record-keeping must aggregate partials when calculating average entry. Personal spreadsheets need a child table keyed by parent order ID if the platform provides one.
Rejected orders on live for margin shortfall appear in journals with reason codes. Demo may auto-resize or ignore constraints. Learners should not infer that live will accept the same size without reading equity and margin reports.
Psychological Artifacts Are Still Artifacts
Emotional responses differ between modes even when charts match. That difference is not mystical; it appears in timestamp patterns—more impulsive entries live, more experimental grids demo. A documentary self-study can log emotion tags, but the filing rule remains: separate databases. Comparing trade frequency per hour between modes is valid only within each database.
Screen recordings are optional exhibits. If used, watermark them DEMO or LIVE in the filename.
Tax and Compliance Boundaries
Tax reporting generally concerns live realized outcomes in account currency, translated per local rules. Demo P and L is not income. Educational articles cannot provide tax advice; they can state that mixing demo gains into personal net-worth statements is a category error. Employers learning on demo time should follow company policy on simulation use.
Anti-money-laundering onboarding exists only for live relationships. Demo logins do not replace know-your-customer records. Keep identity documents out of trading journals.
Building Parallel Ledger Templates
A sound template for demo includes columns: datetime, pair, direction, size, requested price, fill price, spread at click, platform ticket, notes on feed lag. Live adds: commission, swap, balance after fill, margin used, statement cross-check flag. Weekly, run a checksum: sum of closed trade P and L versus platform closed P and L for that week. Demo drift indicates export bugs; live drift indicates a reconciliation task.
Version Control for Strategy Labels
If you tag trades with strategy names, version the definition in a text file. Changing rules mid-month without versioning corrupts later statistics. Live capital deserves stricter version discipline because consequences are monetary.
Backtesting exports pulled from third-party history are neither demo nor live account records; they are a third category. Store them separately.
Migration Week Procedures
When opening a first live account after long demo use, run a migration checklist: new folder structure, duplicate spreadsheets cleared of demo rows, risk limits written on paper, calendar of expected statement emails, and a frozen archive of demo work labeled historical simulation only. Do not roll demo equity curves forward as if they were live track records.
Some traders keep a tiny live size while continuing demo experiments. Maintain two filenames even if the pair symbols match.
Support and Dispute Records
Live disputes rely on ticket numbers and UTC timestamps. Demo disputes are product feedback. Correspondence should be filed under different headings. Save PDF replies from compliance departments in live folders only.
Chargebacks and deposit history belong to live banking rails, not demo resets.
Summing the Filing Difference
Demo is for interface fluency and hypothetical performance logging with clear labels. Live is for balances that can decrease to zero and statements that must reconcile. Treat the distinction like paper versus settled funds in banking: similar font, different legal weight.
Keep demo exports and live exports in separate dated folders so that a later audit can tell which numbers were simulated and which numbers moved cash.
Disclaimer: This website is not a broker, does not execute trades, and does not provide trade signals or individualized financial advice. Foreign exchange quotations can move sharply; leveraged accounts can incur losses that exceed deposits. Information here is for general education only.


