Roles & permissions
Preparer, reviewer, approver and administrator roles determine who can edit logic, resolve exceptions and release output.
Platform
Reporting is a process, not a spreadsheet.
A reporting cycle involves preparers, reviewers, approvers and sometimes external parties. Datox holds that process inside the platform, so ownership is explicit, review is evidenced and sign-off is recorded against the period.
Working together
Collaboration built into the reporting cycle
Ownership
Each workflow, entity or fund has a named owner, so nothing sits unattended at period end.
Comments & context
Discussion happens against the specific value, exception or run, not in a separate thread that loses the context.
Approvals
Explicit sign-off steps before output is generated or delivered, recorded with the approver and timestamp.
Recurring cycles
Periods are created on a schedule with tasks, owners and deadlines carried forward from the previous cycle.
Audit trail
A chronological record of what ran, what changed, what was flagged and who decided what.
Segregation of duties
The person who prepares is not the person who approves
Control frameworks generally require independence between preparation and approval. Datox supports that separation through permissions rather than convention, and records it as evidence.
Supported controls
- Permission sets that prevent self-approval where required.
- Restricted rights to change mapping and validation logic.
- Read-only access for oversight, audit or client-side users.
- A complete record of who approved which reporting period, and when.
Period management
Every cycle starts from a known state
Instead of rebuilding the cycle from last quarter's folder, each period opens with the same configured workflow, the same owners and the outstanding items from the previous run visible.
- Status visibility across all entities or funds in a reporting cycle.
- Exceptions carried forward with their prior-period resolution attached.
- Deadlines and progress tracked in one place for the whole team.
- Late-arriving data handled as a controlled rerun, not an untracked patch.