.png)
Business Central Second Opinion: When Going Live Doesn’t Mean the Work Is Done
How a consumer products manufacturer used our Second Opinion for Business Central after go-live to validate its Business Central setup, realign business processes, and reconnect operations, inventory, and accounting. |
Going live with Microsoft Dynamics 365 Business Central is a major milestone. But it doesn’t automatically mean the implementation delivered the processes, understanding, or confidence the business needs.
A consumer products manufacturer was already live on Business Central when Elliott Clark Consulting became involved. Our role was not to rescue the implementation before launch or start the project over. It was to validate what had been configured, understand where the system and the business processes were out of alignment, and help the team determine what needed to change after go-live.
For Debbie H., the company’s Controller, the biggest problem was not one isolated configuration. It was that operations, inventory, accounting, and financials had not been treated as parts of one connected business process.
“We had very little support and communication. There was no concept of looking at Operations/Inventory in tandem with Accounting/Financials, so there was a big disconnect on how those go together. We had two separate consultants for each process and they did not talk to one another.”
That disconnect continued after go-live, leaving the team with a working ERP system but without enough confidence that the processes inside it were working together correctly.
Why Business Central implementations struggle when processes are not aligned
Business Central connects the operational and financial sides of a company. Inventory movements affect costing. Purchasing affects inventory valuation, payables, and cash. Operational transactions eventually become financial transactions. Those processes cannot be designed independently and expected to align automatically at the end.
Debbie felt the original implementation focused too narrowly on individual areas of the system without spending enough time understanding how the company worked across departments.
“There was also a lack of understanding of our business processes and how to implement them the correct way in BC. I don’t think the consultants asked enough questions of us to truly understand the process.”
The company knew its business. But this was its first experience moving inventory into an ERP environment. The team could explain what it did, but it needed its implementation consultants to ask the right questions, identify where processes intersected, and explain how those processes should work in Business Central.
“For us, moving inventory to an ERP was a new experience, and honestly, we didn’t know what we didn’t know.”
That is where good ERP consulting matters. A consultant should not simply ask a client how it wants the system configured. The consultant has to understand what the business is trying to accomplish, challenge assumptions when needed, and help determine whether the system, the process, or both should change.
The warning signs appeared before go-live
For Debbie, one of the clearest signs that something was wrong came when the implementation date had to be moved for a second time.
“Clearly there was a disconnect between the consultants and the business and both were frustrated with each other.”
The company also went through several project managers. Instead of feeling that one person was guiding the implementation, maintaining the timeline, and keeping everyone aligned, Debbie felt the business had to take on much of that responsibility itself.
“I felt like we had to lead a lot of the communication and processes to keep moving forward.”
The company ultimately went live with its original partner. But going live did not resolve the underlying process gaps. The confusion, limited training, and inconsistent communication followed the team into daily use of Business Central.
Going live is not the same as achieving process alignment
An ERP can be technically live while the business is still struggling to use it effectively.
Users may be able to enter orders, receive inventory, post transactions, and run reports. But if they do not understand how one step affects the next, they may still rely on workarounds, spreadsheets, and manual checks.
Debbie expected the implementation team to understand the manufacturer’s processes, identify missing connections, recommend how Business Central should support the company, and train the team on more than which buttons to select.
Instead, she felt too much of the system design had been directed by people who were still learning how an ERP worked.
“There were few questions or concerns from their side. They just did what we said, and we had no idea how the system really worked.”
That statement gets to the heart of many post-go-live Business Central problems. Implementing exactly what a client asks for is not always the same as implementing what the client needs.
If an implementation recreates an old process without first understanding why the process exists, the company can carry old problems into new technology. It may also introduce new gaps where operations, inventory, and accounting fail to connect.
At ECC, that is why we believe the order matters: Process. Technology. Automation. In that order.
How a Business Central Second Opinion identified the real gaps
When ECC stepped in after go-live, we did not assume the manufacturer needed a reimplementation. We also did not begin by changing configurations simply because the team was frustrated.
The first step was to validate the existing Business Central setup and understand the business processes it was supposed to support. That meant asking questions such as:
· How does inventory actually move through the company?
· Where does operations hand off to accounting?
· What financial impact should result from each operational transaction?
· Which processes were carried forward from QuickBooks or other previous ways of working?
· Which processes still made sense, and which needed to change?
· Where could Business Central simplify a process, improve control, or eliminate a workaround?
· Where did one department’s actions create confusion or unexpected results for another?
That changed the conversation from “How do we fix this screen?” to “How should this process actually work from beginning to end?”
“You have taken the time to review our processes, give advice on how to possibly improve them and how to use BC effectively and efficiently.”
That is what a Business Central Second Opinion should accomplish. It should identify the root cause before prescribing the fix. Sometimes the root cause is configuration. Sometimes it is process design, training, data, project decisions, or a lack of ownership. Often, the problem is the connection between several of those areas.
What process alignment looks like after go-live
For Debbie, the most immediate difference was communication.
“Communication is a complete 180!”
But process alignment requires more than faster responses. It requires listening, asking questions, understanding why the business works the way it does, and being willing to recommend a better approach when Business Central can support the goal more effectively.
“I feel like you were willing to listen and help evaluate and understand the business processes we use, because yes, some of ours are a little different, and help implement and train on better ways of using the system.”
Process alignment does not mean forcing every company into a generic best practice. It means separating true business requirements from habits inherited from an old system, then designing a process that connects people, operational activity, and financial results.
For this consumer products manufacturer, that meant looking at Business Central as one connected business system rather than a collection of separate operational and accounting functions.
Rebuilding trust in Business Central after go-live
One of the most damaging outcomes of a difficult implementation is loss of trust in the system.
When users do not understand why Business Central produces a result, they begin protecting themselves from it. They maintain spreadsheets, double-check transactions outside the ERP, create workarounds, and delay decisions while someone verifies the data. That is not just a training issue. It is a business-process issue.
Rebuilding trust requires users to understand what happens in the system, why it happens, and how their part of the process affects everything downstream.
“I appreciate the time that has been given to us to make sure we know how to use the system and be able to TRUST the system we are using.”
Debbie says that understanding has helped restore confidence in both Business Central and the support available to the team.
“I definitely feel more confident in the system, knowing I have support if needed.”
That confidence matters just as much as the technical corrections. A system only creates value when the people using it understand and trust the processes behind it.
Can a Business Central implementation be rescued after go-live?
Yes. A company can be live on Business Central and still need implementation rescue, recovery, or post-go-live process realignment. Going live does not mean every configuration, process, or training decision was correct. But post-go-live problems do not automatically mean the company needs to replace Business Central or start over with a new implementation.
The right first step is to identify what is already working, validate the existing configuration, and determine whether the real problem is setup, process design, training, data, or the way those pieces were brought together.
In this case, ECC’s role was specifically post-go-live. We validated the configuration, helped identify where business processes were out of alignment, and worked with the team to better connect operations, inventory, accounting, and financials.
For companies searching for Business Central implementation rescue, a Second Opinion can provide the diagnosis needed before committing to a reimplementation, partner change, or major system redesign.
A Business Central Second Opinion does not always mean starting over
The manufacturer is still working through its Business Central journey, and Debbie is honest about that.
“We still have a way to go, but I don’t know where we would be if we didn’t have you to support us. Probably still in Quickbooks only.”
A Second Opinion is not a promise that someone can arrive and instantly erase the effects of a difficult implementation. It is a structured way to step back, understand what happened, and create a better path forward.
That means asking more useful questions:
· Are operations, inventory, accounting, and financial reporting actually aligned?
· Does inventory flow through Business Central the way the business operates?
· Do users understand what happens after they post a transaction?
· Were processes intentionally designed, or simply recreated from the prior system?
· Is the configuration wrong, or is the process itself causing the problem?
· Does the team trust the information coming from the system?
Those questions go beyond “Is Business Central working?” They reveal whether Business Central is working for the business.
The client experience that shaped ECC’s Business Central Second Opinion
This engagement helped shape what became ECC’s Second Opinion for Business Central.
The manufacturer did not come to ECC asking for a packaged assessment. The company was already live and needed help understanding why the system, the processes, and the results were not working together as expected.
As we validated the existing configuration, reviewed workflows, and connected operational activity to accounting outcomes, a repeatable need became clear. Companies struggling after go-live often know something is wrong, but they do not know whether the root cause is configuration, process design, training, data, or decisions made during implementation.
ECC created the Second Opinion for Business Central to answer that question before a company commits to another implementation, a partner change, or more disconnected fixes. It starts with the business process, validates how Business Central supports it, and identifies the right path forward.
Before you replace Business Central, understand the process
When a Business Central implementation is struggling, it is easy to assume the software is the problem. Sometimes it is. But sometimes Business Central is doing exactly what it was configured to do. The real problem is that the technology, the people, and the business processes were never fully aligned.
That is what ECC’s Second Opinion for Business Central is designed to uncover.
We look across the entire process, not just at individual screens, features, or departments. We validate the system setup. We examine how operational decisions become financial transactions. We identify where the process and the technology have fallen out of alignment. Then we help determine what needs to change.
Because Business Central should not dictate how your business operates. And a new ERP should not simply recreate everything you did in your old system.
The goal is to understand the business first, design the right process, and then make the technology support it.
Process. Technology. Automation. In that order.
Is your company live on Business Central but still struggling with disconnected processes, workarounds, or a lack of trust in the system?
Comments