Deribit crypto accounting

Deribit crypto accounting is unlike a normal exchange's. Deribit is a derivatives-only venue — options, perpetuals and dated futures, with no spot market — so what reaches your books is realised PnL, funding and option outcomes settled in crypto, not coin-by-coin buys and sells. CryptaCount ingests that activity into a crypto sub-ledger, applies your measurement policy, reconciles it to the venue, and posts summarised journal entries to your general ledger — built for the finance teams, funds and treasuries that trade on Deribit.

Deribit as a source for your sub-ledger

Deribit is where the derivatives trading happens; CryptaCount is where it becomes accounting. Because there is no spot market, the sub-ledger is not tracking purchases and sales of coins — it is recording the realised results of options and futures positions, the funding exchanged on perpetuals, and the crypto collateral that settles them. CryptaCount pulls that activity in, classifies it for the books, and produces summarised journal entries for your general ledger with the position-level detail held behind them.

How to connect

1. Read-only API (recommended). In Deribit, create an API key with read-only permission only — leave trading and withdrawals unchecked. In CryptaCount, go to Integrations → Deribit and paste it.
2. CSV import. Export your transaction history from Deribit 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

A Deribit account mixes several kinds of derivative activity, and each books differently. Sorting the history into these buckets is most of the accounting work:

Options premiums, expiry and exercise

Writing an option brings in a premium; buying one pays one. When an option expires worthless the writer's premium and the buyer's cost crystallise; when it is exercised or assigned, the premium folds into the result of the position that follows. Each is a discrete, dated event that posts to the books — not a coin disposal.

Perpetual and dated futures PnL

Each closed perpetual or dated-futures position produces a realised gain or loss in its own ledger. These are the bulk of what reaches the GL from Deribit, and none of them resemble a spot trade.

Funding payments

Perpetuals exchange periodic funding between long and short holders. Each funding payment is a real cost or receipt that adjusts the net result and is booked accordingly, not ignored.

Collateral and crypto settlement

Deposits, withdrawals and crypto-settled PnL move your collateral balance in BTC, ETH or other assets. Those movements are recorded and, where they are your own transfers, matched rather than booked as disposals.

Built for finance teams

• Built for derivative volume — options legs, perpetual fills and funding events 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 Deribit transaction behind it
• IFRS / US GAAP — measurement applied in the sub-ledger per your policy

See the sub-ledger → · Accounting for firms →

Accounting for a derivatives-only venue

The defining feature of Deribit for the books is that there is no spot trading to fall back on. You are not acquiring and disposing of coins on Deribit in the usual sense — you are opening and closing derivative positions against crypto collateral, so the accounting is built around realised PnL and option outcomes, not lot-by-lot cost basis on a held asset. That reshapes which accounts move: realised gain/loss on closed positions, funding cost or income, and fees, rather than a string of asset acquisitions and disposals.

CryptaCount books that activity as the derivative results it is — each closed position and each settled option posting a realised figure to the general ledger, mapped to your chart of accounts. Where your measurement policy requires open positions to be marked to market at period end, the sub-ledger holds the position detail needed to support that valuation; where it does not, only realised results post. Either way the treatment is your policy choice, applied consistently, with the position-level evidence retained underneath.

Crypto-settled PnL and functional-currency valuation

On Deribit everything is settled in crypto — your collateral and your PnL are denominated in BTC, ETH or other supported assets, not fiat. For the books that adds a valuation step the venue does not do for you: a profit measured in BTC has to be converted to your functional or presentation currency at the time of the event to post a meaningful figure, and the collateral itself moves in value between events. CryptaCount values each crypto-settled result at the appropriate point and records it in the currency you report in, so the GL reflects your accounting position rather than a raw token quantity.

This matters most for multi-entity and treasury setups, where a Deribit result earned in one entity's books has to consolidate cleanly with the rest of the group. Because valuation and matching run inside each entity's workspace, intercompany collateral moves are treated as transfers rather than netted away, and the consolidated picture is not distorted by mismatched crypto-to-fiat conversions. See crypto compliance reporting → for how the same figures feed your statements.

How CryptaCount ingests Deribit activity into the sub-ledger

Once your read-only key is connected, CryptaCount pulls your Deribit 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 Deribit 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 Deribit, ready to be turned into accounting at scale.

Classifying and reconciling Deribit transactions

CryptaCount turns raw Deribit data into accounting events by classifying each record: an option open, close, expiry or exercise; a futures open or close with its realised PnL; a funding payment; or a collateral movement. Each classified event maps to the right accounts in your chart — realised gain/loss, funding cost or income, and the crypto collateral account — ready to become a journal entry. A token-settled result is recognised for what it is, so the economics are captured rather than hidden inside a 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 Deribit 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.

Booking derivative PnL to the general ledger

Because Deribit has no spot market, the gain/loss that reaches your GL is realised derivative PnL, not the result of consuming acquisition lots. Each closed perpetual or dated-futures position, and each option that expires or is exercised, produces a realised figure that CryptaCount posts to the general ledger alongside the collateral movement and any funding and fees attached to it. The number is never opaque: you can drill from a posted PnL line back to the exact Deribit position — its instrument, open and close, funding and fees — that produced it.

Where your policy treats open positions on a measurement basis (for example, marking them to market at period end), the sub-ledger retains the position-level detail required to support that valuation and to reverse it cleanly in the next period. The method is a deliberate policy choice applied uniformly across periods, not per-position guesswork — the same discipline a finance team applies to any derivative book.

Transfers between your own accounts

Finance teams frequently move assets between Deribit 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 Deribit 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

Deribit 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 fees — capitalised into the position result or booked as expense per your measurement policy.
• Funding payments — recorded as cost or income on perpetuals, kept distinct from trading fees so the economics are visible.
• Withdrawal / network fees — captured against the collateral movement so the asset reduction is fully accounted for.
• Internal movements — collateral you move between your own accounts is paired across them and excluded from gain calculations, with basis carried forward intact.

Controls and the audit trail

The Deribit 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 Deribit 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 Deribit at scale rarely run through a single account or a single legal entity. CryptaCount's workspace model keeps each entity's Deribit 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 Deribit activity

• Treating Deribit like a spot exchange. There is no spot; booking it as coin buys and sells misstates the activity — it is derivative PnL, funding and option outcomes.
• Ignoring funding payments. Perpetual funding is a real cost or receipt; leaving it out distorts the net result on every perpetual position.
• Not valuing crypto-settled PnL to your functional currency. A profit in BTC is not a number you can post until it is valued in the currency you report in.
• Conflating realised and unrealised. Whether open positions are marked to market is a policy choice; mixing the two without a basis produces results no one can reconcile.
• Hand-keying summaries into the GL. Manual entry breaks the trail back to the Deribit position and invites reconciliation gaps that are costly to unwind.

How CryptaCount uses your Deribit data

CryptaCount reads your Deribit history through a read-only connection, classifies every option, futures, funding and collateral event into accounting events, reconciles the resulting positions back to the venue, recognises realised PnL (and supports mark-to-market where your policy requires it) in your functional currency, and posts summarised journal entries to your ERP — with the full, position-level detail retained in the sub-ledger so every figure is traceable to its source. It is the layer that turns a derivatives account into auditable books without ever touching your funds. To see how it would handle your Deribit activity, our team can walk through your setup.