Integrations.
ERP connectors, native APIs, scheduled syncs.
How does IDU integrate with our ERP?
IDU integrates using APIs, SQL-based services, direct database connectivity, or secure file-based methods. This ensures compatibility with both on-premise and cloud ERP environments.
What data is integrated?
Typical integrations include actual financial data from the general ledger, chart of accounts and cost centre structures, organisational hierarchies, and historical data for trend and comparative reporting.
Can IDU write data back to the ERP?
Yes. Approved budgets or forecasts can be written back into the ERP where required, ensuring alignment between planning and financial systems.
How often does data update?
Actuals are typically refreshed on a scheduled basis, such as overnight or more frequently where required. This ensures planning and reporting are always based on current data.
How does IDU actually connect to our ERP?
Via native APIs where the ERP provides them, and via SSIS packages or scheduled batch processes where it doesn’t. Either way the data arrives on a defined cadence — typically daily, but configurable up to near-real-time depending on the ERP.
Is the integration one-way or two-way?
Both directions are supported. Actuals flow into IDU from the ERP; approved budgets and forecasts can flow back out where that’s useful. Most customers start with one-way sync and expand as their governance maturity grows.
Do you need access to our production ERP?
Read access, yes — scoped to the tables and fields required. Many customers run IDU against a reporting replica or a data-warehouse layer rather than the live ERP instance, which is equally supported.
How long does the initial integration take?
Days, not weeks. The longest part is agreeing security protocols and provisioning access on your side. Once IDU can see your ERP, chart of accounts reads and historical backfill usually happen inside a single working day.
Can IDU integrate with our payroll system?
Yes. IDU can integrate with payroll and HR systems to import employee and remuneration data for workforce planning, budgeting, forecasting, and reporting. This allows organisations to start the budget process aligned to the latest payroll run, reducing manual preparation and ensuring forecasts and plans are based on current employee and remuneration information. Integrated payroll actuals can also be used for actual versus budget reporting at employee, account, cost centre, or departmental level, providing detailed visibility into workforce costs and variances.
How often does integration run?
Integration schedules are configurable based on organisational requirements. Some organisations refresh data in near real time, while others prefer scheduled batch updates daily, weekly, or on demand. IDU supports both automated and manual integration approaches. Authorised administrators can also execute integrations directly from within the application for ad hoc updates, without requiring IT involvement. This allows finance teams to refresh actuals, payroll, or operational data when needed during budgeting, forecasting, or reporting cycles.