Workday-Procure-to-Pay Exam Questions

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.

Supplier portal access in Workday is granted through Workday user accounts that are associated with individual supplier contact records, meaning a contact representing a real person at the supplier must exist on the supplier record before a Workday account can be linked to that person for login purposes. The Official Workday Pro Procure-to-Pay Guide describes the correct sequence as first adding the supplier contact to the supplier record, and then creating a Workday account for that supplier contact, establishing the credential that allows the individual to log into the supplier portal. Option A is incorrect because creating an initial requisition has no bearing on, and is not a prerequisite for, granting supplier portal access. Option B is incorrect because adding a supplier address provides location information but does not establish a person, the supplier contact, who can be associated with a login account. Option C is incorrect because the sequence is reversed; a Workday account must be linked to an existing supplier contact, so the contact record must be created first, not after the account.

When pricing for catalog items linked to a supplier contract changes regularly, manually updating those prices within Workday can create administrative burden and lag between actual market changes and system pricing. The Official Workday Pro Procure-to-Pay Guide describes the supplier portal as a tool that, once a Workday account is established for a supplier contact, allows the supplier itself to directly maintain and update catalog pricing for items linked to their contract, placing the responsibility for timely updates with the party that has the most current pricing information. Option A is incorrect because Workday does not provide a delivered, automated integration that synchronizes purchase item prices directly with arbitrary supplier systems as a standard configuration. Option B is incorrect because maintaining pricing outside the contract and routing updates through a business process adds manual steps and delay rather than easing the update process. Option D is incorrect because adding more review or approval steps to the Catalog Load business process increases administrative overhead and would make regular pricing updates slower, not easier.

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.

Enterprise Interface Builder, or EIB, integrations commonly use a spreadsheet template, generated by Workday, that defines the columns and structure expected when bulk-loading data such as journal entries. If the analyst discovers that a needed column, representing a required field for the journals, is missing from this template, the underlying spreadsheet itself must be updated before the data can be loaded successfully. The Official Workday Pro Procure-to-Pay Guide indicates that the appropriate action is to edit the template in Excel, adding the missing column with the correct header so the data aligns with the EIB's expected input format and field mapping. Option B is incorrect because an EIB has already been created; the issue is with the existing template's structure, not the absence of an EIB. Option C is incorrect because launching the integration with an incomplete template would simply load the data without the missing field, failing to resolve the underlying issue. Option D is incorrect because the spreadsheet template used for EIB data entry is maintained and edited in Excel, not directly within Workday.