IDU Conference: 13-15 May 2026

Sign up
How it works

From ERP data to decisions, in four steps.

No rip-and-replace. No long implementation cycles. Just your data, governed and connected, from the ledgers to the people who need to act on it.

CONNECT
PLAN
ANALYSE
DEPLOY

Reads your ERP from day one.

IDU connects to your ERP and reads your chart of accounts, organisational structure, and actuals. This forms the foundation of your planning model, without rebuilding your financial structures.

FINANCE / ERPSalesMarketingOperationsHR

Top-down targets. Bottom-up detail.

Finance sets targets, validation rules, and assumptions. Managers contribute their budgets through a guided interface. No spreadsheets. No email consolidation. No version conflicts. Multiple budgeting approaches are supported, including line-item, driver-based, capex, project, and scenario planning, all within the same governed model.

Line-item
Detailed
Driver-based
Capex
Remuneration
Project
Activity
Headcount
Revenue
Cash flow
Departmental
Scenario

From group view to transaction detail.

View performance at group level or drill down to general ledger transactions where supported. Variance analysis, trend reporting, and dashboards are all available within the same platform. Export to Excel, PDF or connect to other tools where required.

Q4 BudgetLive
0
+12.4%
Remaining this quarter

Live in weeks, not months.

IDU is deployed in the environment that suits your organisation, cloud, private cloud, or on-premise. Most organisations are live within weeks, with full functionality available regardless of deployment choice.

Most customers go from kickoff to live cycle inside a quarter.

The architecture

How IDU sits inside your finance stack.

IDU sits between your systems of record and your users. Your ERP remains the source of actuals; IDU provides governance, planning, and reporting; your people work from a single, consistent view.

Your ERP
Integration
Governance
Reporting
Your People
Security & Compliance

Built for controlled environments.

  • ISO-aligned practices

    IDU follows recognised standards for information security and service management, supporting organisations with strict governance requirements.

  • Role-based access

    Users see only what they need to see, with full audit trails on every change.

  • Data protection

    Encryption in transit and at rest, aligned to your organisation’s policies and deployment model.

The difference
12–18months

Typical time-to-live on a traditional enterprise planning platform — requirements, data migration, retraining, rework. Most cycles pass before the tool does any work.

3–6weeks

Typical time-to-live on IDU — ERP connected, chart of accounts read, first cycle in hand. Because we read your existing financial structure, nothing has to be rebuilt.

FAQs about running IDU.

  • 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.

Trusted by teams with no patience for re-implementations
The implementation exceeded our expectations. We were live in a fraction of the time we had anticipated.
Ashley FrancisUniversity of Cape Town
Reporting reduced from months to weeks. Monthly reports at the click of a button.
Dylan Le RouxOperational Finance Manager, Food Lover's Market
For the first time we have been able to include more people in the budgeting process, increasing involvement and transparency.
Zandi EksteenAccountant, Momentum

Your numbers, governed and in motion.

See your ERP connected, your chart of accounts read, and your first budget cycle running in IDU. Book a demo and see IDU in action, live.