Keep file grammar and data meaning as separate decisions
A CSV parser can correctly identify fields while leaving their contents unresolved. RFC 4180 describes common comma-separated field and quoting conventions; it does not specify whether a comma inside an exported number means a decimal mark or a thousands separator.
Record the original file, its declared encoding, separator and quote rule. Preserve the untouched text values before normalisation. A Canadian reporting view may receive files created under different locale conventions, so the machine’s current display preference is not sufficient evidence.
Do not choose a scale from one ambiguous field
The string 1,234 can represent 1.234 under one supplied number convention or 1234 under another. Those values differ by a factor of 1000. Putting the string inside a correctly quoted CSV field protects its column boundary; it does not select the number convention.
A semicolon-separated file can also contain a decimal comma, but the semicolon alone is not proof that every numeric field uses that convention. Preserve the source declaration or other reliable evidence before choosing a conversion.
| Fictional source text | Declared interpretation | Possible numeric value |
|---|---|---|
| "1,234" as one CSV field | Decimal comma | 1.234 |
| "1,234" as one CSV field | Thousands comma | 1234 |
| Convention absent | Ambiguous | Do not silently choose one |
Validate the role of each mapped column
A quantity, a price, a cumulative amount and a fee can all look like decimal strings while having different meanings and units. Record the original column name and mapped role. A successful numeric parse cannot prove that the mapping itself is correct.
Keep base quantity, quote amount and commission asset explicit. Dividing two columns to obtain a plausible average price is not independent confirmation that they describe the same instrument or event. An unresolved mapping should remain visible before an output file is saved.
A readable date still needs its source convention
A date such as 03/04 can mean different calendar dates under different conventions, and a clock without an offset may not identify an instant. Preserve the original timestamp string, its declared format and any separate source time-zone information.
Do not add a current local offset to an old record merely because it makes the table sortable. Missing time evidence can leave event order unresolved. A source event time and the moment you received the export are also separate observations.
Save a review decision, not a false authentication claim
A useful import note states which grammar and data conventions were supplied, which mappings were accepted and which fields remain ambiguous. Preserve a reversible relationship to the original text so later evidence can revise a conversion without losing the source.
This article imports no private file, accesses no account and authenticates no execution. Its text examples are fictional. A clean-looking CSV is not proof of complete coverage, correct fees, profitability or the linked offer’s reliability.
The optional link below leads to this site's separate crypto signals and Telegram updates offer. The record method is usable without that offer. It does not independently verify the offer, establish country eligibility or turn the teaching example into an actual transaction.
Primary sources and scope
- RFC 4180: Common Format for CSV Files
CSV field separators and quoting are format rules. They do not establish the number-format or timestamp convention of a supplied execution export. Checked 2026-10-21. - RFC 3339: Internet timestamps
Full dates and explicit numeric offsets; a timestamp representation does not prove clock synchronisation. Checked 2026-10-21.