Bitcoin Fair Value Accounting Price Data for CFOs and Auditors

This guide is for controllers, CFOs and audit seniors at US companies and funds that carry bitcoin on the balance sheet under ASU 2023-08. You already know the rule: measure at fair value each reporting date, run the change through net income. What the standard leaves to you is the operational part, which price source, at which minute, matched to which block. That is where period-end files fall apart in review.

We sell Bitcoin data, including the hourly price candles and block-level balances this article uses, so weigh that. Every price below came from two public candle feeds read on 2 October 2026, and every block height was checked on two explorers. Where a free source or a benchmark vendor is the better choice, we say so.

What price do you use for bitcoin fair value?

The price in your principal market at the measurement date. Under ASC 820 the principal market is the one with the greatest volume and level of activity for the asset that your company can actually access, usually the exchange or brokerage where you trade. If you have no principal market, you use the most advantageous one. The standard does not name a time of day, so you set one in your policy and apply it every period.

That last sentence is the whole problem. Bitcoin trades every minute of every day, so "the price on 30 September" is not one number. It is a different number at 4:00 pm in New York, at midnight UTC, at midnight in your headquarters timezone, and at whatever minute your treasury system happens to sync.

How much the cutoff time moved the price on 30 September 2026

We pulled hourly candles for the evening of 30 September 2026 from two sources: the single USD order book behind our Bitcoin OHLC API, and Coinbase's public exchange candles. The price at each cutoff is the close of the hour that ends at that minute.

Read the table two ways. Down a column, the cutoff convention moves Coinbase's price from $83,556.14 to $84,075.72, a $519.58 swing per bitcoin, and across both feeds the widest gap is $525.45. Across a row, the two venues never differ by more than $6.44. On this date the choice of minute mattered about 80 times more than the choice of exchange. For a company holding 100 BTC, that is roughly $52,000 of reported gain or loss decided by a timezone, against about $640 decided by the venue.

The intraday range was wider still. Coinbase traded between $82,911.86 and $85,613.72 during the UTC day of 30 September, a $2,701.86 band, so a team that takes "the daily high" or an unweighted midpoint is not reporting a market price at any moment at all.

One honest caveat. Coinbase printed about 582 BTC of volume in the hour before 4:00 pm Eastern, against 85 BTC on the order book our candles read. If Coinbase is where you trade, it is very likely your principal market and its price is the one your auditor expects. The point of the table is not that our feed is better. It is that the convention you pick moves the number far more than the feed does, so the policy has to be written down and the minute has to be reproducible.

Is bitcoin measured at fair value under GAAP?

Yes, for most companies. ASU 2023-08 requires crypto assets that meet its scope, which includes bitcoin held by an ordinary operating company, to be measured at fair value with changes recognized in net income each reporting period. It applies to fiscal years beginning after 15 December 2024, with early adoption allowed, so calendar-year companies are measuring bitcoin at fair value in every 2026 quarter.

Bitcoin fair value price sources compared

Most finance teams end up with two rows: a price from the principal market and a unit count they can defend. The price is the easy half. The units are where reviewers find differences, because a wallet balance read at 9:00 am on 1 October is not the balance at the cutoff, and a custodian statement only covers what the custodian holds.

Match the price minute to a block height

If you pick midnight Pacific for the price, the units should come from the last block before midnight Pacific. For 30 September 2026 we measured the cutoff blocks and cross-checked each hash on two explorers:

• Midnight UTC: block 969,369.
• Midnight Eastern: block 969,391.
• Midnight Pacific: block 969,409, stamped 06:55:11 UTC on 1 October.

Forty blocks and 179,384 transactions sit between the UTC and Pacific answers. A wallet that received or sent coins in that window has two different period-end balances depending on the convention, and the price convention and the unit convention have to be the same one. Mixing a 4:00 pm Eastern price with a midnight Pacific balance is the most common inconsistency we see in workpapers, and it is invisible unless someone writes both the minute and the block height into the file.

Our Bitcoin audit trail API returns the balance and rollforward at a named block, and the balance history API answers the same question one address at a time. On the Growth plan both halves come from one SQL statement: the close of the price_candles row for the hour ending at your cutoff, and the sum of unspent outputs as of the cutoff block.

Can I use CoinMarketCap or CoinGecko for fair value?

Usually not as the primary source. An aggregator publishes a blended price across many venues, and ASC 820 asks for the price in a market your company can access, normally the one you trade in. Aggregators are fine as a reasonableness check against your principal market price. If you rely on one, document why it represents your principal market, and expect the auditor to ask.

What time of day should we use for bitcoin fair value?

Any time you can defend and apply consistently. Common choices are 4:00 pm Eastern, matching US equity markets and the New York benchmark window, and 11:59 pm in the reporting entity's own timezone, matching the calendar date on the balance sheet. Pick one, write it into the accounting policy, and use the same minute for the units.

What an auditor asks for at period end

1. The accounting policy that names the principal market and the cutoff minute with its timezone.
2. The price at that minute, from that market, with how it was obtained, such as an exported hourly candle or a statement line.
3. The units held at the same minute, with the block height used for every self-custody address.
4. A reconciliation of units from the prior period: purchases, sales, transfers and fees, each with a transaction ID.
5. Evidence the price feed is complete for that hour: a candle marked closed, not one still forming when it was pulled.

The fifth point catches more teams than you would expect. A candle pulled at 12:05 am for the hour that ended at midnight may still be the forming hour on some APIs. Our candle endpoint returns a closed flag on every row for exactly this reason, so a script can refuse an open hour instead of booking it.

Bitcoin is also just one more account the controller has to tie out at close. If the rest of the month-end is bank accounts, the same discipline applies there: match every line on the bank reconciliation to the ledger before anyone signs, then bring the bitcoin schedule in with the same cutoff.

Which data you need, by role

A controller at a company holding bitcoin needs the principal market price at the policy minute plus units at the matching block. If all coins sit at one custodian, its statement may cover units; if any are in self-custody, the chain is the only complete record. The Bitcoin API guide for corporate treasury covers quarter-end unit cutoffs in more detail.

An audit senior needs to re-perform both numbers independently. That means pulling the price from the client's named market and the units from the chain at the client's stated block, not from the client's subledger. Our crypto audit software comparison covers the tools audit teams use for the units half.

A fund administrator striking NAV needs the same pair at the fund's valuation point, which is often 4:00 pm Eastern, every day rather than every quarter. Hourly candles with a closed flag and balances by block make that a scheduled query instead of a manual lookup.

What BitcoinDatabase gives a finance team

Hourly and daily OHLCV candles from 18 August 2011, from one USD order book that starts its day at 00:00 UTC and is never stitched from several venues, served over REST as JSON or CSV and as the price_candles table in SQL. Balances, UTXOs and transactions at any block height, so units and price can be pulled for the same minute. Developer at $49 a month covers REST with one year of history, which is enough for the current and prior quarter. Growth at $199 adds SQL and full history, which is what you want when the auditor asks you to re-run a prior year. The Bitcoin price API page shows the candle fields and plans.

BitcoinDatabase provides informational data only. It is not accounting, tax or investment advice. Prices above are hourly candle closes read on 2 October 2026 from public feeds; confirm your principal market and measurement policy with your auditor.