How it works
One data model. Every workflow reads and writes to it.
No export. No import. No reconciliation step between modules. One ledger holds the trade, from the moment it's placed to the moment it shows up on an investor's statement.
The single ledger
A trade, a NAV, a reconciliation, a statement, one row, four views
Most fund-ops stacks are three or four systems stitched together with exports and overnight batch jobs. A trade lands in the OMS, gets re-keyed into the accounting system, gets re-keyed again into the reporting layer. Every hop is a place for the numbers to quietly disagree.
Here, a trade, a position, a NAV component, a reconciliation line and an investor-visible balance are the same record, viewed differently by each workflow. Nothing re-entered. Nothing exported and re-imported. Nothing to reconcile between modules. There is only one module.
Real-time vs. batch, stated precisely
What updates the instant it happens, and what runs on a schedule
Real-time
- Order and execution status
- Positions and exposure
- Cash balances by currency and account
- Reconciliation breaks as they open
Scheduled (per fund's own calendar)
- NAV strikes
- Fee and expense accruals
- Investor statements and regulatory filings
- Performance and risk report generation
The distinction is deliberate: a NAV is a governed event with a specific strike time, not a number that should shift underfoot. Everything feeding into it, though, is current to the second.
Cloud architecture
Multi-tenant by default. Dedicated where it matters.
Multi-tenant / dedicated
Starter, Pro and Ultimate run multi-tenant with logical isolation per account. Enterprise accounts can use a private network or an on-premises deployment.
Disaster recovery
Cross-region replication with defined RPO/RTO targets, see exact figures on the Security page.
Uptime
99.9% uptime target, with status published in real time.
API & extensibility
Keep your OMS. Keep your warehouse. Add this underneath.
Not every desk wants to replace what already works. Positions, trades, NAV, reconciliation status and investor data, all exposed over API. It sits alongside an existing OMS/EMS or data warehouse. It doesn't have to replace one.
See Integrations & APIs
One trade, start to finish
From execution to an investor-visible balance
A real sequence, second by second. The one place on this site where numbered steps earn their keep.
-
1
09:31:02
Trade execution
An order fills on the connected venue. The fill lands on the ledger immediately, tagged to its fund, strategy and currency.
-
2
09:31:04
Settlement tracking begins
Expected settlement date and counterparty details attach automatically from the venue's confirmation.
-
3
09:31:04
Position updates
The fund's position and exposure figures reflect the fill, visible to risk and to the manager, in real time.
-
4
17:00:00
NAV impact
At the fund's scheduled strike, the position, its price and any corporate action or FX translation already agree. The NAV calculation has nothing left to catch.
-
5
17:04:11
Reconciliation check
The custodian feed is matched against the ledger automatically. Because both sides trace to the same trade record, there's nothing to chase the next morning.
-
6
Next statement cycle
Investor-visible balance
The investor's statement is generated straight from the ledger ops already closed. No separate reporting extract to keep in sync.
See the ledger for your funds
Configure your operations and go live in days, not the months this category usually takes.