Fund Tokenization
Fund units issued and redeemed against NAV, with subscription windows, share classes, fees and gates modelled explicitly.
Definition
Fund tokenization represents units in a collective investment vehicle as transfer-restricted tokens. Units are issued and redeemed against a net asset value struck on a schedule, and the register replaces the transfer agent’s book.
What it solves
- Transfer agency costRegister maintenance, subscription processing and redemption handling are a material recurring cost, most of it manual.
- Subscription frictionPaper subscription documents and manual eligibility checks are the reason onboarding takes weeks.
- Share-class administrationMultiple classes with different fees and preferences are error-prone to maintain by hand.
How it works
- NAV is struck on a cadenceThe administrator values the portfolio and publishes a NAV per unit.
- Subscriptions are dealt at the next NAVMoney received before a cut-off is allocated units at the following valuation point.
- Redemptions are dealt in the same wayUnits are burned and the holder is paid at the applicable NAV, subject to notice and any gate.
- Fees accrue and are chargedManagement and performance fees are recognised as they arise.
Architecture
An offering engine holding the subscription book with per-class terms; a valuation record providing NAV with a stated methodology; a register with per-class positions; and a redemption engine applying notice periods and gates before anything is burned.
Tokenization lifecycle
- Fund establishedVehicle, administrator, depositary, auditor and investment manager appointed.
- Classes configuredFees, preferences, seniority and minimums per class.
- DealingSubscription and redemption cycles against NAV.
- ReportingNAV, holdings, performance and statements.
- Wind-downRealisation, final distribution and closure.
Supported token model
Permissioned fungible token, one series per share class. Units within a class are interchangeable; units across classes are not, because they carry different economics. Modelling classes as separate series keeps the difference in the register rather than in a spreadsheet.
Asset requirements
What must be true before this can responsibly be tokenized at all.
- A regulated or exempt fund vehicle appropriate to the strategy and investor base.
- An administrator responsible for NAV, with a documented valuation policy.
- A depositary or custodian where the structure requires one.
- Dealing terms: frequency, cut-off, notice, and any gate or side-pocket mechanism.
Compliance considerations
- Marketing restrictions differ sharply by jurisdiction and are the most common source of enforcement.
- Investor eligibility per class, encoded as policy and evaluated on every subscription and transfer.
- AML obligations sit with the fund and its administrator; the platform records the decision and its evidence.
Investor workflow
- Verify and be assessed for eligibility against the class.
- Subscribe before the dealing cut-off and fund by reference.
- Receive units at the next NAV.
- Redeem on notice, subject to any gate.
Issuer workflow
- Configure classes, fees and dealing terms.
- Publish policy and open subscriptions.
- Run each dealing cycle: strike NAV, allocate, issue or redeem.
- Charge fees and report to holders.
Payments
Subscription money is held as an investor liability until it is dealt. Redemption proceeds become a payable at the moment units are burned. Neither is ever recognised as fund revenue, because it is not.
Lifecycle servicing
Fund servicing is a cycle rather than an event: value, deal, report, repeat. An oversubscribed close is accepted and scaled back deterministically rather than turned away, so the manager keeps the information about demand.
Secondary transfer
Most funds restrict transfers to eligible investors with manager consent. Both constraints are expressible as policy, and the manager’s consent is an approval step rather than an email.
Risks
Named plainly. An instrument whose risks are only in a footnote has been mis-sold before it has been issued.
- Valuation riskNAV is only as good as the valuation policy, and illiquid holdings make it a judgement.
- Liquidity mismatchOffering monthly redemption against annually-realisable assets is the classic fund failure, and it fails all at once.
- Fee complexityPerformance fees with hurdles and high-water marks are easy to compute wrongly and hard to correct afterwards.
- Gate reputational costGates protect remaining holders and are read as distress. Both are true.
How we support it
- Per-class terms and per-class positions on the register.
- Oversubscription resolved by a deterministic, reproducible scale-back so an investor’s complaint can be checked rather than argued about.
- Allocations rounded down to whole units with the residual returned, because a fraction of a unit cannot be issued and the difference is the investor’s money.
Questions
Does this replace the fund administrator?
No. The administrator still strikes NAV and owns the valuation policy. The platform replaces the register and the dealing paperwork.
Can multiple share classes have different fees?
Yes — classes carry their own price, fees, preferred return and voting rights, and positions are held per class.
How are gates handled?
As an explicit refusal at the redemption eligibility check, with the reason recorded, rather than as an unexplained delay.
Next steps
Bring an instrument you are actually considering. Structuring something real is the only way to judge whether the model fits.