How to Earn Yield on Idle Treasury Without Locking Up Working Capital
A practical framework for splitting stablecoin treasury into operating float and idle reserve, assessing liquidity terms, sizing an allocation and understanding the risks of treasury yield.
Earning yield on idle treasury starts with a liquidity decision, not a rate comparison. Finance teams first need to determine how much USDC, USDT and fiat must remain immediately available for payroll, vendors, cards, taxes and customer withdrawals. Only the remaining reserve should be considered for yield.
Stablerail’s Earn capability is designed for eligible treasury balances, with liquidity terms and risks stated for each available product. Yield is variable, carries risk and is not a bank deposit. Stablecoins are also not the same as insured cash, even when designed to track a fiat currency.
Split the treasury into operating float and idle reserve
A useful treasury structure has at least two buckets:
- Operating float: Funds available for obligations due soon, unexpected payments and settlement delays.
- Idle reserve: Funds not expected to be used during the relevant redemption period and therefore potentially eligible for stablecoin earn products.
Some companies add a third bucket for strategic reserves. These funds may not be needed for normal operations but are kept liquid for acquisitions, market shocks or unusually large customer redemptions.
Do not define idle cash as whatever remains in the account at the end of the month. Start with a rolling cash forecast covering at least 30 to 90 days. Include known obligations, plausible downside scenarios and the time required to bring money back from an earn product.
A practical operating-float formula
A simple starting point is:
Operating float = near-term obligations − haircut-adjusted inflows + stress buffer + settlement buffer
For example, assume a company has $2 million equivalent in treasury assets:
- $620,000 of obligations due in the next 30 days
- $450,000 of forecast customer receipts
- A 30% haircut applied to forecast receipts, meaning only $315,000 is treated as reliable
- A $200,000 buffer for unexpected payments or delayed collections
- An $80,000 buffer for settlement, network and conversion delays
The resulting operating float is $585,000: $620,000 minus $315,000, plus $200,000 and $80,000. That leaves $1.415 million outside the minimum operating float.
This does not mean the full $1.415 million should earn yield. The finance team might keep $415,000 as an additional strategic reserve and allocate $1 million. The numbers are illustrative, not a recommendation; the right allocation depends on revenue predictability, customer redemption patterns and access to other liquidity.
Match the reserve to actual replenishment times
“Instant access” should describe the full journey back to a spendable balance, not just the time needed to submit a redemption request. Consider product processing, blockchain confirmation, conversion and fiat settlement.
| Route | Typical timing to plan around | Potential constraint |
|---|---|---|
| Stablecoin redemption to an available wallet balance | Network confirmation may take seconds or minutes | The earn product may have separate processing windows, notice periods or withdrawal queues |
| SEPA Instant | Usually seconds when both institutions and the payment are eligible | Availability, transaction limits and screening can affect processing |
| ACH | Commonly one to three business days | Weekends, holidays, returns and bank processing |
| Fedwire | Generally same business day within operating hours | Cut-off times and banking days |
| SWIFT | Often one to five business days | Correspondent banks, currencies and compliance reviews |
If payroll is due in fiat on Friday, redeeming an earn position on Friday morning may be too late. The operating float should cover the entire redemption and conversion timeline, plus a reasonable delay scenario.
Liquidity terms to demand before allocating
A headline annual percentage yield does not explain whether working capital is genuinely accessible. Before allocating, obtain clear answers to the following:
- Redemption period: Is redemption on demand, same day, next business day or subject to a fixed notice period?
- Processing windows: Are requests handled continuously, only on business days or before a daily cut-off?
- Lockups: Is there a minimum holding period or penalty for early redemption?
- Gates and queues: Can withdrawals be delayed, limited or processed in order during stressed markets?
- Redemption asset: Will principal return in USDC, USDT, fiat or another asset?
- Fees: Are there subscription, management, network, redemption or conversion charges?
- Yield treatment: Is the quoted rate fixed or variable, and how often does it accrue and compound?
- Principal exposure: What assets, borrowers, protocols or counterparties generate the return?
Ask for terms in writing and model the slowest permitted redemption time, not the fastest historical outcome.
Compare net return, not headline APY
For illustration, a 4% annual rate on a $1 million allocation equates to approximately $40,000 over a full year before fees, rate changes, losses and tax. Over 30 days, a simple non-compounded estimate is about $3,288: $1 million multiplied by 4%, then by 30 divided by 365.
That estimate is not a promised return. A variable rate can change quickly, and the net result may also be reduced by blockchain fees, stablecoin conversion spreads, product charges and the operational cost of moving funds.
Finance teams should compare opportunities using the same fields:
| Field | What to record |
|---|---|
| Expected net yield | Rate after disclosed fees and expected transaction costs |
| Redemption time | Normal timeline and maximum contractual or stated timeline |
| Rate type | Fixed, variable or promotional |
| Principal risk | Underlying credit, market, protocol and counterparty exposure |
| Return asset | USDC, USDT, fiat or another instrument |
| Operational fit | Supported network, minimum allocation and approval workflow |
Understand what can go wrong
Treasury yield is compensation for taking risk. It is not interest on a guaranteed or insured deposit. Depending on the product structure, risks may include:
- Credit risk: A borrower or counterparty may fail to repay.
- Liquidity risk: Redemptions may take longer than expected or be limited during market stress.
- Stablecoin risk: USDC or USDT may trade away from its target value, or redemption access may be disrupted.
- Protocol risk: Smart-contract errors, exploits or governance failures can cause losses.
- Network risk: Congestion, outages or high transaction fees can delay movement.
- Custody and operational risk: Incorrect addresses, compromised credentials or approval mistakes can result in loss.
- Regulatory and tax risk: Treatment may differ by jurisdiction, legal entity and product structure.
Review the underlying source of yield rather than treating all stablecoin earn products as equivalent. A higher rate usually reflects additional credit, liquidity, duration or technical risk.
Set an allocation rule the team can operate
Instead of choosing a fixed amount once, define a repeatable rule. For example: allocate only the balance above the 45-day stressed operating requirement, review it weekly and suspend new allocations if forecast coverage falls below the threshold.
Use treasury approval limits and quorum signing so that one person cannot move a material reserve alone. Record the approved amount, product terms, destination address, expected redemption time and decision date. These controls support the liquidity decision without slowing routine operations.
Stablerail business accounts can keep operating USDC and USDT in self-custodial MPC vaults while supporting fiat rails and on/off-ramp activity. Eligible balances can then be assessed separately for Earn rather than mixing payroll liquidity with longer-horizon reserves. Teams that need to keep a dedicated USDC operating balance can also review the USDC business account.
Start conservatively
Begin with an amount the business can operate without through the full redemption period. Test a small allocation, accrue yield, redeem it and confirm how long the complete journey takes back to a usable stablecoin or fiat balance.
Only increase the allocation after reconciling the transaction, confirming the net return and updating the liquidity forecast. The objective is not to maximize treasury yield at all times. It is to earn a measured return on genuinely idle reserves while preserving enough working capital to pay every obligation on time.
Finance writers covering stablecoin treasury, payments, compliance, and risk controls.
More about the Stablerail team- Stablecoin treasury managementApprovals, limits, yield and reporting on one balance.
- Stablecoin payoutsBatch contractor and vendor payments with screening.
- USDT vs USDCWhich stablecoin your company should settle in.
- Stablecoin finance glossaryMPC, off-ramp, travel rule and the rest, in plain English.
- Product updatesEverything we ship, month by month.

