How Much of Your Treasury Should Sit in Yield? A CFO Allocation Framework

The right treasury allocation to yield is rarely a fixed percentage. A business with predictable subscription receipts and low weekly spending can invest more than one with lumpy payroll, vendor settlements or uncertain customer collections.

A better approach is to work backwards from obligations. Protect near-term operating cash, build a liquidity buffer for delays and surprises, separate restricted funds, and only then consider moving the remainder into yield.

This framework applies whether the treasury holds fiat, USDC, USDT or a mixture. For stablecoin yield, finance teams must also account for redemption terms, variable rates and risks that do not apply to ordinary bank balances.

Start with liquidity terms, not the headline rate

Before allocating funds, document how each yield product works. “Liquid” should not be assumed to mean instantly available in every market condition.

• Redemption timing: Is withdrawal on demand, same day, next business day or subject to a notice period?
• Settlement asset: Is principal returned in USDC, USDT, fiat or another asset?
• Cut-off times: Can a Friday redemption fund payroll that day, or does it settle after the weekend?
• Minimum holding period: Are there fixed terms, withdrawal restrictions or early-exit costs?
• Rate structure: Is the quoted rate variable, tiered or dependent on market demand?
• Risk source: Does yield come from lending, tokenised government securities, market-making or another strategy?
• Loss exposure: Who bears borrower default, smart-contract, custodian, stablecoin or market risk?

APY is not the same as guaranteed bank interest. Stablecoin yield may expose the company to principal loss, delayed withdrawals, counterparty failure, smart-contract vulnerabilities and temporary loss of the stablecoin’s peg. Review the stated liquidity terms and risk disclosures for each option available through Stablerail Earn before making an allocation.

Use four treasury buckets

A practical allocation model divides treasury into four buckets. The first three determine how much must remain accessible; the fourth is the amount potentially eligible for yield.

For most companies, the core calculation is:

Yield-eligible balance = total available treasury − operating cash − liquidity buffer − restricted funds.

This is a ceiling, not a target. A CFO may keep part of the eligible balance liquid because forecasts are uncertain or because the expected return does not compensate for the risk.

Build the liquidity buffer from runway

Choose a protected runway based on the reliability of incoming cash and the speed at which spending can be reduced. Ninety days is a useful planning horizon for many businesses, but it is not universal.

Step 1: Map gross obligations

List expected cash outflows by week for the protected period. Use gross obligations rather than only net burn. A company spending $800,000 and collecting $500,000 each month has a $300,000 net burn, but it may still need to pay the full $800,000 before receipts arrive.

Include payroll, payroll taxes, vendors, debt service, rent, card settlements, planned asset purchases and known tax dates. Separate amounts by currency and payment rail. USD needed for ACH or Fedwire cannot always be replaced immediately by a USDT balance on a weekend.

Step 2: Apply a haircut to expected inflows

Count only receipts with a strong basis: contracted customer payments, recurring revenue with low churn, or committed financing that has cleared all conditions. Apply a haircut for late payments, disputes, exchange delays and concentration risk.

The less predictable the inflows, the less they should reduce the liquidity buffer. Early-stage or seasonal companies may choose to ignore uncollected inflows entirely.

Step 3: Add a contingency reserve

Add a reserve for forecast error and operational disruption. This can be expressed as several weeks of gross spending or as a percentage of protected obligations. The appropriate amount depends on revenue volatility, customer concentration and how quickly the company can stop discretionary spending.

Step 4: Match assets to obligations

Keep funds in the currency and form in which they are likely to be spent. Near-term EUR payroll may justify an EUR balance accessible through SEPA, while on-chain vendor payments may justify immediately available USDC or USDT on the required network. Conversion capacity is useful, but it does not remove timing, pricing or network risk.

Worked example: a 90-day allocation

Consider a company with $6 million of combined fiat and stablecoin treasury. It spends $800,000 per month and expects $500,000 of monthly customer receipts. Its simple net-burn runway is 20 months: $6 million divided by $300,000. That figure alone would make most of the treasury appear idle, but it overlooks payment timing.

In this example, up to 60% of treasury is yield-eligible. That does not mean the full $3.6 million should enter a term product. The company could keep part in a same-day option and place only the portion not needed under a stressed forecast into a notice-based or fixed-term option.

For example, if delayed customer receipts would create an additional $1 million liquidity need, the CFO could retain that amount in a same-day-accessible balance. The remaining $2.6 million could then be evaluated against longer redemption terms. The final split should follow actual product documentation rather than labels such as “flexible” or “low risk.”

Stress-test the allocation before funding

Run at least three scenarios: the base forecast, a delayed-receipts case and a severe but plausible case. Test what happens if major customers pay 30 days late, monthly outflows rise by 20%, a stablecoin trades below its target value, or redemptions take longer than expected.

The allocation passes only if the company can still meet payroll, taxes and critical vendors without relying on an untested emergency conversion. Confirm who can redeem funds, what approvals are required and whether the treasury retains enough native network tokens to pay blockchain transaction fees.

Set review triggers, not just a review date

Review the allocation at least monthly and whenever a material event occurs. Useful triggers include a large tax bill, acquisition, fundraising delay, loss of a major customer, change in redemption terms, stablecoin depeg or a sharp increase in the quoted yield.

A higher rate can indicate higher demand for capital or changing risk. It should prompt renewed diligence, not an automatic increase in allocation.

The central rule is straightforward: yield should sit behind operating resilience. Protect near-term obligations, calculate the liquidity buffer from gross cash flows, stress the runway, and allocate only the surplus whose redemption terms match when the business may need it.