How it Works.
Architecture, deployment model, the journey from spreadsheets.
How does IDU read our existing chart of accounts?
IDU connects to your ERP via its native API or an SSIS package and reads your chart of accounts, entities, cost centres, and actuals directly. Nothing has to be recreated — the structure you already operate on becomes the structure IDU plans against.
Does IDU replace our ERP or reporting tools?
Your ERP remains your system of record, and IDU sits alongside it as the planning and reporting layer. Within IDU, finance and operational managers have access to variance reporting and performance visibility in a governed environment. Where needed, outputs can be delivered to tools such as Excel, Power BI, or PDF.
What does a typical implementation look like?
Most customers are live inside 3–6 weeks. A typical rollout: week 1 ERP connection and model read, week 2–3 validation and user workflows, week 4–5 training and soft launch, week 6 first live cycle. The implementation team handles the heavy lifting.
Where does our data live?
Wherever your policy requires. IDU can be deployed on Microsoft Azure in a private or managed cloud environment, or on-premise for organisations with specific security or infrastructure requirements. Functionality remains consistent across all deployment options.
How long does IDU take to deploy across a multi-entity group?
Most multi-entity groups are live across the group in roughly 6–8 weeks. IDU reads each entity’s structure directly from the ERP, so extending the model across subsidiaries is straightforward.