SERVICES
Entity accounting connected to the fund and transaction record.
Entity accounting connected to the fund and transaction record through a controlled, source-linked workflow.
Overview
Entity accounting supports books, expenses, intercompany balances, bank activity and reporting for SPVs/holding/financing entities within an investment structure.
Below SPV & Entity Services.
Why it matters
Large private-market structures can have many entities whose books must remain aligned with fund reporting and transaction events.
Common operating challenges
- Different accountants/providers per entity.
- Intercompany balances not reconciled.
- Bank/expense records incomplete.
- Entity close delayed.
What we deliver
| Capability | What it covers |
|---|---|
| Books support | Maintain entity accounting dataset. |
| Bank/expense reconciliation | Tie cash and costs. |
| Intercompany | Track/reconcile approved balances. |
| Close/reporting | Prepare entity support packs. |
| Fund linkage | Feed consolidation/fund reporting. |
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
- Entity GL/TB
- Bank statements
- Invoices
- Intercompany schedules
- Transaction documents
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Collect | Load accounting sources. |
| 2 | Map | Standardise entity/accounts. |
| 3 | Reconcile | Cash/intercompany. |
| 4 | Calculate | Accruals/entries. |
| 5 | Review | Resolve exceptions. |
| 6 | Publish | Provide close/fund feed. |
Typical outputs
- Entity trial balance support
- Bank reconciliation
- Intercompany schedule
- Close pack
- Fund/consolidation feed
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.
- Entity segregation.
- Intercompany matching.
- Approved accounting policies.
Responsibility boundary
We support entity accounting operations; statutory accounts, tax and formal accounting responsibility remain with 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
- Multi-entity accounting data.
- Reconciliation.
- Consolidation feed.
Expertise
- SPV accounting.
- Private-market entity operations.
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 separate entity accounting?
Fund accounting alone does not cover each legal entity’s books and intercompany activity.
Can it support many SPVs?
Yes; standardised entity masters and recurring workflows are especially valuable at scale.
Discuss Entity Accounting
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.