What does a transfer agent do for a tokenized fund?
The register still needs an accountable owner. On-chain does not mean unowned.
A transfer agent maintains the official register of who owns what, processes subscriptions and redemptions, and is accountable to the fund and its regulator for the accuracy of that record. Tokenizing the units does not remove the role. It changes where the record sits and adds a reconciliation obligation between the chain and the book.
What does a transfer agent do for a tokenized fund?
It keeps the official register of holders and processes the events that change it: subscriptions, redemptions, transfers, distributions and corporate actions. It is accountable, under the fund documentation and to the extent national law provides, for the accuracy of that record. In a tokenized fund it does the same work against a ledger.
The role is legal rather than technical, which is why software does not absorb it. A ledger can hold a record and validate a transfer. It cannot be accountable for whether the record is correct, respond to a court-ordered transfer, certify a holder list to an auditor, or decide what happens when an investor loses a key.
So the first question about any tokenized fund is who that party is. If the documentation names no accountable owner of the register, that is a gap rather than an elegant design, and it will surface at the first reconciliation break or the first compelled transfer.
Does on-chain issuance remove the need for a transfer agent?
No. It changes the work and removes some of it, and it does not remove the accountability. What genuinely disappears is a category of manual processing: transfer instructions routed between parties, register updates applied by hand, and periodic reconciliation across several copies of the same list.
What remains: certifying the holder list at each valuation date, handling corporate actions, operating the whitelist that eligibility enforcement depends on, managing recovery when access is lost, executing compelled transfers on proper legal instruction, and answering to the depositary, the auditor and the regulator for the record.
Some structures perform the role in-house rather than appointing a third party, where national law permits. That is a resourcing decision, not an abolition of the function, and supervisors treat it as such: the obligations attach to whoever performs it.
The claim that tokenization removes intermediaries is best read narrowly. It removes reconciliation intermediation between copies of a register. It does not remove the parties whose duties are legal — depositary, administrator, transfer agent — because their duties were never about copying data.
Which record is the official register — the chain or the book?
It depends on the domicile, and the fund documentation must say. Where national law recognises a distributed ledger as the register of a security, the ledger is the official register and the administrator’s book is an accounting record derived from it. Where it does not, an off-chain register remains legally authoritative and the ledger operates alongside it.
Both arrangements work in practice. What does not work is silence: if the two records disagree tomorrow, someone must be able to say in one sentence which one determines legal ownership and under which law. Allocators ask this, and a structure that cannot answer has not resolved its most basic legal question.
Germany created crypto-securities registers with a supervised registrar role for exactly this purpose. France recognises securities registered in a blockchain under its 2017 decree. Luxembourg amended its financial-instruments definition alongside implementing the pilot regime. Other member states have not legislated, which is a domicile-selection input rather than a technology problem. Read which member states are furthest ahead.
How are the two reconciled, and how often?
At every NAV date, and continuously in between where the process supports it. The reconciliation is narrower than conventional fund reconciliation because there is one shared record rather than several copies, but it is not optional and it must be evidenced.
- Holder list on-chain against subscriptions, redemptions and transfers processed in the period.
- Units in issue on-chain against units in issue in the administrator’s books at the strike.
- Whitelist membership against current verification, jurisdiction and sanctions status for each holder.
- Failed or reverted transfers, with the reason recorded.
- Any use of agent powers — freeze, forced transfer, recovery — with the instruction and authorisation retained.
- A dated sign-off by the accountable party, retained for audit.
Mismatches between units in issue and the ledger are the most common break in tokenized funds, and they are cheapest to catch at the strike rather than after a distribution has been calculated. The administrator should read units in issue from the register under a documented method rather than from a spreadsheet maintained in parallel.
Who is accountable when they diverge?
The named transfer agent or registrar, under the fund documentation, with the depositary’s oversight duties sitting above it. Technology providers are accountable for their software under contract; they are not accountable for the register unless the documentation says they are, and it generally should not.
The procedure matters as much as the name. Who investigates a break, who authorises a correction to the on-chain record, how the correction is evidenced, whether the depositary is notified, and what is reported to investors if a distribution was affected. Funds that have operated for any length of time answer this immediately, because they have used the procedure.
There is also a dependency question that is rarely disclosed. If one provider maintains the register software, can the register be exported and operated independently should that provider fail? Ask before appointment, in writing. Provider concentration is the least-discussed risk in tokenized funds.
Read what four years of running this actually involved and question three of the allocator frame.
How does this differ between the EU and the US?
In the US, transfer agency is a regulated activity in its own right: transfer agents register with the SEC and are subject to specific record-keeping, turnaround, safeguarding and reporting rules. That gives tokenized US structures a ready-made accountable party with an established rulebook, and it is why an SEC-registered transfer agent appears underneath much of the tokenized fund and Treasury market.
In the EU, there is no equivalent single transfer-agent authorisation. The function is discharged under the fund’s regime — the AIFM or management company’s obligations, the depositary’s oversight, and national requirements where they exist — and by whichever party the documentation appoints. Germany’s crypto-securities registrar is the closest thing to a dedicated supervised role, and it applies to crypto securities rather than to fund units generally.
| European Union | United States | |
|---|---|---|
| Dedicated regime for the role | No single EU authorisation; obligations flow through the fund regime and national law | SEC transfer-agent registration with its own rulebook |
| Who is accountable | The party appointed in fund documentation, with depositary oversight | The registered transfer agent |
| Register recognition | Varies by member state | State law and transfer-agent regulation |
| Practical effect on tokenized funds | Accountability must be constructed in the documentation | Accountability is provided by an existing regulated role |
The practical consequence for a European manager: the accountable owner of the register has to be constructed deliberately rather than inherited from a licensing category. That is more work at structuring and produces the same outcome when done properly. Read the EU regulatory stack.
The cluster hub, including who keeps the register.
The whitelist the transfer agent operates.
Custody sits alongside, not instead of, the register.
- Directive 2014/65/EU (MiFID II); Regulation (EU) 2023/1114 (MiCA); Directive 2011/61/EU (AIFMD) — EU Official Journal.
- COSIMO Digital regulatory authorisations, described as of 28 July 2026. Pending authorisations are not effective until granted.
- German Act on Electronic Securities (eWpG) crypto-securities registrar role; French decree of 2017 on securities registered in a blockchain; Luxembourg law of 15 March 2023.
- US Securities and Exchange Commission transfer-agent registration and rules.
This page is for informational purposes only. Nothing in it is an offer to sell, or a solicitation of an offer to buy, any security, and nothing here is investment, legal, tax, or financial advice. Regulatory authorisations are described as of the date stated; pending authorisations are not effective until granted.
← All Learn articles