The Hidden Cost of Session and DST Errors in Backtests

First, fix the estimand as “net performance of signals correctly mapped to actual exchange time and market sessions.” Do not substitute net profit, win rate, or a visually smooth curve for that target. Declare the horizon, account currency, included frictions, and operating-stop boundary before calculation. Any post-result change creates a new hypothesis and version, preventing the question from being selected after the answer is known.

Reconstruct the observation unit as “timezone-aware bars and order events rather than display-local timestamps used as analytical keys” before treating rows as independent evidence. Report raw rows, parent trades, decisions, event clusters, and the denominator used for each average or standard error. Recompute session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations under more than one defensible aggregation rule so that a larger export is not mistaken for a larger information set.

Preserve the hash of the TradingView export and the symbol, timeframe, session, timezone, order-processing settings, costs, account currency, and Pine version. For session and daylight-saving misclassification, daylight-saving boundaries, exchange holidays, early closes, and vendor timezone conversion directly affects reproducibility. Keep immutable source, normalized, and analysis layers separate, with every join, deletion, imputation, and conversion recorded in a transformation ledger.

The export identifies only what can be rebuilt from recorded time, price, quantity, and P&L. unscheduled exchange closures, vendor timestamp conventions, and server-time changes requires additional evidence. Mark each causal link as observed, bounded by assumption, or externally unverified. This prevents daylight-saving boundaries, exchange holidays, early closes, and vendor timezone conversion from being presented as a confirmed fact when the available data support only an interval or conditional conclusion.

Do not adopt the platform summary as ground truth. Independently remap every event to UTC using the IANA timezone database and an exchange calendar, with explicit fold handling for repeated times and gap handling for nonexistent local times. Reconcile total and row-level differences by sign, date, symbol, and order type. If discrepancies concentrate in the exact state associated with session and daylight-saving misclassification, treat that concentration as a primary finding rather than dismissing it as rounding.

Report session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations with intervals or resampling distributions, not point estimates alone. Match the uncertainty method to sample size, skewness, heavy tails, censoring, and selection history. If normal, quantile, and dependence-aware methods disagree on the sign, classify the edge as unidentified and show the minimum detectable effect and lower decision bound.

Do not narrow uncertainty with an IID shuffle alone. Resample calendar blocks that preserve DST-transition weeks, ordinary weeks, and holiday weeks using several fixed block lengths and stationary bootstrap. Preserve random seed, repetition count, wrap rule, and missing-data treatment. For each block specification, report the distribution of session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations, the rejection-side tail mass, and the rate at which the verdict changes sign.

Interrogate the mechanism “daylight-saving boundaries, exchange holidays, early closes, and vendor timezone conversion” with lower quantiles, expected shortfall, influence, cluster length, and boundary-hitting measures. Historical maximum loss is not a loss cap. Define several absorbing or operating boundaries—capital, margin, mandate drawdown, and recovery time—and record which boundary fails first under each stress.

A flat commission deduction is not an execution model for session and daylight-saving misclassification. Allocate spread, slippage, financing, borrow, roll, conversion, rounding, and rejected orders to the relevant unit. Recompute session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations under base, upper-quantile, and crisis states while preserving the possibility that costs and losses worsen together.

Count the complete population of periods, symbols, timeframes, parameters, exits, filters, and metrics that were tried. Do not detach the attractive result for session and daylight-saving misclassification from rejected candidates, interim changes, or repeated validation reviews. Where appropriate, use PBO, SPA, and a Deflated Sharpe Ratio, and treat an unrecorded trial count as a material audit limitation.

Test whether session and daylight-saving misclassification is concentrated in one trend, volatility, liquidity, rate, or session state. Define regimes prospectively or on training data only. Report statewise session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations, occupancy, transition probabilities, and costs, then reweight the mixture to adverse but realistic future compositions.

For the session and DST misclassification case, the same trade set can follow different capital paths under another inception date, order, initial balance, rounding rule, or stop condition. Separate fixed quantity, fixed R, and percentage sizing, then use circular shifts and block orderings to recompute drawdown, recovery, and boundary hits. Equal terminal P&L does not imply equal path risk.

Perturb “±60-minute shifts, DST-boundary exclusions, and exchange-calendar substitutions” one axis at a time before creating a joint sensitivity surface. Add the negative control “apply the same plus-or-minus sixty-minute shift to markets without DST or weeks far from transitions to test whether the degradation is boundary-specific.” Predefine the grid and crisis rule so that neither the most favorable nor the most damaging cell is selected after inspection. Save the slope, curvature, and exact point where the decision boundary is crossed.

Have a second implementation remap every event to UTC using the IANA timezone database and an exchange calendar, with explicit fold handling for repeated times and gap handling for nonexistent local times, then compare critical row-level outputs. Regression fixtures should include empty files, duplicate timestamps, extreme costs, reverse ordering, missing values, and boundary cases. Agreement between implementations is insufficient if they share the same bad input, so separate data construction and review roles where feasible.

Predeclare the decision rule. This case passes only if “critical metrics agree under the exchange-calendar implementation and defensible timestamp policies, with no profit concentration in transition weeks.” Near a boundary, disclose interval width and economic materiality rather than a binary badge. If only one favorable block length, cost state, or implementation passes, classify the result as assumption-sensitive rather than robust.

The evidence ledger must store the input hash, code version, settings, exclusions, “±60-minute shifts, DST-boundary exclusions, and exchange-calendar substitutions,” block lengths, random seed, repetition count, and every scenario output. Keep exploratory and confirmatory results in separate namespaces and retain failed trials. When new TradingView data arrive, create a new version and track exchange-local time, UTC time, session ID, calendar version, and counts of fold and gap resolutions rather than overwriting the old result.

Translate statistical changes into capital consequences. A shift in expectancy, lower quantile, recovery time, or boundary risk caused by session and daylight-saving misclassification should be mapped to trade count, capital, margin, and continuation. A small per-trade difference can compound under high turnover, while a rare loss can be decisive near an absorbing boundary.

Separate hypothesis design, implementation, independent recalculation, and approval where practical. Stop automatically on material reconciliation error, unresolved missing data, non-reproducibility, or a predeclared threshold breach. Audit the chain “fixed offset → session misclassification → wrong bar selection → apparent time-of-day edge → disappearance in real clock time,” and monitor exchange-local time, UTC time, session ID, calendar version, and counts of fold and gap resolutions prospectively without turning a historical pass into a promise of future profit.

The estimand “net performance of signals correctly mapped to actual exchange time and market sessions” is identified only within the columns present in the TradingView export and the stated assumptions. If unscheduled exchange closures, vendor timestamp conventions, and server-time changes cannot be observed, report bounds rather than a false point estimate.

Past estimates of session and daylight-saving misclassification need not belong to the same population after changes in rules, participants, volatility, costs, or data specifications. Track exchange-local time, UTC time, session ID, calendar version, and counts of fold and gap resolutions in rolling and regime-specific windows.

For DST timing, repeatedly applying the same diagnostic battery and editing until it passes turns verification into another optimizer. Every post-audit change therefore creates a new model version and requires untouched evidence.

Even if critical metrics agree under the exchange-calendar implementation and defensible timestamp policies, with no profit concentration in transition weeks, the analysis does not establish tax, regulatory, behavioral, liquidity, order-size, or systems suitability. Separate statistical diagnosis from live-operating approval.

Deleting observations related to daylight-saving boundaries, exchange holidays, early closes, and vendor timezone conversion may improve the result. Compare no deletion, conservative imputation, and worst-case imputation, and display how session-misclassification rate, P&L difference around DST transitions, reconciliation against fixed offsets, and early-close deviations changes.

Run the control “apply the same plus-or-minus sixty-minute shift to markets without DST or weeks far from transitions to test whether the degradation is boundary-specific.” If the control performs similarly, suspect processing rules or common market drift before attributing performance to the strategy.

After a provisional pass, log exchange-local time, UTC time, session ID, calendar version, and counts of fold and gap resolutions sequentially and stop on persistent departures from the predeclared predictive range. Diagnose implementation drift before reoptimizing history.

Multiple methods can agree because they share the same bad input or the same mechanism “daylight-saving boundaries, exchange holidays, early closes, and vendor timezone conversion.” Give lower-tail outcomes, failed scenarios, and unresolved mismatches the same visual prominence as favorable results; test count is not proof of correctness.