Study guide
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings
Microsoft Certified: Dynamics 365 Finance Functional Consultant Associate MB-310
Track your progress as you read
Finished sections get a check mark.
1 Chapter 1: MB-310 Exam Overview & Financial Architecture
1.1 MB-310 Exam Structure, Skills Measured & Consultant Role 1.2 Dynamics 365 Finance Architecture, Legal Entities & Global Address Book 1.3 Hands-on Lab Strategy & Preparation Framework
2 Chapter 2: Chart of Accounts & Main Accounts
2.1 Designing Chart of Accounts & Main Account Types 2.2 Main Account Categories & Ledger Account Aliases 2.3 Balance Control Accounts & Year-End Opening Account Setup 2.4 Legal Entity Overrides for Main Accounts & Dimensions
3 Chapter 3: Financial Dimensions & Account Structures
3.1 Custom & Entity-Backed Financial Dimensions 3.2 Financial Tags: Limits, Storage & Ledger Settlement Use 3.3 Account Structures, Segment Criteria & Activation 3.4 Advanced Rules & Advanced Rule Structures 3.5 Derived Dimensions & Dimension Default Templates
4 Chapter 4: Ledgers, Calendars & Currencies
4.1 Fiscal Calendars, Period Statuses & Module Access Control 4.2 Posting Layers, Multi-GAAP Reporting & the Ledger Form 4.3 Currency Exchange Types, Rate Providers & Triangulation 4.4 Accounting & Reporting Currencies (Dual-Currency Architecture) 4.5 Foreign Currency Revaluation & Revaluation Posting Profiles
5 Chapter 5: General Ledger Journals & Allocations
5.1 Journal Names & Voucher Number Sequences 5.2 Journal Control & Posting Restriction Rules 5.3 Journal Entry, the One-Voucher Rule, Validation & Posting 5.4 Reversals, Storno Corrections & Excel Integration 5.5 Ledger Allocation Rules & the Four Allocation Methods 5.6 Allocation Processing & Periodic (Recurring) Journals
6 Chapter 6: Intercompany Accounting & Settlements
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings 6.2 Intercompany Journal Processing & Multi-Company Vouchers 6.3 Ledger Settlements Configuration & Processing
7 Chapter 7: Cash and Bank Management
7.1 Bank Groups, Bank Accounts & Ledger Integration 7.2 Payment Formats, Bank FX Revaluation & Shared Payment Setup 7.3 Manual vs. Advanced Bank Reconciliation & Statement Formats 7.4 Matching Rule Sets, Reconciliation Execution & Reversals 7.5 Cash Flow Forecasting Setup & Automation 7.6 Customer and Vendor Netting
8 Chapter 8: Periodic Closing & Financial Consolidations
8.1 Financial Period Close Workspace, Closing Roles & Schedules 8.2 Year-End Close Configuration & General Ledger Balance Carryforward 8.3 Consolidations Online: Legal Entity Setup, COA Mapping & Currency Translation 8.4 Import Consolidations & Intercompany Elimination Rules
9 Chapter 9: Sales Tax & Withholding Tax
9.1 Sales Tax Engine Hierarchy, Authorities & Settlement Periods 9.2 Ledger Posting Groups, Sales Tax Codes & Calculation Methods 9.3 Sales Tax Groups, Item Sales Tax Groups & Tax Exemptions 9.4 Sales Tax Adjustments and Settle and Post Sales Tax 9.5 Withholding Tax & US 1099 Vendor Reporting
10 Chapter 10: Accounts Receivable Setup & Invoicing
10.1 Customer Master, Customer Groups & Shared Customers 10.2 Customer Posting Profiles & Account Code Precedence 10.3 Free Text Invoices, Recurring Invoice Templates & AR Charges 10.4 Sales Order Invoicing, Billing Classifications & Prepayments 10.5 Customer Payment Methods, Payment Processing & Customer Bank Accounts
11 Chapter 11: Credit Management & Collections
11.1 Credit Management Architecture & Customer Credit Groups 11.2 Risk Scoring, Credit Limits, Blocking Rules & Credit Holds 11.3 Aging Definitions, Collections Workspace & Customer Pools 11.4 Collection Letter Sequences & Interest Notes 11.5 Customer Write-Offs, Bad Debt & Write-Off Reversals
12 Chapter 12: Subscription Billing & Revenue Deferrals
12.1 Recurring Contract Billing, Billing Schedules & Milestones 12.2 Deferral Principles, Deferral Defaults & Schedule Calculation Methods 12.3 Recognition Processing, Expense Deferrals & Modifying Schedules 12.4 Multiple Element Revenue Allocation (MEA / ASC 606)
13 Chapter 13: Accounts Payable & Invoice Processing
13.1 Shared Vendors, Global Address Book & Vendor Groups 13.2 Vendor Posting Profiles, AP Parameters & Vendor Bank Accounts 13.3 Invoice Matching Setup (2-Way, 3-Way), Tolerances & Exceptions 13.4 Vendor Invoicing Methods, Journals & Invoice Automation
14 Chapter 14: Vendor Payments & Expense Management
14.1 Methods of Payment & the Vendor Payment Proposal Engine 14.2 Generating Payments, Centralized Payments & Check Lifecycle 14.3 Expense Management Configuration, Categories & Policies 14.4 Expense Reports Processing, Mobile Receipts & Intercompany Expenses
15 Chapter 15: Budgeting & Budget Control
15.1 Budget Models, Budget Codes & Allocation Terms 15.2 Budget Register Entries, Workflows & Budget vs. Actual 15.3 Budget Transfer Rules & Processing Budget Transfers 15.4 Budget Control Configuration, Cycles, Rules & Budget Groups 15.5 Budget Funds Available, Over-Budget Permissions & Document Budget Check 15.6 Budget Planning Framework, Organization Hierarchies & Planning Processes 15.7 Budget Plans, Scenarios, Allocations & Generating Register Entries
16 Chapter 16: Fixed Assets Configuration & Transactions
16.1 Fixed Asset Groups, Asset Records & Group/Book Mapping 16.2 Depreciation Profiles: Methods & Conventions 16.3 Fixed Asset Books, Derived Books & Posting Profiles 16.4 Fixed Asset Acquisition Pathways 16.5 Depreciation Proposals, Multi-Company Runs & Fixed Asset Budgets 16.6 Fixed Asset Disposals: Sale, Scrap & Disposal Accounting 16.7 Fixed Asset Splits, Transfers & Reclassification 16.8 Asset Leasing (IFRS 16 / ASC 842)
6.1 Intercompany Accounting Setup & Due-To / Due-From Postings
Key Takeaways Explain This Topic AI
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 Field Description & Functional Purpose Account Type & Classification
- Originating Legal Entity The initiating company context (e.g., USMF ). System Legal Entity Identifier
- Destination Legal Entity The 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:
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.
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.
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 Entity Voucher ID Main Account Account Name Account Type Debit Credit Posting Layer
- USMF (Originating) USMF-GJ-10024 110110 Operating Bank USD Asset — $10,000 Current
- USMF (Originating) USMF-GJ-10024 130500 Due From DEMF (IC Receivable) Asset $10,000 — Current
- DEMF (Destination) DEMF-GJ-00819 618200 IT Infrastructure Expense Expense €9,100 — Current
- DEMF (Destination) DEMF-GJ-00819 210500 Due To USMF (IC Payable) Liability — €9,100 Current
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
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.
Journal Type: Must be configured with Journal type Daily (General journal).
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.
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
Navigate to General ledger > Chart of accounts > Accounts > Main accounts .
Create Account 130500 (Name: Intercompany Receivable - DEMF , Type: Asset ).
Create Account 210500 (Name: Intercompany Payable - USMF , Type: Liability ).
Set Do not allow manual entry to Yes on both accounts to prevent unlinked manual journal tampering.
Step 2: Configure Destination Journal Name
Switch legal entity context to DEMF .
Navigate to General ledger > Journal setup > Journal names .
Create a new Journal name IC_Gen with Journal type Daily and assign an active voucher number sequence.
Step 3: Configure Pairwise Intercompany Relationship
Switch legal entity context back to USMF .
Navigate to General ledger > Posting setup > Intercompany accounting .
Click New :
- Originating legal entity: USMF
- Destination legal entity: DEMF
On the Originating legal entity tab:
- Debit account (Receivable): 130500
- Credit account (Payable): 210500
On the Destination legal entity tab:
- Debit account (Receivable): 130500
- Credit account (Payable): 210500
- Journal name: IC_Gen
Click Save .
Repeat steps with DEMF as Originating and USMF as Destination to establish full bi-directional symmetry.