You are the Dynamics 365 Finance administrator for a manufacturing company with multiple legal entities. The company uses intercompany transactions between Entity A (US) and Entity B (Germany). Entity A sells raw materials to Entity B. The transactions must be recorded in both entities' ledgers, and the intracompany trade must be eliminated during consolidation. Recently, the accounting team reported that intercompany transactions are not being eliminated correctly. Upon investigation, you find that the intercompany transactions were posted using separate purchase orders and sales orders, not through the intercompany module. The elimination process uses intercompany eliminations rules. What should you do to ensure proper elimination?
Ensures automatic matching and elimination.
Why this answer
The intercompany module in Dynamics 365 Finance is specifically designed to automatically generate matching transactions in both legal entities and to flag those transactions for elimination during consolidation. By recreating the transactions through the intercompany module, you ensure that the intercompany eliminations rules can correctly identify and eliminate the intercompany trade. Deleting the original orders removes the manually created purchase and sales orders that were not linked to the elimination process.
Exam trap
The trap here is that candidates may think manual journal entries or adjusting elimination rules can fix the issue, but the core requirement is that intercompany transactions must be created through the intercompany module to be automatically eliminated during consolidation.
How to eliminate wrong answers
Option B is wrong because reversing and reposting the transactions using the same method (separate purchase orders and sales orders) does not create the necessary intercompany linkage; the elimination rules still cannot identify these transactions as intercompany. Option C is wrong because manual elimination journal entries are a workaround that bypasses the automated elimination rules, leading to potential inconsistencies and additional manual effort; the correct approach is to fix the source transactions. Option D is wrong because adjusting the elimination rules to match manually created transactions would require customizing the rules to detect arbitrary transactions, which is not supported and defeats the purpose of the intercompany module's automated matching.