# What can a trading statement prove? > Its own arithmetic and the facts inside the file — the closed ledger — but never the market around your fills, a quote's honesty, or anyone's intent. - Canonical: https://hadalinstruments.com/research/what-can-a-trading-statement-prove/ - Published: 2026-08-05 - Author: Hadal Research - Answers the question: "what can a trading statement prove" - Coins the term: **The Closed Ledger** — A record generated from a single source reconciles with itself by construction, so its internal consistency is evidence of nothing beyond its own arithmetic — corroboration requires a second record produced independently of the first. --- A trading statement is the only document most traders have when something goes wrong, and it is routinely asked to do two jobs at once: establish what happened, and establish who caused it. It is very good at the first and structurally incapable of the second. Knowing which side of that line a question falls on is the difference between a claim that survives scrutiny and one that collapses at the first informed reply. > **WHAT THIS IS — AND WHAT IS NOT PUBLISHED.** This article is method. I have measured and published nothing about broker or prop-firm conduct — no fill-quality rankings, no dispute outcomes, no firm-by-firm comparison — and no such figure appears on this page. This page names no firm and describes no firm's terms. Statement formats differ between platforms and between brokers on the same platform; where this page and your own file disagree, your file is the fact. Status of my own measurements: **NOT YET COMPUTED**. Hadal carries no affiliate links and takes no commission from any firm. ## What is actually in the file Whatever your platform calls its report, the contents fall into four groups, and they are not equally useful. - **Orders** — what you asked for. Instrument, direction, requested volume, order type, requested price where one applied, and the state the order ended in. - **Deals** — what actually executed. The fill price, the filled volume, the moment the server recorded it, and the commission charged. - **Positions** — the aggregate consequence: an opening deal, a closing deal, and the realised result between them. - **The account series** — balance, and in some exports equity, sampled at whatever points the report chose. The distinction between the first two groups is where most of the evidential value sits. An order is an intention; a deal is an event. The difference between the price you requested and the price you received is arithmetic on two numbers in your own file, and it needs nothing external. It is one of the strongest things a statement gives you. Platforms differ in how cleanly they separate these. Some present a single flat list of closed transactions and leave you to infer the order that produced each one; others model orders, deals and positions as three distinct record types with explicit identifiers linking them. The second shape is materially better for reconstruction, because the link between intention and event is recorded rather than inferred. If your platform offers both a summary report and a full record export, the full export is the one worth keeping. ## The closed ledger Here is the property that decides what a statement can and cannot support, and it is almost never stated. **A statement is generated from a single ledger, so its parts agree with each other by construction.** Balance follows from the deals. Equity follows from balance plus open positions. Every internal cross-check you could run tests the arithmetic of the file, and there is no mechanism by which those quantities could disagree — not even if every price in the document were wrong. This is worth sitting with, because "the numbers add up" is the most common reason people trust a statement more than the evidence supports. Internal consistency is not corroboration. **A record that cannot contradict itself cannot corroborate itself either.** The file is a closed ledger: complete, self-consistent, and silent about everything outside its own boundary. What breaks the closure is a second record produced *independently* of the first — a feed captured by a party with no access to the broker's ledger, a counterparty's own record, a venue's published data. Two records that were generated separately can disagree, and because they can disagree, their agreement carries information. That is the entire basis on which anything about the outside world gets established. ## What one statement establishes on its own The questions below are answerable from your file alone, with no second source. They are also, in practice, most of what a dispute actually turns on. - **The arithmetic of a breach.** Given the rule text, the floors it implies can be recomputed from your own balance and equity series and compared against what the record shows. Whether a stated rule, applied to your recorded account, produces the recorded outcome is a closed question — and one that can be answered under each reading when the rule text is ambiguous. - **What execution actually cost you.** Commissions, swaps and financing are itemised. Spread cost is recoverable where both sides of the quote are recorded. Summed across a period, this is frequently a larger number than traders expect and it needs nothing external to compute. - **The gap between requested and received.** Where the order carries a requested price, the difference from the fill price is two numbers in your own file. - **Sequence and timing**, once the timezone offset is established. Which of your own actions preceded which is fully recoverable. - **Consistency with your own account of events.** Where a recollection and the record disagree, the record generally wins, and finding that out privately is better than finding it out publicly. ## What one statement cannot establish, at any level of effort A single statement is a closed ledger, and every question in this section lies outside what it can speak to. - **What the market was doing at that instant.** The file records your fill, not the quote stream around it. Any claim of the form *"the real price was X"* requires a record of X from somewhere else. - **Whether a quote was manipulated or merely wrong.** This needs an independent reference, and even with one it distinguishes a discrepancy from an explanation rather than proving a cause. - **Anyone's intent.** Not merely unproven from client-side data but undecidable from it — a boundary examined at length in [the refutation index](/refutations/) as **The Vantage Limit**, and the reason an honest verdict sometimes has to be *not measurable* rather than *unproven*. - **What would have happened otherwise.** Counterfactuals are not in any record. - **That a rule was applied unfairly**, as distinct from applied as written. A recompute establishes whether the stated rule produces the recorded outcome. Where it does, the disagreement is with the rule rather than with its application, and that is a different argument in a different forum. ## Why this is worth reading before anything goes wrong Two practical consequences, and the first is the reason this page exists. **Export the full record now, not later.** Detail thins with age on most platforms, retention policies differ, and access can end with the account. The richest export your platform offers, taken while everything is still normal, costs nothing and is unrecoverable afterwards. The [assay preparation guide](/docs/assay-preparation/) sets out what to pull and in which format. **Frame the question as the record can answer it.** *"They slipped me"* is a claim about a counterparty and needs evidence your file does not contain. *"My fills departed from my requested prices by this much, in this direction, and it cost this"* is arithmetic on your own record, and it is both stronger and harder to dismiss — a directional, quantified pattern from a document the other party produced is a considerably more uncomfortable thing to answer than an accusation of intent. The narrower claim is the one that survives. That is not a compromise; it is what the evidence actually supports, and stopping there is the whole discipline. ## Where this leads If a rule ended an evaluation and you want the arithmetic behind it reconstructed from your own record, that is [Prop-Breach Forensics](/assays/#prop-breach-forensics). If the question is what execution cost across a period, that is the [Execution-Cost Assay](/assays/#execution-cost-assay). Both take the statement you already have; neither asserts anything about a counterparty's intent, because the record cannot support it. The rules a recompute is run against are defined at [trailing drawdown](/glossary/trailing-drawdown/), [high-water mark](/glossary/high-water-mark/), [daily loss limit](/glossary/daily-loss-limit/) and [consistency rule](/glossary/consistency-rule/). If you are not certain which drawdown architecture governs your account, [work out which drawdown rule you have](/tools/trailing-vs-static-drawdown/) — it classifies from the rule text and computes the floor under each reading that remains possible. --- ## Claims examined ### Claim 01 — canonical: https://hadalinstruments.com/refutations/#claim-3f96e3fc > "My statement proves the broker slipped me." — our reading: Misleading A statement establishes the price you were filled at. Slippage is a difference between that price and a reference — and the reference is not in the statement. Comparing your fill to your own requested price shows the gap existed; it cannot show what the market was doing at that instant, because a single account's record contains one party's view and nothing outside it. Establishing the second half needs an independently produced record of the same moment. The gap is real and measurable from your statement; the attribution is not, and the two get conflated constantly. **What is true:** A statement establishes the price you were filled at and the gap from your requested price; establishing what the market was doing at that instant requires a second record produced independently of the broker's. Evidence: https://hadalinstruments.com/research/what-can-a-trading-statement-prove/#claim-3f96e3fc ### Claim 02 — canonical: https://hadalinstruments.com/refutations/#claim-4f913431 > "The statement reconciles, so the numbers must be right." — our reading: False A statement is generated from one ledger, so its parts agree with each other by construction. Balance follows from deals, equity follows from balance plus open positions, and there is no mechanism by which those could disagree even if every price in the file were wrong. Internal consistency tests the arithmetic and nothing else. A record that cannot contradict itself cannot corroborate itself either — which is why an independent second record, produced by a party with no access to the first, does evidential work that no amount of internal checking can. **What is true:** Internal consistency in a statement tests its arithmetic only; because the whole file comes from one ledger, its parts agree by construction whether or not the prices in it are accurate. Evidence: https://hadalinstruments.com/research/what-can-a-trading-statement-prove/#claim-4f913431 ### Claim 03 — canonical: https://hadalinstruments.com/refutations/#claim-3e944a06 > "The timestamps on my statement show exactly when things happened." — our reading: Misleading Timestamps are usually server time, in a timezone set by the broker and frequently not stated in the file. They record when the server processed an event, not when you acted and not when the market moved. For any question about sequence — which came first, your order or the price move — that distinction decides the answer. It is recoverable: the offset can be established from the record itself, and once established the sequence becomes analysable. Assuming the times are local, or that they mark your action rather than the server's, is where reconstructions go wrong before any arithmetic starts. **What is true:** Statement timestamps are server-side and carry a broker-set timezone, so they record when the server processed an event rather than when a trader acted — the offset is recoverable from the record, and sequence questions depend on recovering it. Evidence: https://hadalinstruments.com/research/what-can-a-trading-statement-prove/#claim-3e944a06 ## Cite This Article APA BibTeX HTML Hadal Research. (2026). What can a trading statement prove?. Hadal Research. https://hadalinstruments.com/research/what-can-a-trading-statement-prove/ Version 52b10d7, 2026-09-14. @misc{hadal_2026_what-can-a-trading-statement-prove, author = {Hadal Research}, title = {What can a trading statement prove?}, year = {2026}, url = {https://hadalinstruments.com/research/what-can-a-trading-statement-prove/}, howpublished = {Hadal Research}, version = {52b10d7}, note = {Published: 2026-08-05; version dated 2026-09-14} } Source: Hadal Research, What can a trading statement prove?. Original Research Copy Citation **Version 52b10d7** identifies the commit that last changed this page in Hadal's content repository. That repository is not public, so the identifier does not resolve externally — it is published so a citation pins one specific state rather than a moving page. To obtain the exact version cited, use the [press and research route](https://hadalinstruments.com/press/). ## Explore further ### Instruments - [Broker Feed Auditor](https://hadalinstruments.com/instruments/broker-feed-auditor/) - [Prop-Evaluee Risk Guardian](https://hadalinstruments.com/instruments/prop-evaluee-risk-guardian/) ### Concepts - [Execution Cost](https://hadalinstruments.com/glossary/execution-cost/) - [High-Water Mark](https://hadalinstruments.com/glossary/high-water-mark/) - [Slippage](https://hadalinstruments.com/glossary/slippage/) - [Tick Data Provenance](https://hadalinstruments.com/glossary/tick-data-provenance/) - [Trailing Drawdown](https://hadalinstruments.com/glossary/trailing-drawdown/) ### Research - [What a funded trading account breach means](https://hadalinstruments.com/research/what-a-funded-trading-account-breach-means/) Asked as: what does a funded account breach mean - [Where a funded-account breach dispute can go](https://hadalinstruments.com/research/where-does-a-breach-dispute-go/) Asked as: where does a prop firm breach dispute go - [Why is my live spread wider than my backtest?](https://hadalinstruments.com/research/why-is-my-live-spread-wider-than-my-backtest/) Asked as: why is my live spread wider than my backtest [All Hadal research](https://hadalinstruments.com/research/)[This article as plain markdown](https://hadalinstruments.com/research/what-can-a-trading-statement-prove.md) --- ## Raw artifact — NOT PUBLISHED FOR THIS PAGE No downloadable artifact ships with this page. Eight published measurements do, each content-hashed so a reader can verify the figures independently. Where a measurement is published here without one, that is a gap rather than a policy, and it is stated rather than left to be noticed. [Measurements that ship their data](https://hadalinstruments.com/research/)