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

There is no safe universal percentage of treasury that should sit in yield. The defensible allocation is the amount left after reserving immediately spendable operating cash, a stress-tested liquidity buffer and any restricted or strategically committed funds. Even then, yield is only appropriate when the principal can be redeemed, converted and delivered in the required currency and location before the company needs it.

Start with access to principal, not the headline rate

A treasury position is only as liquid as its complete route back to spendable cash. For a USDC position funding USD payroll, that route may include submitting a redemption, completing provider checks, transferring onchain, converting into fiat and settling into the correct bank account before the payroll cut-off.

Finance should classify access based on documented terms and stressed operational timing. Do not treat labels such as “liquid” or “on demand” as sufficient evidence.

“T+1” generally means one business day after the redemption request is accepted, not necessarily the day after someone clicks withdraw. Confirm the applicable time zone, cut-off, holidays, minimum amounts, fees and contractual circumstances in which withdrawals may be delayed or suspended.

For each opportunity, document the source of yield, the entities holding or using the assets, whether returns are fixed or variable, how fees are deducted and what could impair principal. A higher stated rate does not solve a liquidity mismatch with payroll.

Use a four-bucket runway framework

1. Immediate operating cash

This bucket covers obligations that cannot tolerate a redemption or conversion delay: payroll, taxes, rent, critical suppliers, debt service, card settlement and known exceptional payments. A practical starting point is one to two months of gross cash outflows plus committed one-off expenses, adjusted to the company’s forecast accuracy and operational risks.

Gross outflows are generally more useful than net burn when collections are volatile. An expected customer payment cannot fund an obligation until it has settled and is available in the correct account.

Hold this bucket where payments originate. A company paying EUR payroll through SEPA and USD vendors through ACH or Fedwire should not assume that a USDC balance is equivalent to cash already present in both bank accounts.

2. Liquidity buffer

The liquidity buffer protects the next several months of runway against forecast error and operational disruption. Some of it may qualify for same-day or T+1 opportunities, but only if stressed access remains comfortably ahead of payment deadlines.

Size the buffer using scenarios rather than historical averages. Model delayed customer receipts, an expense increase, blockchain congestion, a provider review, off-ramp delays, weekends and public holidays. Also test an urgent need to change currency or move to another network.

For example, four months of expenses at $800,000 per month equals $3.2 million. If the company’s approved stress policy adds a 10% cushion, the buffer becomes $3.52 million. The 10% is an example policy assumption, not a universal standard.

3. Extended runway

Funds needed later in the forecast may be considered for notice-period or fixed-term positions. Stagger maturity dates so the company does not depend on one large redemption. If monthly gross outflows are $800,000, finance might cap each maturity date at no more than one month of expenses and arrange for a portion to become available as each spending month approaches.

A ladder does not eliminate provider or principal risk. It reduces the timing concentration created when multiple obligations depend on a single maturity date.

4. Strategic surplus

Cash beyond approved runway may support acquisitions, expansion, debt repayment or shareholder distributions. It is not automatically spare cash. Its permitted duration should follow the board-approved capital plan, including any dates when management may need to deploy it.

Worked example: a $12 million treasury

Consider a company holding $12 million across USD and USDC. Gross monthly outflows are $800,000, management requires at least 12 months of runway, and a $400,000 tax payment plus a $200,000 annual software renewal are due within 60 days.

Under this framework, $2.2 million, or 18.3% of treasury, remains immediately available and outside yield. Up to $9.8 million, or 81.7%, could be evaluated for yield. That figure is an eligibility ceiling, not a recommendation to allocate the full amount.

The actual allocation may be materially lower after excluding network-fee balances, restricted cash, uninsured operating balances, concentration-limit headroom and funds whose conversion route cannot meet stressed deadlines. Finance may also keep part or all of the liquidity buffer outside yield.

Separate runway by currency, stablecoin and network

A consolidated USD-equivalent balance can hide operational shortfalls. Forecast the location and form of cash needed for each obligation.

• Fiat obligations: Include the time to redeem or sell USDC or USDT, convert currency and settle through the required rail, such as ACH, Fedwire, SEPA, Faster Payments or SWIFT.
• Stablecoin obligations: Hold enough of the required asset on the network accepted by the recipient. Moving between networks adds execution, fee and operational dependencies.
• Blockchain fees: Maintain the relevant network token where transaction fees cannot be paid in the stablecoin being sent.
• Restricted balances: Exclude pledged, reserved or otherwise unavailable funds from operating runway.
• Banking calendars: Map payroll and supplier deadlines against cut-offs, weekends and public holidays in every relevant jurisdiction.

A business account such as Stablerail can bring fiat, USDC and USDT treasury operations together with approvals and signing quorum, sanctions and address screening before send, global payouts, fiat off-ramp, corporate cards and exportable audit evidence. Those operating controls help govern movement, but they do not replace diligence on the risk or redemption terms of a yield position.

Apply risk and concentration limits after calculating liquidity

Liquidity determines which funds may be considered for yield. Risk limits determine how much should actually be allocated. Finance should evaluate the legal claim, asset custody, source of return, counterparty chain, stablecoin exposure and loss scenarios for each position.

Set the policy before funds move

A treasury policy should define more than a maximum yield percentage. It should identify minimum operating cash, the required liquidity buffer, approved assets and providers, exposure limits, permitted maturities, authorized approvers and the evidence retained for each decision.

Finance can use this implementation checklist:

1. Forecast gross outflows by payment date, currency, bank account, stablecoin and network.
2. Reserve immediate operating cash and known exceptional payments.
3. Stress customer receipts, expenses, redemption timing and off-ramp settlement.
4. Classify each opportunity using contractual liquidity terms, not marketing labels.
5. Apply provider, asset, network and maturity concentration limits.
6. Require appropriate approvals for allocations, redemptions and exceptions.
7. Record balances, terms, approvals and transaction evidence for audit and close.
8. Recalculate after financings, acquisitions, material forecast changes or market events.

Monthly review may be a workable baseline, but review frequency should match the company’s cash volatility and payment cadence. A company with weekly payroll and variable collections may need more frequent monitoring.

The CFO decision rule

Allocate funds to yield only when the expected redemption time, conversion time and a documented stress margin all fall before the earliest date the cash could be needed.

Protect operating cash first, size the liquidity buffer second and stagger any extended-runway positions. The appropriate percentage is the output of those decisions—not a target selected in advance. Return matters only after principal risk, access, currency, network and payment timing are acceptable.