A well-defined business requirement must be specific, measurable, and actionable. Option C provides all the necessary components for a complete requirement: it identifies the roles involved (Accounts receivable clerks, managers), the specific business process (review and submit payments), a quantifiable condition (over $100,000), and the business justification (to meet industry compliance). This level of detail allows a solution architect to design and configure a specific feature, such as an approval workflow, within Dynamics 365 Finance to meet the stated need.

A. This is a low-level user interface (UI) preference, not a core business requirement. It prescribes a solution ("move the button") rather than defining the underlying business problem or need.

B. This statement is too generic. It describes a fundamental accounting principle inherent in any ERP system rather than a specific business requirement that needs to be configured or developed.

D. This requirement is too vague and incomplete. It lacks critical details such as the purpose of the reports, the specific data points needed, and the frequency, making it impossible to act upon.

1. Microsoft Learn. "Business requirements and process analysis". Dynamics 365 Implementation Guide. This guide emphasizes that during the analysis phase, requirements must be captured with sufficient detail to define the scope. A requirement like C is detailed, whereas D is a high-level, undefined goal.

2. Microsoft Learn. "Plan your workflow". Finance and Operations apps documentation. This document outlines the questions to ask before creating a workflow, which align directly with the information provided in option C: "Who submits the document for approval?", "What conditions must be met for the workflow to run?", and "Who must approve the document?". The details in option C directly answer these planning questions.

3. Microsoft Learn. "Solution blueprint overview". Dynamics 365 Implementation Guide. A solution blueprint is built upon detailed business requirements. A vague statement like "managers need reporting" (Option D) is insufficient for a blueprint, while a specific, conditional process like the one in Option C is a perfect example of a requirement that would be documented and addressed in the solution design.