Kraken Institutional crypto accounting

Kraken Institutional crypto accounting brings institutional trading, custody and staking into auditable books. Kraken's institutional offering combines trading, qualified custody and staking for funds and businesses, so an account mixes executed trades, custody movements and reward income — all of which must reach the general ledger correctly. CryptaCount ingests the activity into a crypto sub-ledger, reconciles it, and posts summarised journal entries to your GL, built for funds, treasuries and the firms that serve them.

Kraken Institutional as a source for your sub-ledger

Kraken Institutional is an institutional trading, custody and staking venue; CryptaCount is where its activity becomes accounting. It pulls trades, custody movements and staking into a crypto sub-ledger, applies your measurement policy, and produces summarised journal entries for your general ledger with full detail behind every line.

How to connect

1. Read-only API (recommended). In Kraken Institutional, create an API key with read-only permission only — leave trading and withdrawals unchecked. In CryptaCount, go to Integrations → Kraken Institutional and paste it.
2. CSV import. Export your transaction history from Kraken Institutional 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 Kraken Institutional account mixes trading, custody and staking, and each books differently. Sorting the history into these buckets is most of the work:

Executed trades

Each trade is a disposal of one asset and an acquisition of another, posting realised gain/loss against cost basis.

Custody movements and transfers

Moving assets between custody and your own wallets is a transfer, not a disposal, matched across legs.

Staking rewards

Kraken's institutional staking pays rewards recognised as income at fair value on receipt, then carried forward as basis.

Settlements and fees

Settlements are payments or receipts, and fees are captured per policy, kept distinct from trading results.

Built for finance teams

• Built for institutional volume — trades, custody movements and staking 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 Kraken Institutional transaction behind it
• IFRS / US GAAP — measurement applied in the sub-ledger per your policy

See the sub-ledger → · Accounting for firms →

Trading, custody and staking in one set of books

Kraken Institutional combines trading, qualified custody and staking, so the accounting job is to keep three different kinds of activity straight. Trades post realised gains or losses against cost basis; custody movements are transfers that must not be booked as sales; staking rewards are income at fair value on receipt. Treating them alike is how institutional books drift, because a custody transfer mistaken for a trade or a reward left unrecorded both distort the result. CryptaCount classifies each record for what it is and maps it to the right account, with cost basis following assets across custody movements.

Reconciliation is the control that holds it together at scale: CryptaCount tracks the positions implied by your classified history and compares them to what Kraken reports, so a missing fill, an unsettled trade or an unrecorded reward surfaces as a discrepancy rather than quietly distorting balances. Every posted figure drills back to the specific trade, transfer or reward that produced it.

Institutional staking and multi-entity reporting

Institutional staking is a meaningful income stream that a trades-only view misses, so CryptaCount recognises each reward at fair value on receipt and tracks the basis forward into a later disposal. And because funds and firms operate through multiple entities, the workspace model keeps each entity's Kraken Institutional activity in its own books with its own policy and chart of accounts — so intercompany movements stay clean, consolidation is not distorted, and review can be scoped per entity for the segregation of duties auditors expect.

Qualified custody and the audit trail

Institutions choose Kraken's qualified custody for security and assurance, and the accounting should match that bar. Every position CryptaCount reports from Kraken Institutional traces back through the sub-ledger to the specific trade, custody movement or staking reward that produced it, and each of those ties to an exchange record — so the unbroken chain from a general-ledger figure to its source is recorded as you go rather than reconstructed at year-end. For a fund or a firm whose books face an auditor, that traceability across both the trading and the custodied side is exactly what turns an institutional crypto position into a defensible set of accounts.

How CryptaCount ingests Kraken Institutional activity into the sub-ledger

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

Classifying and reconciling Kraken Institutional transactions

CryptaCount turns raw Kraken Institutional data into accounting events by classifying each record: an executed trade with its realised result, a custody transfer, a staking reward, or a settlement. Each maps to the right accounts — digital assets, realised gain/loss, income and fees — so institutional trading, custody and staking become clean journal entries rather than mixed activity.

Reconciliation proves the books against the exchange. CryptaCount tracks the running balance implied by your classified history and compares it to the position Kraken Institutional 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 Kraken Institutional — 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 Kraken Institutional 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 Kraken Institutional 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

Kraken Institutional 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 basis or netted against proceeds per your measurement policy.
• Network / withdrawal fees — captured against the movement so the asset reduction is fully accounted for.
• Staking rewards — recognised at fair value on receipt and given a cost basis for the later disposal.
• Internal custody movements — paired across your own accounts and excluded from gain calculations.

Controls and the audit trail

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

• Booking custody movements as trades — moving your own assets is a transfer, not a disposal.
• Missing staking income — institutional staking rewards are income at receipt.
• Mixing settlements into trading results — they book to different accounts.
• Losing basis across custody movements — cost basis must follow the asset.
• Hand-keying institutional summaries into the GL — manual entry breaks the trail back to the source record.

How CryptaCount uses your Kraken Institutional data

CryptaCount reads your Kraken Institutional activity through a read-only connection, classifies every executed trade, custody movement, staking reward and settlement into accounting events, matches internal transfers, reconciles back to the platform, calculates results under your policy, and posts summarised journal entries to your ERP — with full detail retained in the sub-ledger so every figure is traceable to its source.