Setting a Treasury Yield Policy Your Board Will Approve

A board-ready treasury yield policy should answer six questions: where funds may be placed, how much may be allocated, how quickly funds must be accessible, what triggers a withdrawal, who can move funds and what the board will receive in reporting.

For companies holding USDC or USDT, the policy also needs to address risks that do not arise with a conventional bank deposit. These include stablecoin depegging, wallet compromise, smart-contract failure, counterparty default and delays when redeeming into fiat.

The objective is not to eliminate risk or maximise headline yield. It is to set boundaries within which the finance team can manage idle treasury without requesting board approval for every transaction.

Start with the cash requirement, not the yield

Before setting an allocation, divide treasury into operating, reserve and strategic balances. Only funds that are not required for near-term obligations should be considered for yield.

A simple starting rule is to keep a minimum number of months of forecast operating expenses outside yield products. For example, a board might require 90 days of expenses to remain available for payments. That figure is illustrative, not a universal recommendation; it should reflect revenue concentration, fundraising plans and the reliability of fiat and stablecoin off-ramps.

When using Stablerail Earn, finance teams should review the stated liquidity terms and risks for each opportunity before allocating. A quoted annual percentage yield does not show how quickly funds can be withdrawn or what could cause a loss.

Define eligible venues precisely

“Approved yield products” is too broad for a treasury policy. The policy should define both the eligible instrument and the venue or counterparty through which it can be accessed.

Possible categories include regulated deposit products, tokenised money-market funds, secured or unsecured lending arrangements and decentralised finance protocols. Each has a different risk structure. A tokenised fund may expose the company to the fund manager, custodian and underlying assets. A lending product adds borrower and collateral risk. A protocol adds smart-contract, oracle and governance risk.

For each proposed venue, the finance team should document:

• Legal counterparty: the entity responsible for holding, investing or returning the funds.
• Underlying assets: what generates the return and whether leverage is used.
• Liquidity: withdrawal notice, settlement time, lock-up period and any redemption gates.
• Loss position: whether the company is senior, secured, unsecured or exposed through a pooled structure.
• Jurisdiction: governing law and any restrictions affecting the company.
• Operational route: wallets, networks and approvals required to allocate or redeem.
• Evidence: agreements, disclosures, audited reports or other documents supporting the review.

The policy can require a documented review before a venue is added to an approved list. Material changes to its counterparty, terms, assets or withdrawal process should trigger a new review.

Set maximum allocations and concentration limits

The maximum allocation should be expressed in a way that remains useful as treasury changes. A percentage of total liquid assets is generally easier to maintain than a fixed currency amount, although both can be used.

An illustrative policy might limit total yield allocations to 20% of liquid treasury, with no more than 10% placed with one venue and no more than 5% in an arrangement without same-day liquidity. These numbers are examples only. A board should choose limits based on runway, cash-flow volatility, counterparty quality and its tolerance for loss or delayed access.

Define the denominator carefully. “Treasury” might include restricted cash, customer funds or assets held for settlement that should never be eligible. A clearer measure is unrestricted cash and stablecoins beneficially owned by the company.

Specify minimum liquidity

Liquidity needs more detail than “funds must be liquid.” The yield policy should state how much must be available immediately and how quickly the remainder must be redeemable.

A practical liquidity ladder could require:

• enough immediately available cash and stablecoins for the next 30 days of forecast payments;
• enough assets redeemable within one business day to cover days 31–60;
• no allocation with a lock-up longer than the board-approved planning horizon; and
• a documented route for converting redeemed USDC or USDT into the fiat currencies needed for payroll, tax and vendors.

Settlement timing should be measured end to end. “T+1 redemption” means settlement one business day after a valid request; it does not necessarily include blockchain confirmation, compliance review, banking cut-offs or the final fiat transfer.

Write objective drawdown triggers

Drawdown triggers tell the treasury team when to reduce or exit a position without waiting for the next board meeting. They should be observable and linked to a defined action.

The policy should set actual thresholds rather than leaving terms such as “material depeg” undefined. It should also distinguish between pausing new allocations, partial reduction and full exit. Forced sales during market stress can create additional losses, so the response should account for available liquidity and execution risk.

Control who can move funds

Board approval should authorise a process, not give one person unrestricted authority. The policy should name roles rather than individuals so it remains usable when staff change.

For example, a treasury analyst may prepare an allocation, the controller may verify the destination and the CFO may provide final approval. Transfers above a defined threshold can require an additional director or board signatory.

Where funds are held in a self-custodial MPC vault, quorum signing can require multiple authorised participants before a transfer is executed. An MPC vault distributes signing authority so that no single person holds the complete private key. Approved wallet allowlists, transaction limits and an audit log can further reduce operational error.

Set the reporting cadence

Management may need weekly reporting while the board receives a monthly or quarterly summary. A useful report should include:

• opening and closing balances by stablecoin, venue and network;
• allocation as a percentage of eligible treasury;
• yield earned, fees paid and realised losses;
• current liquidity and the longest withdrawal period;
• counterparty and venue concentration;
• policy breaches, delayed withdrawals and trigger events; and
• changes proposed for the approved venue list.

Report yield net of known fees where possible. Avoid presenting an annualised rate as earned income, particularly when rates are variable.

A concise policy template

The following structure can be adapted for a board paper:

• Purpose: permit controlled use of surplus USDC, USDT and fiat balances to earn yield while preserving operating liquidity.
• Scope: define eligible company entities, assets and accounts; exclude customer, restricted and settlement funds.
• Eligible venues: allocations only to venues on a CFO-maintained list following documented legal, financial, security and operational review.
• Maximum allocation: set total, per-venue, per-counterparty and illiquid allocation limits.
• Minimum liquidity: state the required operating buffer and maximum acceptable redemption period.
• Drawdown triggers: define measurable triggers, required actions and escalation contacts.
• Authority: specify preparation, approval and signing roles, including thresholds requiring board approval.
• Reporting: set management and board reporting frequency, required metrics and breach notification timing.
• Review: require at least annual review and earlier review after material market, product or business changes.

For board approval, attach the current venue list, product terms, liquidity scenarios and a worked example showing the effect of a delayed withdrawal or stablecoin depeg. This turns the treasury policy from a statement of intent into an operating framework the board can evaluate and the finance team can follow.