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.
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.
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.
The same customer under several codes, from one company to another.
Numbers missing, mistyped or in different formats.
Open items and invoicing anomalies to explain.
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.
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.
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.
Each AX customer code has its counterpart in Sage X3. The program maintains the table and feeds Sage X3 in production.
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.
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.
Timeline
Four workstreams in ten months
SIRET numbers, duplicates and formats checked before go-live.
Sage X3 fed from Dynamics AX, with the mapping table.
Open items and invoicing anomalies resolved.
Entries checked, support for the closes and for management control.
Results
A better-prepared switchover, secure invoicing
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.
An ERP migration ahead?
A first 30-minute conversation, free and with no commitment.