Prop Account CSV IDs: Preserve Text Before Joining Executions
An execution join can fail before any profit calculation begins if identifiers change during import. Preserve IDs as exact text and keep the original export. A visually similar spreadsheet cell is not enough to prove an unchanged key.
Explore this site’s existing research resource
Separate CSV syntax from field meaning
RFC 4180 describes CSV field and quoting conventions; it does not provide a typed account schema that forces every importer to treat an ID as text. Set the import interpretation deliberately and check the actual retained string.
For example, original key 000123 is different text from 123. A system may define a normalisation rule, but that rule must be documented rather than guessed. A second identifier in a different account can also share the same digits without identifying the same execution.
Test a fictional precision boundary
The strings 9007199254740992 and 9007199254740993 are distinct identifiers. Converting both through a standard binary 64 numeric representation can lose that distinction. Keep these keys as strings rather than relying on a rounded numeric display.
A safe local round-trip check compares exact original and exported key strings, including leading zeros. It should also detect collisions and unmatched rows. A changed key needs reconciliation from source evidence; it should not be repaired by selecting the nearest-looking number.
| Original field | Potential transformation | Audit result |
|---|---|---|
| 000123 | 123 | Changed key unless explicit source rule |
| 9007199254740992 | Numeric import | Precision-sensitive boundary |
| 9007199254740993 | Same rounded numeric value possible | Keep exact text |
| Two account namespaces | Same local digits | Do not merge without full identity |
Join account records only after identity is sound
The existing CSV checker on this site remains the companion. A British date display can be useful, but it must not alter IDs or decimal fields. Keep numeric amounts, asset units and timestamps separately typed from identity fields.
The optional sponsored HashHedge link offers current programme conditions. This article uploads no private export and joins no real account data. Its fictional examples establish an integrity check, not an execution record, account result or confirmed provider schema.
Sources and rule dates
- RFC4180: CSV field syntax
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: challenge types
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.