# Epicor UAT Test Script Worksheet > Source: https://netray.co/tools/epicor-uat-test-script-worksheet > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: Free Tools ## Short answer An editable UAT script for Epicor with expected results, tester, status and defect counts. Track pass rate and export to Excel. ## Category epicor ## Erp Epicor Kinetic ## Audience - Epicor consultant - Project manager - Process owner ## Tool **Kind:** worksheet **Mode:** editable **Columns:** #### Test ID **Key:** id **Type:** text #### Process **Key:** process **Type:** select **Options:** - Quote to cash - Procure to pay - Make to stock - Make to order - Inventory - Financial close - Reporting #### Step **Key:** step **Type:** text #### Expected result **Key:** expected **Type:** text #### Tester **Key:** tester **Type:** text #### Status **Key:** status **Type:** select **Options:** - Not run - Pass - Fail - Blocked #### Passed (1/0) **Key:** passed **Type:** number #### Defects **Key:** defects **Type:** number #### Date run **Key:** run **Type:** date **Rows:** #### Enter sales order for stock part **Id:** QC-01 **Process:** Quote to cash **Expected:** Order saves, price from price list **Tester:** Sales rep **Status:** Pass **Passed:** 1 **Defects:** 0 **Run:** 2026-11-03 #### Ship order and invoice **Id:** QC-02 **Process:** Quote to cash **Expected:** Shipment posts, invoice created **Tester:** Shipping **Status:** Fail **Passed:** 0 **Defects:** 1 **Run:** 2026-11-03 #### Create PO and receive **Id:** PP-01 **Process:** Procure to pay **Expected:** Receipt updates on-hand quantity **Tester:** Buyer **Status:** Pass **Passed:** 1 **Defects:** 0 **Run:** 2026-11-04 #### Release job and report labor **Id:** MO-01 **Process:** Make to order **Expected:** Labor posts to operation **Tester:** Supervisor **Status:** Not run **Passed:** 0 **Defects:** 0 **Run:** 2026-11-05 #### Post GL transactions and run trial balance **Id:** FC-01 **Process:** Financial close **Expected:** Balances agree to subledgers **Tester:** Controller **Status:** Blocked **Passed:** 0 **Defects:** 0 **Run:** 2026-11-06 **Totals:** #### Test cases **Key:** id **Agg:** count **Format:** integer #### Passed **Key:** passed **Agg:** sum **Format:** integer #### Open defects **Key:** defects **Agg:** sum **Format:** integer **Summary:** #### Pass rate **Key:** rate **Expr:** sum_passed / count * 100 **Format:** percent **Primary:** true #### Defects per test case **Key:** dpt **Expr:** sum_defects / count **Format:** decimal **Notes:** Set Passed to 1 when status is Pass so the pass rate updates. Write steps in business language, use real customers, parts and jobs from your data, and have each tester sign off their own area. ## Content **Intro:** User acceptance testing is where an Epicor project is won or lost. This worksheet keeps the script, tester, status and defects together and calculates the pass rate you need for the go live decision. **Sections:** #### How to use the worksheet **Body:** Add a row per test case with a short ID, the business process, the step and the result you expect. Assign a tester from the business, not the project team. During testing, update status, set Passed to 1 for passes and record defects found. The summary calculates pass rate and defects per test so you can report progress each day. Export to Excel for the steering group. **Bullets:** - Write steps in business terms - Use real data - Assign business testers - Update daily #### Designing good test cases **Body:** Cover whole processes end to end, from quote to cash or procurement to payment, and not only individual screens. Include negative cases such as invalid parts, missing approvals and credit holds. Add cases for your customizations, BPM directives and reports, since these are where the standard test scripts do not reach. #### Reading the results **Body:** A high pass rate with untested areas is misleading, so count blocked and not run tests too. Look at where defects cluster by process. Agree entry and exit criteria before testing starts, such as no open critical defects and a minimum pass rate for each process, and record any accepted risks with owners. #### Common mistakes **Body:** Testing with clean demo data hides problems that appear with real master data. Letting consultants run the tests instead of users hides usability and training gaps. Failing to retest after a fix is the third common error, so re-run failed cases and record the new date. **Cta:** If you want help building a test script from your actual processes and customizations, Netray can support the effort. **Faq:** #### What is UAT in an Epicor project? **Answer:** User acceptance testing is when business users run real processes in a test or pilot environment to confirm Epicor works for them before go live. It checks configuration, data, customizations and reports against real needs, and ends with a documented sign off. #### How many test cases do I need? **Answer:** Enough to cover each core process and each customization, usually dozens to a few hundred depending on scope. Quality matters more than count: end to end scenarios with realistic data find more problems than many isolated screen checks. #### What pass rate is acceptable? **Answer:** Set it before testing. Many teams require all critical cases to pass and a high overall rate with no open critical defects. The right threshold depends on your risk tolerance, so record exceptions and who accepted them. #### Who should run the tests? **Answer:** The people who will do the work after go live. They know the exceptions and will spot gaps a consultant would miss. The project team supports, logs defects and retests, but should not be the main testers. ## Search terms epicor uat test script, epicor user acceptance testing template, epicor test plan excel, epicor upgrade test script, epicor go live testing, erp uat template, epicor regression test checklist --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json