Our intercompany transaction workflow initiated via ION is getting stuck at the partner resolution step on ICS 2022. The workflow starts successfully but fails to route transactions between our subsidiary entities.
The ION workflow monitor shows status “Pending Partner Resolution” for all intercompany transactions. We have three subsidiaries that need to exchange financial transactions automatically. ION Desk shows the connections as active, but the partner mapping seems incomplete. The logical IDs appear configured, but something in the workflow mapping activity isn’t triggering correctly.
This is blocking our month-end intercompany reconciliation process. Transactions are piling up in pending status. Has anyone successfully configured ION workflows for automated intercompany transaction routing across multiple entities?
We have logical IDs configured for each entity, but I’m not sure about bidirectional setup. Could you clarify what that means? Do we need separate connection points for send and receive?
Your issue stems from incomplete configuration across three critical areas.
ION Desk Partner Setup:
Each subsidiary must be registered as a distinct partner in ION Desk with proper connection points. For three subsidiaries (A, B, C), you need:
- Six connection points total (inbound + outbound per entity)
- Partner relationships defined between all pairs: A↔B, B↔C, A↔C
- Each partner marked as “trusted” for intercompany transaction exchange
- Verify in ION Desk > Partners > Connection Points that all six show “Active” status
Logical ID Configuration:
Your logical IDs must follow the strict format: `lid://infor.cloudsuite.financials.[EntityCode]
- EntityCode must match exactly what’s in your Financials module setup
- Common mistake: using company code instead of entity code
- Test logical ID resolution using ION Desk’s “Test Connection” feature
- Each entity needs its logical ID registered in both ION and the Financials module’s intercompany setup
Workflow Mapping Activity:
This is where routing rules are defined:
- Open ION Desk > Workflows > [Your Intercompany Workflow]
- Edit the “Route Transaction” activity
- Add routing rules for each transaction path:
- Source Logical ID: lid://infor.cloudsuite.financials.ENTITY_A
- Destination Logical ID: lid://infor.cloudsuite.financials.ENTITY_B
- Document Type: SyncIntercompanyTransaction
- Repeat for all six directional paths (A→B, B→A, B→C, C→B, A→C, C→A)
- Set routing priority if multiple paths exist
Verification Steps:
- Test each partner connection individually in ION Desk
- Send a test document from A to B to verify routing works
- Check workflow monitor for successful routing (should show “Routed to Partner” not “Pending”)
- Verify transaction appears in destination entity’s intercompany inbox
Once all three areas are properly configured with bidirectional relationships and correct logical ID formats, your intercompany automation should flow smoothly. The “Pending Partner Resolution” status will resolve once the workflow can match source and destination logical IDs to registered partners.
Yes, bidirectional means each entity needs both outbound and inbound connection points defined in ION Desk. For three subsidiaries, that’s six connection points total (two per entity). Also verify that your workflow mapping activity has the correct routing rules. The activity needs to map source logical ID to destination logical ID for each possible transaction path. Without proper routing rules, the workflow engine can’t determine where to send transactions.
We checked and our logical ID format was incorrect - missing the entity prefix. We’re updating that now. But I’m still unclear on the workflow mapping activity configuration. Where exactly do we define the routing rules between subsidiaries?
Check your ION Desk partner setup first. Each subsidiary needs to be registered as a separate partner with unique logical IDs. The workflow mapping won’t trigger if partner relationships aren’t bidirectional. Did you set up partner connections in both directions between all three subsidiaries?
Beyond connection points, check the logical ID format. ICS 2022 expects a specific format: lid://infor.cloudsuite.entity.[EntityCode]. If your logical IDs don’t match this pattern, partner resolution will fail silently. Also ensure the EntityCode in your logical ID matches exactly what’s configured in the Financials module for each subsidiary.