Consolidation reporting shows currency mismatch errors for multi-entity reports

ERP Infor CloudSuite
, , , , , , , ,
1

Our month-end consolidation reports are failing with currency mismatch errors when we try to generate consolidated financial statements across our European entities. This is critical as we’re three days into our close process and can’t finalize the consolidated results.

The specific error we’re seeing:


ERROR: Currency conversion failed
Entity: DE_Operations (EUR)
Target Currency: USD
Conversion Date: 2025-06-30
Rate not found for currency pair EUR/USD

The strange thing is that we have exchange rates loaded in the currency conversion table for June 2025, and individual entity reports in EUR work fine. The issue only appears when the consolidation report tries to convert multiple entities to USD for the consolidated view.

We’ve verified that the entity rate setup includes all our entities (Germany, France, Netherlands) and their base currencies are correctly configured. The currency conversion table shows daily rates through June 30th. However, when we try to reprocess the consolidation report, it still fails with the same currency pair error.

This is blocking our month-end close and we need to report consolidated results to corporate by end of week. Has anyone dealt with similar currency conversion issues in ICS 2022 consolidation reporting? Do we need to refresh the conversion cache or is there a specific report reprocessing sequence we should follow?

system 2

Here’s the complete resolution process addressing all three focus areas systematically:

Currency Conversion Table: The error indicates rates aren’t being found during consolidation processing. ICS 2022 uses a dedicated consolidation rate table separate from GL rates. Here’s how to fix it:

  1. Navigate to Financial Management > Currency Management > Consolidation Exchange Rates
  2. Verify rates exist for all currency pairs needed for your consolidation:
    • EUR/USD
    • Any other entity currencies to USD
  3. Check the rate effective dates - they must match your report period end date (June 30, 2025) exactly
  4. If rates are missing, you have two options:

Option A - Manual entry:


Currency From: EUR
Currency To: USD
Rate Type: PERIOD_END
Effective Date: 2025-06-30
Rate: 1.0734

Option B - Sync from GL rates:

Run the batch job “SYNC_CONSOLIDATION_RATES” from System Administration > Batch Jobs. This copies rates from GL_DAILY_RATES to CONSOLIDATION_RATES for the specified period.

  1. After loading rates, verify them by running a test query: Financial Management > Reports > Currency Rate Validation Report

Enter date range: 2025-06-01 to 2025-06-30

This shows all available consolidation rates and highlights any gaps.

Entity Rate Setup: Each entity must be properly configured for consolidation currency conversion:

  1. Go to Financial Management > Entity Management > Entity Master
  2. For each entity (DE_Operations, FR_Operations, NL_Operations):
    • Verify “Functional Currency” is set correctly (EUR for European entities)
    • Check “Consolidation Currency” is set to USD
    • Confirm “Rate Type” matches what’s in your rate table (typically PERIOD_END for balance sheet, MONTHLY_AVG for P&L)
  3. Critical: The “Consolidation Rate Method” field must be set to “Use Consolidation Rate Table” not “Use GL Rates”
  4. Save changes and verify by viewing the entity consolidation settings summary

If any entity has the wrong rate method configured, the consolidation engine won’t find rates even if they exist in the table.

Report Reprocessing: After fixing rates and entity configuration, proper reprocessing is essential:

  1. First, clear the consolidation cache to remove failed calculation attempts: System Administration > Cache Management > Clear Consolidation Cache

    Select date range: June 2025

  2. Reprocess the consolidation in the correct sequence:

    • Stage 1: Refresh entity-level data (Financial Management > Consolidation > Refresh Entity Data)
    • Stage 2: Run currency translation (Financial Management > Consolidation > Execute Currency Translation)
    • Stage 3: Run elimination entries if applicable
    • Stage 4: Generate consolidated reports

  3. Don’t skip stages - the consolidation engine requires sequential processing. If you jump straight to report generation, cached errors persist.

  4. Monitor the consolidation process log (Financial Management > Consolidation > Process Monitor) to verify each stage completes successfully.

  5. If translation still fails, check the detailed log for specific entity/currency pair causing issues: View Consolidation Log > Filter by Error Type: Currency Conversion

    This shows exactly which entity and date combination is missing rates.

Additional Troubleshooting: If the above steps don’t resolve it:

  • Verify no entity hierarchies have circular references that could cause consolidation loops
  • Check if any entities have “Exclude from Consolidation” flag accidentally set
  • Confirm the consolidation report template is set to use the correct rate types for balance sheet vs. income statement accounts
  • Review security settings - ensure your user role has access to consolidation rate tables (some installations restrict this to treasury roles)

For urgent month-end close, you can temporarily use a manual consolidation approach: export entity reports to Excel, apply rates manually, and import consolidated results. This is a workaround while you resolve the systematic issue, but it lets you meet reporting deadlines.

After successful reprocessing, schedule the SYNC_CONSOLIDATION_RATES job to run automatically on the last business day of each month to prevent recurrence.

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.

3

I’ve seen this before - the consolidation engine uses a different rate table than standard reporting. Check if you’ve loaded rates into both the GL_DAILY_RATES table and the CONSOLIDATION_RATES table. They’re separate in ICS 2022 and consolidation reports specifically look at the consolidation rate table.

4

That’s a good point about separate tables. How do I verify which table the rates are in? And if they’re only in GL_DAILY_RATES, how do we copy them to CONSOLIDATION_RATES?

5

You can check the rates in CloudSuite admin under Financial Management > Currency Management > Consolidation Exchange Rates. If the June rates aren’t there, you’ll need to either manually enter them or run the rate synchronization job that copies from GL rates to consolidation rates. The job is usually scheduled monthly but can be run on-demand. Look for the “Sync Exchange Rates” batch job in the job scheduler.

6

Beyond just having rates in the table, check the effective date ranges. Consolidation reports in ICS 2022 are very particular about rate effective dates matching the report period end date exactly. If your rates are dated June 29th but the report period ends June 30th, it will fail with that “rate not found” error even though a rate exists. The date matching has to be precise.

7

Also verify the entity setup includes the correct rate type for consolidation. Each entity should have a designated rate type (like MONTHLY_AVG or PERIOD_END) configured in the entity master data. If the rate type doesn’t match what’s in the consolidation rate table, the lookup fails. This is a common configuration oversight after entity additions or reorganizations.