SERVICES
AIFM / ManCo coordination with responsibilities, data and oversight flows clearly mapped.
Support managers working with third-party regulated management companies without implying Kelton itself performs the AIFM/ManCo role.
Overview
In European fund structures an authorised AIFM or management company can hold formal responsibilities such as risk management, compliance/oversight and, depending on the operating model, portfolio-management responsibilities. Non-European managers can use third-party AIFM/ManCo arrangements for European funds or market access.
A specialist page below Market Access.
Why it matters
The manager, AIFM/ManCo, administrator, depositary and advisers need recurring data/evidence. Coordination fails when retained/delegated responsibilities and deadlines are not explicit.
Common operating challenges
- Duplicate provider requests.
- Unclear delegated vs retained responsibility.
- Late risk/compliance data.
- Investment/transaction workflows not routed through required controls.
- Cross-border launch/marketing tasks fragmented.
What we deliver
| Capability | What it covers |
|---|---|
| Responsibility mapping | Document retained/delegated roles. |
| Provider onboarding | Coordinate data, KYC and setup. |
| Operating data support | Provide agreed recurring information to AIFM/ManCo. |
| Risk/compliance reporting support | Coordinate requested data/evidence. |
| Governance evidence | Maintain meeting/oversight records. |
| Change support | Add funds/markets/providers. |
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
- AIFM/ManCo agreement/requirements
- Fund structure
- Portfolio/risk data
- Compliance reports
- Governance records
- Distribution/marketing instructions
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Map model | Document parties and duties. |
| 2 | Onboard | Set data/providers/calendars. |
| 3 | Feed data | Deliver approved information. |
| 4 | Monitor | Track requests/exceptions. |
| 5 | Review | Prepare oversight evidence. |
| 6 | Change | Manage new fund/market/provider. |
Typical outputs
- Responsibility matrix
- AIFM data-delivery calendar
- Oversight pack
- Open request tracker
- Governance evidence
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.
- No claim Kelton is an authorised AIFM/ManCo.
- Authorised provider retains formal regulatory role.
- Jurisdiction-specific content validated.
Responsibility boundary
Kelton coordinates and supports the operating interface; the authorised AIFM/ManCo retains its formal duties.
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
- Provider workflow.
- Data-delivery schedule.
- Secure evidence exchange.
- RACI/obligation tracking.
Expertise
- Fund operating models.
- European provider interfaces.
- Governance/data coordination.
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
Does every fund need an AIFM?
No. Applicability depends on structure/jurisdiction.
What does a third-party AIFM do?
Market providers describe formal risk/compliance/oversight and potentially portfolio-management functions depending on the model.
Why does Kelton need this page?
Asian managers may need an operating layer to coordinate the regulated-provider ecosystem.
Discuss AIFM / ManCo Coordination
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.