Bidev Consulting Logo
References Blog
Stelliant

Moving accounting to Sage X3 without carrying over bad data

How Stelliant cleaned its customer master data, fed Sage X3 from its former ERP and secured the invoicing of its claim files during the migration.

Insurance servicesSage X3Data10 months of support

The client

Stelliant

Stelliant is a major player in insurance services. The group handles property and casualty claims on behalf of insurers.

The group grew partly through acquisitions, and each company it bought came with its own tools and data. The finance department launched the migration of its accounting tools from Dynamics AX to Sage X3 and entrusted us with part of the work: data quality and interfaces.

SectorInsurance services
BusinessProperty and casualty claims management
MigrationDynamics AX to Sage X3
Duration10 months
A calculator on an accounting binder, next to a laptop

The project

Customer master data inherited from several companies

The same customer could exist several times, under different codes depending on the original company, with a missing or mistyped SIRET number. Loading these records into Sage X3 as they were would have exposed accounting to rejections at switchover.

Invoicing also had to keep running during the migration. The invoicing tools were not yet connected to Sage X3, so a bridge was needed between the old and the new ERP.

Duplicates

The same customer under several codes, from one company to another.

SIRET

Numbers missing, mistyped or in different formats.

Work in progress

Open items and invoicing anomalies to explain.

Interfaces

No direct link yet between invoicing and Sage X3.

What we put in place

Clean the data, then connect the two ERPs

Our consultant worked within the IT department, alongside the Finance teams. He ran three technical workstreams in parallel.

1

Clean customer master data before switchover

SIRET analysis, duplicate matching (exact, then fuzzy), format normalisation. Before go-live, each check produced an anomaly report that the teams worked through.

CheckSIRET
CheckExact duplicates
CheckNear duplicates
CheckFormats
2

An interface between Dynamics AX and Sage X3

Until direct interfaces between the invoicing tools and the ERP are built, a program retrieves the master data, translates AX customer codes into Sage X3 codes and keeps the mapping table up to date. It reads from and bulk-writes to Sage X3 through its APIs.

Mapping table

Each AX customer code has its counterpart in Sage X3. The program maintains the table and feeds Sage X3 in production.

3

Outstanding balances explained, item by item

Cross-checking several sources brought out the invoicing anomalies and open items in the claim files. The macro that generated migration and correction entries gave way to a dedicated program.

EntriesMigration and correction entries, generated automatically

How we got there

Working closely with the Finance teams

Our consultant entered and checked entries in Sage X3, took part in the accounting closes and supported management control on budget tracking and P&L analysis. He also ran functional acceptance tests.

On the claims side, he presented the quality follow-up to claims handlers and coordinated his work with teams already stretched by the migration.

Sage X3Dynamics AXSage X3 SOAP and REST APIsInvoicing tools

Timeline

Four workstreams in ten months

Workstream 1Master data

SIRET numbers, duplicates and formats checked before go-live.

Workstream 2Interface

Sage X3 fed from Dynamics AX, with the mapping table.

Workstream 3Work in progress

Open items and invoicing anomalies resolved.

Workstream 4Closes

Entries checked, support for the closes and for management control.

Results

A better-prepared switchover, secure invoicing

Master dataSIRET numbers, duplicates and formats cleaned to reduce the rejections expected at the accounting switchover.
AX → X3An interface that feeds Sage X3 in production.
Work in progressReliable outstanding balances and open items resolved.
IntercompanyDiscrepancies on accounts between group companies brought to light.

I am pleased to recommend Bidev Consulting, who are supporting me on the project to migrate our accounting tools to Sage X3 at Stelliant.

Their consultant runs the interface between AX and Sage X3, which feeds Sage X3 in production until the direct interfaces between our billing tools and the ERP are developed. He built a Python program that retrieves the reference data from these tools, makes the code mapping between AX and Sage X3 customer codes reliable, and maintains the mapping table.

He has shown great professionalism and real rigour, as well as solid expertise in developing macros and programs. He understands Finance business issues as well as technical constraints, which makes him an invaluable partner on an ERP project.

I recommend Bidev Consulting without reservation.

Emmanuel Hesse, Finance Projects Director, Stelliant Group

An ERP migration ahead?

A first 30-minute conversation, free and with no commitment.