Workday Workday-Procure-to-Pay Practice Test Questions Answers

Three-way matching compares the amounts, quantities, and prices recorded on a supplier invoice against the corresponding purchase order and receipt, and when an invoice line amount exceeds what the purchase order authorizes, a match exception is generated that must be resolved before the invoice can proceed to payment. The Official Workday Pro Procure-to-Pay Guide describes contacting the supplier to obtain a corrected invoice as the appropriate resolution when an invoice is billed at a higher amount than the agreed purchase order price, since the discrepancy reflects a billing error on the supplier's part rather than a system configuration issue. Option A is incorrect because adding the supplier to the portal addresses access and self-service capability, not a pricing discrepancy on a specific invoice. Option B is incorrect because creating a new match exception rule would alter system-wide tolerance configurations rather than resolve this individual transactional discrepancy, and is not an appropriate response to a one-off pricing error. Option C is incorrect because creating an additional receipt would misrepresent actual receiving activity unless additional goods were genuinely received, which is not indicated here.

The Supplier Request business process provides a controlled, approval-based workflow for onboarding new suppliers or modifying key supplier information before that supplier becomes eligible for transactional activity such as receiving purchase orders or invoices. The Official Workday Pro Procure-to-Pay Guide identifies Supplier Request as the business process that allows for review and approval prior to a supplier being enabled for procurement transactions, giving stakeholders such as procurement or finance teams control over which suppliers are activated. Option A is incorrect because Supplier Status Change is used to change the status, such as active to inactive, of a supplier that already exists in the system, rather than to control initial setup before transacting. Option B is incorrect because Supplier Change Event manages updates to existing supplier records after the supplier has already been established. Option C is incorrect because Supplier Event is not the specific delivered business process name associated with pre-transaction supplier review and approval; Supplier Request is the precise, correct process for this purpose.

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.

After a worker submits a requisition, it is routed through the requisition business process to a buyer for sourcing, the step in which the buyer determines how the requisition will be fulfilled. The Official Workday Pro Procure-to-Pay Guide describes sourcing as the point where the buyer reviews requisition lines and assigns or confirms the supplier that will fulfill the order, among other sourcing actions such as setting pricing. Specifying a supplier is therefore a core action the buyer performs directly on the requisition during this step. Option A is incorrect because requisitions are internal documents and are not forwarded directly to suppliers; communication with suppliers occurs through purchase orders. Option B is incorrect because creating a purchase item is a separate procurement catalog setup activity, unrelated to processing an individual requisition. Option C is incorrect because Issue is an action performed on a purchase order after it has been created from the sourced requisition, not an action available directly on the requisition itself.

Every purchase item in Workday must be assigned exactly one spend category, which serves as its primary, required classification, but organizations frequently need to report on items using additional, secondary classifications that do not fit within the single spend category model. The Official Workday Pro Procure-to-Pay Guide identifies Related Worktags as the mechanism for associating one or more additional classification values, such as General Use or Promotional, with a single item, supplementing its primary spend category without altering it. Option A is incorrect because item substitutes define alternative items that can be used in place of another for sourcing purposes, and have no role in classification or reporting tags. Option B is incorrect because spend category is limited to a single required value per item, the Office Supplies classification in this scenario, and cannot be used to add further classifications. Option D is incorrect because purchase item groups bundle multiple distinct items together for grouped reporting, rather than adding multiple classification tags to a single item.