Sharing our implementation of automated intercompany elimination entries that reduced our monthly close time by 3 days. Previously, our accounting team manually created elimination journal entries for intercompany transactions across 8 legal entities - a process taking 15-20 hours each month and prone to errors.
We built a Power Automate solution that leverages D365’s data entities to identify intercompany transactions, calculate elimination amounts, and automatically post elimination entries. The flow triggers on the 3rd business day of each month and processes all prior month intercompany activity. Key components include automated data entity queries, Power Automate flow orchestration, and validation of intercompany elimination rules before posting. Happy to detail our approach for others facing similar consolidation challenges.
This sounds exactly like what we need. Can you share which specific data entities you’re querying for intercompany transactions? We’ve struggled to identify all intercompany activity reliably - sometimes transactions are coded correctly, sometimes not.
We query three primary entities: GeneralJournalAccountEntry for GL transactions, VendInvoiceJour for AP intercompany invoices, and CustInvoiceJour for AR intercompany invoices. The key is filtering by the IntercompanyAccountType field and matching trading partner relationships. We also implemented data quality checks - the flow flags transactions without proper intercompany coding for manual review before processing eliminations.
For validation in automated financial processes, I always recommend a multi-stage approach: 1) Data quality checks at extraction, 2) Business rule validation before transformation, 3) Reconciliation after posting. In your case, you should validate that intercompany transactions balance to zero across entities before posting eliminations. If they don’t balance, flag for manual review rather than posting partial eliminations.