We’re having issues with PO approval workflows not starting for certain supplier categories. The workflow triggers correctly for most suppliers, but for our consulting and professional services categories, POs are being created without going through approval at all.
I’ve checked the workflow design and the conditions look correct, but something about the supplier master data attributes or the approval flag configuration isn’t working. The workflow condition logic references supplier category and spend thresholds, but it seems like certain category combinations are bypassing the approval requirement entirely.
This is a major compliance risk since high-value professional services POs are going straight to issued status without any review. Has anyone experienced approval workflows failing to trigger based on supplier attributes?
Let me provide a complete solution covering all three configuration areas:
Supplier Master Data Attributes:
First, audit your supplier records for the affected categories:
Navigate to Suppliers and filter for Consulting and Professional Services categories
For each supplier, verify these critical fields:
Supplier Category: Must exactly match the values used in workflow conditions (case-sensitive)
Requires PO Approval flag: Should be checked unless there’s a specific business reason to bypass
Spend Category: Ensure this aligns with your approval thresholds
Supplier Status: Active suppliers only should be creating POs
Run a supplier data quality report to identify any suppliers missing category assignments
Bulk update supplier flags if needed using EIB to ensure consistency
The key issue is often that supplier records are incomplete or use category values that don’t match workflow conditions exactly. Even trailing spaces in category names can cause matching failures.
Workflow Condition Logic:
Review and fix your PO approval workflow conditions:
Go to Configure Business Process > Purchase Order Approval
Examine the condition steps that should trigger approval
Look for logic like: “IF Supplier_Category IN (‘Consulting’, ‘Professional Services’) AND Amount > 5000 THEN Route to Approval”
Common problems:
Using OR when AND is needed: “Category = Consulting OR Amount > 5000” will trigger for ANY high-value PO, not just consulting
Missing categories: Your condition might check for “Consulting” but suppliers are tagged as “Professional Services - Consulting”
Threshold logic errors: Using >= vs > can create gaps at boundary values
Add explicit conditions for each problematic category
Include a catch-all rule at the end: “IF no previous conditions matched AND Amount > 1000 THEN Route to Default Approver”
This ensures no POs slip through without review.
Approval Flag Configuration:
Ensure approval requirements are properly configured at multiple levels:
Workflow level: Set “Require Approval for All POs” as the baseline rule
Supplier category level: Define category-specific approval requirements in your spend category configuration
Supplier level: Use the “Requires PO Approval” flag as an override only when needed
The hierarchy should be: Workflow default → Category rules → Supplier-specific exceptions
To fix your immediate issue:
Set the approval flag to TRUE for all consulting/professional services suppliers
Update your workflow conditions to explicitly check for these categories
Add validation that prevents PO creation if approval routing fails
Test by creating sample POs for each problematic supplier category
The root cause is likely a combination of incomplete supplier data and workflow conditions that don’t account for all category variations. Fix both the data and the logic to ensure complete approval coverage.
This draft is based on general Workday knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.
Check if your supplier category field is actually populated for those problematic suppliers. Sometimes suppliers get created without complete categorization, and if the workflow condition is looking for a specific category value that’s blank, the condition evaluates to false and the workflow never triggers.
I’d look at the supplier master data setup for those consulting firms. We had a similar issue where certain suppliers had the “Requires PO Approval” flag unchecked at the supplier level, which overrode the workflow conditions. Even though the workflow was configured to require approval for the category, the supplier-specific flag took precedence. Check the supplier records themselves for any flags that might be bypassing workflow logic. Also verify that the supplier category taxonomy matches exactly what your workflow conditions expect - even small differences in category names can cause routing failures.
Good point about the supplier-level flags. I checked about a dozen of the problematic suppliers and found that three of them had approval flags inconsistent with our policy. But that doesn’t explain all the cases. I’m wondering if there’s also an issue with how the workflow evaluates multiple conditions - like category AND amount threshold.
Have you reviewed the workflow condition logic itself in the business process configuration? Sometimes the AND/OR logic between conditions isn’t structured the way you think it is. If your condition is “Category = Consulting OR Amount > 10000” when it should be “Category = Consulting AND Amount > 10000”, you’ll get unexpected behavior. Pull up the actual workflow definition and trace through the condition evaluation.
Also check if your supplier categories are using the current taxonomy version. We had an issue where workflow conditions referenced an old category structure, but suppliers were being tagged with new category values that didn’t match the workflow logic. This created gaps where certain suppliers weren’t caught by any approval rule.
One more thing to verify - does your workflow have a default catch-all rule? If none of the specific conditions match, what happens? Best practice is to have a final condition that catches anything not explicitly routed and sends it to a default approval path. Without that, unmatched POs might slip through with no approval.