Which Bitcoin exchange price should an accountant use?

There is no universal exchange: the principal market is determined from the entity's own perspective and depends on the venues it can access (IFRS 13.19). Averaging exchanges because it feels safer is not a substitute for that analysis.

Are transaction costs part of Bitcoin fair value?

No. Fair value is the exit price in the principal market at the measurement date, and that price is not adjusted for transaction costs, because they are specific to a transaction rather than a characteristic of the asset. Exchange commissions and network fees may still be capitalised, expensed or allocated elsewhere under another standard.

Bitcoin Valuation for Accounting: Which BTC Price to Use

Q: Does a daily closing price exist for Bitcoin?

Not on its own. Bitcoin trades continuously, so there is no universal close analogous to an exchange that shuts at 4 p.m. local time. A daily closing price means nothing until the policy defines the day, the timezone and the data methodology. Where an event spans time, the contract or the recognition policy must fix the measurement moment before any price is selected.

Q: Can a benchmark rate replace the principal-market price?

No. A benchmark such as the CME CF Bitcoin Reference Rate is struck over a defined calculation window, so it is not necessarily the entity's transaction price or the principal-market quote at year end. Good controls keep corroboration and measurement source in separate boxes, and use the benchmark as a reasonableness check.

Ask four systems what Bitcoin (BTC) was worth at 14:32 UTC, Coordinated Universal Time, last Tuesday and you get four different numbers, each arguably correct. Bitcoin valuation for accounting is the discipline of choosing one of them and being able to show why it was the right measurement input.

Those four numbers are a custodian's portfolio value, an aggregator's composite index, an exchange's last trade, and a benchmark's once-a-day rate struck over a window unrelated to when your entity transacted. None of them is wrong. They answer different questions, and Bitcoin valuation for accounting goes badly when an entity treats them as interchangeable. The question is not "what was Bitcoin worth?" but:

Which market, which price, which timestamp and which evidence are appropriate for this specific accounting measurement?

BTC is easy to price in one sense: many active venues quote it. The difficulty is establishing which market the entity can access, what the number represents, and whether one policy governed every relevant moment.

That policy sits underneath every fair market value figure in the books and underneath the cost basis of every lot, so it is worth settling before the first journal entry rather than during the audit. Our crypto accounting guide covers the wider workflow it sits in, and how to account for Bitcoin transactions covers the entries the price feeds.

Which Bitcoin price, from which market, at what moment

Finding a price is easy. Proving why that price was the right accounting input is the work.

Fix the unit and the timestampBitcoin trades continuously. “Daily close” is meaningless without a timezone convention.
Identify the principal marketThe accessible market with greatest volume for the entity, not the most convenient feed.
Take the quoted priceKnow whether it is a last trade, midpoint, composite or retail quote.
Translate to functional currencyApply the entity's FX policy consistently with the measurement date.

Evidence controls

Retain raw observationsNot just the derived figure
Run an outlier checkDetect bad ticks before they reach the ledger
Define the fallback in advanceHistorical candle data can be incomplete

Define the policy before the period, not after. A price chosen retrospectively is difficult to defend as a measurement input.

Bitcoin valuation for accounting starts with the accounting event, not the price website

Identify what is being measured before choosing a data source. Purchase cost, noncash customer consideration, a mining reward, period-end fair value, impairment and tax valuation are not one measurement objective, and they do not all resolve to a market quote.

The central distinction is between what actually happened in a transaction and a market-data value used for accounting measurement. An entity buying 0.2 BTC at an executed price of $98,750/BTC has direct evidence of the transaction price. Receiving 0.2 BTC from a mining pool (a service that pays participating miners a share of block rewards) attaches no US-dollar trade to the receipt, so a documented convention is needed to measure the noncash amount. A year-end fair-value measurement is a third timestamp under a third objective, governed by IFRS 13 or ASC 820. Using one "Bitcoin closing price" for all three is wrong, because the objectives and the moments differ; tax may then prescribe a fourth rule.

Functional currency comes first

Quantity and functional-currency value belong in separate fields. A US-dollar-functional-currency entity holding 0.5 BTC preserves all four of these, not just the last:

quantity: 0.50000000 BTC;
measurement currency: USD;
price: say $100,000/BTC at the relevant moment;
functional-currency amount: $50,000.

If the functional currency is CAD, GBP or EUR, the measurement must end in that currency by a documented, reproducible path: a direct BTC/CAD market, or a supported two-step conversion.

One conceptual point prevents a family of errors. Bitcoin is not translated as a foreign currency. The IFRS Interpretations Committee's route to this is IAS 21.16, cited to establish that a cryptocurrency holding is a non-monetary item: the essential feature of a non-monetary item is the absence of a right to receive a fixed or determinable number of units of currency, and BTC gives the holder no such right (IFRS Interpretations Committee, June 2019). There is no closing-rate retranslation of a BTC balance as there is for a foreign-currency bank account, and BTC/USD being the most liquid quoted pair does not turn Bitcoin into a foreign currency. It is market data used to measure an asset.

The market question is narrower than "which exchange?"

Neither framework lets an entity simply nominate a venue it likes. A fair value measurement assumes the sale takes place in the principal market for the asset or, in its absence, in the most advantageous market (IFRS 13.16); the principal market is the one with the greatest volume and level of activity for that asset, and an active market is one in which transactions occur with sufficient frequency and volume to provide pricing information on an ongoing basis (IFRS 13, Appendix A). Four further requirements do most of the work for a multi-venue asset like Bitcoin, and each is a separate test:

No exhaustive search, but a rebuttable presumption. The entity need not search every venue, but it must take into account all information that is reasonably available; absent evidence to the contrary the market in which it would normally transact is presumed to be its principal market (IFRS 13.17).
The principal market wins even when another is better. Where a principal market exists, fair value is the price in that market even if a different market is potentially more advantageous at the measurement date (IFRS 13.18). An entity therefore does not survey exchanges after period end and choose the highest quote.
Access is a condition, and it is entity-specific. The entity must have access to that market at the measurement date, and because different entities access different markets the principal market is determined from the entity's own perspective (IFRS 13.19).
US GAAP states the same test. The paragraph below is written for financial assets and liabilities, but the principal-market emphasis it states carries across (ASC 820-10-35-5 to 35-6). Where an item is exchanged in multiple active markets ("for example, on different exchanges"), the emphasis is on determining both the principal or most advantageous market and whether the reporting entity can enter into a transaction at the price in that market at the measurement date (ASC 820-10-35-41B).

So what an entity documents is a conclusion about volume, activity, access and instrument (including whether the quoted product is native BTC rather than a derivative or a wrapped token on another network), not a preference for a familiar ticker. Only then does the price source arise, and no displayed "Bitcoin price" is reproducible until its methodology is known: a custodian's "portfolio value" may be an indicative composite, a stale last trade, a mid-market price or that custodian's own retail execution quote. The test is whether another accountant could reconstruct the value from the same policy next year.

Choose the recognition timestamp before choosing the price

Price selection follows the accounting recognition time, not the reverse; do not observe prices first and then pick the timestamp that produces a preferred result.

This matters more for Bitcoin than for almost any other asset, because Bitcoin trades continuously. There is no universal close analogous to an exchange that shuts at 4 p.m. local time, so "daily closing price" means nothing until the policy defines the day, the timezone and the data methodology. If an event spans time, the contract or the recognition policy must fix the measurement moment before any price is selected.

One category is not the valuation team's choice. Where BTC is received as noncash consideration from a customer, ASC 606-10-32-21 fixes the measurement date at contract inception, which can precede both receipt and revenue recognition. The US Securities and Exchange Commission (SEC) staff objected to a listed miner measuring pool-participant rewards at "the spot rate of bitcoin at the time that the block is successfully mined," because that "does not comply with the requirement in ASC 606-10-32-21" (SEC staff comment letter to MARA, 2 February 2024). That is a comment to one issuer, not codified GAAP, but it shows how the staff reads the paragraph. IFRS 15 requires noncash consideration to be measured at fair value but specifies no date, so an IFRS entity adopts and discloses a measurement-date policy of its own. Either way, the valuation policy prices a date the revenue standard has already chosen.

The one-minute candle convention, and what it is not

The worked example running through this series uses the Coinbase Exchange BTC-USD one-minute candle close for the UTC minute beginning at each event time, except where a standard fixes a different measurement date, as it does for the pool reward below. A candle summarises trading in a fixed interval; the venue's application programming interface (API) documents close as the "closing price (last trade) in the bucket interval" (Coinbase Exchange API, Get product candles).

Take the caution before the convenience. A candle close is not an appraisal, not an authoritative published rate, and not a guarantee that the entity could have executed its full order at that price. It is an illustrative execution proxy, appropriate only where the entity's own principal-market and transaction evidence support it; it does not discharge the market analysis above, and it is no pricing rule other entities may inherit.

The producer of the number deserves the same scrutiny as the number. Coinbase Exchange calculates these candles from trades on its own venue; it is a private operator, not a regulated benchmark administrator, and the entity has no contractual claim on continued publication, since the venue can change its API, restate history or withdraw the endpoint entirely. Its own documentation states the limitation plainly: "Historical rate data may be incomplete. No data is published for intervals where there are no ticks" (Coinbase Exchange API, Get product candles). A minute with no trades returns nothing at all, which is a policy question rather than a technical annoyance.

An illustrative walk-through

The figures below are the illustrative BTC-USD prices this series uses in its worked example, presented as one-minute candle closes for the UTC minutes stated. Treat them as example inputs only: they are not verified market observations, not evidence of what Bitcoin traded at, and not a rate any entity may adopt without its own analysis.

UTC minute begins	Event	Illustrative BTC-USD close
11 Feb 2025 15:30	BTC purchase	$97,039.85
8 May 2025 18:45	Mining-pool reward	$101,321.82
16 Jul 2025 09:20	Network fee	$119,077.69
22 Sep 2025 16:10	Sale and supplier payment	$112,830.75
31 Dec 2025 23:59	Closing measurement	$87,497.94

The second column names the event, not the measurement date. Where the pool operator is a customer under an enforceable contract, the measurement date for the reward is the one the revenue standard fixes (contract inception under ASC 606-10-32-21, or the entity's disclosed policy date under IFRS 15), and not the moment the payout arrives. Pricing a pool reward at the moment of block success, or later still at payout, is the measurement basis the SEC staff objected to above. This series' illustration assumes the evergreen pool contract is a series of daily contracts, so that contract inception and block success fall on the same day, and that the entity has elected a consistent inception-date convention which the 8 May observation represents. Without that analysis, the 8 May figure would not be a defensible input. The valuation policy supplies the price for a date the revenue standard has already chosen.

A 0.00003142 BTC network fee on 16 July, at the illustrative $119,077.69/BTC, measures as 0.00003142 × $119,077.69 = approximately $3.74. What that $3.74 is (an expense, part of another asset's cost, a selling cost) is a separate question, as is the disposal of the BTC paid away. The valuation does not answer the classification question.

Last trade, bid, ask, midpoint or candle close?

The fields are not interchangeable, and none is right independent of the accounting objective and the market facts. The policy should state which is used, why, and when it changes.

Price field	What it is	Where it fails
Last trade	The last executed transaction on that venue	Goes stale in a thin market
Bid and ask	Executable-side quotations at a point in time	Order-book depth matters as much as the quote for a large position
Midpoint	A calculation halfway between bid and ask	Not an executed price; nobody need have traded there
Candle close	The last trade in a defined interval	Adds a time convention, not a market conclusion

Level 1 does not mean "any public Bitcoin price"

Level 1 inputs are quoted prices (unadjusted) in active markets for identical assets that the entity can access at the measurement date (IFRS 13.76; ASC 820-10-35-40), and such a quote provides the most reliable evidence of fair value, to be used without adjustment except in the narrow circumstances the standards specify (IFRS 13.77). Every word is load-bearing: quoted price, active market, identical asset, accessible market, measurement date. So an unadjusted quote for identical BTC in an accessible active market is normally Level 1, while a price for a Bitcoin derivative, a wrapped token on another network, or an inaccessible offshore venue is not, merely because it is public.

Transaction costs stay outside fair value

Fair value is the exit price in the principal market at the measurement date (IFRS 13.24), and that price "shall not be adjusted for transaction costs," because they "are not a characteristic of an asset or a liability; rather, they are specific to a transaction" (IFRS 13.25; ASC 820-10-35-9B). Exchange commissions and network fees are characteristics of a transaction, not of the Bitcoin itself.

That does not make them invisible: another standard may add qualifying costs to acquisition cost, reduce disposal proceeds, expense them, or allocate them to another asset. US GAAP deliberately left the question open for crypto: the Board "decided not to provide guidance on how to recognize or present transaction costs to acquire crypto assets," and did not amend industry-specific capitalisation requirements (FASB ASU 2023-08, BC36). The control point is narrow: quoted fair value should not be silently netted for commissions merely because the entity would incur them if it traded.

Bitcoin also adds a cost category with no equivalent in equities. A network fee pays for inclusion of a transaction in the Bitcoin blockchain and is derived as total inputs minus total outputs, because the protocol has no separate fee field (Bitcoin Developer Guide, Transactions; authoritative, though a frozen 2020 snapshot). It is not an exchange commission, a bid-ask spread or a custodian withdrawal charge, and a custodian's fixed "withdrawal fee" may differ from the network fee actually paid, so the two belong in separate accounts.

When the preferred source fails, and what you keep either way

A valuation policy that works only when the venue's API is healthy is not a policy. Venues halt trading, delist products, change APIs, omit intervals and suffer outages, so the fallback must be designed before the result is known:

primary principal-market source;
alternate official endpoint for the same market;
independently retained transaction or order-book evidence;
predefined secondary market where the principal-market quote is unavailable under the framework;
benchmark or corroborating source under documented conditions;
manual valuation review for exceptional cases.

The hierarchy has to fit the entity, but the control is the same everywhere: a fallback is evidence control, not permission to choose the result that improves earnings.

For each material price observation, retain the pair, the venue, the endpoint, the raw returned value, the field used, the retrieval date, the event, recognition and market-data timestamps with their timezone and the reason for any difference between them, any foreign-exchange conversion, the resulting functional-currency amount, the fallback source if one was used, and reviewer approval where required. A screenshot is weaker evidence than a reproducible observation, because interfaces change and the methodology behind a displayed number is invisible; for an API, keep the raw response or enough of the query to reproduce it. Validating outliers against a second independent source costs little and catches the failure mode that matters most: a bad number nobody questioned.

Benchmarks corroborate; they do not replace the principal market

The CME CF Bitcoin Reference Rate aggregates trade flow from major cryptocurrency spot exchanges during specific calculation windows into a once-a-day reference rate, with an oversight committee reviewing the methodology. It is a useful reasonableness check, and the required input where a contract or regulation calls for it. It does not replace the principal-market measurement, because a benchmark struck over a defined window is not necessarily the price at 14:32 UTC, the entity's transaction price, or the principal-market quote at year end. Good controls keep corroboration and measurement source in separate boxes.

One price observation, five different accounting outcomes

IFRS 13 and ASC 820 share the core fair-value architecture, but Bitcoin is not carried the same way under both, and flattening that divergence into one answer is a reporting error, not a simplification:

An in-scope US GAAP holding under ASC 350-60 is measured at fair value under ASC 820 each reporting period, with every change in net income (ASC 350-60-35-1). The Subtopic applies to all entities that hold crypto assets (ASC 350-60-15-2), for fiscal years beginning after 15 December 2024 including interim periods within them (ASC 350-60-65-1(a)) (FASB ASU 2023-08).
A typical IFRS IAS 38 cost-model holding is not marked up and down each period at all; it is carried at cost less accumulated impairment.
IAS 38's revaluation model is available only where fair value can be measured by reference to an active market, and applies to the entire class, except that an asset in that class with no active market continues at cost (IAS 38.75, 38.72 and 38.81).
IAS 36 impairment works on recoverable amount, the higher of value in use and fair value less costs of disposal, not on a daily fair-value journal. Where IAS 36.21 applies, that assessment may rest on fair value less costs of disposal without computing value in use.
Where BTC is held for sale in the ordinary course of business, IAS 2 applies instead, at the lower of cost and net realisable value, the fair-value-less-costs-to-sell exception being available only to a qualifying commodity broker-trader (IAS 2.3(b) and 2.5).

One high-quality price observation therefore feeds five outcomes. Valuation input and accounting treatment are separate layers, and confusing them is how an entity ends up with a beautifully evidenced price posted through the wrong model. Bitcoin valuation for accounting supplies the input; the models that consume it are set out in Bitcoin accounting under IFRS and Bitcoin accounting under US GAAP.

Sources and further reading

Educational research, not accounting, tax, legal, valuation or investment advice. The correct measurement source depends on the entity's facts, accessible markets and applicable framework. The BTC-USD figures in the worked example are illustrative figures under one stated convention, not verified market observations, and not a rate any entity may adopt without its own principal-market analysis.