Workday Pro Financial Management Workday-Procure-to-Pay Reddit Questions

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.

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.

Workday distinguishes between manual journals, which accountants create directly using the Create Journal task, and operational journals, which are generated automatically by the system as a byproduct of posting business transactions such as supplier invoices, expense reports, and payments. The Official Workday Pro Procure-to-Pay Guide identifies the Create Supplier Invoice task as an example of a transaction that, once completed and posted, automatically generates the corresponding operational journal entries based on Account Posting Rules, without requiring any manual journal entry. Option B is incorrect because Print Checks executes the payment process for previously approved supplier invoices and is a downstream payment activity rather than the originating transaction that generates the invoice-related operational journal. Option C is incorrect because Create Journal produces a manual journal entered directly by an accountant, which is the opposite of an operational journal. Option D is incorrect because Create Recurring Journal Template defines a template used to generate manual journals on a schedule, and does not itself produce an operational journal tied to a business transaction.

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.