I implemented this exact fix for a client with 12 international subsidiaries last quarter. Here’s the complete solution addressing all three critical areas:
1. Approval Matrix Currency Mapping:
First, reconfigure your approval matrix to work with normalized amounts. In Infor OS Workflow Designer, navigate to your quote approval workflow and modify the approval routing node:
// Set currency normalization property
workflow.approvalMatrix.useCurrencyConversion=true
workflow.approvalMatrix.baseCurrency=USD
workflow.approvalMatrix.conversionTiming=PRE_EVALUATION
This ensures the workflow converts quote amounts to your base currency BEFORE comparing against approval thresholds.
2. Localized ISO Currency Codes:
Verify your currency mappings include proper ISO 4217 codes and decimal precision for each subsidiary:
- Navigate to System Configuration > Localization > Currency Mappings
- Ensure mappings exist: EUR (978, 2 decimals), JPY (392, 0 decimals), SGD (702, 2 decimals)
- Set the conversion rate source to “Daily” for operational workflows
- Enable “Real-time Rate Fetch” if you have integration with external rate providers
The decimal precision is critical - JPY calculations will fail if the system expects 2 decimal places.
3. Workflow Error Handling:
Implement proper error handling for currency conversion failures:
- Add a validation node before approval routing that checks for valid exchange rates
- Configure fallback behavior: either use last known rate with warning notification, or route to manual approval queue
- Set up alerts to finance team when rate fetch fails
In your workflow XML, add this validation step:
<validate-currency-conversion>
<on-failure action="route-to-manual-queue"/>
<notify role="FinanceOps"/>
</validate-currency-conversion>
Testing Approach:
After making these changes, test with quotes in each subsidiary currency at amounts just above and below each threshold level. Create test quotes at 9K EUR, 11K EUR, 48K JPY, and 52K JPY to verify proper routing.
Additional Configuration:
If you’re still seeing issues, check that your subsidiary legal entities have the “Currency Override” flag disabled in their entity configuration. This flag can cause the system to bypass currency conversion logic entirely.
The key insight is that approval matrix evaluation must happen AFTER currency normalization, and your ISO currency codes must match exactly what’s configured in the localization module. This is a common issue when companies expand internationally without updating their workflow architecture to handle multi-currency scenarios properly.
This draft is based on general Infor CloudSuite knowledge. It has not been verified against your specific version and environment. Practitioners: verify the steps and share your experience below.