Approval workflow for journal entries in financial accounting routing inconsistently with multiple cost centers

We’re having major issues with our journal entry approval workflow that’s causing significant delays in our month-end close process. The problem specifically occurs when journal entries span multiple cost centers.

The workflow routing is completely inconsistent - sometimes entries go to the right approvers, sometimes they skip approval levels, and occasionally they get stuck entirely. When a journal entry includes transactions across 3-4 different cost centers, the approval routing seems to get confused about who should review what.

This is severely impacting our close timeline. Last month-end took an extra 3 days because we had to manually track down approvers and push entries through the system. We need the workflow to reliably route based on cost center ownership, but right now it’s unpredictable.

Anyone else dealt with multi-cost-center approval routing problems in Workday R1 2024? We’re using the standard financial accounting business process with some custom routing rules.

Your inconsistent routing with multiple cost centers stems from three interconnected configuration issues that need to be addressed systematically:

1. MULTIPLE COST CENTERS ON JOURNAL ENTRY: When a journal entry spans multiple cost centers, Workday’s default behavior is to evaluate ALL cost centers against your routing rules, which creates conflicts if the rules aren’t designed for this scenario. You need to explicitly define which cost center takes routing precedence.

In your business process configuration, add a primary routing rule that determines the controlling cost center. Common approaches:

  • Route based on the cost center with the largest transaction amount
  • Route based on the debit side cost center (or credit side, be consistent)
  • Route based on a designated ‘primary’ cost center field if your journal entry template includes one

Implement this by adding a condition at the TOP of your approval step: ‘If journal entry has multiple cost centers, route to [Primary Cost Center Manager]’. Define ‘Primary Cost Center’ using a calculated field or business process variable that evaluates your chosen logic.

2. APPROVAL ROUTING INCONSISTENT: The inconsistency happens because your routing conditions lack proper prioritization and conflict resolution. Based on your description of having rules for cost centers, amounts, and GL accounts, these are likely triggering simultaneously and competing.

Restructure your approval step conditions in this priority order:

  1. Exception handling rules (specific GL accounts requiring special approval)
  2. High-value thresholds (amount-based routing that overrides normal flow)
  3. Multi-cost-center logic (as described above)
  4. Standard single-cost-center routing
  5. Default/catch-all rule

Each condition should use ‘AND’ logic to be mutually exclusive. For example:

  • Condition 1: ‘GL Account = 7000-7999 AND Amount > 10000’ → Route to Controller
  • Condition 2: ‘Multiple Cost Centers = True AND Amount > 5000’ → Route to Primary Cost Center Manager THEN Accounting Director
  • Condition 3: ‘Single Cost Center = True’ → Route to Cost Center Manager

The key is ensuring only ONE condition can be true for any given journal entry. Test your logic by creating a decision matrix that maps different journal entry scenarios to their expected routing path.

3. DELAYS IN WORKFLOW COMPLETION: The delays during month-end close occur because your workflow lacks timeout and escalation handling for multi-cost-center approvals. When entries get stuck, there’s no automatic escalation path.

Add these configurations to your approval steps:

  • Set approval deadlines: Configure ‘Due Date’ to be 24 hours from submission for standard entries, 48 hours for multi-cost-center entries
  • Enable escalation: If approval isn’t completed within the deadline, escalate to the next level manager or to a designated accounting supervisor group
  • Add notification reminders: Send reminder notifications at 12 hours and 23 hours if approval is still pending
  • Configure ‘Approve on Behalf’ permissions: Allow accounting supervisors to approve on behalf of cost center managers during close periods to prevent bottlenecks

For your specific multi-cost-center scenario, I recommend implementing a two-tier approval structure:

  • Tier 1: Primary cost center manager (determined by your precedence logic)
  • Tier 2: Accounting operations manager (reviews all multi-cost-center entries as a control point)

This ensures consistent routing while maintaining proper segregation of duties. The accounting ops manager serves as the conflict resolver when multiple cost centers are involved.

To implement these fixes without disrupting current operations, create a copy of your existing business process, make these configuration changes in the copy, and test thoroughly with representative journal entries before activating. Focus your testing on entries that previously routed inconsistently to validate the new logic handles them correctly.


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.

I think the issue might be with how your conditional routing is set up. When you have multiple cost centers on a single journal entry, Workday needs clear logic about which cost center takes precedence for routing. Check if your business process has conflicting conditions - like one rule saying ‘route to Cost Center A manager’ and another saying ‘route to Cost Center B manager’ for the same entry. This creates ambiguity that causes the inconsistent behavior you’re seeing.

We had a similar problem and discovered it was related to the approval chain configuration. For journal entries with multiple cost centers, you need to decide whether approvals should be sequential (each cost center manager approves in order) or parallel (all cost center managers approve simultaneously). If your business process isn’t explicitly configured for one approach, the system defaults to unpredictable behavior. Also check if you have ‘Approve All’ versus ‘Approve Any’ logic configured correctly.

That’s helpful context. Looking at our business process, I see we have multiple routing conditions but they’re not prioritized. We have rules for primary cost center, rules for transaction amount thresholds, and rules for specific GL accounts. When a journal entry triggers multiple conditions simultaneously, I think that’s where the routing breaks down. How do you handle prioritization when multiple routing rules could apply?

Prioritization is done through the order of conditions in your business process steps. Workday evaluates routing conditions from top to bottom and applies the first matching condition. If you have overlapping rules, you need to structure them hierarchically. Put your most specific conditions first (like ‘if amount > 50000 AND multiple cost centers’) and more general conditions last (like ‘route to cost center manager’). This prevents conflicts when multiple criteria match.

Tested this on Workday Financial Management 2023R2 — adding a primary routing rule in Business Process Framework to designate the controlling cost center eliminated our inconsistent multi-cost-center journal entry approvals immediately.

Don’t forget about the security group assignments in your routing rules. If a cost center manager isn’t in the correct security group or if there are multiple people in overlapping groups, the workflow can’t determine the correct approver. For multi-cost-center entries, I recommend creating a dedicated ‘Multi-Entity Journal Approvers’ security group with clear membership rules so the workflow has a consistent target for routing these complex entries.