SERVICES
A governed investor record behind every onboarding, dealing and communication event.
A governed investor record behind every onboarding, dealing and communication event through a controlled, source-linked workflow.
Overview
Investor records/static data is the controlled master of investor identity, entity relationships, contacts, payment instructions, tax/KYC status, holdings/commitments and servicing attributes.
Below Transfer Agency and Investor Onboarding.
Why it matters
Static-data errors propagate into payments, dealing, notices, tax reporting and access permissions.
Common operating challenges
- Duplicate investor records.
- Outdated contacts/bank details.
- Different IDs across provider systems.
- KYC/tax status not synchronised.
What we deliver
| Capability | What it covers |
|---|---|
| Investor master | Maintain approved identifiers/attributes. |
| Change workflow | Control bank/contact/entity changes. |
| Provider reconciliation | Compare administrator/TA records. |
| History | Retain effective-date changes and evidence. |
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
- Investor onboarding pack
- TA/register files
- KYC/tax status
- Payment details
- Commitment/holding data
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Create | Establish master record. |
| 2 | Validate | Check mandatory fields/duplicates. |
| 3 | Approve changes | Route sensitive updates. |
| 4 | Synchronise | Share with providers. |
| 5 | Reconcile | Compare versions. |
| 6 | Archive | Retain history. |
Typical outputs
- Investor master
- Static-data exception report
- Change log
- Provider reconciliation
- Permission attributes
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.
- Sensitive field approval.
- Bank-detail controls.
- Effective-date history.
- Role permissions.
Responsibility boundary
We support manager-side records; formal register/registrar responsibility remains with appointed TA/registrar.
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 management.
- Duplicate/entity matching.
- Change workflow.
Expertise
- Investor operations.
- KYC/TA interfaces.
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
Why is static data a separate capability?
Because many downstream errors originate in incorrect investor master data.
Can the investor master replace a TA register?
Not by default; it can be a manager-side governed record and reconciliation layer.
Discuss Investor Records & Static Data
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.