What Workday-Procure-to-Pay Questions and Answers feature?

Changes to an organization's overall structure, such as creating a new company or restructuring how organizations relate to one another within a hierarchy, affect historical reporting, security, and financial data, and therefore require a controlled, effective-dated mechanism to implement properly. The Official Workday Pro Procure-to-Pay Guide describes the reorganization event as the required mechanism for creating a company or making structural changes to an organization hierarchy, ensuring that the change is properly effective-dated, documented, and that dependent data, such as worker assignments and reporting relationships, is updated consistently. Option A is incorrect because custom worktags are reporting dimensions used for tagging transactions and do not themselves capture or implement organizational structure changes. Option B is incorrect because, while transactional changes to cost centers may route through business processes, the question concerns structural changes to the organization hierarchy itself, which specifically requires a reorganization event. Option D is incorrect because reassigning workers to appropriate sub-types is typically a consequence that occurs as part of, or following, a reorganization event, not the mechanism that creates the structural change itself.

Account Posting Rules, such as the APR spend rule described, define the conditions under which a transaction posts to a specific general ledger account by specifying allowed values across multiple worktag dimensions, in this case Spend Category and Cost Center. For a supplier invoice to post to 7200 Marketing, it must satisfy all specified dimensions: its spend category worktag must fall within Meetings, Marketing, or Travel, and its cost center worktag must be either 37000 Learning or 24000 Outsourcing. The Official Workday Pro Procure-to-Pay Guide confirms that all listed dimension conditions must be satisfied for the rule to apply. Option C correctly pairs Travel, an allowed spend category, with 24000 Outsourcing, an allowed cost center, satisfying both conditions. Option A is incorrect because no spend category is identified, leaving the spend category condition unverified. Option B is incorrect because Office Supplies is not within the allowed spend category values. Option D is incorrect because US-Central Region is not one of the allowed cost center values, failing the cost center condition.

Worktags are the dimensions, such as cost center, fund, project, and custom worktags, used throughout Workday for accounting, reporting, and security. Because some worktag values should only be usable in combination with certain other worktags or organizations, Workday provides a configuration layer to control these allowed combinations. The Official Workday Pro Procure-to-Pay Guide identifies Maintain Related Worktag Usage as the task used to view and modify which worktag values are allowed together on a transaction, effectively defining the permitted, or allowed, worktag relationships across the tenant. Option A, Maintain Worktag Usage, is incorrect because that task controls whether a worktag type is Required, Optional, Primary, or Not Used on a given business object, rather than which specific values are allowed in combination. Option B is incorrect because Maintain Custom Validations creates conditional messages for transactions, not allow-lists of worktag values. Option C is incorrect because Maintain Spend Categories manages the spend category hierarchy and its attributes, and has no role in defining allowed combinations of worktags across the tenant.