What Happens When Investors Redeem a Tokenized Fund?

An investor submits a redemption request on Friday afternoon. The transaction appears onchain immediately, while the fund still needs to price the request, establish how much it can fulfill, and arrange payment.
For a tokenized fund holding assets that settle through traditional systems, those steps can run on different schedules. The investor experience depends on how clearly the platform connects them and communicates progress.
A request moves through several states
Tokenized funds can support different redemption models. Some offer immediate execution against available liquidity; others process requests in batches or at specified dealing times. The ERC-7540 standard explicitly supports asynchronous redemptions, separating a pending request from one whose assets are ready to claim.
That distinction gives the platform something useful to explain. An investor should be able to distinguish a request awaiting processing from an approved redemption awaiting payment. Each status represents a different obligation for the operator.
Consider a fund with requests to redeem 100,000 shares. The amount payable depends on the applicable dealing price and any adjustments specified in the fund’s terms. If fulfillment is partial, the system also needs to preserve the remaining request and explain how the allocation was determined.
The operator needs a consistent record connecting the original request, the shares processed, the price applied, and the assets delivered.
Available liquidity needs its own calculation
A fund’s portfolio value and the amount it can pay out today answer different questions. Cash may already be committed to other obligations. Asset-sale proceeds may still be settling, and liquidity buffers may need to remain in place.
For an upcoming redemption cycle, the administrator needs to bring those records together under the fund’s rules. Expected proceeds should remain distinguishable from funds already available, with changes reflected as settlement progresses.
This also helps the team explain delays accurately. A request waiting for the next dealing window requires a different response from one affected by an unsettled asset sale. Clear internal records make those distinctions visible to investor support.
Connecting fund records with onchain requests
Space and Time can support this workflow by bringing indexed redemption activity together with supplied valuation, cash, and settlement records. An administrator could use that foundation to calculate the amount due for a processing cycle and reconcile fulfilled requests against payments.
For supported queries, Proof of SQL makes the computation independently verifiable against the committed data. The fund’s terms and authorized administrators still determine pricing and fulfillment; the calculation has a checkable basis.
As participation grows, this infrastructure can help a fund process more requests without multiplying manual handoffs. Investors get a clearer account of their exit, and operators can identify what remains outstanding before the next cycle begins.