How Spaces helps
ERP migrations usually include a parallel run. Agents reconcile the old ERP against the new one, explain each difference and keep decisions documented through cutover.
Still manual today Parallel-run reconciliation between the legacy and new ERP is manual and ties up scarce people.
Example MarketCo MY intercompany payable differs by 117,680: the old ERP uses a consolidated average rate, the new one the policy month-end rate. Explained and mapped to the rate policy.
- HoldCo SG trial balance Fully reconciled Done
- OpsCo HK revenue Mapping difference explained Done
- TechCo IN fixed assets Depreciation method difference For approval
- OpsCo HK intercompany Elimination timing explained Done
- TechCo IN accrued expenses Unexplained difference, owner assigned Needs review
Decisions documented through cutover
What the agent does
- Compares old and new ERP balances by entity, account and period
- Explains each difference: mapping, timing, configuration or data
- Tracks differences to resolution, with owners and decisions logged
- Carries policies and judgment calls into the new ERP with sources attached
How it runs
- 01 Connect both Reads trial balances from both ERPs for each parallel period.
- 02 Compare Matches accounts through the agreed mapping and lists differences.
- 03 Explain Drafts a cause for each difference with cited mapping or configuration evidence.
- 04 Sign off Project and finance leads approve resolutions before cutover decisions.
Reconciliation work is prepared, not hand-built each cycle.
Policies and judgments move to the new ERP with sources.
Same agents and approvals before and after go-live.
- How does this fit with our implementation partner?
- Your partner leads configuration and delivery. Agents support the parallel run by reconciling, explaining differences and documenting decisions.
- Which ERPs does it support?
- We confirm connector coverage for your source and target ERPs and scope the parallel run with you during onboarding.