Entity reporting
Consolidated reporting across legal entities, branches and business lines with consistent definitions.
Use case
Controlled reporting across entities and systems.
Institutions operate many systems and many reporting obligations, with control expectations that make informal spreadsheet processes increasingly hard to defend. Datox provides the automated production layer and the evidence to go with it.
Pain points
Control expectations meet manual processes
The reporting obligation is usually well understood. The difficulty is demonstrating that the process producing the numbers is controlled, repeatable and reviewable, particularly where spreadsheets sit between systems.
- End-user computing risk in spreadsheet-based reporting steps.
- Data spread across core systems, sub-ledgers, investment platforms and operational tools.
- Manual review that is difficult to evidence after the fact.
- Multiple entities with different structures reporting into the same cycle.
- Audit and assurance requests that require reconstructing historical figures.
Applications
Where Datox is applied
Fund & investment reporting
Reporting on funds and investment holdings drawn from custodial and accounting sources.
Management reporting
Recurring management and committee reporting assembled from multiple systems.
Operational reporting
Service, exception and KPI reporting produced on a fixed cycle.
Control
Evidence produced by the process, not after it
The most expensive part of a control framework is usually the evidence collection. When the workflow itself records inputs, logic versions, exceptions and approvals, that cost largely disappears.
Control features
- Role-based access to data, logic and approval rights.
- Enforced separation between preparation and approval.
- Versioned reporting logic so prior periods remain reproducible.
- Chronological audit trail of runs, exceptions and decisions.
- Retained source evidence behind every reported figure.