Coinbase crypto accounting

Connect Coinbase to CryptaCount and turn your exchange activity into clean books. CryptaCount ingests every transaction, calculates cost basis, and posts journal entries to your ERP — with the transaction-level detail held in the sub-ledger.

Coinbase as a source for your sub-ledger

Coinbase records your trades; it isn't your accounting system. CryptaCount sits between them — it pulls your Coinbase activity into a crypto sub-ledger, applies cost basis and your measurement policy, and produces summarized journal entries for your general ledger.

How to connect

1. Read-only API (recommended). In Coinbase, create an API key with read-only access. In CryptaCount, go to Integrations → Coinbase and paste it — CryptaCount syncs continuously and never has trade or withdrawal access.
2. CSV import. Export your transaction history from Coinbase as a CSV and upload it in CryptaCount.

What flows into your books

Your Coinbase trades, deposits and withdrawals, staking and rewards (e.g. Coinbase Earn), and fees — each classified for accounting, with realized gains and income calculated, and transfers matched so they aren't booked as disposals.

Built for finance teams

• 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 — summarized and posted to QuickBooks, Xero, NetSuite, or Sage → ERP integrations →
• Audit-ready — every GL line drills back to the Coinbase transaction
• IFRS / US GAAP — measurement handled per your policy

See the sub-ledger → · Accounting for firms →

How CryptaCount ingests your Coinbase activity into the sub-ledger

Once your read-only Coinbase key is connected, CryptaCount pulls the full transaction history and keeps it current as new activity lands. Every fill, deposit, withdrawal, conversion, reward and fee becomes a discrete, timestamped record inside the crypto sub-ledger — not a summary line, but the underlying economic event with its asset, quantity, counterparty side and exchange reference intact. That granularity is the whole point: your general ledger only needs the net journal entries, but your auditors, your reconciliations and your gain calculations all depend on the detail sitting behind those entries, queryable at any time.

Ingestion is idempotent, so re-syncing the same period never double-counts a trade. CryptaCount keys each event to its Coinbase identifiers, recognises records it has already seen, and only writes what is genuinely new. That matters for a finance team because it means you can re-run a sync after a period close, after a corrected export, or after adding history, and trust that quantities and balances stay consistent rather than drifting with every refresh. The result is a single source of truth for everything that happened on Coinbase, ready to be turned into accounting.

Classifying and reconciling Coinbase transactions

Raw exchange data is not accounting data until each line has a meaning your books can use. CryptaCount classifies every Coinbase record into an accounting event type — a buy, a sale, a conversion between two assets, a deposit of crypto or fiat, a withdrawal, a reward or income receipt, or a fee — and maps that event to the right accounts in your chart. A conversion of one token into another is recognised for what it is: a disposal of the outgoing asset and an acquisition of the incoming one, each priced independently, rather than a single opaque movement that hides a taxable gain.

Reconciliation then proves the books against the exchange. CryptaCount tracks the running quantity of each asset implied by your classified history and checks it against the position Coinbase reports, so a missing import, a gap in history, or an unclassified line surfaces as a discrepancy instead of silently distorting your balances. This is the same control an accountant applies to a bank reconciliation, extended to crypto: the sub-ledger should reconcile to the venue, and any break should be explainable. The reconciliation status flows through to your crypto sub-ledger → so reviewers can see exactly where the books and the exchange agree.

Cost basis and gain/loss for the books

Every disposal on Coinbase — a sale to fiat, a conversion into another asset, or a withdrawal that your policy treats as a disposal — needs a cost basis so the realised gain or loss can be measured and posted. CryptaCount maintains the acquisition lots for each asset and consumes them on disposal under the method your accounting policy specifies, then books the resulting gain or loss to the general ledger alongside the movement of the asset itself. Because the lots live in the sub-ledger, the figure on the GL is never a black box: you can drill from the posted gain back to the specific acquisitions it consumed.

The engine supports the full range of disposal strategies a finance team may be required to use, and applies jurisdiction-mandated treatments automatically where they apply. The method you choose is a policy decision with real consequences for reported results, so it is set deliberately and applied consistently across periods rather than guessed per transaction — see the available cost-basis methods → for how each one consumes lots.

Transfers between your own accounts

One of the most common ways crypto books go wrong is treating an internal movement as a sale. When you move an asset from Coinbase to a self-custody wallet, or in from another venue, nothing has been disposed of — the asset has simply changed location within the organisation — yet a naive import sees a withdrawal on one side and a deposit on the other and risks booking a phantom gain. CryptaCount matches the two legs of an internal transfer so they are recognised as a single movement of the same asset, preserving the original cost basis across the move instead of resetting it or crystallising a gain that never happened.

Matching uses the asset, quantity, timing and direction of the two legs, and surfaces anything it cannot confidently pair for a human to confirm. That keeps you in control: an ambiguous transfer is flagged for review rather than quietly assumed, which is exactly the behaviour an auditor expects when cost basis is being carried from one account to another. The carried basis then follows the asset into whichever wallet or venue received it, so a later disposal there is still measured against the true original cost.

Fees and internal movements

Coinbase charges fees on trades, conversions and withdrawals, and those fees are part of the economics of each transaction rather than a footnote. CryptaCount captures every fee and treats it according to your policy — adding a trading fee to the cost basis of an acquisition, netting it against proceeds on a disposal, or booking it as an expense — so your reported cost and gain reflect what the activity actually cost you. Small per-transaction fees are easy to lose by hand, but across a high volume of activity they add up to a real number, and leaving them out understates cost and overstates gains.

• Trading and conversion fees — capitalised into basis or netted against proceeds per your measurement policy, never silently dropped.
• Network / withdrawal fees — captured against the relevant movement so the asset reduction is fully accounted for.
• Reward and income receipts — recognised at fair value on receipt and given a cost basis for the eventual disposal, so income and later gain are not conflated.
• Internal movements — paired across accounts and excluded from gain calculations, with basis carried forward intact.

Controls and audit trail

Because the connection is read-only, CryptaCount can see your Coinbase history but can never trade or withdraw — a control that is easy to evidence to an auditor or a board. Beyond access, every general-ledger line CryptaCount produces is traceable: a posted journal entry drills back through the sub-ledger to the exact Coinbase transaction that gave rise to it, with its date, asset, quantity and the cost-basis lots consumed. That unbroken chain from the GL to the source event is what turns a pile of exchange data into something an auditor can actually sign off, and it is generated as a by-product of normal processing rather than reconstructed at year-end.

Summarised entries post to your ERP, while the transaction-level detail stays in the sub-ledger for inspection, which keeps the general ledger clean without sacrificing the evidence behind it. For period reporting and disclosures, the same data feeds your crypto compliance reporting →, so the numbers in your statements and the numbers in your sub-ledger are the same numbers, derived once. The journals themselves — debits, credits and account mappings — are visible and reviewable before they ever reach the GL via journal entries →.

Multi-entity and treasury considerations

Most organisations that use Coinbase at scale do not have a single account or a single legal entity. CryptaCount is built around a workspace model, so you can keep each entity's Coinbase activity in its own set of books, apply the measurement policy and chart of accounts that entity uses, and still report across the group when you need a consolidated view. A fund administrator running several vehicles, an accounting firm serving multiple clients, or a corporate treasury spanning subsidiaries can each connect the relevant Coinbase accounts to the right workspace without the data bleeding across boundaries.

This separation matters for both accuracy and governance. Cost basis, transfer matching and gain calculation all operate within an entity's books, so an internal transfer between two entities is treated as the intercompany movement it actually is, not netted away as if the group were one wallet. Permissions and review can be scoped per workspace too, so the people who reconcile one entity are not necessarily the people who close another — the kind of segregation of duties an auditor looks for.

Common pitfalls when accounting for Coinbase activity

• Treating conversions as non-events. A swap of one asset for another is a disposal and an acquisition; ignoring it hides a realised gain or loss that belongs in the period.
• Booking internal transfers as sales. Moving crypto from Coinbase to your own wallet is not a disposal — matching the legs prevents a phantom gain and preserves basis.
• Dropping fees. Trading and withdrawal fees affect cost and proceeds; omitting them quietly overstates gains over a year of activity.
• Mixing income and disposal. A reward is income at receipt and a separate gain or loss on later sale; collapsing the two distorts both figures.
• Re-keying summaries into the GL by hand. Manual entry breaks the audit trail back to the source transaction and invites reconciliation gaps that are painful to unwind at close.

How CryptaCount uses your Coinbase data

In short: CryptaCount reads your Coinbase history through a read-only connection, classifies every trade, conversion, transfer, reward and fee into accounting events, reconciles the resulting positions back to the exchange, calculates cost basis and realised gains under your policy, and posts summarised journal entries to your ERP — with the full transaction-level detail retained in the sub-ledger so every number is traceable to its source. It is the layer that turns an exchange account into auditable books, without touching your funds. If you want to see how it would handle your specific Coinbase setup, our team can walk through it with you.

Does CryptaCount keep transaction-level detail or just summaries?

Both. The general ledger receives summarised journal entries so it stays clean, but the full, classified, transaction-level history lives in the sub-ledger. Every summarised line drills back to the individual Coinbase transactions behind it, so you get a tidy GL and complete evidence at the same time.

Can we change cost-basis method after connecting Coinbase?

The disposal method is a policy choice applied consistently to your books, so it is configured deliberately rather than switched casually mid-period. Because the acquisition lots are stored in the sub-ledger, CryptaCount can recompute gains under the method your policy requires, and any change is something to make as a considered accounting decision with your auditor, not a per-transaction toggle.

How does CryptaCount handle Coinbase rewards and staking income for the books?

Rewards and staking receipts are recognised as income at their fair value on the date received, and that same value becomes the cost basis of the received asset. When the asset is later disposed of, the gain or loss is measured against that basis, so the income event and the disposal event are kept distinct in the books rather than collapsed into one figure.

What if our Coinbase history predates the connection?

You can bring in historical activity by extending the synced range or by importing a CSV of earlier transactions, and the idempotent ingestion means adding history will not double-count anything already present. Complete history matters for cost basis, because the lots acquired in earlier periods determine the gain on disposals you make today.