Workday Pro Procure-to-Pay Certification Workday-Procure-to-Pay Exam Questions

Answer : C

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.

Answer : B

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.

Answer : A

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.

Answer : B

While Workday provides tenant-wide settings to control worktag requirements, sometimes a business requirement applies only to a single company rather than the entire tenant, requiring a more targeted configuration approach. The Official Workday Pro Procure-to-Pay Guide describes Maintain Custom Validations as the task used to build condition-based rules, such as requiring the Location worktag on supplier invoices only when the Company equals a specific value, displaying an error message if the requirement is not met. This approach scopes the requirement precisely to the company in question without affecting other companies in the tenant. Option A is incorrect because Maintain Related Worktag Usage governs allowed combinations of worktag values across the tenant, not company-specific field requirements. Option C is incorrect because Configure Optional Fields manages broad field visibility settings rather than conditional, company-specific requirement logic. Option D is incorrect because Maintain Worktag Usage sets tenant-wide usage levels, such as Required or Optional, for a worktag type on a transaction, and does not provide the granularity to apply a requirement to one company only.

Answer : D

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.

Answer : D

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.

Answer : A

While creating a requisition, requesters often need to browse external supplier catalogs or websites to identify items to purchase, and Workday provides a delivered link within the requisition creation experience to facilitate this navigation directly from the requisition. The Official Workday Pro Procure-to-Pay Guide identifies Connect to Suppliers as the delivered link that requesters click from within the Create Requisition task to access supplier websites, such as punch-out catalogs, for browsing and selecting items. Option B is incorrect because Access Supplier Website is not the actual delivered link label presented within the requisition creation screen. Option C is incorrect because Connect to Supplier Website, while similar in wording, does not match the precise delivered terminology used by Workday for this link. Option D is incorrect because Go to Websites is a generic, plausible-sounding label that does not correspond to any actual link available within the Create Requisition task, making it a distractor rather than a correct delivered feature.