We’re encountering balance mismatches in our intercompany reporting after implementing event rules to automate cross-company journal entries. When Company A records a transaction that should create a corresponding entry in Company B, the intercompany reconciliation report shows the entries are out of balance by varying amounts.
The event rules are firing correctly and creating journal entries in both companies, but the amounts don’t always match. Sometimes the difference is in the foreign currency translation, other times it appears to be a rounding issue. This is creating significant delays in our period-end close process because we have to manually investigate and correct each discrepancy.
The intercompany rules mapping looks correct in the configuration, and the same account mapping works fine when we manually post intercompany journals. It’s specifically when the event rules trigger the automated entries that we see these balance issues. Has anyone experienced similar problems with event rules impacting intercompany reconciliation report logic?
That’s definitely part of the problem. When event rules fire asynchronously, each company’s journal entry might query the exchange rate table (F0015) at slightly different times. If your exchange rates are being updated frequently or if there’s any caching involved, you could get different rates for what should be a matched pair of entries. You need to pass the exchange rate explicitly in the event rule parameters rather than letting each entry fetch it independently. Also check your intercompany rules mapping - make sure the currency conversion method is set to use the originating company’s rate, not recalculate at the destination.
Susan’s advice about exchange rates is solid. I’d also look at the reconciliation report logic itself. After implementing event rules, you might need to adjust how the intercompany reconciliation report queries data. Event rules can create entries with different timestamps or batch numbers than manual entries, and if your reconciliation report filters by batch or date range, it might be catching one side of the transaction but not the other. Try running the report with broader date parameters to see if the mismatches disappear - that would indicate a timing/filtering issue rather than an actual balance problem.