How to Set Up Intercompany Transactions in Business Central in the UK

Introduction

Group structures with two or more legal entities usually mean the same commercial event gets keyed twice: once as a sale in one company, again as a purchase in another. Microsoft Dynamics 365 Business Central's intercompany feature lets separate entities in the same group exchange sales, purchases, services, goods, and journal entries without duplicating that work.

But flipping the switch on isn't enough. Each company needs matching partner references, compatible master data, correct account and dimension mappings, and a controlled sending and receiving process. Skip any of these, and transactions either stall in an outbox or post incorrectly on the other side.

This guide walks through the setup sequence, UK-specific VAT and compliance checks, day-to-day transaction workflows, the configuration choices that matter most, and the mistakes worth testing for before you go live.

Key Takeaways

• IC codes, partner records, and matching customer/vendor setup must exist in every company before transactions flow.
• IC chart of accounts, dimension mappings, item references, and transfer method control whether transactions land correctly on the receiving side.
• Auto-send and auto-accept speed processing but can create duplicates if orders, invoices, and journals are not tested separately.
• UK groups need to validate VAT treatment, currency handling, and transfer-pricing evidence alongside the technical setup.

How to Set Up and Use Intercompany Transactions in Business Central

Step 1: Prepare the participating companies and assign IC codes

Confirm every legal entity already exists in Business Central, then decide which ones will send, receive, or do both. In each company's Intercompany Setup area, assign a unique Intercompany Partner Code. Use a naming convention that makes the entity obvious at a glance rather than a generic abbreviation.

You'll also need to:

• Choose the IC Inbox Type (Database, Email, File Location, or No IC Transfer) based on how your companies are deployed
• Decide whether Auto. Send Transactions should be switched on for invoices and journals
• Document who reviews and releases transactions before they leave the sending company

Step 2: Create and link the intercompany partners

In each relevant company, open Intercompany Setup, use Add IC Partner, and link the partner to the correct company name or external environment. This is the step most setups get wrong.

The IC code entered in Company A must match, character for character, the code configured in Company B. Open both company setups side by side (two browser tabs work well) and compare them directly rather than trusting memory.

For trading relationships, complete the Sales Transaction and Purchase Transaction tabs with the correct customer and vendor records, plus receivables and payables posting accounts.

Then decide on Auto. Accept Transactions: manual acceptance gives the receiving company a review checkpoint; automatic acceptance is faster but removes that checkpoint entirely.

Step 3: Configure master-data and accounting mappings

Build (or confirm) a common IC chart of accounts, mapping the sending company's accounts to the receiving company's equivalents — particularly where revenue, expense, receivable, and payable accounts use different numbering schemes between entities.

Also set up:

• Dimension mappings so department, cost centre, project, or location values stay consistent in management reports after a transaction crosses companies
• An outbound item-number method (own item number, Common Item No., or Item Reference), with matching item cards in both companies
• Intercompany bank accounts, if payments will move between entities, with mapping that supports the intended payment workflow

Step 4: Choose the transfer method and test document flows

Compare Database, Email, and File Location. File Location only works on-premises — Business Central Online can't reach a local network, so a file selected online simply downloads to the user's Downloads folder instead of transferring.

If your entities sit in separate environments, register an app, exchange connection details, and confirm user permissions before anything moves.

Then test, one document type at a time:

1. A sales invoice from the sending company
2. A purchase invoice
3. A sales or purchase order
4. An intercompany general journal

In the receiving company, review the Intercompany Inbox, check lines and dimensions, accept or reject, post, and confirm the resulting ledger entries and document references match the sending side.

Step 5: Establish the operating process for live transactions

Define who creates, sends, accepts, edits, posts, and reconciles each transaction, and how the sending and receiving finance teams hand off work between them. Posted invoices may send automatically depending on configuration, whereas orders often need an explicit Send to IC Partner action.

Use the Intercompany Outbox and Handled Intercompany Outbox to monitor pending, sent, cancelled, or completed items. Investigate anything that has not reached the receiving company within your expected timeframe.

Reconcile intercompany receivables, payables, currencies, tax treatment, and document numbers at month end, not only when something looks wrong.

When Should You Use Intercompany Features and What Do You Need Beforehand?

Intercompany transactions earn their keep when separate legal entities regularly exchange goods, services, stock, management charges, shared-service costs, payments, or recurring journals, and manual double-entry is creating control gaps or wasted hours.

If your group only has the occasional one-off adjustment, the manual approach may still be simpler.

Plan for extra design work where:

• Master data between entities is genuinely incompatible (different item structures, incompatible posting groups)
• Transactions involve complex tax treatment across jurisdictions
• The group actually needs consolidation and elimination reporting, not just document automation

Before configuration, gather:

• Legal-entity structure and company names
• Proposed IC codes and customer/vendor numbers
• Charts of accounts, dimensions, and item references
• Currencies, bank accounts, and approval rules
• Transfer-pricing policy
• Current UK VAT guidance for the transaction types involved

UK businesses with entities or investment flows linked to India face an added layer: Indian FEMA and FDI rules, GST, and ROC compliance sit alongside the UK side of the transaction. VJM Global works with UK groups on exactly this combination: cross-border accounting, tax compliance, and reporting support that runs in parallel with the Business Central process design rather than replacing it.

Key Parameters That Affect Intercompany Results

Intercompany codes and partner matching

Every sending-company partner code must correspond exactly to the receiving company's configured IC code. If Company A's outbound code reads "UKCO01" but Company B has configured "UKC001," the transaction either fails validation or, worse, tries to route to an unintended entity.

Before go-live, pull up both partner records and confirm:

• The code strings match exactly (no trailing spaces, no case mismatches)
• The company link points to the correct target company
• No duplicate codes exist across your partner list

A duplicated or mismatched code typically throws a warning at send time rather than silently posting, but only if someone is watching the outbox.

Transfer method, automation, and approval controls

Database, Email, and File Location differ in reliability and where they can run:

• Database transfers move data directly between companies in the same database
• Email sends the intercompany document as an attachment
• File Location depends on network access that Business Central Online does not support

Check current Microsoft documentation for your specific deployment before locking in a choice.

Auto. Send Transactions and Auto. Accept Transactions trade control for speed. Microsoft's own documentation notes that enabling automatic acceptance suppresses the warning that a purchase invoice duplicates an existing purchase order.

That matters most for order-based workflows. An order and its later invoice can otherwise create two separate intercompany transactions for one commercial event.

Account, dimension, currency, and tax mapping

The IC chart of accounts translates entries between companies with different ledgers. A management recharge from a UK holding company to an operating subsidiary, for example, needs the recharge expense account in the sending company mapped to the matching intercompany income or expense account in the receiving company.

Confirm the actual account numbers with your finance team rather than assuming a standard mapping applies.

Currency and tax add further layers:

• Agree exchange-rate source, posting-date convention, and rounding treatment upfront when entities trade in different currencies
• Establish whether the companies are in the same UK VAT group — HMRC's VAT Notice 700/2 confirms that supplies between group members are normally disregarded for VAT, but this only applies if the group registration is actually in place
• Where entities sit outside a VAT group, treat recharges under normal VAT rules and check invoice content against HMRC's record-keeping requirements
• Retain transfer-pricing support for the transaction; this is a finance and tax adviser decision, not a Business Central configuration setting

Master data and item references

Choose between your own item number, Common Item No., or Item Reference based on how consistently your companies name and code items. Inconsistent units of measure, variants, or blocked items are a common reason an inbound document fails to post cleanly.

Before go-live, reconcile:

• Customer and vendor cards in every connected company
• Item cards, posting groups, and dimension values
• Bank account mappings, where intercompany payments are involved

Common Mistakes and Troubleshooting Intercompany Transactions

Mismatched IC codes or incomplete customer/vendor setup

Likely cause: the partner code, company link, customer, or vendor record is missing or differs between entities. Compare both Intercompany Partner records directly and confirm the Sales and Purchase Transaction tabs are complete on each side.

What to check:

• IC Inbox and Outbox status
• Validation messages on the document
• Partner code and transaction direction
• Whether the receiving company holds the matching master record

Incorrect account, dimension, item, or bank-account mappings

Likely cause: the receiving company lacks a mapped account, dimension value, item reference, or bank account for the incoming transaction.

Fix: correct the specific IC mapping, run a controlled test document, and confirm the resulting lines and ledger postings before reopening live processing.

Duplicate orders or invoices from automation settings

Enabling automatic sending on an order workflow can generate an order transaction and then a separate transaction when that order is later invoiced. That effectively duplicates one commercial event.

Test order and invoice flows separately. Document when transactions are sent, accepted, amended, and posted, and keep approval controls in place for anything material or unusual.

Transactions stuck in the Inbox, Outbox, or handled queues

Check these points first:

• Transfer type and user permissions
• Environment connectivity
• Whether the item was cancelled or returned rather than accepted
• Whether a manual send or accept action is still outstanding

Some transactions only need that manual send or accept step.

Preserve the audit trail: record the error, the correction, the resubmission, and the final posting. Don't delete evidence of a failed transaction. Auditors and tax advisers will want to see it later.

UK control and reconciliation issues

Before period close, investigate differences in:

• VAT codes and posting dates
• Exchange rates and document references
• Outstanding intercompany balances

Reconcile both sides of every transaction. Escalate tax, statutory reporting, or audit questions to your UK finance or tax adviser rather than resolving them only inside Business Central.

Conclusion

Intercompany transactions in Business Central work best when every participating company has:

• Aligned partner records
• Compatible master data
• Correct account and dimension mappings
• A clearly owned review process

Get the technical setup right, and the rest (sending, accepting, posting, reconciling) becomes routine rather than a monthly scramble.

The real implementation work sits in validating how a transaction moves from sender to Inbox, through acceptance and posting, into a reconciled intercompany balance. For UK groups, that means pairing technical testing with VAT, currency, transfer-pricing, approval, and audit checks before switching on broad automation.

Where the group includes India-linked entities, that combination gets more complex. VJM Global supports UK businesses with intercompany agreement drafting, cost-sharing agreements, and transfer-pricing policy work that complements the Business Central configuration itself.

Frequently Asked Questions

How do you account for intercompany transactions?

Record the transaction in both legal entities using linked customer/vendor records or intercompany journal entries, supported by mapped accounts, dimensions, and tax treatment. Reconcile the reciprocal balances between entities each period.

What's the main difference between intercompany and intracompany transactions?

Intercompany transactions happen between separate legal entities within a group. Intracompany transactions move between departments, branches, or locations inside one legal entity. The accounting and reporting treatment differs because only intercompany dealings involve separate sets of statutory accounts.

What are the three main types of intercompany transactions?

The three main types are sales and purchases of goods or services, shared-service or management recharges, and intercompany financing or journal entries. The exact categories your group uses will depend on its operating model.

Which transfer method should a UK business use for Business Central intercompany transactions?

It depends on your deployment: Database suits companies in the same database, Email works well for straightforward cross-environment sending, and File Location is on-premises only. Check current Microsoft guidance against your specific setup before deciding.

Should Auto. Send Transactions and Auto. Accept Transactions be enabled?

Both speed up processing, but automatic acceptance removes a review checkpoint and can suppress duplicate-document warnings. Test each setting separately for invoices, orders, and journals before enabling either broadly.

What UK tax and compliance checks are needed for intercompany transactions?

Confirm VAT treatment (including whether a VAT group applies), invoice content, currency handling, and transfer-pricing documentation requirements where relevant. Keep a clear audit trail and involve a qualified adviser for transaction-specific guidance.