The vendor's testers can confirm that new software works as it was built. Only your own team can confirm that it works the way your business actually runs. That second check is user acceptance testing, or UAT, and it is the stage most often rushed: a manager clicks through a demo for an hour, signs, and the real problems surface in the first billing cycle.
This guide explains how to plan UAT for business software: who should test, what to prepare, how to write scenarios from daily work, how to test migrated data, how to log issues, and when it is safe to sign off.
Quick answer: User acceptance testing is when the people who will use new software test it with realistic data and scenarios before go-live. Choose testers from each department, write scenarios from daily work including exceptions, test on a staging copy loaded with your migrated data, log every issue with steps and severity, retest the fixes, and sign off only against acceptance criteria agreed in advance.
What UAT is, and what it is not
UAT is not the vendor's quality assurance, not a demo, and not training, although it doubles as early training for your testers. The difference matters because each stage answers a different question.
| Point | Vendor QA testing | User acceptance testing |
|---|---|---|
| Who tests | The vendor's testers | Your staff who will use the software |
| Question answered | Does it work as specified? | Does it work for our business? |
| Data used | Test data | A copy of your real, migrated data |
| Output | Defect reports and test results | A signed go-live decision |
What to prepare before UAT starts
Most UAT problems are planning problems. Have these ready before the first tester logs in:
- Named testers: one or two people from each department, including the staff who do the work, not only their managers. Block time in their calendars.
- A scenario list: written from your daily operations, mapped to the agreed requirements.
- A staging environment: a separate copy of the software loaded with migrated data, so testing cannot damage live records.
- Test accounts for every role: so testers check what each role can and cannot see.
- An issue log: a shared tracker or spreadsheet with fixed columns.
- Severity definitions and exit criteria: agreed with the vendor before testing, not argued about after.
- A schedule: at least one full test round and one retest round after fixes.
How to write UAT scenarios from daily work
A scenario is a short, real piece of work with an expected result. Write each one with an ID, the role, the steps, the expected result, and columns for the actual result and pass or fail. Good scenarios come from what your staff did last week. For example:
- Raise a GST invoice for a customer in another state with two items at different tax rates, and check that IGST is applied instead of CGST and SGST.
- Record one part payment against two invoices, then check that the outstanding report shows the correct balance for each.
- Log in as a branch user and try to open another branch's orders. The expected result is that access is refused.
- Return part of a dispatched order and check stock, the credit note and the customer ledger.
- Print an invoice and a delivery challan on the actual printer your counter uses.
- Run the month-end stock report and compare it with the closing figures from your old system.
Include negative tests: wrong inputs, missing fields, duplicate entries and actions a role should not be allowed to perform. Software that accepts bad data quietly will fill your reports with errors.
Test with your real data, especially migrated data
Migrated data is where many go-lives go wrong. Customer balances, opening stock, open orders and item masters move from spreadsheets or old software, and small errors in mapping create large differences. During UAT, ask your accounts team to reconcile totals as of the cut-off date: customer and vendor outstanding, stock quantity and value by location, and open orders. Every difference should be explained or fixed before sign-off.
For billing, accounts and stock, consider a short parallel run in which transactions are entered in both systems and the results compared. It doubles the work, so keep it short and limit it to the modules where errors are costly.
Log issues properly and agree on severity
Each issue needs the screen, the steps to repeat it, the expected and actual result, a screenshot, the tester and the date. Then classify it:
- Critical: blocks a core process or produces wrong financial or stock figures.
- Major: a real problem, but a workaround exists.
- Minor: cosmetic, such as a label or alignment.
- Change request: the software works as specified, but you now want it to work differently.
Keep change requests separate from defects. Defects are fixed within the project. Change requests alter scope, so they are estimated and approved on their own, otherwise UAT never ends and nobody knows why the timeline moved.
Sign-off and go-live readiness
Agree the exit criteria before testing begins. A practical set: no open critical issues, every major issue has a workaround and a fix date, all scenarios have been run, the data reconciliation is signed by accounts, users are trained and a rollback plan exists. Choose a cut-over date away from month-end closing, GST return filing dates and the financial year close, when your accounts team has the least spare time.
Mistakes to avoid
- Only managers test, so daily shortcuts and edge cases are missed.
- Testing with dummy entries like “test123” instead of real customers and items.
- Signing off under deadline pressure with critical issues still open.
- Skipping reports, print formats and email or SMS notifications.
- Not testing on the actual devices: warehouse phones, barcode scanners and thermal printers.
How EthicsComputer can help
In our business software development projects, UAT follows sprint previews you test as the build progresses, and the deliverables include data migration scripts with a verification audit. Standard business software is typically delivered in 6–10 weeks, with UAT planned into that schedule. After go-live, support and maintenance covers fixes and enhancements, and business process automation can take over repetitive steps your team still does by hand. Explore the full scope of custom business software to see what is included.
Still running billing, stock or approvals on spreadsheets?
Tell us which processes cause the most rework, and we will suggest how to replace them and how the testing would be planned.
About the author
Vinay Grover founded EthicsComputer in Rohtak, Haryana in 2018 and leads its cybersecurity, software and AI work for clients across India and abroad. EthicsComputer is ISO 9001, ISO/IEC 27001 and ISO 20000-1 certified.