Intercompany trade in Dynamics 365 Finance & Operations

A group with multiple legal entities (one per country, one per business unit, or one per regulatory regime) often has goods, services, or financial flows moving between entities. Intercompany trade in F&O models these flows as paired transactions in two legal entities, with automation that keeps them in sync, and with intercompany elimination support for consolidation.

The basic pattern. Entity A sells to Entity B. F&O can model this as:

• A sales order in Entity A (the seller).
• A purchase order in Entity B (the buyer).
• Both orders linked; updates flow between them.

Without F&O intercompany automation, each entity would have to manually create its side; with automation, creating one creates the other.

Setup.

1. Intercompany customer / vendor relationships — Entity A holds Entity B as a customer (and vice versa, B holds A as a vendor).
2. Intercompany trading partner records define each direction's defaults: cost mark-up, allowed document types, currency.
3. Item mappings — sometimes the same product has different item numbers in different entities; mapping reconciles them.
4. Default sites and warehouses — where intercompany orders ship from and to.

Intercompany sales/purchase order pairing. When a purchase order is created in Entity B with vendor = Entity A's intercompany vendor:

1. The purchase order is created in Entity B.
2. A linked sales order is automatically generated in Entity A.
3. Confirmation, picking, and shipping in Entity A trigger receipt updates in Entity B.
4. Invoice in Entity A creates a purchase invoice in Entity B automatically.

This bidirectional sync is the headline efficiency: cross-entity orders become near-zero rekeying.

Intercompany pricing. Transfer pricing rules (the regulatory-driven question of "at what price do related entities transact") are configured per partner pair:

• Cost plus — markup on cost.
• Resale minus — discount on customer-facing price.
• Fixed price — negotiated price.

For tax compliance, transfer pricing must be defensible against regulatory standards (OECD guidelines, BEPS). F&O captures the price; the policy and documentation are the tax team's responsibility.

Direct delivery. A pattern where the goods physically ship from Entity A directly to Entity B's customer, but financially flow through Entity B. F&O handles this as:

1. End customer order in Entity B (sales order).
2. Intercompany sales order in Entity B pulls from Entity A.
3. Entity A's direct delivery ships goods straight to the end customer; the paperwork shows the chain.

Direct delivery saves shipping cost and time while keeping the legal entity flows correct.

Intercompany inventory transfers. For goods moved between entities without a sale (rebalancing stock):

• A transfer order between sites within one entity is the simplest case.
• A cross-entity transfer is modeled as a sales order in the source and a purchase order in the destination, at zero margin or cost-only.

Intercompany services. Entity A provides shared services (IT, finance) to Entity B. Modeled as service items (non-stocked) on intercompany sales/purchase orders, billed periodically. Pricing follows the transfer pricing policy.

Intercompany journals. For financial-only movements (recharges, allocations, loans), the intercompany journal posts to both entities simultaneously — a single posting creates G/L entries in two ledgers with matching offsets.

Intercompany AR/AP reconciliation. Periodic reconciliation ensures that Entity A's AR balance with Entity B equals Entity B's AP balance with Entity A:

• Trial balance per intercompany pair, by currency.
• Reconciliation differences identified and resolved.
• Reconciliation report fed to consolidation as starting evidence.

Without reconciliation, consolidation elimination journals miss amounts and consolidated financials carry residual intercompany balances.

Intercompany chains. A multi-step chain (Entity A → Entity B → Entity C) is supported but adds complexity. Each link is a paired transaction; the chain is constructed by linking orders explicitly.

Tax and customs. Cross-border intercompany trade triggers:

• VAT/customs at the border.
• Withholding taxes on services and royalties.
• Transfer pricing documentation for tax authorities.

F&O's tax engine handles VAT/customs; transfer pricing documentation is typically managed in dedicated tax tools.

Consolidation flow. Intercompany transactions flow into consolidated reporting:

• Each entity's GL is consolidated normally.
• Elimination journals in the consolidation company reverse intercompany sales/COGS and intercompany AR/AP.
• Reconciled intercompany balances net to zero in eliminations; un-reconciled balances flag the gap.

Common pitfalls.

• Inconsistent item codes. Same product, different numbers; mapping missing; intercompany orders fail.
• Trade agreement gaps. Intercompany prices not set; defaults to zero or to external customer pricing; transfer pricing wrong.
• Reconciliation skipped. Differences accumulate; year-end consolidation has gaps.
• No process for intercompany returns. Returns paths exist but rarely tested; first real return causes confusion.
• Document type proliferation. Some teams create custom intercompany documents to add fields; complicates upgrades.

Operational rhythm. Daily order syncing is automatic. Monthly intercompany reconciliation is a finance team task — one per pair, formalised and signed off. Quarterly transfer pricing review is a tax/finance joint task. Year-end consolidation pulls all of this together.