SERVICES
Fund formation coordinated from structure map to operating readiness.
Sequence entity setup, provider onboarding, KYC/tax tasks, accounts, data and launch dependencies in one controlled plan.
Overview
Fund formation is the operational coordination required to move an approved fund structure from concept to launch. Legal and tax advisers design and document the legal/tax structure; operating teams coordinate entities, appointed providers, bank/accounts, KYC, FATCA/CRS classifications, data setup, governance calendars and day-one operating readiness.
Relevant to new funds, feeders, SPVs, new jurisdictions, first closes and provider migrations. It is a bridge from structuring to recurring Fund Administration, Investor Services, Corporate and Regulatory operations.
Why it matters
Fund launches often slip because of dependencies rather than investment strategy: an entity is not incorporated, provider KYC is pending, a bank account is not ready, tax classifications are unresolved or the data/operating model has not been designed.
Common operating challenges
- No single launch plan across legal, administrator, bank, tax and technology workstreams.
- Entity and provider KYC delays.
- Bank/account setup starts too late.
- FATCA/CRS classification or registration tasks are disconnected from formation.
- Day-one data, reporting and responsibility models are not defined.
What we deliver
| Capability | What it covers |
|---|---|
| Launch planning | Create workstreams, dependencies, owners, milestones and readiness gates. |
| Entity/provider coordination | Track incorporation and service-provider onboarding. |
| Operational setup | Define accounts, data flows, calendars and master records. |
| KYC/tax coordination | Track entity KYC and FATCA/CRS tasks based on authorised advice. |
| Governance readiness | Establish recurring fund/entity obligations and authorities. |
| Day-one hand-off | Move formation records into BAU services and controls. |
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
- Approved structure diagram
- Legal/constitutional documents
- Service-provider list and requirements
- KYC/ownership information
- Bank/account requirements
- Fund terms and launch milestones
- Jurisdiction instructions from advisers
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Map | Document entities, providers, responsibilities and dependencies. |
| 2 | Plan | Sequence formation, onboarding and operating tasks. |
| 3 | Coordinate | Track providers, accounts, classifications and approvals. |
| 4 | Build the operating record | Create fund/entity masters, calendars and data interfaces. |
| 5 | Test readiness | Verify required accounts, data, systems and controls. |
| 6 | Launch & hand over | Close open items and transition into recurring operations. |
Typical outputs
- Fund launch plan
- Structure/responsibility map
- Provider onboarding tracker
- Fund/entity master data
- Launch-readiness checklist
- Day-one operations hand-off pack
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.
- Formal legal/tax/regulatory advice separated from operational coordination.
- Named owner/dependency for each launch task.
- No tax/regulatory classification without an authorised basis.
- Version-controlled structure map.
- Explicit launch-readiness sign-off.
Responsibility boundary
Kelton coordinates formation and operating readiness. Legal formation documents, tax advice, regulatory authorisations and formal fiduciary/regulated roles remain with qualified appointed professionals.
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
- Project/dependency workflow.
- Document and entity master.
- Provider onboarding tracker.
- Checklist/rule engine.
- Launch-readiness dashboard.
Expertise
- Fund operating-model design.
- Provider ecosystem coordination.
- Entity/onboarding operations.
- Knowledge of common cross-jurisdiction launch dependencies.
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 Kelton legally form the fund?
Kelton can coordinate the operating process; legal formation and legal advice remain with counsel/authorised providers.
Why include data/technology at launch?
A well-designed fund launch creates reusable master data, calendars and workflows rather than a one-off email project.
What happens after launch?
The same controlled records then flow into fund administration, investor, entity and regulatory workflows.
Discuss Fund Formation
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.