SERVICES
An operating report that shows what is unresolved before it becomes a reporting problem.
An operating report that shows what is unresolved before it becomes a reporting problem through a controlled, source-linked workflow.
Overview
Portfolio operations reporting consolidates middle-office status—trades, settlements, reconciliations, cash, collateral, corporate actions and exceptions—into a daily/periodic control view.
Below Middle Office, distinct from investment Portfolio Reporting.
Why it matters
Teams need one operational view of open breaks, deadlines and provider status rather than separate spreadsheets per function.
Common operating challenges
- No consolidated daily control view.
- Open issues hidden in functional trackers.
- Management cannot see ageing/materiality.
- Provider SLA problems surface late.
What we deliver
| Capability | What it covers |
|---|---|
| Control dashboard | Combine operating statuses. |
| Exception summary | Show material open items. |
| SLA/provider view | Track external dependencies. |
| Trend/root-cause | Report recurring operational issues. |
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
- Trade status
- Reconciliation breaks
- Cash/collateral
- Corporate actions
- Provider queues
Controlled workflow
| Step | Activity | What happens |
|---|---|---|
| 1 | Collect | Load workflow statuses. |
| 2 | Normalise | Apply common severity/owner. |
| 3 | Prioritise | Identify time-critical issues. |
| 4 | Review | Run daily operating check. |
| 5 | Escalate | Route material items. |
| 6 | Publish | Release control report. |
Typical outputs
- Daily operations dashboard
- Aged exception list
- Provider SLA view
- Control KPI trend
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.
- Common severity taxonomy.
- Data freshness.
- No green status with unresolved material break.
Responsibility boundary
This is operating control reporting, not portfolio investment advice or risk analytics.
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 telemetry.
- Exception aggregation.
- Operational KPI reporting.
Expertise
- Middle-office control.
- Provider 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
How is this different from Portfolio Reporting?
This page reports operational status; Portfolio Reporting reports investment/portfolio information.
Who uses it?
COO/operations, fund controller, treasury and service-provider oversight teams.
Discuss Portfolio Operations Reporting
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.