Prop Trading CSV Results: Resolve Decimal Ambiguity Before Summing
Opening an execution CSV into columns is not enough to make its numeric interpretation correct. Save the export schema, delimiter, quoting and number convention before calculating a prop-account result. Language or residence alone should not decide how a value is parsed.
Explore this site’s existing research resource
Keep the raw field and declared convention
A quoted field containing 1,250 can be read as one thousand two hundred fifty or as one point two five under different conventions. Quoting protects a delimiter inside a field; it does not declare the numeric convention. Preserve the original field and documented schema.
For a Canadian reader working with English and French records, the safest evidence is the actual export definition rather than a guessed locale. A spreadsheet’s automatic conversion can remove the ambiguity from view without resolving its cause.
Separate a known subtotal from an unresolved row
In a fictional file, row A is a documented 12.50 quote-unit profit, row B is a documented −2.00 cost, and row C contains the ambiguous field. The confirmed subtotal is 10.50 before row C. Do not report 10.50 as the complete account total.
Retain row C’s movement ID, original field and unresolved convention. Once the actual schema establishes its meaning, add the interpreted amount with that source recorded. Never infer a zero because a parser rejected the field or because a cell looks blank.
| Row | Raw or interpreted field | Treatment |
|---|---|---|
| A | 12.50 with documented convention | +12.50 |
| B | −2.00 with documented convention | −2.00 |
| C | Quoted 1,250; convention absent | Unresolved, not zero |
| Confirmed subtotal | A + B | 10.50 excluding unresolved C |
Reconcile before checking the evaluation
The earlier CSV resource on this site remains the detailed companion for field quoting. An actual account review also needs duplicate handling, asset units, period and costs. HashHedge’s daily-loss rules cannot be assessed from an incomplete trade subtotal alone.
The sponsored link offers current HashHedge information. This article reads no private export, uploads no financial data and does not claim a measured account result. Its worked rows are fictional, with uncertainty deliberately retained.
Sources and rule dates
- HashHedge: daily loss calculation
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established. - HashHedge: terms and conditions
Checked 2026-10-23. Selected published description only. Worked numbers and event records are fictional; no actual provider account, search result, live price, eligibility or payment is established.