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

Start with liabilities, not a yield percentage

There is no universally safe percentage of corporate treasury to place in yield. A company with predictable subscription receipts, modest weekly spending and flexible costs can generally tolerate less immediate liquidity than one facing lumpy payroll, concentrated customers, seasonal collections or large tax payments.

The defensible approach is to work backwards from obligations. Protect operating cash, establish a buffer for delays and surprises, separate restricted balances, and consider yield only for the remainder. This liability-led framework applies whether treasury consists of fiat, USDC, USDT or a combination.

The central calculation is:

Maximum yield-eligible balance = available treasury − operating cash − liquidity buffer − restricted funds

This is a ceiling, not an allocation target. Finance may keep some eligible funds liquid when forecasts are uncertain, conversion routes are untested or the expected return does not justify the additional risk.

Define liquidity before comparing rates

A quoted annual percentage yield says little about whether funds will be available for Friday payroll. Before allocating, document the actual withdrawal process and the source of return. Terms such as liquid or flexible should not substitute for operational diligence.

Stablecoin yield is not equivalent to guaranteed bank interest. Depending on the product, the company may face borrower default, counterparty failure, smart-contract vulnerabilities, custody failures, stablecoin depegging, market losses or delayed withdrawals. Tokenised government securities can also have transfer restrictions, market-value changes and redemption processes that differ from holding cash.

Use four treasury buckets

A four-bucket structure makes the allocation decision explainable to management, auditors and the board. Each balance should belong to a defined bucket rather than being labelled broadly as “cash.”

Build the liquidity requirement from gross cash flows

1. Map obligations by week

Choose a protected planning horizon based on the reliability of receipts and the speed at which spending can be reduced. Ninety days can be a useful scenario, but it is not a universal rule. A seasonal business, a company approaching a debt maturity or one dependent on a few customers may require a longer or more conservative horizon.

List gross outflows by week. Do not rely only on net burn. A business that spends $800,000 and collects $500,000 each month has a $300,000 net burn, but it may have to fund the full $800,000 before customer payments arrive. Include payroll and payroll taxes, vendor batches, rent, debt service, corporate card settlement, planned purchases and known tax dates.

2. Separate obligations by asset, currency and rail

Availability must be measured in the form required for payment. USD needed for ACH or wire transfer may not be replaceable immediately with USDT, particularly outside banking hours. Likewise, an on-chain vendor payment may require USDC or USDT on a specific network plus the network’s native token for transaction fees.

Conversion capability reduces friction but does not eliminate settlement timing, banking cut-offs, network congestion, stablecoin price movement or execution risk. Near-term liabilities should therefore be backed by assets that can reach the required payment rail with minimal dependency on conversion.

3. Discount expected inflows

Count receipts only when there is a strong basis for timing and amount. Contracted recurring payments may deserve more recognition than disputed invoices, uncommitted financing or collections from a concentrated customer. Apply a haircut for payment delays, churn, disputes, banking interruptions and foreign-exchange timing. Companies with volatile or seasonal collections may choose not to offset protected obligations with uncollected inflows at all.

4. Add a contingency reserve

The reserve should cover forecast error and operational disruption. It can be expressed as additional weeks of gross spending or as an amount tied to identified scenarios. Relevant factors include customer concentration, revenue volatility, access to committed credit, payroll rigidity and how quickly discretionary costs can actually be stopped.

Worked example: a 90-day allocation

Consider a company with $6 million across fiat and stablecoin balances. It spends $800,000 per month and expects $500,000 in monthly customer receipts. Dividing treasury by the $300,000 monthly net burn suggests 20 months of runway, but that figure does not capture when gross payments fall due.

In this example, 60% of treasury is mathematically yield-eligible. That does not mean all $3.6 million belongs in a notice-based or fixed-term product. If a delayed-receipts scenario creates an additional $1 million need, finance could retain that amount in a same-day-accessible balance and evaluate only the remaining $2.6 million for longer redemption terms.

A layered allocation can reduce maturity concentration. For example, one portion may remain immediately available, another may use short-notice redemption, and only the portion that survives the severe scenario may accept a longer term. The exact split should follow contractual documentation and tested settlement timelines rather than product labels.

Stress-test access before funding

Run at least a base case, a delayed-receipts case and a severe but plausible case. The allocation passes only if the company can meet payroll, taxes, debt service and critical vendors without depending on an untested emergency conversion.

• Delay major customer receipts by one billing cycle.
• Increase gross outflows to reflect a cost overrun or accelerated vendor payment.
• Extend the stated redemption timeline across a weekend or holiday.
• Model a stablecoin trading below its target value during conversion.
• Assume one banking, exchange or blockchain route is temporarily unavailable.
• Confirm sufficient network-fee tokens and access to the correct wallet and chain.

Do not count the same liquidity twice. A stablecoin balance pledged as collateral, committed to a term product or reserved for a particular liability cannot simultaneously support general operating needs.

Put governance around the allocation

A sound calculation can still fail through weak execution. Assign an owner for the forecast, an approver for allocation changes and a documented process for redemption. Record the product terms reviewed, wallet or account destination, approval evidence, transaction identifier, accounting treatment and reconciliation outcome.

Before moving funds, finance should complete this control checklist:

1. Reconcile the source balance to the general ledger.
2. Confirm the destination, network and settlement asset using an independently verified instruction.
3. Apply the company’s required approvals and signing quorum.
4. Screen the destination and relevant addresses before sending.
5. Test the route with an appropriately controlled amount when it is new.
6. Retain statements, transaction records, approvals and valuation evidence for audit.

For companies managing their own USDC or USDT, Stablerail can support approvals and signing quorum, sanctions and address screening before send, fiat conversion, global payouts and exportable audit evidence. These controls help govern execution, but they do not replace diligence on the yield product, issuer or counterparty.

Use event-driven review triggers

Review the allocation on a regular treasury cadence and whenever assumptions change. Triggers should include a large tax payment, acquisition, fundraising delay, loss of a major customer, change in redemption terms, stablecoin depeg, counterparty concern or a material rate movement.

A rising rate is not automatically a reason to increase exposure. It may reflect changing demand for capital, reduced liquidity or higher perceived risk. Re-underwrite the source of return and exit mechanics before changing the allocation.

The governing rule is simple: yield sits behind operating resilience. Protect gross obligations, discount uncertain receipts, preserve a contingency reserve and allocate only the surplus whose risk and redemption terms fit the company’s actual payment calendar.