Spreadsheets & CSV
Excel workbooks with multiple tabs, merged headers, footnotes and layouts that change between providers and periods.
Platform
Work with the data you actually have.
Reporting data rarely arrives in one clean format. Datox is built to accept inconsistent inputs, spreadsheets with changing layouts, PDF statements, system exports, database tables and API responses, and turn them into a consistent reporting model.
Inputs
Sources Datox is designed to ingest
Documents
PDF and Word statements, confirmations, valuation reports and disclosure documents read by extraction agents with evidence references.
System exports
Fixed-format extracts from accounting, portfolio, custody, administration and operational systems.
Databases
Direct reads from relational databases and warehouse tables where a governed connection is available.
APIs & applications
Scheduled pulls from cloud applications and internal services that expose a data interface.
Secure file transfer
SFTP drops from providers, with files matched automatically to the right reporting period and entity.
Philosophy
Input-agnostic by design
Forcing every data provider onto a standard template is the slowest way to automate reporting, because it makes your progress dependent on other organisations. Datox takes the opposite approach: accept the source as it is, and hold the interpretation logic inside the platform where you control it.
- Each source has its own mapping definition, versioned and owned by your team.
- Layout drift is detected during extraction rather than discovered in the output.
- New providers are onboarded by adding a mapping, not by changing the pipeline.
- Where a template does exist, Datox uses it, but does not depend on one.
Ingestion controls
Secure, repeatable ingestion
Connectivity is part of the governed workflow. Inputs are recorded, matched to a reporting period, and retained as the evidence behind the output.
What is controlled
- Which sources feed which reporting workflow, and who can change that.
- Period matching, so late or duplicate files are identified rather than merged silently.
- Retention of the original input as evidence for lineage and review.
- Access control over sensitive source data by role.
- A record of when each input arrived and which run consumed it.
Outputs
Connectivity works in both directions
Files
Generated XML, PDF, Excel and CSV artefacts delivered to a location you control.
SFTP
Scheduled delivery of outputs to providers, clients or internal destinations.
APIs
Programmatic retrieval of finished reporting datasets by downstream services.
Datasets
Clean tables that BI and analytics tools can consume directly.
Specific connectors, credentials and delivery destinations are confirmed during deployment based on your systems and security requirements.