A tokenised fund can accept a redemption instruction while being unable to pay it immediately. That is an ordinary consequence of holding assets that mature, trade or settle on a different timetable from the fund token. The operating question is what happens between submitting shares and receiving an asset that the investor can actually spend.
A clear exit process distinguishes the investor's right to request payment, the manager's authority to limit payment, the price used for payment and the instrument delivered. A transaction hash answers none of those questions by itself. Our discussion of tokenised fund interests and liquidity explains the wrapper. Redemptions require a closer look at the liabilities inside it.
Three states that treasury must keep separate
An accepted request records an intention to leave. A fulfilled request establishes the amount available for collection under the fund's process. A collected payment puts the settlement asset in the receiver's account. Treating those as one event overstates available liquidity and obscures where an exception belongs.
The ERC-7540 asynchronous vault standard formalises Pending, Claimable and Claimed states. It also leaves important economics to the implementation, including whether pending redemptions continue earning yield and whether their exchange rate remains variable. Its interface is useful evidence of status, rather than a complete statement of investor rights.
An institution integrating such a vault needs separate records for shares still invested, shares committed to an exit, assets available to claim and assets received. The share balance can fall before cash arrives. Unless accounting and treasury ingest the request record as well as token transfers, the investment may appear to disappear temporarily.
A gate allocates scarce liquidity
A redemption gate limits what can be paid during a period or under specified conditions. It can apply to the whole fund, an investor, a share class or another category established by the documents. A queue records requests awaiting processing. Either can exist without the other: a queue may simply bridge a routine processing delay, while a gate may defer part of every eligible request.
Allocation matters as much as the headline percentage. First-in-first-out treatment rewards earlier submission. Pro rata treatment shares available capacity across a defined batch. Priority for older unfilled requests changes the position of new requests. The terms should say whether investors must resubmit deferred amounts, whether partial requests retain priority and whether cancellation changes their place.
There is no universal queue order implied by the presence of a standard token interface. A system can batch requests technically while the legal allocation rule depends on class rights or administrator decisions. The investor needs evidence linking the request identifier to the applicable allocation, rather than inferring fairness from the visibility of a timestamp.
A partial payment example
Consider a hypothetical fund with $100 million of net assets, a gate allowing up to $5 million of redemptions in a dealing period and $8 million of eligible requests. Assume the documents allocate capacity pro rata, use a $1 share price and carry forward unpaid requests with their original status. An investor requesting $2 million receives a $1.25 million allocation, or one quarter of the available $5 million.
The remaining $750,000 is deferred. It is neither a fresh cash balance nor necessarily a fixed dollar receivable. If the documents keep deferred shares exposed to changes in net asset value, a later allocation can pay a different amount. If the shares are cancelled and a fixed payable created instead, the legal and economic position differs. Those choices need explicit treatment.
Now assume only $4 million is available after other permitted fund obligations. A stated $5 million gate does not itself create the missing $1 million. The documents must resolve whether actual liquidity reduces payment further, whether a facility can be drawn and who has discretion. The example is illustrative, not a description of a particular fund's terms.
The price date can move the exposure
An investor may request an exit on one day, receive a valuation on another and collect the proceeds later. The critical issue is the point at which exposure to the underlying portfolio ends. A fixed payment amount can leave the investor waiting for settlement without continuing portfolio exposure. A variable request can leave both timing and value uncertain.
That difference affects internal reporting. Portfolio risk should not infer exposure solely from ownership of transferable fund tokens, because a pending claim may preserve economic exposure after the token has been locked. Nor should it assume the latest published NAV is the amount payable. Our article on fund administration and NAV sets out why valuation evidence needs its own controls.
Suspension provisions deserve separate attention. A routine gate distributes limited exit capacity; a suspension can stop valuation or dealing under the conditions in the documents. The operational response should preserve the original instruction, notices received and any changed rights. Relabelling every delay as a queue hides a materially different decision.
What arrives at the end
Redemption proceeds might arrive as bank money, a stablecoin or an in-kind distribution of portfolio assets. Those are different outcomes even if a dashboard labels each one paid. A stablecoin settlement completes delivery of that token; converting it into bank money creates another transaction with another access route and timetable.
The reserve disclosures for USDC, for example, distinguish the assets backing the token. They do not make a token received in a fund redemption equivalent to an unrestricted balance in the investor's own bank account. The institution still needs an eligible account, a supported network and a usable route for the payment it ultimately intends to make.
For an in-kind exit, the receiving institution may need custody support and mandate eligibility for every distributed asset. A right to receive a diversified basket can be operationally unusable if the investor can custody only the fund share. Receiving an unsupported asset under stress is a different liquidity problem from waiting for cash.
Reconcile the exit, including the residue
A workable redemption record can explain the starting share quantity, allocation rule, valuation applied, fees deducted, unpaid quantity and asset actually delivered. Partial fills need a stable connection to the original request. Otherwise an administrator report, wallet balance and treasury forecast can each be individually correct while describing different pieces of the same exit.
The most revealing diligence exercise is to trace one request across two dealing periods. Ask the manager to demonstrate how a partial allocation is calculated, how the unpaid balance is reported and what changes if the receiving address becomes ineligible. Require the answer for the actual share class and settlement asset. A demonstration of a small, immediately fulfilled exit proves very little about a gated one.
The final measure is usable proceeds by the required time. A transparent queue helps investors estimate that outcome, but its value comes from the rights, valuation and funding process behind it. Institutions need to know which uncertainty remains at each step before treating a redemption as liquidity.