Workday Workday-Procure-to-Pay Workday Pro Procure-to-Pay Certification Exam Exam Practice Test

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.

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.

Every purchase item carries one required spend category, but organizations often need to analyze spend across additional, overlapping groupings that cut across spend categories, such as wanting to see a laptop reported both under its existing Office Supplies spend category and alongside other items classified as Computers. The Official Workday Pro Procure-to-Pay Guide identifies Purchase Item Groups as the mechanism for creating these additional, flexible groupings of items for reporting purposes, allowing the laptop to be included in a Computers group without changing its primary spend category assignment. Option A is incorrect because catalog items describe how items are presented for ordering, such as through punch-out or internal catalogs, and are not a reporting classification mechanism. Option B is incorrect because web items relate to externally hosted, punch-out catalog integrations and do not provide a grouping mechanism for cross-category reporting. Option D is incorrect because spend categories are limited to one per item, the existing Office Supplies assignment, and cannot be used to add the additional Computers reporting dimension.

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.

Tax applicability determines whether tax is calculated on a transaction line and is one of several attributes configured during procurement setup to streamline requisition, purchase order, and supplier invoice entry. The Official Workday Pro Procure-to-Pay Guide identifies the purchase item record as the location where a default Tax Applicability value is assigned, so that whenever the item is added to a transaction, the correct default tax treatment automatically populates, reducing manual entry and errors. Option B is incorrect because suppliers do not carry a tax applicability default for items; tax treatment depends on what is being purchased, not who it is purchased from. Option C is incorrect because Edit Company Procurement Options governs company-wide procurement behaviors such as defaults for shipping, sourcing, and requisition settings, not item-specific tax defaults. Option D is incorrect because Edit Tenant Setup - Financials configures tenant-level financial settings such as currencies, fiscal calendars, and general ledger options, and does not provide a mechanism for setting tax applicability on individual purchase items.

Workday categorizes procurement at a high level into Goods and Services to support different transactional behaviors, particularly around receiving, since physical items typically require quantity-based confirmation of delivery while services do not. The Official Workday Pro Procure-to-Pay Guide identifies Goods as the procurement type used to track spend for physical, tangible items, enabling the standard requisition, purchase order, and receiving workflow appropriate for inventory-type purchases. Option A is incorrect because Project-based Services is used for tracking billable, project-related service work rather than physical items, and follows a different tracking model tied to project worktags. Option C is incorrect because Matching is not a procurement type at all; it refers to the three-way matching process used to reconcile supplier invoices against purchase orders and receipts. Option D is incorrect because the general Service procurement type covers intangible deliverables such as labor or consulting, which typically do not involve the physical receipt of goods in the same manner as items procured under the Goods type.

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.

Supplier contracts in Workday are formal, approved agreements that govern terms such as pricing, dates, and total contract amount with a supplier. Once a contract reaches Approved status, its terms are locked and cannot simply be overwritten through direct editing. Per the Official Workday Pro Procure-to-Pay Guide, the correct mechanism for changing approved contract data, such as the contract amount, is to initiate a Create Contract Amendment business process. The amendment creates a new version of the contract with the corrected amount while preserving the original document and a full audit trail of the change, including any required re-approval. Option A is incorrect because catalogs hold pricing for items, not the overall contract amount, and changing a catalog does not alter the contract record itself. Option B is incorrect because an attachment is purely supplementary documentation; it does not update the actual data field driving contract value or downstream processing. Option C is incorrect because invoices are transactional documents created against POs or contracts during the procure-to-pay cycle and cannot be used to replace or modify a contract record.

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.

Workday's foundation organization types each serve specific purposes, and the Company organization type represents a legal entity capable of holding government-issued identifiers such as tax IDs, and of being assigned its own ledger for financial reporting. The Official Workday Pro Procure-to-Pay Guide identifies Company as the appropriate organization type when an implementation requires multiple units of the same type, each carrying unique government identifiers and grouping financial transactions on separate ledgers, since these characteristics, tax identification and ledger assignment, are defining features of the Company organization type. Option A is incorrect because Location organizations track physical sites and do not carry government tax identifiers or ledger assignments. Option B is incorrect because Company Hierarchy is a structure used to group and roll up companies for reporting, not an organization type that itself holds a tax ID or ledger. Option D is incorrect because Cost Centers track departmental or functional spend within a company and do not have their own government identifiers or separate ledgers; they post into the ledger of the company to which they belong.

Purchase items can carry additional reference codes beyond their standard Workday item identifier, which is useful when organizations need to track external identifiers, such as manufacturer part numbers, and associate suppliers with specific identifier values to support sourcing decisions and supplier prioritization. The Official Workday Pro Procure-to-Pay Guide identifies Alternate Item Identifiers configured on the purchase item as the correct setup for tracking manufacturer part numbers and linking suppliers to those identifiers, since this is where item-specific identifier and supplier association data is maintained directly on the item record. Option A is incorrect because spend categories classify broad groups of items for reporting and accounting purposes and do not hold item-specific identifiers like manufacturer part numbers. Option B is incorrect because configuring identifiers on suppliers would not tie a specific manufacturer part number to a specific purchase item in a structured, reusable way. Option C is incorrect because supplier contracts govern pricing and contractual terms and are not the storage location for alternate item identifier data on procurement items.

Evaluated Receipt Settlement, or ERS, is a Workday feature that allows supplier invoices to be generated automatically rather than requiring the supplier to submit an invoice for manual entry. The Official Workday Pro Procure-to-Pay Guide explains that this automated supplier invoice creation process is triggered by the recording of a receipt of goods or services against a purchase order line that has been configured for automatic invoicing, with the invoice amount derived from the PO price and received quantity. Option A is incorrect because, while a purchase order is a prerequisite for the PO line to exist, the act of placing or approving a PO does not itself trigger automatic invoice creation; receipt confirmation is the actual trigger. Option C is incorrect because there is no configurable trigger called supplier business process that drives automated invoicing. Option D is incorrect because a supplier contract establishes pricing and terms that may feed into the PO, but the contract's existence does not initiate automatic invoice generation; receipt activity does.

When a purchase item on a requisition line is already covered by an active, on-contract supplier agreement, Workday has sufficient information, including the supplier and negotiated pricing, to bypass the manual sourcing step that would otherwise be required for the buyer to assign a supplier. The Official Workday Pro Procure-to-Pay Guide explains that once the requisition business process completes approval for an on-contract item, the requisition line automatically becomes a purchase order line, since the contract has already established the supplier and pricing terms needed to generate the PO. Option A is incorrect because requisition lines are not sent to suppliers for review; supplier-facing communication occurs through purchase orders. Option B is incorrect because the defining characteristic of an on-contract item is that it does not require buyer sourcing, since the supplier is already determined by the contract. Option C is incorrect because the requisition line becomes a transactional purchase order line, not a catalog item, which is a setup record rather than an output of the requisition process.

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.

Edit Company Procurement Options centralizes company-specific configuration settings that streamline procurement transactions for that company, including default values that automatically populate on new requisitions and purchase orders to reduce manual data entry. The Official Workday Pro Procure-to-Pay Guide identifies Default Ship-To Contact and Shipping Terms as fields available within Edit Company Procurement Options, allowing the company to establish standard shipping defaults that apply across procurement transactions unless overridden. Option B is incorrect because enabling multi-company functionality on purchase orders is a broader, cross-company configuration concern and is not a field found within this company-specific procurement options task. Option C is incorrect because Enable Company Accounting Details relates to the separate Edit Company Accounting Details task, which governs ledger and accounting configuration, not procurement defaults. Option D is incorrect because Mass Update Ledger Period Status is an accounting period management task entirely unrelated to procurement configuration and would not appear within Edit Company Procurement Options.

Manual journal entries created through the Create Journal task differ from operational journals in that the accountant directly specifies the ledger accounts on each journal line, rather than relying on Account Posting Rules to derive the accounts from worktag combinations. The Official Workday Pro Procure-to-Pay Guide clarifies that because the journal described is balanced, with explicit accounts entered on both lines including the liability account, and the period is open, the journal will successfully complete its business process and reach a Posted status, regardless of whether Account Posting Rules have been configured for the new spend category worktag, since posting rules are not required for manually entered journals. Option A is incorrect because a balanced manual journal in an open period does not remain Unposted upon completing its process. Option B is incorrect because an Error status would arise from issues like an unbalanced entry or invalid period, not from missing posting rules that are irrelevant to manual journals. Option C is incorrect because the scenario specifies the business process has completed, meaning the journal has reached a final status rather than remaining In Progress.