Setting a Treasury Yield Policy Your Board Will Approve
A practical framework for setting stablecoin treasury yield limits, liquidity requirements, approval controls, drawdown triggers and board reporting.
A board-ready treasury yield policy defines which assets and venues are eligible, allocation and concentration limits, minimum liquidity, objective withdrawal triggers, approval authority and reporting requirements. For USDC and USDT, it should also cover depegging, issuer and redemption risk, wallet security, blockchain operations, smart contracts and fiat off-ramp timing. The goal is controlled deployment of surplus funds, not maximising headline yield.
Start with cash requirements, not the advertised yield
A treasury yield policy should preserve the company’s ability to pay payroll, taxes, vendors and other obligations under both normal and stressed conditions. Only balances that are not needed for near-term operations should be considered for yield.
Begin by dividing unrestricted, company-owned treasury into operating, reserve and strategic balances. Exclude customer assets, restricted cash, collateral and funds held for settlement unless the relevant legal agreements expressly permit investment.
| Balance category | Primary purpose | Liquidity expectation | Typical yield eligibility |
|---|---|---|---|
| Operating | Payroll, taxes, vendors, cards and routine payments | Immediately or same day | Usually excluded |
| Reserve | Revenue interruption, unexpected expenses and delayed funding | Same day to a few business days | Partially eligible, subject to limits |
| Strategic | Funds not expected to be used during the board-approved planning period | Defined by forecast and risk tolerance | Potentially eligible |
The board can require a minimum operating buffer expressed as forecast expenses, forecast net cash outflows or a fixed amount. For example, retaining 90 days of forecast payments outside yield products may be a useful scenario to test, but it is not a universal recommendation. The appropriate buffer depends on cash-flow volatility, revenue concentration, fundraising plans, banking access and the reliability of stablecoin-to-fiat conversion routes.
Finance should calculate the buffer using stressed as well as base-case forecasts. A delayed customer payment, blocked bank transfer or slower-than-expected stablecoin redemption can turn an apparently liquid position into an operational shortfall.
Define eligible instruments, venues and counterparties
Wording such as “approved yield products” is too broad. The policy should define both the permitted instrument and the venue or legal counterparty through which the company accesses it. A familiar interface or a stable quoted price does not establish who owes the company money or what happens during insolvency.
| Option | Source of return | Key diligence questions | Liquidity considerations |
|---|---|---|---|
| Bank or regulated deposit product | Interest paid by the deposit-taking institution | Which entity holds the deposit, what protections apply and are withdrawals subject to account restrictions? | May be same day, but banking hours, compliance reviews and transfer cut-offs matter |
| Tokenised money-market fund | Income from the fund’s underlying portfolio | Who manages and custodies assets, what does the fund own and how are token holders recorded? | Redemption may depend on dealing windows, business days, transfer-agent processing and banking rails |
| Centralised lending arrangement | Interest paid by a borrower or intermediary | Is the claim secured, what collateral exists, can assets be rehypothecated and where does the company rank on default? | Notice periods, withdrawal queues or contractual lock-ups may apply |
| Decentralised finance protocol | Borrowing demand, trading fees or incentives | Which contracts, administrators, oracles and governance mechanisms affect the position? | Onchain withdrawal may be fast in normal conditions but constrained by utilisation, chain congestion or contract controls |
For every proposed venue, the finance team should document the legal counterparty, governing law, underlying assets, use of leverage, custody structure, loss position, fees, withdrawal terms and operational route. It should also identify every wallet, network and conversion step needed to return funds to the fiat currencies used for company obligations.
The approved list should record the specific legal entity and product, not only a trading name. A change in counterparty, custodian, underlying assets, smart contract, redemption process or material terms should move the venue back into review status.
Set allocation and concentration limits
Limits should remain meaningful as treasury balances change. A percentage of eligible liquid treasury is often easier to maintain than a fixed amount, although a policy can use both. The denominator must be explicit: unrestricted cash and stablecoins beneficially owned by the company is clearer than the undefined term “treasury.”
A policy should address four separate limits:
- Total allocation: the maximum share of eligible treasury that may be placed into yield products.
- Venue and counterparty concentration: the maximum exposure to one product, legal entity or related group.
- Liquidity concentration: the maximum amount subject to notice periods, lock-ups or redemption gates.
- Asset and network concentration: limits on dependence on one stablecoin, blockchain or conversion route.
Illustrative limits such as 20% in all yield positions, 10% with one venue or 5% without same-day liquidity can help a board discuss risk, but they should not be copied without analysis. Actual limits should reflect runway, forecast accuracy, counterparty quality and the amount the company could tolerate losing or having unavailable.
Measure liquidity end to end
“Liquid” should be replaced with testable time periods. The policy might require enough immediately available cash and stablecoins for the next 30 days of forecast payments, additional assets redeemable within one business day for days 31–60, and no lock-up beyond the board-approved planning horizon. Those periods are examples; the company should set its own.
Measure from the decision to withdraw until spendable funds reach the required destination. A product described as T+1 may settle one business day after a valid request, but that description may exclude blockchain confirmation, venue compliance review, a weekend, banking cut-offs and the final fiat transfer.
Finance should test redemption routes periodically with an appropriately controlled amount. A theoretical off-ramp is not sufficient if the relevant bank account, beneficiary, network or authorised signer is unavailable when funds are needed.
Write objective drawdown triggers
Drawdown triggers allow management to pause, reduce or exit a position without waiting for the next board meeting. Each trigger needs an observable threshold, a required action, an owner and an escalation deadline.
| Trigger | Immediate action | Decision required |
|---|---|---|
| Stablecoin price or redemption value crosses the policy threshold | Pause new allocations and verify available redemption and trading routes | Hold, reduce or convert exposure based on liquidity and execution risk |
| Withdrawal exceeds the documented timeframe | Stop additional funding and escalate to the CFO | Determine whether the delay is operational, contractual or a sign of counterparty distress |
| Operating liquidity falls below the minimum | Redeem sufficient eligible positions | Restore the buffer and review the forecast variance |
| Counterparty, contract or material terms change | Move the venue to review status | Repeat legal, financial, security and operational diligence |
| Security, sanctions or adverse legal event occurs | Freeze affected activity where possible and begin incident procedures | Assess recovery, reporting and exit options |
Avoid undefined phrases such as “material depeg” or “significant delay.” The policy should state the approved threshold and observation method. It should also distinguish between pausing new allocations, making a partial reduction and requiring a full exit, because a forced sale during market stress can deepen losses.
Separate preparation, approval and execution
Board approval should authorise a controlled process rather than give one person unrestricted authority. Define responsibilities by role so staff changes do not make the policy obsolete. A treasury analyst might prepare an allocation, the controller might confirm eligibility and destination details, and the CFO might approve execution. Transactions above a stated threshold can require an additional director or board signatory.
For self-custodied assets, signing quorum should prevent one participant from moving funds alone. Destination verification, sanctions and address screening before send, access reviews and exportable transaction evidence should be part of the operating procedure. Stablerail supports approvals and signing quorum, pre-send sanctions and address screening, global payouts, fiat off-ramp and exportable audit evidence within one business account for USDC and USDT treasury.
Give the board decision-useful reporting
Management may monitor positions weekly or more frequently, while the board receives a monthly or quarterly summary. Reporting should show opening and closing balances by asset, venue and network; exposure as a percentage of eligible treasury; yield actually earned; fees and realised losses; current redemption periods; concentration; policy breaches; delayed withdrawals; and changes to the approved list.
Report realised or accrued income according to the company’s accounting treatment rather than presenting an annualised promotional rate as earned income. Finance should also document valuation sources, token balances, wallet ownership evidence and reconciliations to the general ledger. Accounting, tax and financial-statement disclosure consequences should be reviewed before a new instrument is approved.
Board approval checklist
- Define eligible company entities, assets and accounts, including explicit exclusions.
- Attach the current venue list and identify each legal counterparty and product.
- Set total, per-counterparty, illiquid, stablecoin and network limits.
- Specify the operating buffer and end-to-end redemption deadlines.
- Approve measurable drawdown triggers, actions and escalation owners.
- Document preparation, approval, signing and exception authorities.
- Provide a sample board report and breach-notification process.
- Run scenarios for a depeg, delayed withdrawal, bank closure and signer unavailability.
- Require review at least annually and after material business, market or product changes.
The final board paper should include the policy, approved venue list, relevant product terms, diligence summary and worked liquidity scenarios. This gives directors enough information to approve risk boundaries while allowing the finance team to manage surplus balances without returning to the board for every routine transaction.
Frequently asked questions
What should a treasury yield policy include?
It should define eligible assets and venues, allocation and concentration limits, minimum liquidity, drawdown triggers, approval authority and reporting. It should also specify exclusions, exception handling and when a venue or the overall policy must be reviewed again.
How much treasury should a company allocate to yield?
There is no universal percentage. The limit should follow a cash-flow forecast and reflect operating runway, revenue concentration, withdrawal timing, counterparty quality and the amount the company could tolerate losing or having temporarily unavailable.
How should a board evaluate stablecoin yield risk?
The board should assess the stablecoin issuer and redemption route as well as the specific product, legal counterparty, custody structure and underlying assets. It should also consider depegging, blockchain, wallet, smart-contract, sanctions and fiat off-ramp risks.
What liquidity terms belong in a treasury yield policy?
The policy should state how much must be immediately available, how quickly other positions must be redeemable and the maximum permitted lock-up. Timing should be measured end to end, including product redemption, blockchain settlement, compliance review, banking cut-offs and fiat delivery.
Who should approve stablecoin treasury yield transactions?
Preparation, review, approval and signing should be separated where staffing permits. The policy should assign authority by role, require multiple approvals or signing quorum where appropriate, and reserve larger transactions or policy exceptions for additional executive or board approval.
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.

