Crypto cost-basis methods

The method you use to value disposals changes your gains — and most jurisdictions mandate a specific one. Get it wrong across thousands of transactions and you've got the wrong numbers and an audit problem. CryptaCount supports the full range of methods and applies the treatment your jurisdiction requires automatically.

Why the method matters

A gain is proceeds minus cost basis — but *which* units you're deemed to have sold depends on the method. FIFO, average cost, and highest-in-first-out can produce very different results from the same trades, and the gap compounds across a real portfolio. On top of that, your jurisdiction usually doesn't leave it to preference: the UK requires pooling, Canada requires an adjusted cost base, the US now expects wallet-by-wallet. Using the wrong basis isn't a style choice — it's a filing error.

The methods CryptaCount supports

Choose the method that fits your accounting policy — 12 disposal methods in all:

• FIFO — oldest lots first
• LIFO — newest lots first
• HIFO — highest-cost lots first (minimises gain)
• LOFO — lowest-cost lots first
• Weighted average — averaged cost across your holdings
• Moving average and total average — running or period averages (as used in jurisdictions like Japan and Austria)
• Specific identification — you select the exact lots disposed
• Wallet-by-wallet — lots tracked per wallet, aligned to US Rev. Proc. 2024-28

Plus specialist treatments — including net-realisable-value and fair-market-value handling for internal transfers — for the accounting situations that need them.

Jurisdiction-correct by default

This is the part that keeps you compliant: you set your jurisdiction, and CryptaCount applies the treatment that jurisdiction mandates — automatically. Your chosen method applies; jurisdiction-mandated treatments apply automatically. You don't have to know which method a country requires, and you can't accidentally file on the wrong basis:

• United Kingdom — Section 104 pooling, with same-day and 30-day matching
• Canada — Adjusted Cost Base (ACB)
• France — the portfolio-wide method behind the *flat tax* (PFU)
• United States — wallet-by-wallet basis (Rev. Proc. 2024-28)
• Netherlands — the Box 3 deemed-return basis
• Japan — moving or total average

…and the correct treatment across 70+ jurisdictions. Where a country mandates a method, CryptaCount uses it — these aren't dropdown choices you're left to get right on your own.

Consistent, audit-ready, standards-aware

• Applied consistently across every exchange and wallet you connect — one basis, not a patchwork
• Works with your accounting standard — historical cost or fair value, under IFRS or US GAAP, including impairment under IAS 36, IAS 2, or fair-value measurement (ASU 2023-08)
• Fully traceable — every gain ties back to the underlying lots and transactions, with a tamper-evident trail for your auditors

Explore the engine: The crypto sub-ledger → · Compliance & reporting → · Accounting for firms →

Cost basis as an accounting policy, not a tax preference

Most explanations of FIFO, LIFO and HIFO are written for an individual filer trying to shrink a personal tax bill. For a business running its crypto on the books, the question is different. Your cost-basis method is part of your accounting policy — the consistent basis on which you measure disposals, recognize realized gains and losses, and value the digital assets that remain on the balance sheet at period end. It sits alongside your decisions on revenue recognition and depreciation, and like those policies it should be chosen deliberately, documented, and applied the same way every close. A method picked at random, or one that silently changes between periods, undermines the comparability of your financial statements and is exactly the kind of inconsistency an auditor is trained to find. Running the calculation inside the crypto sub-ledger keeps the policy in one place, applied uniformly across every wallet and exchange, rather than reconstructed by hand in a spreadsheet each quarter. See how the engine fits your books on the crypto sub-ledger → page.

The method matters because a disposal posts two things to your ledger at once: the proceeds you received and the cost basis of the units you are deemed to have given up. Proceeds are usually unambiguous — it is the value you actually received. Cost basis is where the method lives, because when you hold many lots of the same asset acquired at different prices, the method decides which lots are consumed. That single decision flows straight through to the realized gain or loss on your income statement and to the carrying amount of what is left on the balance sheet. It is an accounting figure first, and a tax figure second.

The core methods in plain accounting terms

Each method is simply a rule for ordering the lots you consume on a disposal. The mechanics are the same whatever the asset; only the ordering changes:

• FIFO (first-in, first-out) — the oldest lots are consumed first. It is the most widely accepted default, tends to leave the most recently acquired (and often higher-cost) units on the balance sheet, and is the easiest basis to explain to an auditor.
• LIFO (last-in, first-out) — the newest lots are consumed first. Permitted under some frameworks and not others, so its use is a policy decision that depends on the standard you report under.
• HIFO (highest-in, first-out) — the highest-cost lots are consumed first, which tends to minimize the realized gain on a disposal. Powerful, but it leans on complete and accurate lot data, because a missing acquisition can distort which lot is genuinely the highest-cost one.
• Weighted average / moving average — instead of tracking discrete lots, holdings are pooled and disposals are measured against an averaged unit cost. Several jurisdictions mandate an average-based approach, and it is often the most stable basis for high-volume trading.
• Specific identification — you nominate the exact lots disposed of. It offers the most control, but it only stands up if each lot is uniquely identifiable and the selection is documented and defensible.

There is no universally 'correct' method in the abstract. The right one is the method your reporting framework permits, your jurisdiction allows or mandates, and your accounting policy commits to — applied consistently. The discipline matters more than the label.

A worked example (illustrative numbers only)

The figures below are illustrative only — round numbers chosen to show the mechanics, not a quote of any real price. Suppose your entity acquires three lots of the same token: Lot A is 1 unit at a cost of 100, Lot B is 1 unit at 300, and Lot C is 1 unit at 200. You later dispose of 1 unit for proceeds of 250. The proceeds are 250 regardless of method; only the cost basis — and therefore the realized gain or loss — changes with the ordering rule:

• FIFO consumes Lot A (cost 100). Realized gain = 250 − 100 = 150. Lots B and C remain on the balance sheet at a combined carrying cost of 500.
• LIFO consumes Lot C (cost 200). Realized gain = 250 − 200 = 50. Lots A and B remain, carried at 400.
• HIFO consumes Lot B (cost 300). Realized result = 250 − 300 = (50), a loss. Lots A and C remain, carried at 300.
• Weighted average pools the three lots at a unit cost of (100 + 300 + 200) ÷ 3 = 200. Realized gain = 250 − 200 = 50, with the remaining two units carried at 200 each.

Same trades, same proceeds — yet the realized result swings from a 150 gain to a 50 loss purely on the choice of method, and the carrying amount of the holdings left on the balance sheet differs in every case. Multiply that spread across thousands of disposals in a real trading book and the method is no longer a footnote: it materially shapes both your income statement and your balance sheet. That is why the basis has to be deliberate and consistent, and why re-deriving it by hand each period is so risky. The sub-ledger applies the chosen rule the same way to every disposal and shows the lot-level workings behind each posted number. Explore the method set in detail on the cost-basis methods → page.

How the method lands on your books

Once a disposal is measured, it has to become a journal entry. The realized gain or loss is posted to an income-statement account, the digital-asset holdings account is relieved of the cost basis consumed, and the proceeds are recognized in cash, stablecoin or whatever was received. Doing this correctly is what separates an accounting record from a performance dashboard: every disposal must net to a balanced, double-entry posting that ties back to the specific lots consumed. Your choice of method also interacts with how you carry the remaining assets — whether you measure them at historical cost with impairment, or at fair value, depends on your reporting framework, and the cost basis the method leaves behind is the starting point for that measurement. See how the postings are built on the journal entries → page, and how the carrying basis feeds measurement under IFRS → and US GAAP →.

Common pitfalls when applying a cost-basis method

• Switching methods mid-stream. Changing basis between periods without treating it as a formal change in accounting policy breaks comparability and is a classic audit finding. Pick one and hold it.
• Inconsistency across venues. Running FIFO on one exchange and average cost on another produces numbers that cannot be added together. The method must apply across every connected wallet and exchange as one population.
• Incomplete lot history. HIFO, LIFO and specific identification all depend on a complete, accurate record of every acquisition. A single missing buy can silently select the wrong lot and misstate the gain.
• Treating internal transfers as disposals. Moving assets between your own wallets is not a sale. If the system mistakes a transfer for a disposal it invents a realized gain that never happened — one of the most common ways crypto books go wrong.
• Netting fees into the wrong figure. Quietly folding network and exchange fees into proceeds distorts both the gain on the disposal and your fee reporting. Fees belong in their own expense treatment.
• Ignoring a jurisdiction-mandated treatment. Where a country requires a specific basis, your own preference does not override it. The mandated treatment has to apply automatically, or the filing is simply wrong.

How CryptaCount handles cost basis

CryptaCount runs the cost-basis calculation as a first-class part of the sub-ledger rather than a spreadsheet bolt-on. You set the method that matches your accounting policy, and it is applied consistently across every exchange and wallet you connect, as a single population of lots — not a patchwork that has to be stitched together at close. Where your jurisdiction mandates a particular treatment, CryptaCount applies it automatically, so the books and any filing land on the correct basis without you having to memorize each country's rules. Every realized gain or loss drills back to the exact lots and source transactions that produced it, giving you a tamper-evident trail your auditors can follow line by line. The carrying basis the method leaves behind then feeds straight into measurement under your chosen standard, so the balance sheet and the income statement come from the same engine. The result is a basis that is deliberate, consistent and defensible — exactly what crypto on the books has to be.

More questions about cost-basis methods

Does the cost-basis method change my proceeds, or only my cost basis?

Only the cost basis. Proceeds are the value you actually received on the disposal and do not depend on the method. What the method changes is which acquisition lots are deemed consumed, and therefore the cost basis subtracted from those proceeds. That is why the same trade can produce a different realized gain or loss under FIFO, HIFO or average cost — the proceeds are fixed, the basis is not.

Can I use different methods for different accounting standards?

Your method has to be permissible under the framework you report on, and applied consistently within it. Some methods accepted under one framework are not allowed under another, so the choice is constrained by whether you report under IFRS or US GAAP, and by any jurisdiction-mandated treatment that overrides preference. The practical rule is to choose a method your framework permits and your policy commits to, then hold it across every period and every venue so the statements stay comparable.

What happens to the assets I haven't disposed of yet?

They stay on the balance sheet carried at the cost basis the method leaves behind. After each disposal, the lots that were not consumed remain at their original cost, and that carrying amount becomes the starting point for any period-end measurement — impairment under a historical-cost policy, or remeasurement under a fair-value policy. So the method does not only affect realized results; it also determines the basis of the holdings you continue to carry.

How do I prove the gain figure to an auditor?

By tracing it back to the underlying lots and transactions. A defensible cost-basis figure is one where every realized gain or loss can be decomposed into the specific acquisitions it consumed and the disposal that triggered it, with the source transactions retained behind each line. Because CryptaCount keeps that lot-level detail and a tamper-evident trail, the number on the income statement is not an assertion — it is evidence an auditor can follow.