Header Background

Funds

Table of contents
Close

Funds

T-Suite Funds is infrastructure for fund administrators. It runs inside T-Suite as its own Funds tab, under the administrator’s brand.

Status: Live — access by request

Overview

A fund administrator uses Funds to serve one or many fund managers from one workspace. The administrator imports its numbers, and T-Suite enforces the fund’s rules, publishes the approved NAV on-chain, reconciles the on-chain register against the administrator’s register and the bank, and exports journals and evidence.

The administrator stays in charge. The fund administrator remains the NAV calculation agent and the transfer agent. Funds is software that imports, enforces, publishes, reconciles and exports what the administrator’s people approve. Libertum is not the administrator, transfer agent or issuer of any fund on the platform.

Who it’s for

  • Fund administrators serving one or many fund managers, and their staff: operator admins, preparers, approvers and auditors.
  • Fund managers and GPs onboarded by their administrator, who see only their own funds.
  • Fund accountants and transfer agents who prepare NAV packs, dealing and reconciliations.
  • Investors in those funds, who subscribe, redeem, pay and follow their commitments from their T-Suite investor dashboard.

Key capabilities

  • Multi-client operator mode. One administrator (the operator) serves many fund managers. Each manager sees only its own funds. Staff are invited by link, with access that can be limited to particular funds and given an expiry date.
  • Roles. Operator admin, preparer, approver and auditor on the administrator side; manager admin and manager viewer on the fund manager side. A person never approves their own request unless the fund uses one-person approval.
  • Approvals you configure. Each fund chooses one, two, three or four approvers (new funds start at one). 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. Lowering the number of approvers is itself an approval.
  • NAV packs. Import a NAV pack as CSV, XLSX or JSON. Validation checks share classes, currency, units against the register and the fund’s tolerance; a tolerance breach needs a written explanation. After approval, the NAV is published to the on-chain NAV registry with the pack’s SHA-256 hash in the transaction, and a Verify button recomputes the hash from the stored files. Restatements are supported and never move the live NAV backwards. If a NAV is overdue, dealing in that class pauses.
  • Dealing for open-ended funds. 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 come from investors in T-Suite, from the administrator’s TA system by CSV import, or over the API. Approved dealing runs mint or burn units on-chain and produce branded PDF contract notes.
  • Investor payments. Payment details per fund and per share class: a bank account or a USDC address, as an approved change. Investors see their payment reference and How to pay on the order screen and by email. USD classes can be paid from the investor’s USDC custodian balance after two-factor verification; a payment is marked paid only when the exact amount arrives.
  • Private markets for closed-ended funds. Commitments, closings, capital calls with branded PDF notices, payments, and distributions (return of capital, income, gains, recallable amounts, withholding), with ILPA-style capital accounts for each investor.
  • Three-way reconciliation. The on-chain register against the administrator’s register and the bank statement (camt.053, MT940 or CSV). Cash is matched on the exact amount. Breaks have owners, ageing and comments. Libby suggests matches with evidence, and a person confirms each one. A run ends with sign-off.
  • Journals. Balanced general-ledger journal export in CSV or XLSX, mapped to the fund’s chart of accounts, with approval and reversals. Entries post on the fund’s own time-zone day.
  • Enforcement. Freeze, unfreeze, forced transfer and wallet recovery on ERC-3643 share-class tokens, always approved by two people; a fund can also require the manager’s consent.
  • File drops and outbox. Upload files with saved column mappings, and schedule exports such as the register.
  • Tokens under fund control. Link a share class to a T-Suite ERC-3643 offering, and the fund runs it: investors subscribe and redeem through the fund at the next NAV, and the issuer-side shortcuts for that offering (direct buys, Update NAV, redemption windows, dividends, P2P listings) are refused with a note pointing to the fund.
  • Developer platform. A REST API described in 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. An API key created for another person stays pending until that person accepts it, and only they see the secret. AI assistants can read and draft; they never approve or move money.
  • Audit trail. A hash-chained access log (tampering shows as a break when the chain is verified) and a monthly evidence pack in XLSX for auditors.
  • Your brand. Notices, contract notes and portals carry the administrator’s branding.

Status and availability

Status: Live — access by request

  • Funds is not self-serve. A customer opens Settings → Manage Subscription, finds the Funds card and clicks Request access. Libertum reviews the request and grants the module; the administrator’s operator workspace is then created automatically, pre-filled from what T-Suite already knows about the firm.
  • If the module lapses, the operator workspace is suspended and nothing is deleted. It reopens with all its data when the module is active again.
  • Enforcement actions on share-class tokens run on ERC-3643 tokens on EVM networks, including Base, Ethereum, Polygon and Arbitrum.
  • Funds is software. It does not make Libertum the fund’s administrator, transfer agent, manager or issuer, and it gives no one a licence. Each administrator and fund needs its own authorisations where it operates. See Licences.

Pricing

USD 1,000/month for the operator, with unlimited funds, plus a distribution fee agreed with each administrator. The standard platform distribution rate does not apply to Funds dealing. Access is by request. See the plans page.

Watch the demo

Learn more