Pass the Workday Workday Pro Financial Management Workday-Procure-to-Pay Questions and answers with CertsForce

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.

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.

The Create Purchase Order task provides several starting points for generating a new purchase order, allowing buyers to choose an approach that best fits the procurement scenario, whether starting fresh or leveraging previously defined structures. The Official Workday Pro Procure-to-Pay Guide identifies Create from purchase order template as one of the available options when initiating Create Purchase Order, enabling buyers to reuse a predefined template containing standard lines, suppliers, or settings for recurring purchase scenarios, improving consistency and efficiency. Option A is incorrect because creating a purchase order from a blank starting point is not how the task is structured; purchase orders are generated from templates, requisitions, or contracts rather than an unstructured blank document. Option C is incorrect because creating from a request for quote is part of the sourcing and RFQ process, which may ultimately lead to a purchase order, but is not itself a direct option presented within the Create Purchase Order task. Option D is incorrect because supplier invoices are separate downstream documents and there is no option to create a purchase order from a supplier invoice.

Workday's Location organization type represents physical places, such as buildings, campuses, or rooms, and can be structured hierarchically to reflect an institution's physical footprint, while also serving as a worktag that can be applied to assets and transactions to indicate where they are physically situated. The Official Workday Pro Procure-to-Pay Guide identifies Locations Organization as the appropriate organization type for a large university needing to track the physical location of equipment for a specific school, such as the School of Engineering, since locations can be defined down to granular levels like buildings or rooms and associated with equipment records. Option A is incorrect because Company Organization represents the legal and financial entity, not physical equipment locations. Option C is incorrect because Region Organization is typically used for broader geographic groupings for reporting rather than granular, building-level equipment tracking. Option D is incorrect because Cost Center Organization groups financial spend and budgets by department or function, and does not represent physical locations where equipment resides.

Requisition sourcing is the process by which buyers review approved requisition lines and determine how they will be fulfilled, including assigning suppliers and pricing, and Workday provides tools to help buyers manage this workload efficiently across many requisitions and lines. The Official Workday Pro Procure-to-Pay Guide confirms that the requisition sourcing console can be used to manage requisitions, giving buyers a centralized view to filter, review, and act on requisition lines awaiting sourcing. Option A is incorrect because there is no requirement that all lines of a requisition be sourced from the same supplier; different lines can be sourced to different suppliers based on what each line requires. Option C is incorrect because items on a requisition do not have to be sourced all at the same time; sourcing can occur at different times for different lines. Option D is incorrect because, during manual sourcing, the buyer can in fact change or assign the supplier for a requisition line, which is a core part of the sourcing action rather than a restriction.

Workday distinguishes between supplier categories, used as a single-value classification on each supplier record for reporting purposes, and supplier groups, which provide a more flexible, multi-value grouping mechanism that can be used for security, routing, and reporting across many overlapping use cases. The Official Workday Pro Procure-to-Pay Guide confirms that each supplier may be assigned to exactly one supplier category, while being added to an unlimited number of supplier groups, allowing suppliers to participate in many different group-based configurations simultaneously while maintaining a single primary classification. Option A is incorrect because limiting supplier groups to one would eliminate the flexibility that groups are specifically designed to provide. Option C is incorrect because allowing no limits on supplier categories would contradict the single-category design intended for consistent primary classification. Option D is incorrect because, although supplier groups are indeed unlimited, the option also incorrectly claims unlimited supplier categories, which is not supported by the supplier record's single-category field.

On a supplier invoice line, the total line amount represents the cost being billed for a given item or service, but in many organizations that cost must be allocated across multiple cost centers or other worktag combinations for accounting purposes. The Official Workday Pro Procure-to-Pay Guide identifies the Splits field as the mechanism for dividing a single invoice line's total amount across multiple sets of worktags, whether by percentage or by specific amounts, so that the expense is recorded against the appropriate cost centers in the ledger. Option A is incorrect because Unit Cost reflects the per-unit price used in quantity-based calculations and has no function for allocating an amount across cost centers. Option B is incorrect because Item Tags are used to categorize or label items for identification purposes, not to distribute monetary amounts. Option D is incorrect because Matching refers to the three-way matching process that reconciles invoice, purchase order, and receipt data, and does not provide a mechanism for splitting an amount across accounting dimensions.

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.

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.

Custom validations allow administrators to enforce business rules on transactions beyond standard system requirements by evaluating condition rules and displaying a message when conditions are or are not met. The Official Workday Pro Procure-to-Pay Guide explains that custom validations can be configured to display either a Warning message, which alerts the user but allows them to continue, or an Error message, which blocks the user from proceeding until the issue is corrected. This dual capability gives administrators flexibility to either guide users with soft reminders or enforce hard stops for critical business rules. Option A is incorrect because restricting custom validations to warnings only would prevent administrators from enforcing mandatory rules that must block submission. Option C is incorrect because limiting to errors only would remove the ability to provide non-blocking guidance, which is a commonly used and valuable feature. Option D is incorrect because the entire purpose of a custom validation is to communicate a message to the user when a defined condition is triggered; a validation that displays no message would serve no functional purpose.