Writing a Stablecoin Treasury Policy: A Template for Boards

Most startups adopt a stablecoin treasury policy after the fact, once USDC is already sitting on the balance sheet and an auditor or a board member starts asking questions. Writing the policy first is the cheaper order of operations. A short, board-approved document turns a set of informal habits into a rule your finance team can point to, and it gives directors a reason to say yes before the first dollar of USDC is held.

This is a section-by-section template for a stablecoin treasury policy that a board can review, edit, and approve. It covers objectives and risk tolerance, which stablecoins are approved and why, custody and wallet controls, chain selection, concentration and counterparty limits, signing authority, liquidity floors, accounting, and how often the policy gets reviewed. Adapt the language to your company. This is general information, not legal, accounting, or investment advice.

Why a Stablecoin Treasury Policy Matters

A treasury policy exists so that decisions about company cash are not made one Slack message at a time. For fiat that logic is old news. For stablecoins it is newer, and that is exactly why boards want it written down. Three reasons come up again and again.

Fiduciary duty: directors are responsible for how the company handles its money. A written policy is evidence that the board set the guardrails and that management operated inside them. If a stablecoin loses its peg or a wallet is compromised, the first question is whether there was a policy and whether it was followed.

Auditor and board comfort: auditors and audit committees ask for the policy before they ask about the balances. A document that names the approved assets, the custody model, and the reconciliation process answers most of the questions in one pass, which shortens the review and the back and forth.

Guardrails before you hold USDC: the policy is worth the most before the position exists. Once you are holding a seven-figure USDC balance, changing the rules feels like criticizing a decision already made. Writing the policy first lets the board set limits calmly, in the abstract, rather than under pressure.

The rest of this post walks through the sections a policy should contain. Treat each heading as a section of the document you are drafting.

Objectives and Risk Tolerance

Open with what the treasury is for. A startup treasury usually has three jobs, and they rank in this order: preserve capital, keep enough liquidity to run the business, and earn a return on what is left. Stablecoins mostly serve the first two. Say so plainly, because the ranking decides every trade-off that follows.

State the risk tolerance in words a non-specialist director can hold in their head. A common formulation is that the company will not take principal risk with operating cash, will accept the peg and counterparty risk of a named stablecoin for payment and settlement purposes, and will keep any yield-seeking activity in a separate, clearly labeled bucket. If your board wants a number, tie the tolerance to a share of total cash rather than a dollar figure, so the policy still makes sense as the balance grows.

Approved Stablecoins and Why

List the specific stablecoins the company may hold, and give the reason for each. A one-line rationale per asset is enough, and it forces the drafter to actually check. Two criteria carry most of the weight.

Reserve quality: what backs the token, and how transparent is the backing. USDC, for example, is backed by cash and short-dated US Treasury holdings, with reserve composition published and monthly third-party attestations. You can point a director at the source directly: Circle's transparency page shows the reserve breakdown and the attestation history. A policy that names the reserve model is far easier to defend than one that just names a ticker.

Redemption: how the token converts back to dollars, and who guarantees it. A stablecoin that is redeemable one for one with the issuer is a different risk than one that depends on a secondary market to hold its price. Write down the redemption path for each approved asset, including which regulated entity stands behind it.

Be explicit about what is not approved. If the policy allows USDC and, say, USDT for specific counterparties but excludes algorithmic or thinly backed tokens, name that exclusion. The excluded list is often the most useful part of the section, because it tells the finance team where the line is.

Custody, Wallet Controls, and Chain Selection

Custody is where a stablecoin policy either has teeth or does not. Decide who holds the keys and how a transaction gets signed, then write it down.

Custody model: state whether the company self-custodies, uses a qualified custodian, or holds USDC on a platform that runs it alongside fiat. Each model has a different failure mode, and the board should pick one on purpose rather than inherit it from whichever tool the team happened to open first.

Wallet controls: specify multi-user approval for outbound transfers, address allowlisting so funds can only move to pre-approved destinations, and separation between the person who initiates a payment and the person who approves it. If account and routing details or private keys exist, say who can see them and who cannot.

Chain selection: name the blockchains the company will transact on and why. USDC settles natively on several chains, including Ethereum, Solana, Base, and Arbitrum, and each has a different cost and finality profile. A policy that approves specific chains, rather than leaving the choice to whoever sends the payment, keeps you from receiving funds on a network your accounting and custody setup does not support.

Concentration, Counterparty Limits, and Signing Authority

This section sets the numeric guardrails. Keep them as percentages and thresholds so they age well.

Concentration limits: cap how much of total treasury can sit in any single stablecoin, and how much can sit with any single issuer, custodian, or bank. Concentration risk is the one most startups ignore until a counterparty wobbles, so a simple ceiling here does a lot of work.

Counterparty limits: list the issuers, custodians, exchanges, and banks the company is willing to face, and set a maximum exposure to each. Add the condition that triggers a review of a counterparty, such as a downgrade, a delayed attestation, or a public liquidity event.

Approval and signing authority: define who can move money and up to what size. A typical structure gives the finance lead authority up to a threshold, requires a second approver above it, and reserves the largest transfers or any new counterparty for board or committee sign-off. Tie the authority to roles, not names, so the policy survives a personnel change.

Liquidity and Operating-Cash Floors

Set a floor of cash the company keeps accessible at all times, and define accessible clearly. For most startups the floor is stated as months of operating expense, held in fiat or in same-day redeemable instruments, and untouched by any yield strategy. The point of the floor is that a peg event or a chain outage never puts payroll at risk.

If the company sweeps idle cash into yield-bearing instruments such as US Treasury bills, keep that activity above the floor and in a separate policy bucket. Note in the policy that securities investments are not FDIC insured, are not bank guaranteed, and may lose value, and that yield-seeking is subordinate to the liquidity floor. Stablecoin holdings held for payments are a liquidity tool, not an investment, and the policy should say which bucket a given balance belongs to.

Accounting, Reconciliation, and Review Cadence

A stablecoin policy that ignores the books gets undone at close. Write down how the holdings are recorded and checked.

Accounting treatment: reference the standard your auditors apply. US GAAP now has a specific model for many crypto assets under the FASB's crypto assets standard, which calls for fair value measurement with changes in the income statement. The FASB's project page is the primary reference; confirm the treatment for your specific holdings with your accountant, since a fiat-backed stablecoin may be analyzed differently from other tokens.

Reconciliation: state how on-chain balances tie back to the general ledger and how often. Daily or same-day reconciliation is the standard to aim for, with the on-chain transaction record serving as the audit trail. Name the accounting system the balances reconcile to.

Review cadence: say how often the board revisits the policy and what forces an off-cycle review. An annual review is the baseline. Add triggers: a new approved asset, a change in reserve disclosures, a regulatory shift, or a loss event at a counterparty. A policy with no review date is a policy nobody reads again.

Frequently Asked Questions

Do we need a treasury policy before holding any USDC? You are not legally required to have one to hold USDC, but it is the practical starting point. Auditors and boards ask for it, and writing the guardrails before the position exists is easier than editing them after. Even a one-page version is better than nothing.

What should the policy say about which stablecoins are approved? Name the specific tokens, give a one-line reason for each based on reserve quality and redemption, and list what is excluded. Pointing to a primary source such as the issuer's reserve disclosures makes the section easy to defend.

Who should have authority to move stablecoins? Tie authority to roles and dollar thresholds, not to individuals. A common pattern is single approval up to a limit, dual approval above it, and board or committee sign-off for the largest transfers or any new counterparty.

How do we handle accounting for stablecoin holdings? Reference the accounting standard your auditors apply and confirm the treatment for your specific holdings with your accountant. Reconcile on-chain balances to the general ledger on a same-day or daily basis, using the on-chain record as the audit trail.

How is a liquidity floor different from a stablecoin balance? The liquidity floor is the cash you keep accessible at all times to run the business, usually stated in months of operating expense. Stablecoin balances held for payments can count toward accessible funds if they are same-day redeemable, but yield-seeking positions should sit above the floor in a separate bucket.

How often should the board review the policy? Review it at least annually, and sooner if you add an asset, change custodians, see a regulatory change, or a counterparty has a loss event. Put the review date and the triggers in the document itself.

A Note on Meow

Meow is built for the version of this policy that actually runs day to day. USDC is held on the same balance as fiat, with reconciliation to QuickBooks and Xero, so the accounting section of your policy is satisfied by the platform rather than by a spreadsheet. Approvals and spend controls are native: you set who can move money and at what size, and outbound transfers can require a second approver. The custody and chain choices your board makes have a home in the product, which is the point of writing the policy in the first place.

Put the Policy in Front of Your Board

A treasury policy is short, and the hardest part is starting the draft. Use these sections as the outline, fill in the numbers your board is comfortable with, and bring it to the next meeting. When you are ready to hold USDC alongside your fiat with reconciliation and approvals built in, open an account at meow.com.

This post is general information, not legal, accounting, or investment advice.

Meow Technologies is a financial technology company, not a bank or FDIC-insured depository institution. Banking services are provided by Grasshopper Bank, N.A.; Member FDIC. The FDIC's deposit insurance coverage only protects against the failure of an FDIC-insured bank.