Choosing an ERP system is not only about checking whether it has the right features. For Information Workers (IWs), the real question is whether the ERP helps them access information, complete daily tasks, collaborate across departments, and make decisions without unnecessary complexity. Information Workers are the business users who interact with business processes and depend on information to do their jobs, processing business data, creating reports, managing transactions and coordinating activities across teams.
Microsoft Dynamics 365 Business Central brings financial management, purchasing, sales, inventory, projects, warehouse operations and other business processes into one connected environment. But before selecting it as your ERP, the workflows your Information Workers actually perform every day are what should be tested. A business central ERP decision made on a feature list alone tends to surface problems only after go-live, when the people doing the work discover that a routine task takes eleven clicks instead of three.
A practical evaluation involves representative users from Sales, Finance, Purchasing, Warehouse and Production not only an IT-led product demonstration. This article sets out what those users should test, how to structure the testing, and how to judge the results.
Why Information Worker Testing Matters More Than a Feature Checklist
Almost every mid-market ERP on the shortlist can post a sales invoice. The difference between systems shows how much effort that posting takes, how easily an error is traced, and whether the person doing it can answer a customer’s question without leaving the screen.
Feature checklists measure capability. Information Worker testing measures friction. Friction is what drives the outcomes that determine ERP success or failure:
- Users building shadow spreadsheets because the system’s own reports are hard to reach
- Month-end close taking longer than it should because reconciliation requires manual export
- Data entry errors caused by screens that do not match the real-world process
- Low adoption, which quietly undermines the entire business case
This is why business central erp testing should be scenario-based rather than feature-based. Instead of asking “does it support approval workflows?”, ask a purchasing clerk to raise a requisition, route it for approval, convert it to a purchase order and receive it partially then watch how long it takes and where they hesitate.
How to Set Up a Realistic Business Central Evaluation
A meaningful business central evaluation needs three things in place before the first test is run.
- A sandbox environment with your own data.Dynamics 365 Business Central provides sandbox environments alongside production, and the demonstration company (CRONUS) is useful for orientation only. Load a representative slice of your own chart of accounts, item master, customers,vendors and open transactions. Users cannot judge usability against unfamiliar data.
- Real user roles, not administrator access.Assign the permission sets each person would actually have.A process that feels smooth with full administrator rights can break down a user restricted to their own department, and role centers differ significantly by role.
- Written test scripts with pass/failscriteria.Each scenario should state the starting condition, the steps, the expected result and the measure — number of clicks, time taken, whether the user needed help. Without this, testing produces opinions rather than evidence.
Allow two to three weeks of part-time testing rather than a single-day workshop. Users need to hit the second and third day of a process before they can say whether they could live with it.
What Finance Users Should Test
Finance is usually where ERP friction is most expensive. The scenarios worth running in Dynamics 365 Business Central include:
- Full invoice-to-cash cycle — post a sales invoice, apply a partial payment, handle a short payment and issue a credit memo
- Bank reconciliation — import a bank statement and reconcile it, including the handling of unmatched lines
- Dimensions — post transactions with department and project dimensions, then report them. Dimensions replace the need for a bloated account code structure, and how well users grasp them is a strong predictor of reporting success
- Financial reporting — build a comparative P&L and balance sheet using the financial reporting (row and column definition) tools, and export to Excel
- Month-end close — run the closing steps for a period, including accrual entries and fixed asset depreciation
- Multi-currency and tax — post a foreign currency invoice and check revaluation, plus your local tax treatment
The question to answer is not whether these are possible. It is whether your accountant can do them unaided after training, and whether the audit trail satisfies your auditors.
What Sales and Customer Service Users Should Test
Sales users judge an ERP on speed of answer. Test:
- Creating a quote, converting it to an order, and shipping and invoicing in stages
- Checking item availability and promised delivery dates from within the sales order
- Applying customer-specific pricing, discounts and price groups
- Viewing a customer’s full history — open orders, ledger entries, credit limit and overdue balance — from one place
- Handling a return or a replacement shipment
- Working from Outlook, where the Business Central add-in surfaces customer and document context alongside the email thread
That last point matters more than it appears. Information Workers in sales roles spend their day in email; an ERP they must switch away from is an ERP they will use reluctantly.
What Purchasing, Inventory and Warehouse Users Should Test
This is where a Business Central ERP implementation most often runs into surprises, because physical processes are unforgiving of a poor fit.
Purchasing Scenarios
- Requisition to purchase order, including approval routing
- Partial receipt, over-receipt and receipt of the wrong item
- Three-way match between order, receipt and vendor invoice
- Vendor pricing and blanket orders
Inventory Scenarios
- Item setup with your costing method (FIFO, LIFO, average, standard or specific) and confirm the method matches your accounting policy, because changing it later is disruptive
- Item tracking with lot or serial numbers, if you need traceability
- Physical inventory count and posting the variance
- Transfers between locations
- Unit of measure conversions, including purchase in one unit and sale in another
Warehouse Scenarios
- Test both the basic and advanced warehouse configurations. Business Central supports a simple location-only model as well as directed put-away and pick with bins, and the gap between them is large in both capability and setup effort
- Receiving, put-away, pick and ship as separate warehouse documents
- Barcode scanning or mobile device use, if that is part of your operation
Ask the warehouse team to test standing up, at the pace they actually work. A screen that reads well on a desktop can fail on a scanner in a cold store.
What Manufacturing Users Should Test
If you produce or assemble, test the production side thoroughly:
- Build a bill of materials and a routing for a real product, including a multi-level BOM
- Release a production order, consume components, post output and close it
- Run the planning worksheet or requisition worksheet and review the suggested supply
- Check capacity against work and machine centers
- Compare standard cost to actual cost on a finished order and explain the variance
- Test assembly orders, which suit kit-style products better than full production orders
The test that reveals most is a deliberately imperfect one: post a production order where a component ran short and a substitute was used. Real shop floors are full of these, and how the system absorbs them tells you a great deal.
What Every Information Worker Should Test, Regardless of Department
Some capabilities cut across all roles and deserve their own place in your business central erp testing plan.
|
Area |
What to test |
Why it matters |
| Search and navigation | Find a record, a page and a report using the Tell Me search | Determines how fast a new user becomes productive |
| Personalisation | Add, remove and move fields on a card and list page | Users who can shape their own screens adopt faster |
| Excel integration | Open a list in Excel, edit it and publish it back | Most finance and operations users live partly in Excel |
| List analysis | Filter, group and pivot a list using the analysis mode on list pages | Reduces dependence on IT for routine questions |
| Approval workflows | Route a document for approval and reject it | Controls only work if they are usable |
| Notes and links | Attach a document, note or link to a record | Everyday collaboration, easily overlooked in demos |
| Teams and Outlook | Share a record in Teams and view details from Outlook | Where cross-department coordination actually happens |
| Reporting and Power BI | Run built-in reports and view a Power BI dashboard in context | Separates a working system from a data entry system |
| Copilot features | Test the AI assistance available in your region and licence | Useful, but verify the output rather than assume it |
| Mobile and browser | Complete a task on a tablet or phone | Relevant for approvers and field staff |
| Performance | Open a large list and post a batch during business hours | Slowness is the most common adoption complaint |
A Business Central ERP Testing Checklist You Can Use
Run each scenario and score it. Keep the scoring simple so that comparison across departments stays honest.
- Could the user complete the task without help? (Yes / With guidance / No)
- How long did it take compared with the current process?
- How many workarounds or manual steps were needed?
- Did the result match the expected outcome exactly?
- Would the user accept this as their daily process? (Yes / With changes / No)
Log every gap in one register, then classify each entry into four categories:
- Configuration — solved by setup, no cost beyond time
- Training — the system does it, the user did not know how
- Extension or app — needs an AppSource solution or custom development
- Genuine limitation — the system does not do this and will not
That fourth category is the only one that should influence your ERP decision. Confusing a training gap with a genuine limitation is the most common error in ERP selection, and it disqualifies otherwise suitable systems.
How to Read the Results of Your Business Central Evaluation
Expect gaps. Every ERP evaluation produces them, and a shortlist with no gaps usually means the testing was too shallow. What matters is their distribution.
Gaps concentrated in configuration and training point to a good fit with implementation work ahead. Gaps concentrated in genuine limitations, particularly in a core revenue process, are a warning. And a small number of limitations in a peripheral process is normally acceptable the cost of customizing around it is usually lower than the cost of choosing a system that fits that one process but fits nothing else as well.
Weight the results by transaction volume, not by how strongly the objection was voiced. A friction point on a process to run two hundred times a day matters far more than one on a monthly task, however loudly the latter is raised.
Conclusion
The value of an ERP is realized through the people who use it every day. A business central evaluation that focuses only on features tells you what the software can do; testing with your own Information Workers, on your own data, in the processes they run tells you what your organization will get.
Test the ordinary tasks and the awkward exceptions. Involve users from every department. Score the results, classify the gaps and weight them by volume. Done this way, choosing Dynamics 365 Business Central or deciding against it becomes a decision you can defend with evidence rather than a demonstration you were impressed by.
Frequently Asked Questions
What does IW mean in Business Central?
IW stands for Information Worker — a business user who works with information and business processes as part of their job, such as an accountant, sales coordinator, purchasing clerk, warehouse supervisor or production planner. In Microsoft licensing terms, these users are typically covered by Business Central Essentials or Premium licenses, as distinct from Team Members, who have limited read and light-write access.
How long should a Business Central evaluation take?
For a mid-sized organization, two to four weeks of structured, part-time testing across departments is reasonable. Less than a week rarely surfaces real usability issues; more than six weeks tend to stall the decision without adding information.
Can we test Business Central with our own data before buying?
Yes. A trial or sandbox environment can be loaded with a representative subset of your master data and open transactions. Testing your own data rather than the demonstration company is what makes the exercise meaningful.
What is the difference between Business Central Essentials and Premium?
Essentials covers finance, sales, purchasing, inventory, projects, and basic warehouse functionality. Premium adds manufacturing and service management. Confirm which license your tested scenarios require, because a process demonstrated on Premium may not be available to Essentials users.
Who should be involved in business central ERP testing?
The people who will use the system daily, one or two from each functional area, plus a finance lead and someone able to make decisions on process change. Testing that involves only IT and management consistently misses the friction that determines adoption.
