T-Suite Funds
White-label infrastructure for fund administrators running tokenized funds. You remain the NAV calculation agent and the transfer agent. T-Suite imports your numbers, enforces your rules, publishes them on-chain, reconciles and exports.
Fund administration still runs on spreadsheets, emails, transfer-agent exports and bank PDFs. T-Suite Funds puts it all in one place, on-chain, under your brand.
See every client manager, fund and share class, with the last NAV published for each.
Each fund chooses one to four people to approve its work, and every sensitive step waits for them.
Import the administrator's NAV file. Every line is checked, and breaches need a written reason.
Once approved, the NAV is published on-chain with the pack's fingerprint.
Investors subscribe through the fund, forward priced at the next NAV.
They get a payment reference and exactly how to pay: by bank, in USDC, or straight from their balance.
Dealing runs apply fees and gates, mint the units, and send every contract note.
Closed-ended funds get commitments, capital calls and distributions.
Three-way reconciliation matches exact amounts only, so a short payment is never a silent match.
Everything is in a tamper-evident log, with an evidence pack for your auditors.
T-Suite Funds. One thousand US dollars a month, with unlimited funds. Request access at libertum dot io.
Who it's for
Pick a role to see what T-Suite Funds does for you. The capabilities that matter most are highlighted below.
Fund Administrator
Onboard your managers, staff and funds in operator mode. You stay the NAV calculation agent and the transfer agent. T-Suite enforces, publishes, reconciles and exports what you approve.
Most relevant for you
Capabilities
One administrator serves many fund managers. Each manager sees only its own funds. Invite staff by link, with access scoped to funds and an expiry date.
Each fund chooses one, two, three or four approvers. In a one-person fund the preparer can approve their own work, and it is still logged. Freeze, forced transfer and wallet recovery always need two people.
Calendars and cut-offs, forward pricing at the next NAV, minimums and investor eligibility per share class, redemption gates per investor and per fund (pro rata, carried forward) and lock-ups. Approved runs mint or burn units on-chain and produce PDF contract notes.
Set payment details per fund and class: a bank account or a USDC address. Investors see their reference and how to pay on the order screen and by email. USD classes can be paid from the investor's USDC custodian balance.
For closed-ended funds: commitments, closings, capital calls with PDF notices, payments and distributions (return of capital, income, gains, recallable, withholding), with ILPA-style capital accounts.
The on-chain register against the administrator's register and the bank (camt.053, MT940 or CSV). Exact-amount matching, breaks with owners and ageing, AI match suggestions that a person confirms, and sign-off.
Balanced general-ledger journal export in CSV or XLSX, with reversals. File drops with column mapping, and scheduled exports.
Link a share class to a T-Suite token and the fund manages it, with no direct buys around dealing. Freeze, forced transfer and recovery are enforced on ERC-3643 tokens on Base, Ethereum, Polygon, Arbitrum and other EVM networks.
REST API (OpenAPI 3.1), scoped API keys and OAuth client credentials, idempotent writes, signed webhooks with replay, a TypeScript SDK, the tsuite CLI and an MCP server for AI assistants.
A hash-chained access log that makes tampering evident, and an evidence pack in XLSX for your auditors.
Notices, contract notes and portals carry the operator's branding, not ours.
How it works
Tell us about your firm and your funds. Access is by request, not self-serve.
Set up your operator, invite your team and the fund managers you serve, and configure share classes, approvers and dealing rules.
Load your latest NAV pack and your register by file or API. T-Suite validates them before anything is published.
Run dealing, reconcile the on-chain register with yours and the bank, and export journals and evidence for your auditors.
See it in action
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.
Crypto funds and crypto ETFs
Create a fund as a crypto fund or crypto ETF from the start. T-Suite reads your sources at valuation time, proposes the NAV, and stops when anything looks wrong.
Crypto funds and ETFs trade around the clock, yet most still value their holdings by hand, in spreadsheets.
In T-Suite Funds, you create a crypto fund or crypto ETF from the start.
Declare the assets it holds, with target weights and bands. T-Suite values only what you declare.
You choose where the data comes from: your own valuation API, with your exchange, custodian or price provider behind it. Your keys stay with you.
Your Libertum custodian wallet is read automatically, straight from the chain.
At your valuation time, T-Suite reads every source, prices each asset and proposes the NAV against the last one.
If something looks wrong, it stops. An undeclared asset, a stale price or a source it cannot read means no NAV is made.
Every NAV goes to approval with the full breakdown and its fingerprint, and the person who prepared it can never approve it.
If a holder must be stopped, freeze their tokens, with a written reason and always two people.
A forced transfer or wallet recovery also needs two people, and the manager's consent when the fund requires it.
Frozen tokens cannot be redeemed, and only verified, eligible investors can subscribe.
Withdrawals from the custodian wallet need a one-time code, a saved address and sanctions screening.
Every step is in a tamper-evident log you can verify.
Crypto funds on T-Suite: valued automatically, controlled by people. Request access at libertum dot io.
Developer platform
One OpenAPI 3.1 specification behind all four. Scoped API keys or OAuth client credentials, idempotent writes, and signed webhooks you can replay. Approvals stay with people in T-Suite.
A REST API described in OpenAPI 3.1. Authenticate with a scoped API key or OAuth client credentials. Writes are idempotent.
curl -H "Authorization: Bearer tsk_live_…" \
https://tsuitenew-api.libertum.io/marketplace/v1/api/funds/v1/fundsPricing
T-Suite Funds
USD 1,000per month
Founding Fund Council
Run a fund administration or fund management business? Join the fund leaders shaping how tokenised funds really work, with free Fund module access for the council period.
FAQ
Fund tokenization records fund units or interests as tokens on a blockchain, while the fund keeps its legal structure, its administrator and its transfer agent. With T-Suite Funds, a share class can be linked to an ERC-3643 token: approved dealing mints and burns units on-chain, and each approved NAV is published on-chain with its pack's SHA-256 hash.
You are. The fund administrator remains the NAV calculation agent and the transfer agent. T-Suite is software that imports, enforces, publishes, reconciles and exports. Libertum is not the fund's administrator, transfer agent or issuer.
Fund administrators serving one or many fund managers, and the fund accountants, transfer agents, managers and GPs who work with them.
Your team imports a NAV pack (CSV, XLSX or JSON). T-Suite validates it, the fund's approvers approve it, and the NAV is published to the NAV registry with the pack's SHA-256 hash in the transaction. Anyone can check that hash against the pack.
If a NAV is overdue, dealing for that fund pauses automatically until a current NAV is published.
Each fund chooses one, two, three or four approvers. In a one-person fund the preparer can approve their own work, and it is still logged. Freeze, forced transfer and wallet recovery always need two people.
Yes. Instructions can come from your TA system by CSV import or over the API, file drops support column mapping, and balanced journals export to CSV or XLSX for your general ledger.
Yes: commitments, closings, capital calls with PDF notices, payments, distributions and ILPA-style capital accounts.
ERC-3643 tokens on EVM networks, including Base, Ethereum, Polygon and Arbitrum.
No. The MCP server lets assistants read and draft. Approvals and anything that moves money stay with people in T-Suite.
USD 1,000 per month for unlimited funds. A distribution fee is agreed with each administrator. Access is by request.
Yes. You create the fund as a crypto fund or crypto ETF and declare the assets it holds, with target weights and bands. T-Suite values only what you declare, reading prices from your own valuation API and your Libertum custodian wallet on-chain.
From your own valuation API, with your exchange, custodian or price provider behind it, so your keys stay with you. The Libertum custodian wallet is read straight from the chain. If an asset is undeclared, a price is stale or a source cannot be read, no NAV is made.
Every NAV goes to approval with the full breakdown and its fingerprint, and the person who prepared it can never approve it. Freezes need a written reason and always two people, and every step is in a tamper-evident audit log.
Request access and we will arrange a walkthrough with your team.