In a legacy ERP refactor, should you fix master data first or align reporting first?

If leadership, finance, sales, production, and operations all use different definitions for the same business metrics, reporting alignment usually deserves first priority. Management cannot improve a system it cannot even read consistently.

This does not mean cleaning every source table first. It means defining a usable interpretation layer around a few critical metrics: order value, shipped value, work in progress, inventory turnover, and similar operational numbers. Once the business speaks the same language, larger governance work gains much stronger support.

If the problem is no longer just conflicting reports, but duplicated item codes, inconsistent customer records, broken supplier identity, or unreliable warehouse mappings, then master data governance cannot stay as a later-phase issue.

In that situation, reporting alignment alone becomes cosmetic. You may standardize dashboards, but the inputs are still too distorted to support reliable operations. Key entities need clear ownership, uniqueness rules, and maintenance paths before the rest of the system can stabilize.

Because the organizational work behind them is different. Reporting alignment is about management language and operating consensus. Master data governance is about ownership, maintenance discipline, and system constraints. Pushing both as equal large-scale programs usually produces more meetings, more rules, and not enough stable daily behavior.

A better delivery pattern is to choose one business slice first. For example, align reporting around the order-to-shipment chain, or govern master data around item coding and warehouse control. Once one slice holds, expansion becomes much easier.

If I have to simplify the decision, I usually frame it this way: does the business currently lack a shared operating view, or a trustworthy data base? Phase one should solve only the more dangerous side, while the other side supports it at the minimum necessary level.

For example, if reporting alignment comes first, master data work may only tighten a few critical fields and coding rules. If master data comes first, reporting work may stay limited to the handful of metrics leadership truly needs. That looks less ambitious on paper, but it is far more deliverable.