Your company’s intercompany transactions balance perfectly within each legal entity. General ledger accounts zero out to the cent when you print a subledger report. But when you run the consolidated ledger elimination process in Dynamics 365 Finance, the elimination entries don’t match the detail you’re looking at, the reports don’t tie back, and your financial close process stalls while the accounting team investigates discrepancies that shouldn’t exist.
This isn’t a rounding error or a posting issue. Intercompany accounting in Dynamics 365 Finance operates on assumptions about how intercompany transactions flow through the chart of accounts, how elimination entries get created, and how consolidated reporting aggregates data across legal entities. When those assumptions don’t align with your actual business structure, transactions don’t eliminate cleanly, reconciliation becomes manual, and the close process loses the automation benefit that makes consolidation work.
How Intercompany Accounting Is Supposed to Work
Dynamics 365 Finance treats intercompany transactions as a special case within the general ledger. When one legal entity (the originating company) records a transaction with another legal entity (the counterparty), both sides record the transaction independently. The originating company records the full transaction amount and an intercompany payable or receivable. The counterparty records the mirror transaction and an intercompany receivable or payable. These two sides are supposed to eliminate when you consolidate.
The elimination process is straightforward conceptually: find all intercompany balances, create offsetting entries to zero them out at the consolidation level, and produce a consolidated financial statement that shows only external transactions. In practice, Finance requires you to identify which accounts are intercompany balances, set up elimination rules, and ensure that the consolidation process knows how to match and eliminate transactions.
Where things diverge from this ideal is in the details of how intercompany transactions actually map to accounts. Finance assumes intercompany receivables and payables flow through specific account structures. If your chart of accounts doesn’t follow that structure, or if your intercompany transactions post to unexpected account combinations, the elimination logic can’t find matching pairs to eliminate.
Why Elimination Entries Don’t Match Your Subledger
The root cause usually sits in one of three places: account mapping, transaction routing, or elimination rule configuration.
Account mapping issues: Intercompany receivables and payables need to map to specific accounts that the elimination process recognizes. If your chart of accounts assigns different accounts for intercompany activity than the elimination rules expect, transactions won’t match. For example, if you have intercompany sales recorded against one receivable account but intercompany service fees recorded against another, and your elimination rules only target the first account, service fee intercompany balances persist in the consolidated ledger.
Dimensional mismatch: Dimensions are where intercompany accounting often breaks down in practice. If your originating company records an intercompany transaction tagged with a specific cost center or business unit dimension, but the counterparty company records the mirror transaction without that same dimension combination, the two entries won’t find each other during elimination. The consolidation engine can’t match and eliminate transactions that have different dimension combinations, even if the account numbers and amounts are identical.
Timing and period mismatch: Intercompany transactions posted in one period in the originating company may not be received and matched in the counterparty company until the next period. If you try to run elimination at period-end before the counterparty company has received and recorded the transaction, the elimination process will create a temporary imbalance. This is especially common in month-end closes when one entity’s period ends before another’s, or when intercompany invoices are issued late in the month.
Control account vs. detail account confusion: Many implementations assign intercompany transactions to control accounts in the general ledger but then try to reconcile using subledger detail accounts. Finance’s elimination engine works at the general ledger level, not the subledger level. If the control account total is correct but the subledger detail account distribution doesn’t match what elimination expects, you’ll see reconciliation mismatches.
How to Diagnose the Problem
Start with a simple reconciliation: for each intercompany payable and receivable account, calculate the balance in the originating company’s general ledger, then calculate the mirror balance in the counterparty company’s general ledger. These two numbers should be equal and opposite. If they’re not, the problem is upstream of the elimination process.
If the balances match, the issue is in how the consolidation process is configured. Navigate to the consolidation elimination rules in Finance and verify that the account mappings and dimension rules are set up to match your actual posting. The elimination rules should specify which accounts contain intercompany balances, how they map between legal entities, and which dimension combinations are included in the elimination logic.
A common troubleshooting technique is to export the elimination entries that Finance generated, then manually reconcile them back to the intercompany transactions in your subledger. If the elimination entries don’t match specific subledger transactions, you’ve found the problem: either a transaction posted to an account the elimination rules don’t cover, or a dimension combination that doesn’t align between the two companies.
Designing Intercompany Accounting That Actually Eliminates
The cleanest approach is to standardize how intercompany transactions post across all legal entities. Define a consistent chart of accounts for intercompany receivables and payables, with the same account numbers used in every legal entity. If you use dimensions to tag transactions, establish a rule that intercompany transactions must be tagged with identical dimension combinations in both the originating and counterparty companies.
Consider whether you truly need dimensional detail on intercompany balances. Many implementations create dimensional complexity that adds no value to the intercompany reconciliation. If cost center assignment doesn’t affect how you manage intercompany payables, don’t require a cost center dimension on those transactions. Simpler account structures mean cleaner eliminations.
Set up a pre-consolidation reconciliation process in Finance. Before running elimination, generate a report of all intercompany balances, grouped by company pair, account, and dimension. Reconcile this to your subledger detail. If discrepancies appear, resolve them before you run the consolidation. This prevents the elimination engine from encountering unmatched transactions.
If you’re running multiple consolidation entities with nested parent-subsidiary relationships, test your elimination logic at each level. A common failure mode is that consolidation works correctly at the first level (subsidiary to intermediate parent) but breaks at the second level (intermediate parent to ultimate parent) because dimension combinations or account assignments drift as you go up the hierarchy.
When to Use External vs. Internal Elimination
Finance supports two elimination approaches: internal elimination (within Finance, using the consolidation module) and external elimination (in a separate consolidation tool or process). Internal elimination is simpler if your intercompany transactions follow a clean, standardized structure. External elimination is more flexible if your transactions are complex or your intercompany relationships don’t fit Finance’s default assumptions.
If you’ve been troubleshooting intercompany eliminations for months and the mismatches persist, it may be worth evaluating whether an external consolidation engine better serves your structure. Some organizations find that moving complex intercompany and consolidation logic to a dedicated consolidation tool reduces the burden on the Finance general ledger and makes the close process more transparent.
Preparation for Implementation
If you’re building an intercompany accounting structure from scratch, start by documenting your actual intercompany flow: which companies transact with each other, what types of transactions (sales, services, loans, expense allocations), and whether dimensional detail is needed on each type. Then design your chart of accounts and elimination rules to match that flow exactly.
Before you go live, run a full consolidation cycle with representative historical data. Create test transactions that cover every intercompany transaction type, post them in both the originating and counterparty companies, and run elimination. Verify that the elimination entries match the transactions you created, and that the consolidated ledger balances correctly. If you find mismatches at this point, you’re catching them before real transactions are in the system.
Assign one person ownership of the intercompany reconciliation and elimination process. That person should understand how the system is configured, have access to the elimination rules and the subledger detail, and be responsible for ensuring the process runs correctly every month. Intercompany accounting has a way of drifting if no one is explicitly in charge of keeping it clean.
Intercompany accounting is one of the places where small configuration oversights create large reconciliation problems. Taking time upfront to design and test your structure eliminates months of frustration during the close process.
Routeget Technologies: Our Finance & Operations consulting team helps enterprises design and implement intercompany accounting structures that consolidate cleanly and close on time, whether you’re building from scratch or fixing an existing implementation that’s struggling with elimination reconciliation.
#IntercompanyAccounting #Dynamics365Finance #FinanceImplementation #ConsolidatedReporting #ERPGovernance #AccountingAutomation #FinanceOperations #Dynamics365Implementation
No comment yet, add your voice below!