Platform

Your reporting logic, visible and reusable.

Between raw source data and a finished report sits a layer of mappings, calculations and conventions. In most organisations that layer lives in spreadsheets and scripts. In Datox it is configuration: inspectable, versioned and reused every period.

Capabilities

What the transformation layer handles

Field mapping

Connect source columns and document fields to the reporting model, including one-to-many and conditional mappings.

Normalisation

Standardise currencies, dates, identifiers, counterparty names, asset classes and jurisdiction codes across providers.

Calculations

Apply the arithmetic your report requires, exposures, ratios, weightings, fees, performance and derived measures.

Aggregation

Roll data up by fund, entity, share class, region, strategy or any dimension the output needs.

Reference data enrichment

Resolve ISINs against an integrated Security Master, append governed reference attributes and classifications, then carry the enriched record into downstream mapping and calculations.

Learn more

Reusable rule sets

Package a set of transformations once and apply it across similar funds, entities or reporting periods.

Transparency

Logic you can read, not logic you have to trust

Every transformation applied to a value can be inspected from the output side. When a reviewer or auditor asks why a figure looks the way it does, the answer is in the platform rather than in someone's spreadsheet.

For each reported value you can see

The source record and input file it came from.
The mapping that placed it in the reporting model.
The calculation or normalisation applied, with inputs.
The version of the logic that was in effect for that period.
Who last changed that logic and when.

Change management

Business-configurable, with versioning

Reporting changes are constant, and each one that requires an engineering ticket adds delay and risk. Datox lets the people who own the report adjust mapping and calculation logic within their permissions, while keeping the change controlled.

Changes are versioned and attributable, so prior periods remain reproducible.
Draft changes can be tested against a previous period before being applied.
Permissions determine who can edit logic and who can only view it.
The reporting model stays consistent even as source layouts change.

Examples

Typical transformations in a reporting cycle

Classification mapping

Provider asset-class labels mapped to the taxonomy required by the report.

FX normalisation

Multi-currency positions converted at the correct period rate and reported in base currency.

Exposure calculation

Gross and net exposures derived from positions, notionals and instrument data.

Investor roll-up

Investor-level records aggregated by group, jurisdiction or share class for disclosure.