Coinbase Prime crypto accounting

Coinbase Prime crypto accounting brings institutional trading and custody into auditable books. Coinbase Prime combines prime brokerage, custody and trading for institutions, so a single account mixes executed trades, custody movements and staking — all of which must reach the general ledger correctly. CryptaCount ingests Coinbase Prime 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.

Coinbase Prime as a source for your sub-ledger

Coinbase Prime is an institutional trading and custody venue; CryptaCount is where its activity becomes accounting. It pulls executed 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 Coinbase Prime, create an API key with read-only permission only — leave trading and withdrawals unchecked. In CryptaCount, go to Integrations → Coinbase Prime and paste it.
2. CSV import. Export your transaction history from Coinbase Prime 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 Coinbase Prime account mixes trading and custody, 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 measured against cost basis.

Custody movements and transfers

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

Staking and rewards

Assets staked through Prime earn rewards recognised as income at fair value on receipt, then carried forward as basis.

Financing and settlements

Settlements and any financing activity are classified as payments, receipts or costs for the books, not folded into trading results.

Built for finance teams

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

See the sub-ledger → · Accounting for firms →

Institutional trading and custody in the books

Coinbase Prime brings trading and custody under one institutional roof, and the accounting job is to keep the two straight. Executed trades are disposals and acquisitions that post realised gains or losses against cost basis; custody movements — assets moving in, out, or between your own holdings — are transfers that must not be booked as sales. Conflating them is how institutional crypto books go wrong, because a custody transfer mistaken for a trade invents a gain that never occurred. CryptaCount classifies each Prime record for what it is and maps it to the right account.

At institutional scale, reconciliation is the control that makes the books trustworthy. CryptaCount tracks the positions implied by your classified Prime history and compares them to what the platform reports, so a missing fill, an unsettled trade or an unexplained custody movement surfaces as a discrepancy to investigate. Cost basis follows assets across custody movements, so a disposal is measured against the true original cost even after the asset has moved within the custody setup.

Staking, settlements and multi-entity

Beyond trading, Prime supports staking and institutional settlement flows, each with its own treatment: staking rewards are income at fair value on receipt; settlements are payments or receipts rather than trading results. And because institutions rarely operate through a single entity, CryptaCount's workspace model keeps each entity's Prime activity in its own books with its own policy and chart of accounts, so intercompany movements stay clean and consolidation is not distorted — the segregation auditors expect from an institutional setup.

Financing and prime-brokerage flows

Prime brokerage brings flows a plain trading account does not — financing, margin and OTC settlement among them — and each books on its own basis rather than as a simple buy or sell. Financing costs are expenses attached to the activity that incurred them; OTC settlements are payments or receipts; and the underlying trades still post realised gains or losses against cost basis. CryptaCount keeps these strands distinct in the sub-ledger and maps each to the right account, so the sophistication that makes Coinbase Prime useful for an institution does not turn its books into a single undifferentiated balance an auditor cannot unpick.

How CryptaCount ingests Coinbase Prime activity into the sub-ledger

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

Classifying and reconciling Coinbase Prime transactions

CryptaCount turns raw Coinbase Prime 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 and custody become clean journal entries rather than a stream of 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 Coinbase Prime 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 Coinbase Prime — 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 Coinbase Prime 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 Coinbase Prime 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

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

• Booking custody movements as trades — moving your own assets is a transfer, not a disposal.
• Mixing settlements into trading results — they book to different accounts.
• Missing staking income — institutional staking rewards are income at receipt.
• 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 Prime record.

How CryptaCount uses your Coinbase Prime data

CryptaCount reads your Coinbase Prime 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.