Practical market worksheet

Crypto Execution CSV Field Mapper and Validator

Turn an execution export into a file you can inspect row by row.

Your inputsBrowser calculationCSV export

Two hypothetical buy fills contain IDs a and b, quantities 3 and 2, and prices 100 and 101. Their timestamps are one second apart and explicitly in UTC. Both records are accepted. If another row repeats ID a, that later occurrence is rejected, making 3 input rows, 2 accepted rows and 1 rejected row.

What this helps you check

An exchange fill is one execution, while a closed trade may combine several fills. This worksheet maps your five column names, checks each execution and keeps a visible audit beside the accepted records. It helps you find an import problem before a spreadsheet or journal turns it into a misleading trade history.

Accepted means the supplied row passed these structural rules. It does not prove that your exchange export includes every execution. Read the rejection reason and correct the source record; the normalized export omits rejected rows rather than silently inventing replacements.

Your worksheet

No account connection required

Inputs are processed in your browser by this calculator. There is no quote lookup or file upload for the calculation. Site measurement and consent are handled separately by the site's privacy and consent controls.

CSV schema: fill_id (text), timestamp (iso8601), side (enum), quantity (number), price (number). Header required; comma delimiter. Numeric fields use decimal points. Timestamps require Z or a numeric UTC offset. The original input remains unchanged.

Interactive calculation requires JavaScript. The method and hypothetical worked example below remain readable.

Hypothetical worked example

Check the example by hand

Input rows: 2
Accepted rows: 2
Rejected rows: 0

Exact example inputs

{
  "fill_id_column": "fill_id",
  "timestamp_column": "timestamp",
  "side_column": "side",
  "quantity_column": "quantity",
  "price_column": "price",
  "csv": "fill_id,timestamp,side,quantity,price\na,2026-01-01T10:00:00Z,buy,3,100\nb,2026-01-01T10:00:01Z,buy,2,101"
}

The example is invented to demonstrate the method. It is not a current market quote, a provider's fee schedule or verified trading performance.

How the worksheet works

Parse mapped columns without rewriting the input.
Each accepted row needs nonempty unique fill_id, explicit-offset ISO8601 timestamp, buy/sell side, quantity>0 and price>0.
Keep first valid occurrence of a fill ID; later duplicates are rejected with row-specific audit warnings.
Normalize accepted timestamps to UTC ISO8601 and preserve source row order.

Boundaries to keep in view

Do not infer a local time zone or date format.
No automatic exchange-specific adapter or universal journal import claim.
Rejected rows remain visible in the audit and are excluded from normalized export.

Compare resources for this task

Execution-file preparation needs a clear boundary between raw fills, portfolio transactions and grouped journal trades. The resources here perform different jobs: some provide import workflows, others provide journals or a spreadsheet where you control the mapping.

10 Services for Crypto Execution CSV Preparation

Official sources and scope

The sources document formats, mechanisms or record workflows. The arithmetic and editorial comparison on this page use the supplied worksheet definitions.

Microsoft Excel CSV import/export
CSV import/export and explicit column interpretation; opening CSV applies default formats.
Reference checked 2026-10-01. Consult the source for current product rules.
Google Sheets data ingestion
CSV ingestion and spreadsheet analysis; file size and format limitations apply.
Reference checked 2026-10-01. Consult the source for current product rules.
LibreOffice Calc Text Import
Delimited text import with charset, separator, language and column settings.
Reference checked 2026-10-01. Consult the source for current product rules.
TradeZella generic CSV
Execution-based and trade-history templates, column mapping and crypto category.
Reference checked 2026-10-01. Consult the source for current product rules.
TraderSync trade file import
Trade file imports with explicit date format and time zone.
Reference checked 2026-10-01. Consult the source for current product rules.