Procure to Pay encompasses the end-to-end process by which an organization acquires the goods and services it needs, from initial requisitioning through receiving, invoicing, and ultimately payment, and is distinct from other financial processes that handle different types of transactions. The Official Workday Pro Procure-to-Pay Guide confirms that Goods, representing tangible, physical items, is a core type of spend tracked through the Procure to Pay process, supported by requisitions, purchase orders, receiving, and supplier invoicing workflows. Option A is incorrect because customer refunds belong to the order-to-cash or accounts receivable process, which deals with money owed to customers, not procurement spend. Option B is incorrect because employee payroll is managed through Human Capital Management and Payroll, an entirely separate functional area from Procure to Pay. Option C is incorrect because expense reports are processed through the Expenses module for employee-initiated reimbursable spend, which, while related to overall spend management, follows a distinct process from supplier-based Procure to Pay transactions.

Maintain Worktag Usage is the central configuration task that defines, for each worktag type, how that worktag behaves on different transactional business objects, such as requisitions, purchase orders, and supplier invoices. The Official Workday Pro Procure-to-Pay Guide explains that through this task, administrators can add additional worktags, beyond the standard delivered set, making them available for entry on specific transaction types by setting their usage to Optional, Required, or Primary for those transactions. Option A is incorrect because conditional, rule-based requirements that depend on transaction data are configured through Maintain Custom Validations, not Maintain Worktag Usage. Option B is incorrect because Maintain Worktag Usage applies to transactional business objects, such as purchase orders and supplier invoices, not non-transactional objects like suppliers or purchase items. Option C is incorrect for the same reason, non-transactional objects fall outside the scope of this task, and additionally Primary designations are most relevant to transactional documents where routing and reporting are based on the primary worktag value.

In this scenario, every procurement item being loaded must be identified as Office Supplies, which represents the single, required classification that every purchase item in Workday must carry through its spend category assignment. The Official Workday Pro Procure-to-Pay Guide explains that fulfilling this required association means creating a spend category named Office Supplies and assigning it to these items, since spend category is the mandatory, primary classification field on every purchase item. Option B is incorrect because purchase groups provide additional, optional grouping for reporting but are not the required, primary classification mechanism that spend category represents. Option C is incorrect because item tags, or related worktags, are used for additional, non-required classifications, such as the General Use or Promotional categorizations described in the related scenario, not for the mandatory primary classification. Option D is incorrect because alternate item identifiers store supplementary reference codes, such as part numbers, and have no role in fulfilling a categorical classification requirement like Office Supplies.

When setting up a new spend category, administrators determine certain item-level controls that apply to purchase items assigned to that category, including whether items must be individually tracked once received, which is particularly important for assets that require formal registration, such as equipment reviewed by a business asset accountant. The Official Workday Pro Procure-to-Pay Guide identifies Track Items as the configuration that must be applied so that goods received under the Office Machines spend category can be individually identified and registered as trackable assets. Option B is incorrect because Alternate Item Identifiers store additional reference numbers, such as manufacturer part numbers, for identification purposes, but do not enable the asset tracking and registration workflow. Option C is incorrect because Allocate Other Charges is used to distribute additional costs, such as freight or handling, across lines and is unrelated to asset registration. Option D is incorrect because Classification provides a categorization or tagging mechanism for items but does not drive the requirement for individual item tracking and registration upon receipt.

Supplier categories are a classification attribute on the supplier record used for reporting and grouping purposes, such as distinguishing diversity suppliers or spend types, and are distinct from supplier groups, which serve more flexible administrative and security purposes. The Official Workday Pro Procure-to-Pay Guide specifies that each supplier can be assigned to exactly one supplier category at a time, reflecting the field's design as a single-value classification attribute on the supplier record, while supplier groups, by contrast, support unlimited assignments per supplier. Option B, allowing two categories, is incorrect because the supplier category field does not support multiple simultaneous values. Option C, allowing six categories, is incorrect for the same reason and significantly overstates the field's capacity. Option D, allowing twelve categories, is also incorrect and would contradict the single-value design used for consistent reporting and classification. Understanding this one-category limit is important when designing supplier classification strategies, since broader, multi-value groupings for a supplier must instead be accomplished using supplier groups rather than supplier categories.

Purchase orders move through a defined lifecycle of statuses, and only certain statuses indicate that the order has been finalized and communicated to the supplier, making it eligible to have goods or services recorded against it as received. The Official Workday Pro Procure-to-Pay Guide specifies that a purchase order must be in Issued status before a receipt can be created against it, since Issued confirms the order has completed its approval process and has been sent to the supplier, who is now expected to fulfill it. Option A is incorrect because a Closed purchase order has already completed its lifecycle, whether through full receiving and invoicing or manual closure, and is not eligible for new receiving activity. Option B is incorrect because In Progress indicates the purchase order is still moving through its internal approval business process and has not yet been finalized or sent to the supplier. Option D is incorrect because Approved is an internal status that precedes issuance; the order must still be issued before receiving can occur.

Supplier portal access in Workday is granted through Workday user accounts that are associated with individual supplier contact records, meaning a contact representing a real person at the supplier must exist on the supplier record before a Workday account can be linked to that person for login purposes. The Official Workday Pro Procure-to-Pay Guide describes the correct sequence as first adding the supplier contact to the supplier record, and then creating a Workday account for that supplier contact, establishing the credential that allows the individual to log into the supplier portal. Option A is incorrect because creating an initial requisition has no bearing on, and is not a prerequisite for, granting supplier portal access. Option B is incorrect because adding a supplier address provides location information but does not establish a person, the supplier contact, who can be associated with a login account. Option C is incorrect because the sequence is reversed; a Workday account must be linked to an existing supplier contact, so the contact record must be created first, not after the account.

After a requisition is approved, it must still go through sourcing, the step in which a buyer confirms or assigns the supplier, pricing, and other purchase order details, before Workday can generate the corresponding purchase order; certain on-contract or catalog items may source automatically, but others require manual buyer action. The Official Workday Pro Procure-to-Pay Guide explains that if an approved requisition has not yet produced a purchase order, the next required action is to source the requisition, completing the step that converts the requisition line into a purchase order line. Option A is incorrect because manually creating a separate purchase order would bypass the requisition-to-PO linkage and audit trail that sourcing the existing requisition preserves. Option B is incorrect because resubmitting the requisition would restart the approval business process unnecessarily on a requisition that has already been approved. Option C is incorrect because issuing a purchase order presumes that a purchase order already exists, but the scenario states none has been generated, meaning there is nothing yet to issue.

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.

Enterprise Interface Builder, or EIB, integrations commonly use a spreadsheet template, generated by Workday, that defines the columns and structure expected when bulk-loading data such as journal entries. If the analyst discovers that a needed column, representing a required field for the journals, is missing from this template, the underlying spreadsheet itself must be updated before the data can be loaded successfully. The Official Workday Pro Procure-to-Pay Guide indicates that the appropriate action is to edit the template in Excel, adding the missing column with the correct header so the data aligns with the EIB's expected input format and field mapping. Option B is incorrect because an EIB has already been created; the issue is with the existing template's structure, not the absence of an EIB. Option C is incorrect because launching the integration with an incomplete template would simply load the data without the missing field, failing to resolve the underlying issue. Option D is incorrect because the spreadsheet template used for EIB data entry is maintained and edited in Excel, not directly within Workday.