Arkar Fund System

One platform for the entire fund lifecycle

Eight modules on one database and one audit trail. None of them exports a spreadsheet to the next.

Module 01

Funds, classes and series in the right hierarchy

CVM Resolution 175 split the fund into classes and subclasses. The platform was born in that hierarchy — it isn't an extra field bolted onto an old record.

  • Fund → class → subclass → series, each level with its own net assets and bylaws
  • FIP, FIP-IE, FIDC, FII and FIA in one record, each with its own rules
  • Service-provider records synced with CVM open data

Module 02

One record per investor, not one per fund

The same investor joins several of your funds. The record is single; what changes is the link to each fund's liabilities.

  • Qualification (retail, qualified, professional) with a change history
  • Versioned KYC documents, with validity and expiry alerts
  • Personal data isolated per tenant, access denied by default

Module 03

The unit price closes with validation, not faith

The engine strikes the price, checks the portfolio against custody, and blocks publication while any validation fails.

  • Fee accruals, mark-to-market and liability reconciliation on every strike
  • Dual approval required before a unit price is published
  • Reprocessing keeps history — the prior version never disappears

Module 04

The distribution network inside the same liabilities

Subscription, payment, amortization and redemption recorded where the unit price is computed — no parallel control spreadsheet.

  • Distributors, allocations and commissions by class and series
  • Movement statement checked against the fund's liabilities
  • Holders can query their own position, within their own scope

Module 05

An audit trail that doesn't rely on anyone remembering

The record is written by the database, not the application. There is no write path that bypasses the trail.

  • Who, when, what and under which permission — including denied actions
  • AI agents log exactly like humans, with the scope they used
  • Immutable log, 5-year retention

Module 06

A repository the agents can actually read

Bylaws, minutes, valuation reports and contracts versioned in one place — and available for assisted lookup, within the asker's scope.

  • Versioning with a record of who uploaded what, and when
  • Scope by fund and by tenant, applied before the search runs
  • Agent-assisted reading, always citing the source document

Module 07

Legally binding signatures, in the same flow

The document leaves the repository, circulates, gets signed and comes back archived — without leaving the platform or becoming an e-mail thread.

  • Signature by OTP or ICP-Brasil certificate, per the act's requirement
  • Automatic reminders for whoever hasn't signed yet
  • Signature receipt and trail attached to the source document

Module 08

Non-resident filings generated from the real data

The CMN 4.373 XML comes from the same data that struck the unit price. Nothing is re-keyed, and the calendar warns ahead of the deadline.

  • Monthly and semiannual filings in the CVM layout, validated before submission
  • Several INRs consolidated into one file when the structure requires it
  • Status pipeline — generated, transmitted, accepted — with a date for each step

One platform, four operating profiles

What changes isn't the product — it's what you need from it. Pick the role your firm plays.

Start with your most complex fund

If Arkar handles that one, it handles the rest of your book. We'll walk the platform through a structure like yours.

Book a demoTalk to the team

Guided walkthrough · 30 minutes · No commitment