During UAT, any incident related to invoice totals must include information that allows the consultant or tester to reproduce and diagnose the issue quickly.
✔ B — Quote number, Order number, or Invoice numberThese IDs allow the consultant to immediately:
Locate the exact transaction
Review invoice lines, tax, proration, billing rules
Check data mapping and calculation sequence
This is essential for any Revenue Cloud troubleshooting scenario.
✔ D — Steps to replicate the issueWithout reproducible steps, diagnosis is almost impossible.
UAT defect triage requires:
Exact user actions
Fields populated
Sequence of operations (e.g., "Bill Now", "Invoice Run", etc.)
This is a Salesforce UAT best practice.
✔ E — Expected resultsCrucial for determining:
Whether the system is incorrect
Whether requirements were misunderstood
Whether recalculation logic (tax, proration, discounts) was expected to behave differently
Why Other Options Are IncorrectOption
Why Wrong
A — Description of new requirements
UAT incidents are not for new requirements; they are for defects.
C — Expected resolution date
Not part of incident description; it's part of project management, not defect logging.
Final Answer: B, D, E
