For fund administrators and fund accountants

Tokenized fund administration: what changes for administrators and fund accountants

Tokenized fund administration is running a fund’s NAV, dealing, register and books when its units are tokens on a blockchain. The administrator stays the NAV calculation agent and the transfer agent. Software such as T-Suite Funds imports the administrator’s numbers, publishes the approved NAV on-chain, mints and burns units, reconciles the chain against the books and exports journals and evidence.

Last updated:

What changes for a fund administrator when units are tokenized?

Less than people expect. The fund’s legal structure, its documents and your role stay the same: you still calculate the NAV, keep the register and process dealing. What changes is where the register lives and how it is evidenced. Units become tokens, so the share register can be read on-chain by anyone entitled to see it, and every issue, redemption and transfer leaves a record that cannot be edited afterwards.

That adds three jobs to the month: publishing the approved NAV where token holders can verify it, keeping the on-chain register, your own register and the bank in agreement, and posting the result to the general ledger. T-Suite Funds is built around those three jobs.

How does dealing work for tokenized open-ended funds?

You set dealing calendars and cut-offs, forward pricing at the next NAV, minimums and investor eligibility per share class, redemption gates per investor and per fund (scaled pro rata and carried forward) and lock-ups. Instructions arrive from investors in T-Suite, from your TA system by CSV import, or over the API. After the cut-off and the NAV, an approved dealing run applies fees and gates, mints or burns units on-chain and produces branded PDF contract notes.

What about closed-ended and private-market funds?

Commitments, closings, capital calls with branded PDF notices, payments and distributions (return of capital, income, gains, recallable amounts and withholding) are run in the same workspace, with ILPA-style capital accounts for each investor.

How does three-way reconciliation work?

  1. 01

    Load the inputs

    Upload your register and the bank statement (camt.053, MT940 or CSV) and set the as-of date. On-chain balances are read at a pinned block.

  2. 02

    Match

    Cash is matched on the exact amount. Libby, Libertum’s AI assistant, suggests matches with its evidence; a person confirms each one.

  3. 03

    Work the breaks

    Breaks have owners, ageing and comments, so open items are visible until they are cleared.

  4. 04

    Sign off

    The run is submitted for sign-off; when an approver signs off, it locks.

How are journals produced for the general ledger?

Map the fund’s chart of accounts once (bank, subscriptions in advance, capital per class, fee income, redemptions payable). Then generate a journal batch for a period: debits equal credits per currency, with control totals and a hash. After approval, export it as CSV or XLSX for your accounting system and mark it posted. A batch can be reversed with a reason, and the reversal is approved too. Entries post on the fund’s own time-zone day.

What evidence do auditors get?

Every action is written to a hash-chained access log, so tampering shows as a break when the chain is verified. Each month you can generate a control evidence pack in XLSX with a summary, approvals, reconciliations, the access log, configuration changes, API keys and webhooks, plus its file hash and the chain status.

Who does what in T-Suite Funds?

RoleTypical personWhat they do
Operator admin Head of fund administration Sets up managers, funds, share classes, staff, branding and calendars
Preparer Fund accountant or TA officer Imports NAV packs, prepares dealing runs, capital calls, reconciliations and journals
Approver Senior fund accountant or controller Approves NAVs, dealing runs, reconciliations and journal batches
Auditor Internal or external auditor Reads and audits the funds named in the invitation; access always has an expiry date
Manager admin / viewer Fund manager or GP Sees only their own funds; can request, not make, changes to terms

Freeze, forced transfer and wallet recovery on ERC-3643 share-class tokens always need two people, and a fund can also require the manager’s consent.

Does it fit with the systems we already use?

Yes, by design it sits next to them. NAV packs, registers and dealing instructions come in as files (with saved column mappings) or over a REST API described in OpenAPI 3.1, with scoped API keys, signed webhooks, a TypeScript SDK, the tsuite CLI and an MCP server for AI assistants. Journals and registers go out as CSV or XLSX, and exports can be scheduled. AI assistants can read and draft; they never approve or move money.

What does it cost?

USD 1,000 per month for the operator, with unlimited funds, plus a distribution fee agreed with each administrator. Access is by request: Libertum reviews the request and then sets up your operator workspace.

Libertum, S.A. de C.V. holds an El Salvador DASP licence from the CNAD, registry entry PSAD-0094. It does not authorise issuance and does not cover structuring, promotion or management of investment products. See Libertum’s licences.

Watch T-Suite Funds end to end

The full walkthrough covers operator setup, a NAV pack from import to on-chain publication, a dealing run, three-way reconciliation and journals.

Transcript: Funds demo

Fund administration still runs on spreadsheets, email threads, transfer-agent exports and bank statements in PDF.

Every NAV, every dealing day and every reconciliation passes through hands, files and inboxes, with nothing proving who checked what.

T-Suite Funds gives fund administrators one place to run it all, on-chain and under their own brand. The administrator stays the NAV calculation agent and the transfer agent. T-Suite imports, enforces, publishes and reconciles.

Funds is available on request. A firm opens Manage Subscription, finds the Funds card at one thousand US dollars a month, and clicks Request access.

They tell us about the firm: its name, website, country, and the funds it runs.

The request is sent, and the Libertum team is told straight away.

Libertum agrees the terms with you, including the distribution fee, and grants the module. Your operator workspace is created automatically, named from what T-Suite already knows about your firm.

The Funds tab is the administrator's home: every client fund manager, every fund and share class, and the last NAV published for each.

Funds can be open-ended or closed-ended, in any currency, each with its own NAV frequency.

Invite your team with clear roles: preparers do the work, approvers check it, and auditors only read. Access can be limited to one fund, and auditors always get an expiry date.

Each fund chooses how many people approve its work: one person, or two, three or four. Freezes, forced transfers and wallet recoveries always need two people.

Investor payment details live with the fund: a bank account and a USDC address, with optional overrides for each share class. Changes take effect only once approved.

Calendars set the business days and holidays behind every NAV deadline and dealing date.

And your branding appears on fund pages, contract notes, notices and emails.

Share classes can be linked to a token issued on T-Suite. From then on, that token is managed by the fund.

On the issuer's side, the offering shows that it is managed in Funds.

And investors see Subscribe through the fund instead of a buy button, so nobody can trade around the fund's rules.

Now, the NAV. The administrator calculates it. T-Suite checks it, gets it approved, and publishes it.

The preparer imports the administrator's file. T-Suite checks every class, the currency, the units against the register, and the move since the last NAV. Here, class B moved more than the five percent tolerance.

A breach can't be waved through: it needs a written reason. Then the pack goes for approval, with a note for the approver.

The pack gets a fingerprint of its lines and files, and waits for approval under the fund's setting.

The approver sees exactly what they are signing, with the reasons and the payload hash. On a one-person fund, the preparer approves it themselves, and that is recorded too.

Once approved, each class's NAV is published on-chain with the pack's fingerprint, and anyone can recompute it to verify the record.

Dealing, for open-ended funds.

It starts with the dealing terms: cut-off times, notice, settlement, fees, minimum holdings, lock-ups and redemption gates. Changes are approved like everything else.

Investors subscribe from the offering page, by amount or by units. Orders are forward priced at the NAV of the dealing date, which is not known yet.

The order is received with its dealing date and a payment reference, and exactly how to pay: the fund's bank account or its USDC address.

The same details stay in the investor's dashboard, under My fund orders, and arrive by email. Investors can also pay straight from their USDC balance, after the usual security checks, and the order is marked paid only when the exact amount arrives.

Orders from the administrator's own transfer-agent system come in by file or through the API, next to orders placed on T-Suite. Cash is marked received before the cut-off.

After the cut-off and the NAV, the preparer builds the dealing run: units for every order, fees, and any gate applied pro rata.

Once the run is approved, units are minted and burned on-chain, and every investor gets a contract note.

Closed-ended funds work through commitments.

Investors commit capital, and a closing issues units in proportion to each commitment.

Capital calls are split across investors automatically, with a notice for each, and payments tracked line by line. Distributions break down into return of capital, income and gains, with withholding.

Capital accounts follow the ILPA layout: committed, contributed, unfunded and distributed, for any period, and export to CSV.

Investors see the same capital account, every call and every distribution notice, in their own dashboard.

Then, reconciliation.

Reconciliation compares three records: the on-chain register, the administrator's register and the bank statement. Each break has an age and an owner.

Payments match only for the exact amount. A short payment becomes a break, never a silent match, and an unknown payment waits for a person to pair it.

Libby, the AI assistant, can suggest pairings with its reasons, but never applies them. A person confirms, and the reconciliation is signed off through approval.

Journals map every event to the administrator's chart of accounts, as balanced batches for the general ledger, exported once approved.

Enforcement covers freezes, forced transfers and wallet recoveries. Each needs a written reason and a second person, always.

Any file from the administrator's system can be dropped in, with saved column mappings, and an outbox prepares register, dealing, capital-account and journal files on a schedule.

Integrations connect the administrator's own systems through the Funds API: scoped keys, limited to chosen funds, each acting for a named person.

That person must accept a key before it works, because everything it does is attributed to them.

Signed webhooks push events to your systems, with retries. Developers also get a software kit, a command line, and an AI assistant connector that can read and prepare, but never approve.

Every change, decision and access is in a tamper-evident access log. Verify the chain at any time, and build an evidence pack for the auditors in one click.

And investors see their fund holdings at the latest published NAV, next to their orders and contract notes.

T-Suite Funds: run every fund you administer in one place, on-chain, under your brand. One thousand US dollars a month, with unlimited funds. Request access in T-Suite, or book a demo at libertum dot io.

Fund operations fit check

See what T-Suite Funds would run for your funds

Three quick choices. The capabilities that match appear on the right as you go, and you can ask for a walkthrough with your answers attached.

Your role
Your funds
What you want to run on T-Suite Funds

Pick all that apply.

How many funds?

Fund administration FAQ

Does the administrator stay the transfer agent and NAV agent?

Yes. In T-Suite Funds the administrator remains the NAV calculation agent and the transfer agent. Libertum is not the administrator, transfer agent, manager or issuer of any fund on the platform.

Can we keep our fund accounting system?

Yes. T-Suite Funds imports NAV packs and registers from files or the API and exports balanced journals in CSV or XLSX mapped to the fund’s chart of accounts, so your accounting system stays the book of record.

Which bank statement formats does reconciliation accept?

camt.053, MT940 and CSV.

How do token holders know the NAV is the one we approved?

The on-chain NAV publication carries the SHA-256 hash of the approved pack, and the Verify button recomputes it from the stored files, so anyone can compare the two.

Can an AI assistant approve a NAV or a dealing run?

No. Libby and assistants connected over MCP can read and draft. Approvals and anything that moves money are done by people.

Which blockchains are supported?

Share classes are linked to ERC-3643 tokens on EVM networks, including Base, Ethereum, Polygon and Arbitrum.

Does T-Suite Funds give us a licence?

No. It is software. Each administrator and fund needs its own authorisations where it operates.

Run your next NAV cycle on T-Suite Funds

See a NAV pack go from import to on-chain publication, a dealing run and a three-way reconciliation, with your funds in mind.

Try the fit check