# D365 Finance and Supply Chain UAT Test Case Worksheet

> Source: https://netray.co/tools/d365-fo-uat-test-case-worksheet
> Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems.
> Section: Free Tools

## Short answer

An editable UAT tracker with process area, scenario, expected result, tester, result and defect reference, with pass-rate totals.

## Category

microsoft-dynamics

## Erp

Microsoft Dynamics 365 Finance and Supply Chain

## Audience

- QA lead
- D365 F&O functional consultant
- Business process owner

## Tool

**Kind:** worksheet

**Mode:** editable

**Columns:**

#### Test ID

**Key:** tc

**Type:** text

#### Business process

**Key:** process

**Type:** select

**Options:**

- Procure to pay
- Order to cash
- Plan to produce
- Record to report
- Inventory and warehouse
- Master data
- Security

#### Scenario

**Key:** scenario

**Type:** text

#### Expected result

**Key:** expected

**Type:** text

#### Tester

**Key:** tester

**Type:** text

#### Result

**Key:** result

**Type:** select

**Options:**

- Not run
- Pass
- Fail
- Blocked

#### Defect ID

**Key:** defect

**Type:** text

#### Run (1 if executed)

**Key:** run

**Type:** number

#### Passed (1 if pass)

**Key:** passed

**Type:** number

**Rows:**

**Tc:** UAT-P2P-01

**Process:** Procure to pay

**Scenario:** Create PO, receive product, post vendor invoice with 3-way match

**Expected:** Invoice posts, GL entries match setup

**Tester:** AP clerk

**Result:** Pass

**Run:** 1

**Passed:** 1

**Tc:** UAT-O2C-04

**Process:** Order to cash

**Scenario:** Sales order with partial shipment and credit hold release

**Expected:** Hold releases, packing slip posts, invoice for shipped qty

**Tester:** Sales admin

**Result:** Fail

**Defect:** DEF-112

**Run:** 1

**Passed:** 0

**Tc:** UAT-PLN-02

**Process:** Plan to produce

**Scenario:** Release production order, report as finished, end

**Expected:** WIP clears, variance posted to configured account

**Tester:** Planner

**Result:** Pass

**Run:** 1

**Passed:** 1

**Tc:** UAT-R2R-07

**Process:** Record to report

**Scenario:** Month-end ledger settlement and financial statement run

**Expected:** Statements balance and tie to trial balance

**Tester:** Controller

**Result:** Blocked

**Defect:** DEF-120

**Run:** 0

**Passed:** 0

**Tc:** UAT-SEC-01

**Process:** Security

**Scenario:** Buyer role cannot approve own purchase order

**Expected:** Approval action unavailable to same user

**Tester:** IT admin

**Result:** Not run

**Run:** 0

**Passed:** 0

**Totals:**

#### Total test cases

**Key:** tc

**Agg:** count

**Format:** integer

#### Executed

**Key:** run

**Agg:** sum

**Format:** integer

#### Passed

**Key:** passed

**Agg:** sum

**Format:** integer

**Summary:**

#### Execution progress

**Key:** executed_pct

**Expr:** if(gt(count,0), sum_run / count * 100, 0)

**Format:** percent

#### Pass rate of executed

**Key:** pass_pct

**Expr:** if(gt(sum_run,0), sum_passed / sum_run * 100, 0)

**Format:** percent

**Notes:** Set Run to 1 when a case is executed and Passed to 1 when it passes. Link test IDs to Req IDs in your fit-gap register and to Azure DevOps test plans.

## Content

**Intro:** User acceptance testing is where business owners confirm the system supports their daily work. This worksheet gives you a simple tracker for scenarios, results and defects with progress and pass rate calculated for you.

**Sections:**

#### How to use the worksheet

**Body:** Write scenarios in business language, such as a purchase order received and invoiced with three-way match, not a click path. Assign a tester from the business, run the case in the UAT environment, then mark Run and Passed. Link failed cases to a defect ID. The summary shows execution progress and the pass rate of cases actually run, which is a better signal than a pass count alone.

**Bullets:**

- Scenarios should span a whole process end to end
- Testers must be real users, not consultants
- Include negative and security cases
- Record defect IDs so retests are traceable

#### Coverage across D365 processes

**Body:** Organize cases by end-to-end process: procure to pay, order to cash, plan to produce, record to report, and inventory and warehouse. Add security tests that confirm segregation of duties, and period-end cases that matter to finance. Stable, repeatable cases can later be recorded with the Task recorder and automated with the Regression Suite Automation Tool to support One Version updates.

#### Exit criteria

**Body:** Agree the exit criteria before testing starts: for example, all must-have processes executed, no open severity 1 or 2 defects, and agreed workarounds for lower severities. A pass rate is only meaningful when the denominator reflects real coverage, so check the executed percentage first.

#### Common mistakes

**Body:** UAT often fails because testers are borrowed from other work, test data is unrealistic, or scenarios are narrowly scripted so that real-world exceptions are never touched. Another is treating UAT as training. Keep a separate training track so test cycles remain focused on acceptance.

**Cta:** If you want to turn recorded business processes into repeatable regression tests, Netray can help design a private pipeline that generates and maintains test cases from your documentation.

**Faq:**

#### How is UAT different from SIT?

**Answer:** System integration testing is run by the project team to confirm components and integrations work together. UAT is run by business users to confirm the system supports their real processes and meets acceptance criteria before go-live.

#### How many UAT cycles are normal?

**Answer:** Two cycles are common, with a retest of fixes in between. Complex rollouts add more. Plan time for defect fixing and retesting, not only for first-run execution.

#### Can I automate UAT?

**Answer:** Parts of it, yes. Repeatable flows can be recorded and run with the Regression Suite Automation Tool, but business acceptance still needs a human decision. Automation is most valuable for regression after updates.

#### What data should testers use?

**Answer:** Use a recent, masked copy or migrated data close to production quality. Synthetic demo data hides real problems such as long descriptions, special characters and unusual unit conversions.

## Search terms

d365 uat test case template, dynamics 365 uat excel, d365 fo test script template, erp user acceptance testing template, d365 test cases excel, d365 uat sign off

---
Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json