If You Owe 1 BTC, What Is Your Liability Worth?

If you owe 1 BTC, your economic exposure moves when BTC moves. That is the practical starting point.

If Bitcoin goes from $40,000 to $60,000, a liability to repay 1 BTC is no longer a $40,000 problem in treasury terms. It is a $60,000 settlement problem. That is why internal balance-sheet and risk reporting often needs a current settlement value view for crypto-denominated liabilities, even when formal financial reporting gets more nuanced.

If you want the broader bookkeeping context first, start with our crypto accounting guide.

Crypto liability valuation: the short answer

For internal treasury, liquidity, and risk reporting, the answer is usually straightforward:

• If you owe a token, the obligation should usually be shown at its current settlement value.
• If you also hold the same token as an asset, both sides should move together in the economic view.
• If only the asset is revalued and the liability stays at cost, you create artificial equity.

This is less about accounting theory than about avoiding a misleading management report.

A simple example

Assume a company:

• borrows 1 BTC when BTC is $40,000
• keeps that 1 BTC on balance sheet at month-end
• still owes 1 BTC at month-end

Now BTC trades at $60,000.

Cost-only liability view

• Asset: $60,000
• Liability: $40,000
• Reported equity impact: +$20,000

Current settlement view

• Asset: $60,000
• Liability: $60,000
• Reported equity impact: $0

The second result is the better treasury answer. The company is not economically richer just because the reporting package refused to update the liability.

If the company had sold the borrowed BTC for cash, the analysis would change. The liability would still move with BTC, but the offsetting asset would no longer be BTC. That is exactly why treasury reporting should make the exposure explicit instead of relying on historical cost.

Why finance teams get tripped up here

Crypto accounting discussion often starts on the asset side. That makes sense. FASB ASU 2023-08 changed US GAAP for in-scope crypto assets, moving them to fair value through net income.

In-scope crypto assets are measured at fair value each reporting period, with changes recognized in net income.

If you want the asset-side rule change itself, see our guide to digital asset accounting under FASB fair value rules.

That is helpful context, but it does not automatically answer the liability question. A liability to deliver 1 BTC is not the same accounting problem as holding 1 BTC.

That is where teams need to separate economic reporting from formal measurement guidance.

Treasury reporting versus statutory reporting

This distinction matters.

Treasury or management reporting

The goal is decision-useful information:

• What is the company exposed to right now?
• What would it cost to settle obligations today?
• How much of reported equity is real economic cushion versus measurement mismatch?

For that purpose, current settlement value is usually the right answer for a crypto-denominated liability.

Statutory financial reporting

The goal is compliance with the relevant accounting framework and the legal terms of the obligation.

That means the answer depends on questions like:

• Is the obligation denominated in cash or in a crypto asset?
• Does the liability require delivery of a non-cash asset?
• Is there an embedded derivative or another contractual feature?
• Which framework applies: US GAAP, IFRS, or something else?

That is why teams should avoid casually saying every crypto liability should simply be “fair valued.” Sometimes that will be directionally right. Sometimes it will be technically sloppy.

What IFRS helps clarify

IAS 21 is the main IFRS standard for foreign exchange effects. Its definition of a monetary item turns on an obligation to receive or deliver a fixed or determinable number of units of currency.

Monetary items are tied to fixed or determinable numbers of currency units, not just any asset measured in market terms.

That is the important boundary. “Owe 1 BTC” is not automatically the same thing as “owe a foreign-currency payable.”

IFRIC’s March 2019 discussion on holdings of cryptocurrencies also helps frame the issue on the asset side. It concluded that cryptocurrency holdings are not cash and not a financial asset under IFRS Standards.

Holdings of cryptocurrency are not cash and are not financial assets under IFRS Standards.

That does not directly resolve every liability pattern, but it does make one thing clear: teams should be careful about importing simple FX logic into crypto obligations without reading the actual contract.

Questions finance teams should answer before choosing the view

Before you decide how to present a crypto-denominated liability internally, write down the actual facts of the position.

• What exactly must be delivered at settlement: cash, a token, or either at the counterparty's option?
• Is the token liability matched by the same token on the asset side, or has the position already been converted into cash or another asset?
• Is the report trying to explain book carrying values, or is it trying to show current economic exposure to management?
• Which reports will stakeholders actually use to make decisions: board packs, treasury dashboards, close binders, or audit support?

Those questions sound simple, but they prevent a common reporting failure: mixing multiple measurement objectives into one number. A controller may want the carrying amount tied cleanly to the ledger. A treasury lead may want to know the current cash or token burden to settle. Both are valid, but they are not the same output.

That is also why liability reporting should be documented as a policy choice, not handled ad hoc. If two people can run the same period and get different answers because one person used cost and another used current settlement value, the problem is not the market. The problem is the reporting design.

The practical reporting policy that usually works

For most finance teams, the cleanest operating policy is:

1. Keep a carrying-basis view

Use this for:

• book accounting
• period-end reconciliations
• support for statutory reporting
• audit trail continuity

This is the view most closely tied to journal entries, the general ledger, and cost basis tracking.

2. Keep a current settlement view

Use this for:

• treasury reporting
• liquidity planning
• leverage and risk monitoring
• board reporting where economic exposure matters

If the liability is settled in a token, this view should usually move with the token price. In practice, that means you need a defensible reporting-date fair market value process for every close.

3. Label the view precisely

This is the part many teams skip.

If you call every number “fair value,” you blur the distinction between:

• an internal economic estimate
• a settlement-based management view
• a formally defined accounting measurement basis

For liabilities, current settlement value is often a better label than “fair value” in internal reporting.

When cost-only reporting still has a place

Cost-only reporting is still useful when you are answering questions like:

• What is the current carrying amount on the books?
• What was the original basis of this borrowing?
• How did this liability move through the journal structure?

That is valid. It just answers a different question.

The problem starts when cost-only liability numbers are presented next to market-valued assets as if both belong to the same analytical view. That is how false equity appears.

The same discipline matters in monthly close work. If your team runs a structured close, our stablecoin month-end checklist shows how valuation, cut-off, and evidence gathering fit together operationally.

What Tokenbooks would recommend

For crypto-native finance teams, the safest internal reporting pattern is:

1. Show cost/carrying basis and current settlement value side by side where liabilities are material.
2. Reconcile the delta explicitly instead of letting it hide inside equity.
3. Document whether each dashboard or export is a book view or a treasury view.
4. Treat matching token assets and liabilities consistently within the same economic report.

That gives teams a management view that reflects economic reality without overstating what formal accounting standards say.

Final view

If you owe 1 BTC, your liability is not “still $40,000” just because that was true when the position started.

For treasury reporting, the better question is:

What would it cost to settle this obligation now?

That answer will usually move with the token price. The remaining judgment is not whether the economics changed. It is how carefully you distinguish that economic view from the measurement basis required in formal financial statements.