SERVICES
Portfolio data managed as a governed operating record rather than a reporting by-product.
Portfolio data managed as a governed operating record rather than a reporting by-product through a controlled, source-linked workflow.
Overview
Portfolio data management maintains approved security/investment, position, transaction, valuation and classification records used across reporting, risk and operations.
Below Data Aggregation and upstream of analytics.
Why it matters
Aggregation alone is not enough; reusable data needs ownership, definitions, history and controlled changes.
Common operating challenges
- Identifiers inconsistent.
- Classification changes not governed.
- Position/valuation history fragmented.
- No canonical portfolio dataset.
What we deliver
| Capability | What it covers |
|---|---|
| Portfolio master | Maintain investment/security/entity attributes. |
| Position/transaction history | Preserve approved records. |
| Classification | Govern strategy/sector/geography etc. |
| Data quality | Track missing/stale/inconsistent fields. |
Our role can be configured around a defined operating mandate: a recurring managed service, a technology-enabled client workflow, or a co-sourced model in which execution and review are split between Kelton, the client and appointed providers.
Inputs, workflow and outputs
Typical inputs
- Holdings
- Transactions
- Valuations
- Security/entity reference data
- Provider files
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Ingest | Collect data. |
| 2 | Map | Resolve identifiers. |
| 3 | Validate | Check completeness. |
| 4 | Govern changes | Approve mappings/classifications. |
| 5 | Publish | Release canonical dataset. |
| 6 | Monitor | Track quality. |
Typical outputs
- Portfolio master
- Position/transaction dataset
- Classification dictionary
- Data-quality dashboard
Controls and review
The workflow is designed so that automation does not obscure responsibility. Routine processing can be standardised; exceptions, material judgements and formal approvals remain visible and attributable.
- Effective-date history.
- Mapping approvals.
- Source priority.
Responsibility boundary
Kelton manages operating data; investment records remain subject to official source/provider/client ownership.
Technology & expertise
Our operating model combines specialist knowledge with controlled technology. Domain experts define the rules, review logic and exception criteria; the technology layer makes the workflow repeatable, traceable and scalable.
Technology
- Master data.
- Versioning.
- Quality rules.
Expertise
- Investment operations data.
- Reference-data governance.
Expert knowledge is converted into controlled rules, SOPs, checklists, validation tests and exception criteria so that the operating standard is embedded in the workflow rather than dependent on one individual.
Delivery models
| Model | How it works |
|---|---|
| Managed Operations | We execute the agreed recurring workflow. Client and appointed-provider approvals remain explicit. |
| Technology Enablement | We implement the data, workflow and control layer for the client team to operate. |
| Hybrid / Co-sourced | Execution and review are shared through a documented responsibility and escalation model. |
| Transition & Implementation | We mobilise the workflow during a launch, provider change or target-operating-model transition. |
Frequently asked questions
How is this different from Data Aggregation?
Aggregation connects sources; portfolio data management governs the resulting reusable investment record.
Can it replace an OMS/PMS?
Not necessarily. It can be a controlled data layer around existing systems.
Discuss Portfolio Data Management
Start with one workflow, one operating issue or one provider transition. We will map the current process, responsibility boundaries, required data and a practical first engagement.