Most manufacturers and distributors don’t have a reporting routine that looks something like this: data gets pulled from the ERP, adjusted in a spreadsheet, reviewed, questioned, revised, and then shared. The process repeats every week.

Everyone knows it takes too long. Everyone knows the numbers get challenged. But it still gets done, so it’s treated as acceptable.

That’s where things start to break down.

In many organizations running systems like Microsoft Dynamics 365 Business Central, reporting hasn’t failed, it’s just been patched together enough to keep going. Over time, those patches become the process.

ERP Reporting: When it Isn’t Enough

ERP systems are designed to track transactions. They do that well. But most operational decisions in manufacturing and distribution don’t happen at the transaction level. They happen across time, across locations, and across processes.

That gap is where Business Central reporting limitations start to show:

• Production data lives separately from scheduling or capacity context. 
• Inventory is accurate, but availability depends on demand and lead times. 
• Sales, purchasing, and fulfillment data aren’t naturally aligned in a single view. 

Standard reports can surface pieces of this, but not the full picture. So teams build their own.

They export data from Business Central tables (item ledger entries, production orders, sales lines), reshape it in Excel, and combine it with external inputs. That logic gets recreated every time a report is needed or slightly modified depending on who’s building it.

From there, reporting isn’t a system. It’s a workaround.

The Real Cost of Spreadsheet Reporting

Most organizations using Business Central don’t think spreadsheets are the issue. They think the issue is time, but time isn’t the real cost.

The real cost shows up in how decisions are made:

• Finance and operations are working from slightly different definitions. 
• Inventory reports don’t match order fulfillment views.
• Production metrics can change depending on how the data was pulled.

Even small inconsistencies create hesitation. Teams spend time validating numbers before acting on them.

What Changes When Reporting Doesn’t Have to be Rebuilt

Reporting doesn’t improve by creating better reports. It improves when the need to rebuild them is removed. That requires a structural shift. Instead of pulling data into spreadsheets each time, organizations can move to a model where:

• Data from Business Central (finance, inventory, production, sales) is centralized into a consistent data layer. 
• Relationships between tables are defined once (customers, items, orders, dimensions).
• Calculations like margin, inventory turns, or production efficiency are standardized. 
• Refresh processes are automated, so data stays current without manual intervention. 

In practice, this is often implemented using Power BI and the Microsoft data platform layered on top of Business Central. What matters isn’t the dashboard, it’s the model behind it. Once that exists, reports don’t need to be rebuilt. Teams are working from the same definitions, and data can be reused without rework. 

What This Looks Like in Manufacturing

In manufacturing environments running Business Central, this change shows up quickly in day-to-day operations. Without a consistent data layer production output is reviewed after the fact, downtime is tracked manually or inconsistently, and bottlenecks are identified only after they’ve already affected schedules.

With a connected analytics model production orders, capacity data, and output can be viewed together, and machine or line performance can be monitored throughout the day. Exceptions like delays, shortages or overruns surface when they happen. 

This doesn’t require replacing Business Central. It requires extending it with a structure that supports continuous visibility. 

What This Looks Like in Distribution

In distribution, the same shift applies, but the focus is different. The challenge isn’t production, it’s coordination:

• Inventory position vs. demand 
• Order backlog vs. fulfillment capacity 
• Supplier lead times vs. customer expectations 

Without a consistent data model, those views are fragmented. Teams rely on separate reports or manual reconciliation. With a centralized analytics layer:

• Inventory, orders, and purchasing data can be evaluated together.
• Fulfillment risk becomes visible earlier. 
• Decisions around allocation, replenishment, and prioritization can be made with current data. 

Again, the change isn’t the report, it’s the ability to see across processes without rebuilding the logic each time.

Why Most Analytics Efforts Stall and What Works

Most companies go off track when they try to fix everything at once. Large, all-encompassing initiatives take too long to deliver value, and by the time something is ready, the business has already moved on.

At the same time, many teams approach analytics the same way they approached reporting and think they just need better visuals. That leads to a familiar set of issues:

• Treating dashboards as the solution
  Jumping straight to dashboards before the data is consistent usually results in the same problem in a different format. The numbers look better, but they still need to be explained or reconciled. 
• Rebuilding ERP logic outside the system
  Instead of defining calculations once, teams recreate them in Excel or individual reports. Margin, inventory position, and production metrics end up slightly different depending on where they’re calculated. 
• Ignoring how operations actually use the data
  Reporting is often designed around what can be pulled from the ERP, not how decisions are made on the floor or in the warehouse. If the output doesn’t match how teams work, it gets bypassed. 
• Leaving ownership undefined
  When no one owns key metrics, definitions drift. Finance, operations, and sales interpret the same numbers differently, and reporting turns into a debate. 

The organizations that make progress take a different approach. They start with something that’s clearly broken: a report that takes too long, numbers that don’t match, or a lack of visibility into a critical operation.

Fixing that forces an approach that includes structuring data, aligning definitions, and automating data refreshes. Once that foundation exists, expanding becomes easier because the hard part, consistency, is already in place.

What to Do First (Without Starting a Full Project)

Most organizations working in Business Central don’t need a formal analytics initiative to get started. They need to change one thing that’s clearly not working. A good starting point is to look for a report that takes too long to prepare, or one that gets questioned once it’s shared.

That combination usually points to a deeper issue with how data is structured and used. From there, the first step isn’t to build a dashboard. It’s to stabilize the data behind that report. In a Business Central environment, that typically means:

• Identifying the exact tables and fields the report depends on (for example, item ledger entries, sales lines, production orders). 
• Defining how key metrics should be calculated so they’re consistent every time. 
• Removing manual adjustments where possible and replacing them with repeatable logic. 

Once that foundation is in place, the next step is to automate how the data is refreshed and delivered. That might involve connecting Business Central to a reporting layer like Power BI so the same dataset can be reused instead of rebuilt.

At that point, the reporting experience changes without needing a full rollout: it no longer has to be recreated, the numbers are consistent and updates happen automatically.

What It Comes Down To

Most reporting processes in manufacturing and distribution weren’t designed. They evolved. Over time, they become complex enough that no one wants to change them even when they’re slowing the business down.

The shift to modern analytics isn’t about adding dashboards. It’s about removing the need to rebuild the same answers every week. Until that changes, reporting will keep working just well enough to avoid being fixed.

About the Author

Greg Crandall is Practice Director of ERP (Business Central) at JourneyTeam. He works with manufacturers and distributors that have outgrown spreadsheet-based reporting, focusing on structuring data, standardizing metrics, and building scalable analytics environments using Microsoft Dynamics 365 Business Central and the Microsoft data platform.