Business Central User Acceptance Test Script Template
User acceptance testing is when key users prove that Business Central supports their real processes. This template produces a script with test data, steps, expected results, a defect log and sign-off you can print or share.
Fill in
Business Central User Acceptance Test Script Template
UAT Script: Order to cash
Project: Northfield BC Implementation Environment: Sandbox UAT Tester: J. Rivera, Sales Date: 2027-02-15 Overall result: Not run
Test data
Customer C-10020, item ITM-4550, location MAIN, quantity 25.
Test steps
| Step | Action in Business Central | Expected result | Actual result | Pass/Fail |
|---|---|---|---|---|
| 1 | Create a sales quote for the customer and add item lines | Quote saved with correct prices and discounts | ||
| 2 | Convert the quote to a sales order | Order created, quote archived or closed | ||
| 3 | Release the order and post a warehouse or inventory shipment | Shipment posted, inventory reduced | ||
| 4 | Post the sales invoice | Invoice number assigned, customer ledger entry created | ||
| 5 | Apply a customer payment to the invoice | Invoice closed, bank ledger entry created | ||
| 6 | Check G/L entries and value entries | Amounts match posting setup |
Defect log
| ID | Step | Description | Severity | Owner | Status |
|---|---|---|---|---|---|
| D1 | |||||
| D2 |
Sign-off
The steps show an order to cash example. Replace them with steps for your chosen process and your own setup. Severity should follow your agreed defect definitions.
UAT planning help
Get a review of your test coverage and exit criteria before UAT starts. Optional.
Optional. The tool and every export work without this. No spam.
How to use it
Pick the process, name the tester and environment, and list the test data. Export the document, then edit the step rows for your configuration. Testers fill in the actual result and Pass/Fail columns while working in the sandbox, and log each defect with severity and owner. The process owner signs off when all critical steps pass.
Designing scripts that find problems
Test end to end, not screen by screen. Follow the document through the whole chain and check the ledger entries at the end, because posting setup errors surface only there. Use realistic data, including multiple lines, discounts, partial shipments, foreign currency and returns. Add at least one negative case per process, such as posting with a blocked item or exceeding a credit limit.
- Use named business users as testers, not the consultants
- Test with real user permissions, not a super user
- Check dimensions on every posted entry
Defects versus change requests
Agree early on the difference. A defect is a failure against an approved requirement or design. A change request is a new need discovered in testing. Mixing them delays go-live and creates disputes about fees. Record both in the log with a type, and schedule change requests separately.
Common mistakes
Running UAT on a poorly migrated dataset makes it hard to tell data issues from configuration issues. Use a recent trial migration. Another mistake is time-boxing UAT too tightly; plan at least two rounds so fixes can be retested. Finally, record evidence such as screenshots for critical steps to support sign-off.
Frequently Asked Questions
How many UAT scripts does a typical BC project need?
It depends on scope, but a mid-size manufacturing or distribution project often needs 20 to 60 scripts across finance, sales, purchasing, inventory and production. Prioritise high-volume and high-risk processes, then add exceptions.
Who should perform UAT?
Business users who run the process daily, supported by consultants who observe and log defects. Consultants should not press the buttons, because that hides usability and training gaps that real users will meet after go-live.
Which environment should I use?
A sandbox environment refreshed with recent migrated data and the final extensions. Do not test in production. Keep the configuration frozen during a test round, otherwise results are not comparable.
What counts as passing UAT?
Agree exit criteria before testing starts, for example all critical scripts pass, no open critical or high defects, and an agreed workaround for any medium defect. Record the criteria in your project plan and sign-off page.
Netray can help generate test scenarios and compare outputs between legacy and Business Central with private tooling. Ask if reconciliation is slowing your UAT.
Related Tools
Business Central Functional Design Document Template
Document a Business Central customisation, report or integration with requirement, standard behaviour, gap, design, test and sign-off sections.
Microsoft DynamicsBusiness Central Go-Live Cutover Plan Template
A cutover runbook for moving to Business Central: freeze, extract, load, reconcile, go/no-go decision, hypercare and rollback.
Microsoft DynamicsBusiness Central Implementation Statement of Work Template
A fill-in SOW for Business Central projects covering scope, phases, deliverables, assumptions, change control and acceptance.
More Microsoft Dynamics tools
See all- Business Central API v2.0 URL Builder
- Business Central Configuration Package Worksheet
- Business Central Permission Set Design Worksheet
- Business Central Year-End Close Checklist
- Business Central Posting Groups Setup Worksheet
- Business Central Data Migration Field Mapping Worksheet
- Business Central Chart of Accounts Mapping Worksheet
- Business Central License Cost Calculator
- Business Central Core Table Numbers Reference