Stablecoins on the balance sheet: a CFO's field guide

Stablecoins entered most finance departments through the side door — a vendor asked to be paid in USDC, a contractor in another country wanted to skip a three-day wire, or someone on the team pointed out that treasury was sitting on idle cash overnight instead of earning anything on it. Almost nobody adopted stablecoins as a strategy. They adopted them as a workaround, one payment at a time, and now enough of those workarounds have accumulated that it's a real balance sheet question.

That's the right way to think about them going forward too: not as a crypto position, but as payment and settlement infrastructure that happens to be denominated in a way your GL wasn't originally built for. The CFOs handling this well have stopped asking "should we hold stablecoins" and started asking the much more boring, much more useful question — "what does this actually change about how we account for cash?"

Three questions before you touch anything

Before any treasury policy discussion, three questions determine almost everything else:

• Which stablecoin, and who backs it? Fiat-collateralized stablecoins from regulated issuers with regular attestations are a fundamentally different risk profile than algorithmic or undercollateralized designs. This isn't a detail — it's the whole conversation.
• Custody: self-custody or a regulated custodian? Self-custody removes counterparty risk on the custodian side but adds operational and key-management risk that most finance teams aren't staffed to own. Most corporate treasuries land on a regulated custodian for exactly this reason.
• What's the actual use case? Faster cross-border settlement, contractor payments, or idle-cash yield are three different justifications with three different risk tolerances. Conflating them is how a narrow, defensible pilot turns into an undefendable position.

What your auditor is actually going to ask

The accounting questions are more settled than the popular conversation suggests, but they still require documentation most teams haven't built yet. Expect your auditor to want:

Classification and measurement

How the holding is classified on the balance sheet, and the reasoning for that classification, needs to be documented before period-end — not reconstructed after the fact. This is the single most common gap auditors flag: a company holding stablecoins with no written policy on how they're being treated.

Attestation and reserve backing

For fiat-backed stablecoins, auditors will want evidence of the issuer's reserve attestations — not because your team is being audited on the issuer's solvency, but because your risk exposure is directly tied to it. Keep the issuer's published attestation reports on file the same way you'd keep a bank's regulatory standing on file for a large deposit.

Counterparty and custody risk documentation

Whoever holds the keys — you or a custodian — needs a documented risk assessment. This is usually the newest piece of paperwork for a finance team, and the one most often missing entirely on a first stablecoin audit.

The accounting isn't the hard part. The hard part is having a written policy before the auditor asks for one.

A reasonable starting policy

For a company dipping a toe in rather than betting the treasury, a defensible starting position usually looks like:

• Limit holdings to fiat-collateralized stablecoins from issuers with regular, public reserve attestations.
• Use a regulated custodian rather than self-custody, at least until the team has the operational maturity to manage keys directly.
• Cap stablecoin exposure as a fixed percentage of total treasury, reviewed on the same cadence as other cash-equivalent policy limits.
• Write the accounting treatment and risk rationale down before the first transaction, not after the first audit inquiry.

The direction this is heading

Cross-border settlement is the use case with the clearest ROI right now, and it's the one worth piloting first if you haven't already — the time and cost savings versus traditional wires are large enough to be worth defending to a board on their own merits, independent of any broader view on digital currency. Treasury yield and speculative holding are different conversations, with different risk committees, and they shouldn't be adopted on the coattails of a payments pilot that actually made sense.