When a company grows by acquisition, the finance team inherits the problem nobody put on the deal memo: every entity keeps its own books, in its own system, with its own chart of accounts. Consolidation becomes a monthly act of manual reconciliation, and the planning model is only ever as fresh as the last person to update a spreadsheet.
This team ran five general ledgers across five acquired entities. Two were on the same ERP but configured differently. The other three shared nothing. Each close meant exporting trial balances, hand-aligning accounts, and praying the mappings from last quarter still held.
The goal: one model, every entity, every month
The team did not want another integration project. They wanted to describe what they needed and have it work, then trust the result enough to forecast on it.
With Nexadata, the work followed the same four steps every workflow does.
- Connect. Each ERP was connected through its API. The systems that exposed an OpenAPI or OData specification did not need a hand-built connector at all.
- Transform. Trial balances arrived in five shapes. The team reshaped them into one structure in plain language, no scripts.
- Map. Five charts of accounts were mapped to a single planning taxonomy with conditional logic, so an account that means one thing in one entity lands correctly in the consolidated model.
- Review. Before anything reached the planning system, a person checked the mappings, the totals tied out, and the run was approved.
What changed
The monthly consolidation that used to take the better part of a week now refreshes on a schedule. The mappings are versioned and auditable, so when an auditor asks why an account rolled up the way it did, the answer is one click, not one afternoon.
We stopped rebuilding the same reconciliation every month. The model is just current now, and we trust it enough to plan on it.
Head of Financial Planning
The deeper win is not speed. It is that the people who own the numbers own the data pipeline too, instead of waiting in a queue behind every other request to engineering.
See how this applies to your stack on the financial planning solution page.