Skip to main content

Distribution & logistics

ERP transformation across a multi-entity organisation

Centralise data and harmonise finance and operations processes across several entities on a shared ERP foundation.

  • ERP transformation
  • Data migration
  • System integration
  • Quality assurance
Logistics warehouse with orderly volumes

Context

An organisation operating through several legal entities and several sites. Each entity had built its own practices and its own tooling: divergent charts of accounts, duplicated item and third-party reference data, and financial consolidation rebuilt by hand at every close.

The challenge

To put a shared application foundation in place without denying local constraints: harmonise the finance, purchasing and sales processes, make the reference data dependable, and make steering possible on comparable figures — all while the business kept running through the transformation.

What AXENEO did

The work we carried out

  1. 01

    Scoping and core model

    • Analysis of the existing processes entity by entity, and identification of the real gaps
    • Definition of a shared core model and of the local variants that could be accepted
    • Assessment of every departure from the standard: need, alternative, cost of maintenance
    • Requirements repository and acceptance criteria for each process
  2. 02

    Rollout and data

    • Rollout steered in waves, carrying learning from one entity to the next
    • Data migration workstream: perimeter, transformation rules, test sets
    • Consistency checks and reconciliation before every switchover
    • Interfaces with the applications kept in place, and a map of the flows
  3. 03

    Quality and go-live

    • Test strategy and acceptance scripts organised by business process
    • Non-regression campaigns before every move into production
    • Defect management: qualification, prioritisation, tracking through to closure
    • Support at go-live, then continuous improvement

Results

What the set-up changed

Results are described qualitatively. We do not publish figures we would not be able to document.

  • A single repository for master data, with management rules shared across entities.

  • Finance, purchasing and sales processes harmonised on a shared core model.

  • Financial consolidation produced from the system, with no manual rework.

  • Documented and monitored interfaces, with rejects handled explicitly.

  • An acceptance-testing set-up reusable for the deployment waves that follow.

Contact

A comparable situation?

We can talk you through how it actually went, including what we would do differently today.