Crypto Exchange Statement Reconciliation: API, CSV, and the Trade-Fee Trap

Teams reconcile a centralized exchange like a bank and get burned. There is no canonical statement, the API and CSV often disagree, and every trade carries a fee that quietly moves cost basis. This guide is the reconciliation discipline for CEX activity — distinct from on-chain and bank reconciliation — hedged, because the treatment of differences is a controls and auditor question.

TL;DR

• Not bank reconciliation: a CEX has no single canonical statement like a bank; API vs CSV exports diverge (fields, granularity, figures); the exchange is itself the counterparty.
• Neither API nor CSV is universally authoritative — it is a documented entity source-of-record policy, applied consistently.
• Trade fees are the trap: every trade carries a fee (netted / separate / different asset) — inconsistent handling drifts quantity and cost basis even when the headline balance ties.
• Complementary to on-chain recon — wallet↔exchange transfers must reconcile across both without double-count/disposal.
• Defensible = source-of-record policy + consistent fee treatment + complete account capture + cadence + break resolution + audit trail.
• Entity controls; sufficiency/accounting effect are the auditor's. Not accounting advice.

Why it is not bank reconciliation

Bank reconciliation has a canonical statement from the bank as the authoritative external record. A CEX typically does not provide one the same way — the API export and CSV export differ (fields, granularity, sometimes figures), there is no universal format, and the exchange is itself the counterparty whose record you reconcile to. So it needs a defined source-of-record policy and tolerance for source divergence (cf. crypto bank reconciliation).

API or CSV?

Neither universally authoritative — it is an entity policy decision which source is the record and how API/CSV discrepancies are resolved, documented and consistently applied. Silently switching sources, or assuming they agree, produces unexplained breaks. The chosen source-of-record and method are part of the control environment.

The trade-fee trap

Every trade typically carries a fee reducing proceeds / increasing cost, and fee handling differs by exchange and export (netted, separate, or charged in a different asset). Inconsistent fee reconciliation makes quantity and cost basis drift even when the headline balance appears to tie (this feeds auditing cost basis & gains). Fee treatment must be explicit; its accounting effect is framework-specific, auditor-confirmed.

Relation to on-chain reconciliation

Complementary: on-chain reconciliation ties wallet activity to the chain; exchange reconciliation ties exchange-account activity to the exchange's records; wallet↔exchange transfers must reconcile across both without double-count or disposal (see internal transfer vs disposal). Treating either alone as the whole reconciliation leaves a gap.

Practical guidance

1. Don't treat a CEX like a bank — no canonical statement.
2. Document a source-of-record policy (API vs CSV) and apply it consistently.
3. Make fee treatment explicit — inconsistent fees drift cost basis.
4. Reconcile wallet↔exchange transfers across both sources — no double-count/disposal.
5. Capture every exchange account; reconcile at a cadence; resolve breaks.
6. Controls are the entity's; sufficiency/accounting are the auditor's — not accounting advice.

How vendor tools handle exchange reconciliation

Cryptio and Bitwave ingest exchange API/CSV data and reconcile it, handling fees and wallet↔exchange transfers. Confirm the tool lets you set the source-of-record policy and fee treatment — the tool reconciles; the policy choice and accounting effect are entity/auditor judgements.

How Wag3s helps

Wag3s Ledger ingests exchange API/CSV with a configurable source-of-record policy and explicit fee treatment, reconciles wallet↔exchange transfers without double-counting, at a defined cadence with break tracking and an audit trail — while policy and accounting effect stay entity-/auditor-confirmed. See the Ledger product page.

Further reading

• Crypto Bank Reconciliation
• Multi-Chain Reconciliation
• Internal Transfer vs Disposal (Crypto)
• Auditing Crypto Cost Basis & Gains
• Gas Fee Reconciliation
• Reconciliation Break Investigation (Crypto)

Sources

• A centralized exchange has no single canonical statement like a bank; API vs CSV exports diverge (fields/granularity/figures), no universal format, and the exchange is itself the counterparty — needs a documented source-of-record policy and tolerance for source divergence
• Neither API nor CSV is universally authoritative — entity policy decision, documented and consistently applied; silently switching/assuming agreement produces unexplained breaks
• Trade fees (netted/separate/different asset, varying by exchange/export) drift quantity and cost basis if handled inconsistently even when the headline balance ties — fee treatment explicit, accounting effect framework-specific
• Complementary to on-chain reconciliation; wallet↔exchange transfers reconcile across both without double-count/disposal; defensibility = source-of-record policy + consistent fees + complete capture + cadence + break resolution + audit trail — entity controls, sufficiency/accounting the auditor's; not accounting advice