Skip to content
Resources for your own records

Crypto Execution CSV Field Mapper and Resources

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

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.

Calculate and inspect

Crypto Execution CSV Field Mapper and Validator

Map execution columns, flag invalid rows and download a normalized CSV before reviewing trades.

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.

Open the worksheet
Choose references

10 Services for Crypto Execution CSV Preparation

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.

Compare documented roles using execution records versus closed trades, column mapping, explicit timestamps, file completeness, cloud upload versus own spreadsheet. The Telegram channel we promote is disclosed in the first entry.

Read the comparison

Prepare useful inputs

Keep a copy of the original export. Enter the exact column headers for fill ID, timestamp, side, quantity and price. Use one row per fill. A timestamp must contain Z or an explicit UTC offset; quantity is base units and price is quote currency per base unit. Do not paste a closed-trade summary into an execution schema.

Read results in their proper scope

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.

The worked example and method can be read without JavaScript. Running the calculator requires JavaScript; its form values remain in the browser, with no account connection or quote lookup for calculation.

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.

Worksheet definitions and reference review: 1 October 2026. Examples are hypothetical. The calculator processes supplied inputs locally; it does not verify records or fetch current market values.

Main site and channel offer · Learn resources