Manual/automatic journaling, open and closed trades, Performance Intelligence, sessions, setups, mistakes, emotions and Discipline Score.
MT5 journal: CSV import or account sync? Practical checks
MT5 journal: CSV import or account sync? Practical checks
Disciply is our product. Comparison of methods, not an independent product review.
Not just a journal: markets, execution, risk and review in one workflow.
Disciply combines MT5 data, market tools, execution controls and behavioral analytics. The value is not one feature; it is the connection between context → decision → execution → journal → review.
Market workspace, charts, price alerts, Market Breakdown, calendar/context, Market Bias and volatility context available in the market workflow.
Group breakeven, profit protection, SL/TP management across multiple positions with preview and broker checks, plus partial close where supported.
Distribute limit orders inside a range while reviewing order count, size and total exposure before sending them to the connected account.
Sizing proposals using history, session, asset, current risk, exposure and broker volume specs; guardrails reduce size when conditions deteriorate.
Orders, protection and position management linked to the active account, with level, tick, minimum-distance/freeze checks and confirmation before execution.
Reconciliation
## Reconcile net rather than gross results Commissions, swaps, conversion and other charges may alter the financial outcome and may be stored in different fields. Test actual history that includes a profitable and losing trade, plus partial exits and overnight costs where available. Find the first transaction at which the journal differs from the broker. Do not manually alter the final total to conceal missing fees or unsupported currency conversion. Accuracy depends on reconstructing the accounting rule.
Testing
## Repeat the same import Import an identical CSV twice and verify that unique deal identifiers and net totals are not doubled. An automatic connector needs the same property when restarting or retrying a failed sync. Record counts before and after. If historical data are legitimately corrected, the application should disclose the reason. A success message alone does not prove that duplicate prevention works.
Official sources
- MetaTrader 5 reports Checked 2026-10-14
- MetaTrader 5 history Checked 2026-10-14
Analysis of major market moves
Real Disciply candle snapshots with structure, liquidity, sessions and macro context.
Loading market analysis…