Free Workday Workday-Procure-to-Pay Practice Exam with Questions & Answers

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.

Receipts in Workday record the quantity of goods or services that have arrived against a purchase order line, and these records sometimes contain data entry errors that need correction without disturbing the underlying purchase order. The Official Workday Pro Procure-to-Pay Guide identifies the Create Receipt Adjustment task as the correct tool for correcting an incorrect quantity that was recorded on a previously entered receipt, allowing the quantity to be revised up or down while maintaining an accurate audit trail of receiving activity. Option B is incorrect because editing the purchase order changes the ordered quantity or terms, not the quantity that was actually recorded as received. Option C is incorrect because Return to Supplier represents a physical return of goods back to the supplier and is used when goods need to be sent back, not simply to correct a recording error. Option D is incorrect because closing the PO line for receiving prevents future receipts but does nothing to correct the inaccurate quantity already recorded on the existing receipt.

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.

Workday delivers a set of predefined security groups aligned to common roles within the procure-to-pay process, each granting the specific domain permissions needed for that role's typical responsibilities, such as entering supplier invoices for accounts payable staff. The Official Workday Pro Procure-to-Pay Guide identifies Accounts Payable Data Entry Specialist as the security group designed to grant the permissions necessary to create supplier invoices, making it the appropriate assignment for a new employee in the Accounts Payable department with this responsibility. Option B is incorrect because Security Administrator grants broad access to configure security groups, roles, and policies across the tenant, which is unrelated to and far exceeds the access needed for routine invoice entry. Option C is incorrect because Finance Administrator typically provides broad configuration access across financial setup areas, again exceeding what a data-entry-focused new hire requires. Option D is incorrect because Accounts Receivable Specialist relates to the order-to-cash and customer billing side of the ledger, the opposite function from accounts payable supplier invoicing.

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.

Account Posting Rules determine which general ledger account a transaction posts to based on the combination of worktags present, such as company, spend category, and cost center. Because a tenant can have multiple posting rules with varying numbers of conditions, Workday needs a deterministic method for choosing among them when more than one rule's conditions are satisfied by a transaction. The Official Workday Pro Procure-to-Pay Guide confirms that Workday selects the most specific applicable rule, meaning the rule with the greatest number of matching conditions or dimensions, ensuring that granular, targeted rules take precedence over broad, general ones. Option A is incorrect because ledger account determination in posting rules is automated and is not a manual selection made by the end user during transaction entry. Option B is incorrect because Workday does not simply read through all rules without a hierarchy; specificity, not sequence of review, governs selection. Option D is incorrect because relying on the first rule that merely meets conditions, regardless of how specific it is, could cause a broad rule to incorrectly override a more targeted one.

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.

Return reasons in Workday can be configured with attributes that determine the downstream effects of processing a return, including whether an associated supplier invoice adjustment is automatically generated to reflect the reduced billable quantity resulting from the return. The Official Workday Pro Procure-to-Pay Guide explains that if the return reason selected for the damaged keyboard was not configured to trigger automatic creation of a supplier invoice adjustment, the system will process the return itself but will not generate the corresponding adjustment, requiring manual intervention. Option A is incorrect because if the return quantity had exceeded the received quantity, the system would likely prevent or flag the return itself as invalid, rather than silently process it without generating an adjustment. Option C is incorrect because the cost center selected during receiving affects the accounting worktags on the transaction, but does not control whether a supplier invoice adjustment is automatically generated from a return. Option D is incorrect because a supplier Return Material Authorization may be a procedural or supplier-side requirement, but it is not a Workday system configuration that governs automatic invoice adjustment generation.

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.