Consolidation elimination rules not applied correctly for multicurrency intercompany balances

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

We’re having issues with our month-end consolidation process where elimination rules are not processing intercompany balances correctly when multiple currencies are involved. Our elimination rule configuration appears correct for single-currency scenarios, but multicurrency transactions are creating residual balances after elimination.

For example, our US entity (USD) has an intercompany payable of $50,000 to our UK entity (GBP). The UK entity shows a receivable of £38,500. At the month-end exchange rate of 1.30, these should eliminate fully, but we’re seeing a $250 residual difference in the consolidated financials.

I’ve verified the multicurrency setup includes proper exchange rate tables, and individual entity statements are correct. The elimination rule configuration seems to use the exchange rate application at transaction date rather than period-end rate. How should elimination rules handle exchange rate differences for intercompany balances? Is there a specific configuration for multicurrency elimination logic?

2

Let me provide a complete solution covering all three critical areas:

Multicurrency Setup: Your base configuration needs these components properly defined:

  1. Currency Definitions: Consolidation > Setup > Currencies

    • Ensure all entity currencies are defined (USD, GBP, EUR, etc.)
    • Set your consolidation reporting currency (typically parent company currency)
    • Verify precision settings match your reporting requirements (usually 2 decimals for amounts, 6 for rates)

  2. Exchange Rate Tables: Consolidation > Currency Setup > Exchange Rates

    • Maintain two rate types: ‘Transaction Date Rates’ and ‘Period End Rates’
    • Period End Rates table must have rates for the last day of each consolidation period
    • For your example: Ensure December 31 rate of 1.30 USD/GBP exists
    • Load rates for all currency pairs involved in intercompany transactions
    • Use ‘Validate Rate Tables’ utility to identify missing rates before consolidation

  3. Translation Method: Consolidation > Entity Setup > Translation Settings

    • Balance sheet accounts: Use ‘Period End Rate’ for assets/liabilities
    • Income statement: Use ‘Average Rate’ for revenues/expenses
    • Intercompany accounts specifically: Must use ‘Period End Rate’ for elimination matching

Elimination Rule Configuration: This is where your core issue lies. Navigate to Consolidation > Elimination Rules > Intercompany Balances:

  1. Exchange Rate Source Setting:

    • Change from ‘Transaction Date Rate’ to ‘Period End Rate’
    • This ensures both sides of intercompany transactions translate at the same rate during elimination
    • Critical: Without this, your US payable translates at period-end rate but UK receivable might use transaction rate, creating the $250 mismatch

  2. Matching Tolerance:

    • Set ‘Elimination Matching Tolerance’ to handle minor rounding differences
    • Recommended: 0.01% or $10 absolute value, whichever is smaller
    • Your $250 difference exceeds typical rounding, indicating rate source issue

  3. FX Difference Handling:

    • Enable ‘Post FX Differences Separately’ option
    • Specify ‘FX Difference Account’: Create account like 7900-FX-ELIM-VARIANCE
    • This captures legitimate exchange rate timing differences as separate line item
    • These differences should be minimal once rate source is corrected

  4. Elimination Entries Configuration:

    • Ensure rule creates balanced entries: DR Interco Receivable, CR Interco Payable
    • Add third leg for FX variance: DR/CR FX Difference Account
    • Verify the rule uses ‘Consolidated Currency’ for posting amounts

Exchange Rate Application: The specific mechanics of how rates apply during elimination:

  1. Translation Sequence:

    • Entity currencies translate to consolidation currency BEFORE elimination
    • US entity: $50,000 payable stays $50,000 (already in USD)
    • UK entity: £38,500 receivable × 1.30 rate = $50,050 equivalent
    • Difference: $50 is legitimate FX variance (if transaction occurred at different rate)
    • Your $250 variance suggests wrong rate being used somewhere

  2. Rate Application Logic:

    • Period End Rate: Uses last day of consolidation period (Dec 31 rate)
    • Transaction Date Rate: Uses rate from original transaction date (could be Nov 15)
    • Average Rate: Uses weighted average for period (not appropriate for balance sheet)
    • Your elimination rule MUST specify Period End Rate for balance sheet intercompany accounts

  3. Verification Steps:

    • Run ‘Translation Detail Report’ for both entities
    • Verify UK receivable translates at 1.30 rate: £38,500 × 1.30 = $50,050
    • Check if $50,050 vs $50,000 explains your residual
    • If larger variance exists, audit individual transactions for rate inconsistencies

  4. Implementation Path:

    • Backup current elimination configuration and results
    • Update elimination rule: Exchange Rate Source = ‘Period End Rate’
    • Test in sandbox with December data
    • Expected result: Residual should drop from $250 to near-zero (within rounding tolerance)
    • If residual persists, check for missing period-end rates in rate tables
    • Once validated, apply to production and reprocess December consolidation

The root cause is almost certainly the Exchange Rate Source parameter using transaction-date rates instead of period-end rates. This causes each side of the intercompany balance to translate at different rates, creating artificial residuals. After correcting this configuration, your eliminations should balance within acceptable tolerance ranges.

3

You can make the change mid-year, but you’ll need to reverse and reprocess eliminations for all periods you want to correct. The system won’t automatically adjust prior periods. I’d recommend:

  1. Test the change in a sandbox environment first
  2. Document current elimination balances for comparison
  3. Make the configuration change in production
  4. Reverse eliminations starting from the earliest affected period
  5. Rerun consolidation for each period in sequence

This ensures consistency across all periods. The reversal process is clean in CloudSuite - it creates offsetting entries that net to zero.

4

This is a common issue with intercompany eliminations in multicurrency environments. The residual balance you’re seeing is likely the cumulative translation adjustment (CTA) difference. CloudSuite needs to be configured to recognize and handle these FX differences separately from the base elimination.

Check if your elimination rules have the ‘FX Difference Account’ parameter configured. Without this, the system doesn’t know where to post the exchange rate variance.