OKX crypto accounting

OKX crypto accounting spans more than spot. OKX runs spot, perpetual and dated futures, options, and Earn — and each books differently, from lot-based spot disposals to realised derivative PnL to reward income. A spot export captures almost none of the derivative side. CryptaCount ingests every product into a crypto sub-ledger, reconciles it to the venue, and posts summarised journal entries to your general ledger — built for finance teams, funds and treasuries.

OKX as a source for your sub-ledger

OKX is a multi-product venue; CryptaCount is where its spot, derivatives and Earn activity becomes accounting. It pulls each product into a crypto sub-ledger, applies your measurement policy, and produces summarised journal entries for your general ledger, with the position-level detail held behind every line.

How to connect

1. Read-only API (recommended). In OKX, create an API key with read-only permission only — leave trading and withdrawals unchecked. In CryptaCount, go to Integrations → OKX and paste it.
2. CSV import. Export your transaction history from OKX and upload it.

A read-only key lets CryptaCount read your history for the books but never move funds — a control you can evidence directly to an auditor.

What flows into your books

An OKX account mixes several products, and each books to different accounts. Sorting the history into these buckets is most of the work:

Spot trades and conversions

Each spot disposal or token-to-token conversion carries a cost basis and posts to realised gain/loss, with conversions recognised as a paired disposal and acquisition.

Perpetual and dated futures

Closed futures positions post realised PnL, and funding is booked as cost or income — a separate ledger from spot.

Options

OKX option events — premiums written or paid, expiry, exercise or assignment — are recognised as derivative outcomes and posted as realised results, not coin disposals.

Earn and savings rewards

Earn rewards are income at fair value on receipt, carried forward as the basis for a later disposal.

Transfers and in-app conversions

Movements between your own accounts are matched as transfers; in-app conversions are disposals of the asset given up.

Built for finance teams

• Built for multi-product volume — spot, futures, options and Earn run high; the sub-ledger ingests them and posts summarised entries
• Automated cost basis — 12 disposal methods (FIFO, LIFO, HIFO, WAVG, Specific ID, and more); jurisdiction-mandated treatments (UK Section 104 pooling, Canada ACB) apply automatically
• Journal entries to your ERP — QuickBooks, Xero, NetSuite or Sage → ERP integrations →
• Audit-ready — every GL line drills back to the OKX transaction behind it
• IFRS / US GAAP — measurement applied in the sub-ledger per your policy

See the sub-ledger → · Accounting for firms →

Accounting across OKX's spot, derivatives and options

The accounting challenge with OKX is breadth: a single account can hold lot-based spot positions, perpetual and dated futures, and options, each measured on different terms. Spot disposals consume acquisition lots and post a gain or loss; futures post realised PnL per closed position with funding alongside; options post the outcome of premiums, expiries and exercises as derivative results. CryptaCount keeps each product in its own lane within the sub-ledger so they are never conflated, and maps each to the correct accounts in your chart.

That separation is what makes a busy OKX account auditable. Where your policy marks open derivative positions to market at period end, the sub-ledger retains the position detail to support and reverse the valuation; where it does not, only realised results post. Either way the treatment is a consistent policy choice, and every posted figure drills back to the specific OKX event — lot, contract or option — that produced it.

Reconciling a mixed OKX account

With several products in one account, reconciliation is the control that keeps the books honest. CryptaCount tracks the balances implied by your classified spot, futures, options and Earn history and compares them to what OKX reports, so a missing transfer, an unclassified line or a gap in derivative history surfaces as a discrepancy to investigate rather than quietly distorting a balance. Earn rewards are recognised as income on receipt and then tracked as basis, so the income event and the later disposal stay distinct rather than conflated into one number.

How CryptaCount ingests OKX activity into the sub-ledger

Once your read-only key is connected, CryptaCount pulls your OKX history and keeps it current, writing each event as a discrete, timestamped record in the crypto sub-ledger. The general ledger only ever sees summarised journal entries, but the underlying detail is preserved in full so reconciliations, gain calculations and audit queries always have something concrete to stand on.

Ingestion is idempotent: each OKX event is keyed to its own identifiers, so re-syncing a period never duplicates an entry. That matters because you will refresh the data repeatedly — after a close, after a corrected export, after adding history — and balances must stay stable across every refresh rather than inflating each time. The sub-ledger becomes a dependable single source of truth for everything that happened on OKX, ready to be turned into accounting at scale.

Classifying and reconciling OKX transactions

CryptaCount turns raw OKX data into accounting events by classifying each record by product: a spot trade or conversion; a futures open or close with its realised PnL; an option premium, expiry or exercise; a funding payment; an Earn reward; or a transfer. Each maps to the right accounts — realised gain/loss, derivative PnL, reward income, funding and fees — so a single account's mixed activity is split cleanly rather than collapsed into one balance change.

Reconciliation proves the books against the exchange. CryptaCount tracks the running balance implied by your classified history and compares it to the position OKX reports, so a gap in history or an unclassified line surfaces as a discrepancy instead of quietly distorting balances. Any break between the sub-ledger and the venue is explainable and visible in your crypto sub-ledger → — the same control discipline an accountant applies to a bank reconciliation.

Cost basis and gain/loss for the books

Every disposal on OKX — a sale, a conversion into another asset, or a withdrawal your policy treats as a disposal — needs a cost basis so the realised gain or loss can be measured and posted. CryptaCount maintains acquisition lots per asset and consumes them on disposal under your chosen method, then books the resulting gain or loss to the general ledger alongside the asset movement.

Because the lots live in the sub-ledger, the posted figure is never opaque: you can drill from a gain on the GL back to the specific acquisitions it consumed, even across thousands of trades. See the available cost-basis methods → for how each consumes lots and shapes your reported results.

Transfers between your own accounts

Finance teams frequently move assets between OKX and other venues or wallets, and every one of those movements is a chance to mis-book a disposal. When you move an asset out of OKX into your own wallet, or in from another account, nothing has been sold — yet a naive import sees a withdrawal and a deposit and risks recognising a gain that never occurred. CryptaCount matches the two legs into a single movement of the same asset, carrying the original cost basis across the move instead of resetting it.

Matching considers asset, quantity, timing and direction, and flags anything it cannot confidently pair for human confirmation rather than guessing — exactly what an auditor wants to see when an asset crosses between accounts.

Fees and internal movements

OKX charges fees on its activity, and in aggregate those fees are a material part of the economics. CryptaCount captures each fee and treats it per your policy — adding a trading fee to an acquisition's cost basis, netting it against proceeds on a disposal, or booking it as an expense — so reported cost and gain reflect what activity actually cost.

• Trading and conversion fees — capitalised into basis or netted against proceeds per your measurement policy.
• Futures funding — recorded as cost or income on perpetuals, kept distinct from trading fees.
• Withdrawal / network fees — captured against the movement so the asset reduction is fully accounted for.
• Internal movements — paired across your own accounts and excluded from gain calculations, with basis carried forward intact.

Controls and the audit trail

The OKX connection is read-only — transaction history only, never trading or withdrawal access — a control you can evidence directly to an auditor or board. Every general-ledger line CryptaCount produces is traceable: a posted journal entry drills back through the sub-ledger to the exact OKX event behind it, with its date, asset, quantity and the figures that produced it. That unbroken chain from GL to source is what makes high-volume crypto books auditable, produced as a by-product of normal processing rather than reconstructed under deadline pressure at close.

Summarised entries keep your ERP clean while the transaction-level evidence stays in the sub-ledger, and the same data feeds your crypto compliance reporting → so statements and sub-ledger never diverge. The journals — debits, credits and account mappings — are reviewable before they reach the GL via journal entries →, so nothing is posted blind.

Multi-entity and treasury considerations

Organisations operating on OKX at scale rarely run through a single account or a single legal entity. CryptaCount's workspace model keeps each entity's OKX activity in its own books, with its own measurement policy and chart of accounts, while still reporting across the group when needed — a fund running several strategies, a firm serving multiple clients, or a treasury spanning subsidiaries.

That separation underpins both accuracy and governance. Cost basis, transfer matching and gain calculation all run within an entity's books, so a movement between two entities is treated as the intercompany transfer it is, not netted away. Review and permissions are scoped per workspace, supporting the segregation of duties auditors expect.

Common pitfalls when accounting for OKX activity

• Exporting spot only. Futures, options and Earn carry much of the realised result and reward income, and none appear in a spot export.
• Conflating products. Lot-based spot gains, derivative PnL and option outcomes are measured differently and must stay in their own lanes.
• Ignoring funding. Perpetual funding is a real cost or receipt on every futures position.
• Missing Earn income. Rewards are income at receipt and set the basis for a later disposal.
• Hand-keying summaries into the GL. Manual entry breaks the trail back to the OKX event behind each figure.

How CryptaCount uses your OKX data

CryptaCount reads your OKX history through a read-only connection, classifies every spot trade, futures and option position, funding payment, Earn reward and transfer into accounting events, reconciles them back to the venue, calculates results under your policy, and posts summarised journal entries to your ERP — with full, product-by-product detail retained in the sub-ledger so every figure is traceable to its source.