Nado perps CSV and Koinly: a safe way to map closed PnL without inventing trades

Description and use

The mapper converts a Nado CSV into a Koinly‑compatible format by adding closed‑PnL, correct timestamps, and settlement tokens, yet manual review is needed.

Problem

A Nado trader’s CSV export was incompatible with Koinly because it lacked an explicit closed‑realized‑PnL column and proper timezone information.

Outcome

The mapper produces a structurally valid Koinly CSV that includes closed‑realized‑PnL, correct timestamps, and settlement tokens, but it does not guarantee tax correctness without human review.

Workflow

Load 3 fictional closed‑PnL rows in the tool
Read local CSV headers
Select source fields for UTC close date, signed realized PnL, and settlement token
Confirm fields and reconcile funding/fees
Export a Koinly‑compatible CSV
Import into Koinly

Evidence

A CSV containing only fills, not an explicit already-closed realized-PnL column, does not tell you a final gain without additional position and fee state.

Source

The documented tag text for already realized closed futures PnL is realized gain.