SERVICES
A period close with every dependency, break and approval visible.
A period close with every dependency, break and approval visible through a controlled, source-linked workflow.
Overview
Period close coordinates the tasks required to complete an accounting/reporting period: source cut-offs, reconciliations, accruals, valuation inputs, journals, movement analysis, review and locked evidence.
Below Fund Accounting and Financial Reporting.
Why it matters
Close quality depends on sequencing and ownership across many data/provider dependencies.
Common operating challenges
- Late input files.
- Unresolved reconciliations at deadline.
- Close checklist lives in spreadsheets.
- Review comments not tracked.
What we deliver
| Capability | What it covers |
|---|---|
| Close calendar | Define tasks/dependencies/cut-offs. |
| Status management | Track completion and late inputs. |
| Exception gating | Prevent close from silently bypassing material breaks. |
| Review pack | Assemble movement analysis 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
- Close calendar
- Reconciliations
- Trial balance
- Valuation/fee schedules
- Provider status
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Open period | Launch checklist. |
| 2 | Collect | Track required inputs. |
| 3 | Reconcile/calculate | Complete close tasks. |
| 4 | Resolve | Clear material exceptions. |
| 5 | Review | Perform movement/checklist review. |
| 6 | Lock | Archive approved period. |
Typical outputs
- Close dashboard
- Late-input list
- Exception gate report
- Review checklist
- Locked evidence 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.
- Task dependencies.
- Materiality gates.
- Maker/checker.
- Period lock/version control.
Responsibility boundary
Kelton can run/support close workflow while official books/reporting approval remains with responsible parties.
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
- Workflow engine.
- Dependency/status tracking.
- Exception gating.
Expertise
- Accounting close management.
- Administrator oversight.
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
Is period close separate from fund accounting?
It is the orchestration layer around accounting, reconciliation, valuation and reporting tasks.
Can a close be partially co-sourced?
Yes; tasks can be assigned across Kelton, client and administrator with one status/evidence view.
Discuss Period Close
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.