6.1 Intercompany Accounting Setup & Due-To / Due-From Postings

Key Takeaways

  • Intercompany accounting in Dynamics 365 Finance requires explicit pairwise relationship configuration between Originating and Destination legal entities under General ledger > Posting setup > Intercompany accounting.
  • When an intercompany transaction is posted, the posting engine automatically generates dual-company balancing vouchers using configured Due-To (Liability) and Due-From (Asset) balance sheet accounts.
  • For an enterprise with N interacting legal entities, up to N × (N - 1) directional pairwise configurations are defined to govern bi-directional cross-company financial transactions.
  • The Destination legal entity must have an active, valid journal name specified in the setup to receive and post the automated counter-voucher.
  • Intercompany currency conversions resolve transaction amounts into the originating and destination accounting currencies using configured exchange rate types, preserving debit/credit equilibrium across both ledgers.
Last updated: August 2026

6.1 Intercompany Accounting Setup & Due-To / Due-From Postings

Quick Summary: In multi-entity enterprise architectures, business transactions frequently span legal entity boundaries—such as a corporate headquarters paying shared expenses on behalf of an operating subsidiary, or centralized shared service centers invoicing cross-company services. Microsoft Dynamics 365 Finance automates multi-company accounting through the Intercompany Accounting framework (General ledger > Posting setup > Intercompany accounting). By establishing pairwise entity relationships and mapping Due-To (Intercompany Payable) and Due-From (Intercompany Receivable) balance sheet accounts, the posting engine automatically generates self-balancing, dual-company vouchers in real time without manual journal re-entry.


1. Architectural Framework of Intercompany Accounting

In Dynamics 365 Finance, each legal entity (DataAreaId) maintains its own independent General Ledger, Chart of Accounts assignment, accounting currency, and trial balance. When a transaction in one legal entity incurs an obligation or transfers value to another legal entity, standard accounting principles dictate that both balance sheets must reflect the mutual debtor-creditor relationship.

+---------------------------------------------------------------------------------------------------------+
|                                 Intercompany Transaction Conceptual Model                               |
+---------------------------------------------------------------------------------------------------------+
|  ORIGINATING LEGAL ENTITY: USMF (HQ - USA)              DESTINATION LEGAL ENTITY: DEMF (Subsidiary - DE)|
|  Accounting Currency: USD                               Accounting Currency: EUR                        |
|                                                                                                         |
|  1. Initiates payment for consulting services ($5,000)  2. Incurs consulting expense ($5,000 / €4,500)  |
|     on behalf of DEMF.                                     without direct cash disbursement.            |
|                                                                                                         |
|  +--------------------------------------------------+   +---------------------------------------------+ |
|  | Voucher USMF-001                                 |   | Voucher DEMF-001 (Automated Counter-Voucher)| |
|  | - Credit: Cash / Bank (110110)        $5,000     |   | - Debit: Consulting Expense (610500) €4,500 | |
|  | - Debit:  Due From DEMF (Asset 130500)$5,000     |   | - Credit: Due To USMF (Liab 210500)  €4,500 | |
|  +--------------------------------------------------+   +---------------------------------------------+ |
|                                    Mutual Intercompany Balance                                          |
|                             [Asset: Due From DEMF] <---> [Liability: Due To USMF]                       |
+---------------------------------------------------------------------------------------------------------+

Core Roles in Intercompany Postings

  • Originating Legal Entity (Source Company): The legal entity where the user or automated process initiates and posts the journal entry, vendor invoice, or expense report. The originating entity physically records the primary debit or credit (e.g., cash disbursement, vendor liability).
  • Destination Legal Entity (Target Company): The legal entity that receives the allocated expense, revenue distribution, asset addition, or balance sheet reclassification. The destination entity does not disburse cash directly; instead, it incurs a corresponding intercompany liability or asset against the originating entity.

2. Configuring the Pairwise Intercompany Accounting Matrix

Intercompany accounting parameters are not configured globally across all companies simultaneously; instead, they are established as explicit pairwise relationships under General ledger > Posting setup > Intercompany accounting.

Pairwise Configuration Parameters

For every interacting company pair, the functional consultant must define the posting parameters for both directions:

Configuration FieldDescription & Functional PurposeAccount Type & Classification
Originating Legal EntityThe initiating company context (e.g., USMF).System Legal Entity Identifier
Destination Legal EntityThe target company context (e.g., DEMF).System Legal Entity Identifier
Debit Account (Originating)The main account debited in the Originating entity when a transaction creates a receivable against the destination entity.Balance Sheet / Asset (Due From Target)
Credit Account (Originating)The main account credited in the Originating entity when a transaction creates a payable to the destination entity.Balance Sheet / Liability (Due To Target)
Debit Account (Destination)The main account debited in the Destination entity when a transaction creates a receivable against the originating entity.Balance Sheet / Asset (Due From Source)
Credit Account (Destination)The main account credited in the Destination entity when a transaction creates a payable to the originating entity.Balance Sheet / Liability (Due To Source)
Journal Name (Destination)The General Journal name in the Destination entity used to post the automated counter-voucher.Daily / General Ledger Journal Name
+---------------------------------------------------------------------------------------------+
|                     Pairwise Matrix Formula for N Interacting Legal Entities                |
|                                                                                             |
|   Max Configured Directions = N × (N - 1)                                                   |
|   - 2 Legal Entities (USMF, DEMF): 2 × 1 = 2 Pairwise Rules (USMF->DEMF, DEMF->USMF)        |
|   - 4 Legal Entities (USMF, DEMF, GBSI, USRT): 4 × 3 = 12 Pairwise Rules                     |
+---------------------------------------------------------------------------------------------+

[!IMPORTANT] Symmetry Requirement: Intercompany setup is strictly directional. Configuring USMF -> DEMF enables USMF users to post transactions affecting DEMF. However, if a DEMF user attempts to post a journal targeting USMF without a reciprocal DEMF -> USMF record, the system throws a hard posting error: "Intercompany posting setup does not exist between originating legal entity DEMF and destination legal entity USMF."


3. Due-To & Due-From Posting Mechanics & Dual-Company Vouchers

When an intercompany journal line is posted, the Dynamics 365 Finance posting engine evaluates the ledger rules and performs an atomic transaction commit across both company databases:

  1. Originating Voucher Generation: The system creates a voucher in the originating company with the primary transaction line and generates an automatic balancing line using the Originating Due-From (Debit) or Due-To (Credit) main account.
  2. Destination Counter-Voucher Generation: The system creates a counter-voucher in the destination company with the target offset account and the Destination Due-To (Credit) or Due-From (Debit) main account.
  3. Voucher Linkage: Both vouchers are permanently cross-referenced via internal system references (IntercompanyVoucher and IntercompanyCompanyId), allowing auditors to drill directly from the USMF voucher into the DEMF voucher.

Dual-Company Accounting Entry Flow Table

Consider a corporate scenario where USMF pays a $10,000 IT infrastructure bill on behalf of DEMF:

Legal EntityVoucher IDMain AccountAccount NameAccount TypeDebitCreditPosting Layer
USMF (Originating)USMF-GJ-10024110110Operating Bank USDAsset$10,000Current
USMF (Originating)USMF-GJ-10024130500Due From DEMF (IC Receivable)Asset$10,000Current
DEMF (Destination)DEMF-GJ-00819618200IT Infrastructure ExpenseExpense€9,100Current
DEMF (Destination)DEMF-GJ-00819210500Due To USMF (IC Payable)Liability€9,100Current

Note: Exchange rate applied: 1.00 USD = 0.91 EUR (€9,100 EUR equivalent).

Both individual vouchers are fully balanced in their respective accounting currencies ($10,000 USD in USMF and €9,100 EUR in DEMF), preventing any out-of-balance trial balance anomalies.


4. Destination Journal Name & Number Sequence Requirements

A critical, frequently tested configuration component is the Journal Name specified on the Destination tab of the Intercompany accounting form.

Destination Journal Name Constraints

  1. Must Exist in the Destination Legal Entity: The journal name specified in the setup (e.g., IC_GenJrn) must be configured under General ledger > Journal setup > Journal names inside the destination legal entity (DEMF), not just in the originating entity.
  2. Journal Type: Must be configured with Journal type Daily (General journal).
  3. Number Sequence Allocation: The destination journal name must reference a valid, non-depleted number sequence in the destination company to generate the counter-voucher number.
  4. Posting Restrictions & Workflow: If the destination journal name has active journal control restrictions, user group blocks, or mandatory workflow approval activated, automated intercompany counter-voucher posting will fail unless the system background batch service has appropriate posting privileges.

[!CAUTION] If the Destination Journal Name field is left blank, or if the referenced journal name does not exist in the destination legal entity, any attempt to post an intercompany transaction will abort immediately with an execution error during posting validation.


5. Intercompany Currency Translation & Conversion Rules

When the Originating and Destination legal entities operate in different accounting currencies, Dynamics 365 Finance executes real-time multi-currency conversions during posting:

+---------------------------------------------------------------------------------------------------------+
|                                 Multi-Currency Intercompany Translation Engine                          |
+---------------------------------------------------------------------------------------------------------+
|  Journal Line Input (USMF): EUR 10,000 (Transaction Currency)                                           |
|                                                                                                         |
|  Step 1: Convert to USMF Accounting Currency (USD)                                                      |
|          - Uses USMF Exchange Rate Type (Default: 'Default') on Posting Date                            |
|          - Exchange Rate: 1 EUR = 1.10 USD  ==>  USMF Voucher Amount: $11,000 USD                       |
|                                                                                                         |
|  Step 2: Convert to DEMF Accounting Currency (EUR)                                                      |
|          - Uses DEMF Exchange Rate Type on Posting Date                                                 |
|          - Exchange Rate: 1 EUR = 1.00 EUR  ==>  DEMF Voucher Amount: €10,000 EUR                       |
|                                                                                                         |
|  Result: USMF records $11,000 Due-From Asset; DEMF records €10,000 Due-To Liability.                    |
+---------------------------------------------------------------------------------------------------------+

Exchange Rate Provider & Triangulation

  • The system utilizes the exchange rate defined in the originating company to convert the transaction currency to the originating accounting currency.
  • The destination voucher records the transaction currency amount and calculates the destination accounting and reporting currency amounts using the destination ledger's currency parameters and active exchange rates.
  • Realized and unrealized foreign exchange gains and losses are calculated during month-end Foreign Currency Revaluation runs on the Due-To and Due-From main accounts if they hold open foreign currency balances.

6. Step-by-Step Configuration Walkthrough

To establish a fully functional pairwise intercompany accounting relationship between USMF (USA) and DEMF (Germany):

Step 1: Create Dedicated Due-To / Due-From Main Accounts

  1. Navigate to General ledger > Chart of accounts > Accounts > Main accounts.
  2. Create Account 130500 (Name: Intercompany Receivable - DEMF, Type: Asset).
  3. Create Account 210500 (Name: Intercompany Payable - USMF, Type: Liability).
  4. Set Do not allow manual entry to Yes on both accounts to prevent unlinked manual journal tampering.

Step 2: Configure Destination Journal Name

  1. Switch legal entity context to DEMF.
  2. Navigate to General ledger > Journal setup > Journal names.
  3. Create a new Journal name IC_Gen with Journal type Daily and assign an active voucher number sequence.

Step 3: Configure Pairwise Intercompany Relationship

  1. Switch legal entity context back to USMF.
  2. Navigate to General ledger > Posting setup > Intercompany accounting.
  3. Click New:
    • Originating legal entity: USMF
    • Destination legal entity: DEMF
  4. On the Originating legal entity tab:
    • Debit account (Receivable): 130500
    • Credit account (Payable): 210500
  5. On the Destination legal entity tab:
    • Debit account (Receivable): 130500
    • Credit account (Payable): 210500
    • Journal name: IC_Gen
  6. Click Save.
  7. Repeat steps with DEMF as Originating and USMF as Destination to establish full bi-directional symmetry.
Loading diagram...
Pairwise Intercompany Dual-Voucher Generation Engine
Test Your Knowledge

An enterprise operates three legal entities: USMF (United States), DEMF (Germany), and GBSI (United Kingdom). The corporate controller wants accountants in all three legal entities to be able to post intercompany expenses and cross-company journal allocations to one another. What is the minimum number of pairwise intercompany accounting relationship records that must be configured under General ledger > Posting setup > Intercompany accounting?

A
B
C
D
Test Your Knowledge

An accountant in company USMF attempts to post a general journal voucher that distributes a consulting expense to legal entity DEMF. During posting, the system throws an error stating that the counter-voucher cannot be generated in DEMF because the journal name is missing or invalid. Where must the destination journal name be configured and created for this intercompany posting to succeed?

A
B
C
D
Test Your Knowledge

Corporate headquarters (USMF) posts a $50,000 cash payment from its local operating bank account to pay off a third-party vendor liability that was recorded on the books of subsidiary legal entity DEMF. Which accounting entry will Dynamics 365 Finance automatically post in the originating legal entity USMF?

A
B
C
D