What exchange rate do you record a USDC transaction at?

The question has a short answer that surprises people: for most US entities, there is no exchange rate, because there is no foreign currency involved. USDC is denominated in US dollars. A US dollar functional entity receiving USDC has not entered a foreign currency transaction, and ASC 830 does not apply.

For a non-US entity, the answer flips entirely. A euro functional company receiving USDC has taken on dollar exposure, and every rule in ASC 830 applies exactly as it would to receiving a USD wire.

The determinant is your functional currency. The token is incidental.

Why isn't a stablecoin payment a foreign currency transaction?

ASC 830 governs transactions denominated in a currency other than the reporting entity's functional currency. The test is what the obligation is denominated in.

A USDC receivable is denominated in dollars. One USDC entitles the holder to one dollar from the issuer. For a US dollar functional entity, there is no second currency in the transaction and therefore nothing to translate.

This catches teams out because the payment moved over a blockchain and felt exotic. The rail is novel; the denomination is not. A dollar invoice settled in USDC by a US entity is a dollar transaction, recorded at the dollar amount, the same as if it had arrived by ACH.

What you may still have is a difference between the token's face value and its market price, which is a measurement question rather than a translation question. More on that below.

What if the functional currency is not USD?

Then the stablecoin is a foreign currency asset and ASC 830 applies in full.

A euro functional entity invoicing a US customer $100,000 and receiving USDC records the receivable at the spot EUR/USD rate on the transaction date. At each balance sheet date, the USDC balance is a monetary item and is remeasured at the closing rate, with the difference recognised in income. On conversion to euro, the final difference is a realised gain or loss.

This is ordinary foreign currency accounting, and the fact that the dollars arrived as tokens changes nothing about it. The practical consequence is that holding USDC is holding dollars: if your functional currency is not the dollar, you are carrying FX exposure for as long as the balance sits there, and the exposure is identical to a USD bank balance.

Teams sometimes assume stablecoins are "stable" in a way that removes currency risk. They are stable against the dollar. If your books are in euros, rupees or pounds, that is precisely the risk you are holding.

Do you book at one dollar or at the market price?

The token trades, and it does not always trade at exactly par. USDC has printed $0.9995 and $1.0002 on ordinary days and, during the March 2023 banking stress, traded as low as roughly $0.87 before recovering.

Two positions exist in practice.

Record at par. The redemption right is for one dollar, and that is the amount you will receive. Transitory basis points of market deviation are not economically meaningful and, for most companies, not material. This is the common approach for operating flows.

Record at fair value on the transaction date. Strictly, the asset received should be measured at its fair value, and observable market price is the best evidence of that. Where the deviation is material, or where the balance is large enough that basis points become real money, this is the more defensible position.

The pragmatic answer most finance teams land on: record operating transactions at par, set a materiality threshold below which deviation is ignored, document that policy, and apply fair value when the deviation crosses the threshold or when a depeg event is underway.

What matters to an auditor is that you have a policy and follow it, rather than deciding transaction by transaction.

Which price source should you use?

If you are using market prices, the source needs to be consistent and documented. The considerations:

Pick one primary source and stick to it. Switching between venues and aggregators period to period invites the question of whether you are selecting favourable prices.

Prefer volume-weighted aggregates over a single venue. A thin venue can print a price that no meaningful size traded at.

Record the timestamp, not just the date. A chain settles continuously. If the price moved during the day, which moment you used is a real question.

Keep the evidence. A screenshot is weak; an API response with a timestamp is strong. If the price ever matters, it will matter during an audit months later.

Where the real difference shows up: the FX you actually pay

The accounting rate is one question. The rate you are economically charged is another, and it is usually the larger number.

When money crosses currencies, the spread between the rate you receive and the mid-market rate is a cost, whether or not it ever appears as a separate line on an invoice. A provider quoting a conversion at 1.2% below mid-market has charged you 1.2%, and no fee line will say so.

That is worth measuring directly rather than assuming. Pull the rate your provider quotes, compare it to the mid-market rate at the same timestamp, and compute the difference. On meaningful volume the gap compounds quickly, and it is negotiable in a way that posted fee schedules are not.

Plaitr quotes mid-market FX without a hidden spread, and holds USD, EUR, GBP and AED alongside USDC in one balance, so conversions happen when you choose rather than when a wire lands. See cross-border payments for how that works, and our multi-currency account comparison for how providers differ.

FAQ

Is receiving USDC a foreign currency transaction?

Not for a US dollar functional entity. USDC is denominated in dollars, so there is no second currency and ASC 830 does not apply. For an entity with a non-USD functional currency, receiving USDC is a foreign currency transaction and is accounted for exactly like receiving US dollars: spot rate at the transaction date, remeasurement of the monetary balance at each reporting date, and gain or loss through income.

Should I record a USDC payment at $1.00 or the market price?

Most companies record operating transactions at par and set a materiality threshold for deviation, because the redemption right is for a dollar and ordinary market noise is a few basis points. Strictly, the asset should be measured at fair value on the transaction date, so where the deviation is material or a depeg is underway, use the observable market price. Document whichever policy you adopt and apply it consistently.

Does holding USDC remove currency risk?

Only if your functional currency is the US dollar. USDC is stable against the dollar, not against your books. A euro or rupee functional entity holding USDC carries exactly the same dollar exposure as holding a USD bank balance, and must remeasure it each reporting period.

What timestamp should I use for the rate?

The transaction date, and for on-chain activity it is worth recording the specific time or block, because settlement is continuous rather than batched into a banking day. Whichever convention you adopt, use it consistently and retain the evidence with a timestamp rather than relying on a later lookup.

Does ASC 830 apply to the stablecoin itself as an asset?

For a non-USD functional entity, yes, as a monetary item denominated in a foreign currency, remeasured at the closing rate. For a USD functional entity there is no translation; the accounting questions are classification and measurement, covered in where stablecoins go on the balance sheet.

What should you do next?

Confirm your functional currency and write down the resulting policy in one line, because it determines everything else. Then set a materiality threshold for par versus market and name your price source.

If you are converting between currencies regularly, measure the spread you are actually paying against mid-market at the same timestamp. That number is usually larger than the accounting question you started with.

This article describes accounting standards and is not accounting advice.