Financial Services.
Multi-entity consolidation, regulatory audit, driver-based.
Can IDU meet our regulatory and audit obligations?
Every adjustment is timestamped, attributed, and preserved. Role-based access is scoped by entity, region, and function. Encrypted at rest and in transit, hosted on Microsoft Azure, with POPIA-aligned data practices. Groups serving FSCA, SARB, and listed-company audits run their planning and consolidation on IDU today.
How does IDU handle driver-based modelling for insurance and asset management?
Drivers are first-class in IDU. Premium volumes, claims ratios, AUM, fee schedules, and NII curve points all flow through configurable models. When the driver changes, the dependent figures recalculate — audit trail preserved.
Does IDU support multi-entity consolidation natively?
Yes. IDU consolidates across entities natively — intercompany matching, currency translation at the line, multiple consolidation hierarchies (legal, management, segment) running in parallel from the same dataset.
Can IDU meet our regulatory and governance obligations?
Every adjustment is timestamped, attributed, and preserved. Role-based access is scoped by entity, region, and function. Encrypted at rest and in transit, hosted on Microsoft Azure, with POPIA-aligned data practices. Listed and regulated financial-services groups run their planning and consolidation on IDU today.
How does IDU handle driver-based modelling for financial services?
Drivers are first-class in IDU. Volumes, ratios, fee schedules, rate assumptions and product-level inputs all flow through configurable models. When a driver changes, the dependent figures recalculate — every change preserved.
How long does implementation take for a multi-entity group?
Most financial-services groups go live across the group in roughly 6–8 weeks. IDU reads each entity’s existing chart of accounts directly — no rebuild from scratch.