How Should Manufacturers Test Business Central Before Go-Live?
A successful Business Central test doesn't just prove the software works. It proves your manufacturing business can work in the software.
That distinction matters more than many organizations realize.
During an ERP implementation, it is easy to focus on whether individual functions operate correctly. Can someone create a sales order? Can purchasing receive inventory? Can production post output? Can finance generate a report?
Those are important questions.
But they do not necessarily tell you whether the business is ready.
Imagine a manufacturer preparing to move from Microsoft Dynamics GP to Microsoft Dynamics 365 Business Central. Every department has completed its assigned tests. The results look encouraging.
Then someone asks a simple question:
What happens when a customer changes an order after production has started?
Suddenly, the conversation involves planning, inventory, production, purchasing, customer service, and finance.
That is where meaningful manufacturing ERP testing begins.
I believe executives should approach user acceptance testing as a business-readiness exercise, not merely a technical milestone.
The goal is to establish confidence that people, processes, data, and systems can work together when Business Central becomes the operational foundation of the business.
Table of Contents
What Is UAT in a Business Central Migration?
Why Is Manufacturing ERP Testing Different?
How Should Manufacturers Test End-to-End Processes?
Why Should Manufacturers Test Exceptions?
How Should Roles and Security Be Tested?
What Financial and Operational Results Should Be Validated?
Who Should Participate in Business Central UAT?
How Do You Know You Are Ready for Go-Live?
What Should Executives Ask Before Approving Go-Live?
Testing for Business Confidence, Not Just Software Performance
Frequently Asked Questions
What Is UAT in a Business Central Migration?
User acceptance testing (UAT) is the process of having business users validate that Microsoft Dynamics 365 Business Central supports the organization's actual operating requirements before go-live.
It goes beyond confirming the system is configured correctly.
Technical testing helps establish whether software functions, integrations, and data processes behave as designed. UAT asks whether those functions support the way the business needs to operate.
For a manufacturer, that means testing activities such as planning production, purchasing materials, recording consumption, completing manufacturing orders, shipping products, and reviewing financial results.
The distinction is important.
A consultant may successfully demonstrate how to post a production order. But can a production supervisor complete that same process using realistic information, under normal operating conditions, without relying on someone to guide every step?
That is a different level of confidence.
I often frame the question this way:
Are we testing what the system can do, or what our people need to accomplish?
Both matter. But the second question should drive user acceptance testing.
Why Is Manufacturing ERP Testing Different?
Manufacturing ERP testing must validate connected operational processes because decisions made in one department affect inventory, production, fulfillment, costing, and financial reporting elsewhere.
In a manufacturing environment, transactions rarely exist in isolation.
A sales order creates demand. Demand influences purchasing and production planning. Production consumes materials and capacity. Finished goods move into inventory. Shipping fulfills customer commitments. Those activities ultimately affect financial results.
Microsoft's Business Central manufacturing documentation describes how production BOMs, routings, work centers, production orders, inventory, and costing support manufacturing operations.
The migration challenge is ensuring those connected activities work for your business.
Consider a manufacturer that builds products to order.
A customer requests a delivery date. The planner checks material availability and production capacity. Purchasing identifies a missing component. The production manager adjusts the schedule.
If each department tests only its own transactions, the organization may miss problems in how information passes between them.
A purchasing transaction might post successfully while the planner still lacks the information needed to make a reliable commitment.
This is why manufacturing DNA matters.
A make-to-stock manufacturer may emphasize replenishment, inventory availability, and production efficiency.
A make-to-order manufacturer may need stronger validation of demand-driven planning and order-specific commitments.
An engineer-to-order business may need to test revisions, changing requirements, and project-specific production processes.
Mixed-mode manufacturers may need to test several operating models.
No single manufacturing UAT script adequately represents every business.
Testing must reflect how the manufacturer actually makes, moves, and accounts for its products.
How Should Manufacturers Test End-to-End Processes?
Manufacturers should test complete business workflows in Business Central, following transactions from initial demand through production, fulfillment, costing, and financial posting.
A useful manufacturing test scenario follows this sequence:
Demand → Planning → Purchasing → Material Availability → Production → Consumption → Output → Warehouse → Shipment → Costing → Financial Posting
This is not necessarily one uninterrupted transaction. It is a connected business process involving multiple departments and controls.
Effective Business Central user acceptance testing follows the complete manufacturing process, from customer demand and production planning through purchasing, manufacturing, warehousing, shipping, and financial reporting.
Start With Realistic Customer Demand
Begin with a representative sales order, forecast, or other demand signal.
Can the organization identify what to produce and when?
Does planning reflect available inventory, purchasing requirements, and production capacity?
Are customer commitments supported by information the business trusts?
Follow the Materials Into Production
Next, validate purchasing and material availability.
Can the team identify shortages? Can the team receive required materials and make them available for production? Are inventory locations and quantities accurate?
Then test production orders using appropriate bills of materials, routings, work centers, and expected output.
Microsoft's production order guidance explains how Business Central supports material consumption, production output, and production-related activities.
The specific processes available depend on the organization's Business Central configuration, licensing, and any extensions or connected manufacturing systems.
Continue Through Fulfillment and Finance
Testing should not stop when production is completed.
Can finished goods be received into inventory? Can warehouse personnel locate and ship the product? Does the customer order reflect the correct fulfillment status?
Most importantly, do the resulting inventory values, costs, and financial entries make sense?
A test that ends with a successfully posted production order may miss a problem that becomes visible only during shipment, invoicing, or financial reconciliation.
Test Across Departmental Boundaries
I would encourage manufacturers to select several representative products and orders rather than relying on one simple example.
Include high-volume products, complex assemblies, frequently purchased materials, and orders involving important customer requirements.
If the business operates multiple plants or warehouses, test the processes and differences that matter at those locations.
This is also where the previous article in our series becomes relevant.
In our recent article, “What Happens to Dynamics GP Integrations When Moving to Business Central?,” we discuss why manufacturers must understand the systems connected to their ERP.
Include those integrations in end-to-end testing.
A process is not fully validated if it works inside Business Central but fails when information must reach a warehouse management system, manufacturing execution system, or EDI platform.
Why Should Manufacturers Test Exceptions, Not Just Normal Transactions?
Manufacturing UAT should include the unexpected situations employees routinely manage, because these exceptions often reveal whether an ERP process is practical and resilient.
A perfectly planned production order helps demonstrate functionality.
It does not necessarily represent a typical manufacturing day.
Materials arrive late. Machines become unavailable. Customers change quantities. Production generates scrap. Inventory counts reveal discrepancies.
The real question is whether Business Central and the surrounding processes support an appropriate response.
Effective Business Central user acceptance testing includes real-world manufacturing exceptions such as material shortages, substitutions, scrap, rework, partial production, inventory corrections, and product returns.
Test Material Shortages and Substitutions
Suppose a production order requires a component that is not available.
Can the planner identify the shortage? Can purchasing respond? If an approved substitute is available, can the business follow its required approval and transaction process?
The objective is not simply to find a workaround.
The objective is to establish a controlled, repeatable way to manage the situation.
Test Scrap, Rework, and Partial Production
Imagine a production team starts an order for 100 units but completes only 85 acceptable units during the first shift.
Some materials have been consumed. Several units require rework. The remaining production will continue tomorrow.
Can the organization accurately record what happened?
Can supervisors understand the remaining work? Does inventory reflect the correct quantities? Are costs captured appropriately?
Business Central supports recording production consumption, output, and scrap through manufacturing processes, but the exact treatment of rework and other specialized scenarios may require configuration, process design, or additional functionality.
The test should validate the organization's approved approach rather than assume the system handles every scenario automatically.
Test Inventory Corrections and Returns
What happens when a physical count differs from the system quantity?
How does the business investigate and approve an adjustment?
What happens when a customer returns a manufactured product?
These scenarios involve operational decisions and financial consequences.
A successful test should confirm that employees understand both the system steps and the controls surrounding them.
If the organization tests only the ideal process, it may prepare for a manufacturing environment that does not exist.
How Should Roles and Security Be Tested?
Business Central UAT should confirm that employees can perform their assigned responsibilities while appropriate controls prevent unauthorized or inappropriate actions.
A process may work perfectly when tested by a system administrator.
That does not prove it will work for a warehouse employee, production planner, purchasing agent, or controller.
Each person needs access to the information and functions required for their role.
They should not necessarily have access to everything.
For example, a production employee may need to record output but should not automatically have authority to change financial setup.
A purchasing user may need to create purchase orders while certain approvals remain with management.
A controller needs access to financial information and appropriate posting controls.
During UAT, users should test with the roles and permissions they are expected to have after go-live.
This helps identify two different risks: employees who cannot complete essential work and employees who have more access than their responsibilities require.
For executives, this links operational readiness to internal control.
The objective is not merely convenience.
It is a system people can use efficiently without weakening the organization's governance.
What Financial and Operational Results Should Be Validated?
Manufacturers should verify that Business Central produces reliable inventory, production, costing, and financial information, not simply that transactions can be posted successfully.
For a CFO, this may be the most important part of UAT.
A manufacturing system can appear operational while producing information that leadership does not fully trust.
That creates a different kind of business risk.
Validate Inventory and Production Costing
Testing should include representative manufacturing cost scenarios.
Do material consumption, capacity, overhead, and finished-goods values behave as expected under the configured costing approach?
Are production variances understandable?
Can finance reconcile inventory and manufacturing-related entries with the general ledger?
Microsoft's inventory cost management guidance explains how Business Central manages inventory valuation, cost adjustment, and reconciliation.
The specific validation procedures should reflect the manufacturer's costing method and accounting policies.
Validate the Reports Leaders Depend On
Consider the questions executives ask every week.
What orders are late? What materials are short? What inventory is available? Where are production costs increasing? What is happening to gross margin?
If those answers depend on reports, dashboards, or connected analytics tools, those outputs belong in the test plan.
A report that opens successfully is not necessarily accurate.
Users need to validate the underlying figures, filters, timing, and business definitions.
Test Period-End Responsibilities
Finance should also validate representative closing activities and reconciliations.
That does not mean every month-end activity must be completed during every test cycle.
It means the organization should have evidence that its critical financial processes are understood and can be performed using the new environment.
The CFO should not discover after go-live that an essential reconciliation depends on an untested process.
Who Should Participate in Business Central UAT?
Business process owners should lead user acceptance testing, and the people responsible for executing and managing the work after go-live should perform it.
IT and the implementation partner are essential participants.
But they should not be the only people determining whether testing has succeeded.
The right participants typically include operations and plant leadership, production planning, purchasing, warehouse personnel, customer service, finance, IT, process owners, and selected super users.
Each group brings a different perspective.
The planner understands what happens when demand changes.
The warehouse supervisor understands receiving and picking exceptions.
The controller understands reconciliation and financial controls.
Customer service understands the consequences of inaccurate order status.
Together, they can validate processes that no single department sees completely.
I also believe testing should create opportunities for employees to challenge assumptions.
If someone says, “That is not how we actually handle this situation,” the response should not be to dismiss the concern because the configured process technically works.
That comment may reveal a training need, an uncommunicated process change, or a genuine gap in the solution.
Good UAT creates room for those conversations before the business depends on the new system.
How Do You Know You Are Ready for Go-Live?
A manufacturer is ready for Business Central go-live when critical processes have been validated, users can perform their responsibilities, financial and operational results are acceptable, and accountable business leaders have reviewed and explicitly accepted unresolved risks.
That does not require eliminating every minor issue.
It does require clarity about what remains unresolved.
I would encourage executive sponsors to look beyond a simple percentage of completed test scripts.
A report showing 95% of tests passed may sound encouraging.
But what if the remaining 5% includes production consumption, customer shipping, or inventory reconciliation?
The business impact matters more than the percentage.
A practical readiness review should examine:
- Critical processes: Have essential order-to-cash, procure-to-pay, manufacturing, warehouse, and financial workflows passed?
- Exceptions: Have realistic disruptions and corrections been tested?
- People: Can users perform their jobs with appropriate access and training?
- Information: Are inventory, costing, reporting, and financial results acceptable?
- Integrations: Have business-critical connections been validated end-to-end?
- Open issues: Is every significant issue assigned an owner, severity, resolution plan, and business impact?
- Business approval: Are accountable process owners prepared to approve readiness or explicitly accept documented residual risks?
Where a critical issue remains, leadership should understand the operational consequence and whether a tested contingency exists.
A go-live date is important.
But the calendar should not become the primary measure of readiness.
What Should Executives Ask Before Approving Go-Live?
Executives do not need to review every test script. They do need enough evidence to make an informed decision about operational risk.
I would recommend asking these questions in the final readiness review:
- Have we tested complete manufacturing processes, not just individual transactions?
- Have employees tested realistic exceptions, including shortages, scrap, partial production, and inventory corrections?
- Have finance and operations validated inventory, costing, and reporting outcomes?
- Have the people who will use Business Central actually performed the tests?
- Have we tested the integrations that support production, fulfillment, and customer commitments?
- Which unresolved issues could disrupt the business, and who has accepted those risks?
- Are business process owners comfortable confirming that their teams can operate?
I would pay particular attention to that final question.
If the implementation team says the system is ready, but the production manager, warehouse supervisor, or controller is hesitant, leadership should understand why.
That hesitation may identify an important issue before it becomes an operational problem.
Testing for Business Confidence, Not Just Software Performance
A Dynamics GP to Business Central migration is an opportunity to modernize how a manufacturing business operates.
But modernization only creates value when the organization can use the new environment with confidence.
That confidence comes from preparation, realistic testing, clear ownership, and honest conversations about readiness.
At Liberty Grove Software, we connect technology decisions to the manufacturing processes and business outcomes they support.
That means looking beyond whether a transaction posts successfully.
We want manufacturers to understand whether their people can plan production, manage materials, respond to disruptions, fulfill customer commitments, and trust the financial information that follows.
UAT is not proof that Business Central works. It proves your business can work in Business Central.
If your organization is planning a move from Dynamics GP, this is the standard I would encourage you to use.
The next article in our series, “What Should Manufacturers Expect During a Business Central Go-Live?,” will explore what happens when testing gives way to the actual business transition, including cutover, production continuity, and stabilization.
Go-live should not be the first time your organization discovers how its new ERP environment behaves under real operating conditions.
Planning your Dynamics GP to Business Central migration?
Talk with Liberty Grove Software about preparing your manufacturing processes, people, and systems for a successful transition.
Frequently Asked Questions
1. What is UAT in a Business Central implementation?
User acceptance testing (UAT) is the process in which business users verify that Microsoft Dynamics 365 Business Central supports the organization's actual workflows and requirements. For manufacturers, it includes validating production, purchasing, inventory, warehouse, fulfillment, costing, and financial processes before go-live.
2. How should manufacturers test Business Central?
Manufacturers should test complete end-to-end workflows using realistic products, orders, users, and operating conditions. Testing should follow transactions from demand and planning through purchasing, production, inventory, shipment, costing, and financial posting. It should also include exceptions, integrations, permissions, and reporting.
3. Who should participate in ERP user acceptance testing?
ERP UAT should involve business process owners and representative users from manufacturing, operations, planning, purchasing, warehousing, customer service, finance, and IT. Implementation partners should support testing, but business leaders should own acceptance of their critical processes.
4. What manufacturing processes should be tested before go-live?
Critical manufacturing test scenarios typically include demand planning, material purchasing, inventory availability, production orders, BOMs and routings, component consumption, production output, scrap, warehouse movements, shipping, costing, and financial reconciliation. The exact scope depends on the manufacturer's operating model and configured systems.
5. Why should manufacturers test exception scenarios?
Exception testing demonstrates whether the organization can respond appropriately when normal operations change. Material shortages, substitutions, partial production, scrap, rework, inventory corrections, and returns can expose process gaps that routine transactions do not reveal.
6. How do you know Business Central is ready for go-live?
Business Central is ready for go-live when critical business processes have passed testing, users can perform their responsibilities, essential integrations and reports are validated, financial outcomes are acceptable, and business leaders have reviewed unresolved risks. Readiness should be based on business impact and evidence, not simply the percentage of completed test scripts.
About Andrew Good
Andrew Good, CEO, Liberty Grove Software
Andrew Good, CEO of Liberty Grove Software, a leader in digital transformation, directs the company with strategic insights that deliver impactful results. With over two decades of expertise in Microsoft technologies, Andrew has guided businesses through digital transformation across manufacturing, finance, and healthcare.
Andrew's extensive knowledge comes from personal experiences with various companies. His hands-on operational knowledge comes from Engineering, Maintenance, and operational roles at Unilever and Sony Music. Fourteen years of working with Microsoft Dynamics BC/NAV follows successful projects in ERP, Computerized Maintenance Management Systems (EAM), and quality systems.
His passion for technology is matched by his love for sailing, which inspires his leadership. Andrew parallels the precision of navigating the seas and the challenges of steering a successful company. Under his leadership, Liberty Grove Software thrives, offering tailored solutions to empower clients and optimize operations with innovative Microsoft-based systems.
