Two workspaces on one record. Investment, for the people who manage the money: allocations, portfolios and analysis. Control, for the people who oversee it: the policy, its rules, monitoring, cases and evidence. Use both, or the control side alone with positions from your own systems.
For the people who manage the money.
For the people who oversee it.
Allocations set lower, target and upper weights by class, sub-class or strategy for a portfolio or a portfolio group, with benchmark weights beside them. Governing the strategic bands turns them into a rule version with an approval trail. Tactical targets remain the manager’s working decisions: logged, never policy events.
Demo data: the fund’s strategic allocation, governed as a rule, and how compliance reads its bands today. Tap to enlarge.
Value and weight by asset class, currency, region, continent, country, issuer, issuer group and counterparty group, for one portfolio, a group, or an entity with everything beneath it, as of any date and compared with another.
Demo data: the fund by asset class, and its weights against the governed strategic bands. Tap to enlarge.
Holdings as of any date, positions imported from a CSV or Excel file with saved column mappings and checked before anything is applied, and the book cost where it is supplied. Above them, what the approved rules say about the portfolio and the questions compliance has asked.
Demo data: the open cases on the fund, with a question compliance asked of the manager. Tap to enlarge.
Classes, sub-classes, types and strategies you define, in versioned taxonomies. Private-market commitments and vintages have rules of their own, and values convert at approved FX rates once a base currency is set.
Each manager’s mandate runs as its own portfolio, with its governing document and its own rules. Portfolio groups and an entity hierarchy hold the whole, the Analysis view adds it up, and related-portfolio limits measure an instrument or issuer group across several portfolios.
Fund holdings are recorded as dated compositions, so a limit can count what the funds hold, and the cash inside them. A fund with no usable composition is shown as held directly and disclosed, never estimated.
Policy documents are stored as versions. Every clause is given a disposition, and the questions a clause leaves open are recorded as the author’s decisions.
Demo data: two clauses of a fictional investment policy statement, each mapped to the rule it became. Tap to enlarge.
Allocation ranges, issuer and issuer-group concentration, credit quality, duration, liquidity, leverage, derivatives, counterparties, exclusions, private-market commitments and more.
Demo data: the rule register of the demo organisation, with each rule’s category and active version. Tap to enlarge.
Monitoring runs produce immutable results. Each one carries its state, a reason code, the measured value, the headroom to the bounds and the holdings that contribute most.
Demo data: monitoring results for the fictional fund. The breach shows its value against the band, and the reason. Tap to enlarge.
Demo data: a breach case with its latest evaluation, the calculation and the workflow actions. Tap to enlarge.
A continuing breach becomes a case with an owner, escalation and service clocks. Qualitative obligations are attested on a schedule.
Evidence packs and reports are generated from the system of record, and a past result can be reproduced.
Demo data: an evidence pack for the fictional fund, with its integrity hash and its downloads. Tap to enlarge.
Proposed trades are checked against the same rules before execution, with what-if scenarios. Strategic bands are governed rules; tactical positions are the manager’s.
Demo data: a proposed purchase for the fictional fund, projected against each of its rules. Tap to enlarge.
Bring a policy or a mandate and we will walk through its allocation, its rules, its results and its evidence.
