Tokenized Treasury Bills for Treasury Yield: The Lowest-Risk Rung

This article treats tokenized T-bill products specifically as a yield instrument: where they sit on the risk ladder, and whether their liquidity actually matches when a treasury needs the cash. For these products, that is usually the lowest-risk on-chain yield available — short US government debt and cash inside a regulated wrapper. But "lowest" is not "no risk," and the yield is only useful if the redemption mechanic lets you exit when you need to. (For the prior question — what the token is as a balance-sheet instrument, a fund share rather than a stablecoin — see tokenized money market funds for treasury; for how its fixed-ish profile stacks against variable yield, see fixed vs variable yield.)

In short

• Tokenized T-bill and MMF products (BUIDL/BENJI-class) are often the lowest-risk on-chain treasury yield — short US govt debt plus cash, in a regulated wrapper.
• Low-risk relative to DeFi is not no-risk: manager, custodian, redemption, regulatory, and per-chain risk remain.
• They are fund shares, not stablecoins, not cash — the instrument question is covered in tokenized MMF treasury.
• Liquidity is the redemption mechanic (minimums, routes, timing) — map it against your actual cash needs.
• Accounting follows the fund interest and is jurisdiction-specific, not a stablecoin or cash line.
• This is one rung inside the treasury yield risk-budget framework.

Why it is usually the low-risk option

The underlying of a tokenized T-bill fund is short-dated US government debt and cash-like instruments inside a regulated fund wrapper with a named manager and custodian (e.g. BUIDL/BENJI). That is a well-understood, low-credit-risk asset class, so counterparty and duration risk are lower than most DeFi yield. It is the natural first rung of a treasury yield strategy — but lower is not zero.

Fund share, not stablecoin

The recurring error is treating a tokenized T-bill token as a stablecoin or cash. It is a tokenized money market fund share — a yield-bearing fund interest with NAV mechanics, a manager, and a custodian — not a par-redeemable payment stablecoin, and generally not cash for accounting (the full instrument breakdown is in tokenized MMF treasury, alongside stablecoin accounting treatment). Misclassifying it corrupts both the balance sheet and the risk view.

Liquidity is the redemption mechanic

The yield is only useful if the exit matches when cash is needed. Tokenized T-bill products have product-specific redemption:

• minimums, often institutional;
• defined redemption routes — for some products, conversion to USDC; for others, fund-level redemption;
• timing that is not necessarily instant-par like a stablecoin.

A treasury has to map the actual redemption path, timing, and minimums against its own liquidity needs before allocating — the liquidity dimension of the risk budget.

Residual risks

Due-diligence items — not reasons to skip diligence.

Accounting

Yield is accounted per the nature of the fund interest and the jurisdiction — not as stablecoin interest, and not as a cash balance. Accrual may be via NAV growth or token mechanics depending on the product, and tax characterisation is jurisdiction-specific. Confirm classification and yield treatment with your auditor (see stablecoin treasury accounting controls).

Due-diligence framework for tokenized T-bill products

Before allocating to any tokenized T-bill product, the following due-diligence steps are the minimum required:

Issuer and fund structure diligence:

• Identify the fund manager, custodian, and (where applicable) the liquidity partner for redemptions. These are the counterparties, not the blockchain protocol. Confirm each party's regulatory status, custody arrangements, and relevant track record.
• Read the fund's offering documents, not just the product's marketing materials. The documents specify the eligible assets, the redemption mechanics, investor eligibility requirements, and any lock-up or notice periods.
• For multi-chain tokenized products, identify which blockchain deployments are officially supported by the fund manager versus third-party bridges. The fund manager's on-chain token is the authoritative version; tokens on unofficial bridges may carry additional smart-contract risk.

Redemption mechanics mapping:

• Create a written document that maps the full redemption path for the specific product: what must be submitted, to whom, by when, and in what form to receive the proceeds. If the redemption routes through a liquidity partner (e.g. requires holding an intermediary stablecoin), map that step too.
• Compare the mapped redemption path against the treasury's liquidity requirements. If the treasury needs to be able to access funds within 24 hours in a stress scenario, confirm that the redemption path can actually deliver that — do not assume it based on the headline "liquid" description.

Ongoing monitoring:

• Tokenized T-bill fund details change: minimum investment amounts, redemption routes, fee structures, and even the regulatory wrapper can change. The due-diligence assessment is refreshed at least annually and immediately on any material change announcement.
• Monitor the underlying fund's NAV and any divergence from expected yield. A persistent divergence from the expected T-bill rate may signal a change in the portfolio composition.

Accounting treatment: tokenized T-bill fund interests

The accounting for a tokenized T-bill fund interest differs from both a stablecoin and a plain equity security:

• Initial recognition: the fund share is recognised at cost (the amount paid to acquire it) on the acquisition date. The acquisition is not a disposal of the consideration asset if the consideration was fiat or a stablecoin — confirm the exchange accounting with your accountant.
• Subsequent measurement: the fund share is typically measured at fair value (NAV per token at the reporting date) or at amortised cost if the fair-value option is not applicable and the fund meets the conditions for amortised cost measurement. Confirm the measurement basis with your accountant given the applicable framework (IFRS 9, US GAAP ASC 820/946, etc.).
• Yield recognition: depending on whether the fund distributes yield (e.g. daily distributions to a separate wallet) or accretes it into the NAV (rebase-style), the income recognition differs. Distributing funds recognise income when the distribution is received; accreting funds recognise income as the NAV per token increases over the holding period.
• Redemption: at redemption, the proceeds received are compared to the carrying value. Any difference is a realised gain or loss. If the redemption is into a stablecoin (e.g. USDC), the stablecoin received is then a new asset at the received value — not automatically the same as the fund share value.
• Balance sheet presentation: the fund interest is classified as a financial asset — typically a current or non-current asset depending on the expected holding period and liquidity profile. It is not cash, not a stablecoin, and not a "crypto asset" in the undifferentiated sense. The specific line is a policy decision confirmed with your accountant.

Practical guidance

1. Treat it as the low-risk rung, not risk-free — diligence the residual risks.
2. Classify as a fund interest — never a stablecoin or cash.
3. Map the redemption mechanic (minimums/routes/timing) to your liquidity needs.
4. Diligence manager/custodian/wrapper/partner per product.
5. Account per the fund interest, jurisdiction-specific — confirm with auditor.
6. Place it within the policy-bounded yield risk budget.

Choosing a tool for the low-risk yield rung

Tools like Cryptio and Request Finance can classify a tokenized fund interest distinctly and track its yield mechanics. Because this rung sits inside a policy-bounded yield strategy, the checks are about both classification and allocation. Before allocating, confirm the tool:

• does not bucket the token as a stablecoin or cash, and tracks its NAV/redemption mechanics as a fund interest;
• distinguishes accrued yield from principal so the income line is real, whatever the accrual model;
• reports the position's size against your treasury-policy allocation limit for this rung, not just a balance.

Instrument misclassification is the recurring tokenized-fund error; a tool that gets the classification right but cannot show the position against a policy cap leaves the risk-budget side unmanaged.

How Wag3s handles it

Wag3s Ledger classifies a tokenized T-bill fund interest distinctly from stablecoins and cash, tracks its yield and redemption mechanics, and keeps the instrument-specific audit trail and policy-allocation reporting, so the low-risk rung is correctly accounted and policy-bounded. See the Ledger product page and the Wag3s for accountants page.

Further reading

• Crypto Treasury Yield Strategy
• Tokenized Money Market Funds for Treasury
• Tokenized RWA Treasury (Ondo, BUIDL, BENJI)
• DeFi Lending Yield for Treasury
• Fixed vs Variable Yield for Treasury
• Stablecoin Treasury Accounting Controls

Sources

• IFRS Foundation — IFRS 9 Financial Instruments: the measurement bases (fair value or amortised cost) and recognition logic behind treating the holding as a financial asset rather than cash, and recognising NAV-accreted or distributed yield.
• Tokenized money market fund mechanics (BUIDL, BENJI) and their product-specific redemption routes and minimums are taken from the funds' own product documentation; yields vary and product details change. The fund-share-not-stablecoin classification is set out in tokenized MMF treasury.