How an Abu Dhabi-Based Diversified Holding Company Simplified Intercompany Transactions in Dynamics 365 Business Central

Introduction

Organizations operating through multiple legal entities often share resources, incur costs centrally, and recharge expenses to the company that actually benefits from them. Although these entities belong to the same business group, each company maintains its own accounting records, receivables, payables, and financial reporting.

Emirates Consortium LLC is an Abu Dhabi-based diversified holding company with businesses across the UAE and Maldives. As highlighted in the Emirates Consortium customer success story, CloudFronts deployed Dynamics 365 Business Central across five legal entities to support core business processes. For organizations operating across several companies, intercompany recharges and cost allocation are important areas to assess when looking to reduce duplicate finance work.

To explore these capabilities, consider two related companies, Gulf Aquaculture (GA) and Gulf Aquaculture Alliance (GAA). The walkthrough covers two practical routes: an intercompany sales invoice for a formal recharge and an intercompany general journal for direct cost allocation. It explains the setup, accounting impact, and important control points involved in both processes.

The Business Problem

The finance team managed transactions for separate group companies, but some costs, such as consultancy, administration, payroll-related expenditure, and project-related operating expenses, were initially incurred or recorded in GA even when they partly or entirely related to GAA.

For example, GA might receive an external vendor invoice for AED 10,000, of which AED 4,000 is attributable to GAA. Without a standard cross-company workflow, staff must determine the chargeable amount, prepare a corresponding transaction in the second company, and verify that the two sets of books agree.

Handling this manually created five gaps:

The Solution

The proposed approach used standard Business Central intercompany functionality rather than a separate custom integration. Both companies were configured as intercompany partners, with mapped accounts and dimensions to support the exchange of transactions.

1. Establishing the Intercompany Relationship

Each participating Business Central company needs its own Intercompany Setup and a unique IC Partner Code. The other company is then added as an intercompany partner with an appropriate transfer method. For a partnership inside the same Business Central environment, direct company-to-company transfer can be used where supported by the configured environment.

2. Connecting Customers and Vendors

In GA, GAA is represented by an intercompany customer for billing. In GAA, GA is represented by an intercompany vendor for recording the payable. Assigning the relevant IC Partner Code on the customer and vendor records connects the commercial documents to the receiving company.

3. Mapping the Intercompany Chart of Accounts

Business Central uses a shared intercompany chart of accounts as the language between companies. Each company maps its own G/L accounts to the intercompany accounts and maps incoming intercompany accounts back to its local G/L accounts. When account numbering differs between companies, these mappings are essential.

During the walkthrough, the team reviewed how a sales invoice line could carry an IC Partner Reference so that the receiving company would recognize the appropriate expense account. Account mapping in both directions was especially important: an account existing in one company does not guarantee that the other company can post it.

4. Preserving Dimensions and Project Context

Intercompany dimensions can transmit reporting context such as Department, Project, or Cost Centre when corresponding dimension codes and values are set up and mapped. The accounting team should confirm that the receiving company’s dimension values accurately represent the destination project or department.

5. Choosing the Appropriate Transaction Route

The following walkthrough focuses on the first two routes: intercompany invoices and intercompany journals, rather than sales and purchase order processing.

6. Controlling Transactions Through the Inbox and Outbox

When an intercompany invoice or journal is posted, Business Central prepares the corresponding transaction for exchange. With manual sending enabled, the source user reviews it in the Intercompany Outbox and sends it to the partner. The recipient reviews it in the Intercompany Inbox, accepts it, and then posts the created purchase invoice or journal.

Implementation and Process Walkthrough

The following examples use GA as the company initiating a recharge and GAA as the company receiving it. Account names and figures are simplified to show the accounting principle without exposing the customer’s detailed chart of accounts.

1. The Intercompany Setup Checklist

2. Scenario A: GA Charges GAA Through a Sales Invoice

Assume GA needs to recharge AED 4,000 of services to GAA. In GA, the user creates a new Sales Invoice and chooses the customer linked to GAA’s intercompany partner code. The invoice includes a G/L Account line for the recharge and, where necessary, the IC Partner Ref. Type and IC Partner Reference identifying the expense account expected in GAA.

1. In GA, open Sales Invoices and create an invoice for the intercompany customer representing GAA.
2. Add a G/L Account line, enter the recharge description and AED 4,000, and verify the partner reference, dimensions, and applicable tax treatment.
3. Complete internal approval if the organization’s approval workflow requires it, and post the sales invoice in GA.
4. Open Intercompany Outbox Transactions, review the posted entry, use Send to IC Partner, and complete the line action if manual processing is enabled.
5. Switch to GAA, open Intercompany Inbox Transactions, review the entry, and accept it to create a Purchase Invoice.
6. Open the newly created purchase invoice in GAA, verify the mapped expense account, amount, dimensions, and VAT treatment, and post it.
7. Reconcile GA’s customer receivable with GAA’s vendor payable and check the transaction status in the handled Inbox/Outbox.

Intercompany invoice workflow

These are simplified pre-tax accounting illustrations. Actual G/L entries depend on the accounts used, posting groups, invoice type, currency, and tax setup. A formal invoice does not automatically reverse the original vendor expense in GA; the organization must determine whether the credit is appropriately classified as income or an approved cost offset.

3. Scenario B: Allocate Part of a Cost Through an Intercompany Journal

Consider an external consultancy invoice of AED 10,000 recorded in GA, with AED 4,000 relating to GAA. If the business needs a direct redistribution of expense rather than a separate commercial sales invoice, an Intercompany General Journal can transfer the allocated cost.

1. Confirm the original vendor invoice is already recorded in GA and identify the expense portion attributable to GAA.
2. Open Intercompany General Journals in GA and choose the correct template and batch.
3. Create a journal line with Account Type set to IC Partner, choose GAA, enter the AED 4,000 allocation, and specify the balancing expense or recharge clearing account and the IC Partner G/L Acc. No.
4. Review the posting date, document reference, dimensions, posting groups, and whether the sign used produces the intended debit and credit.
5. Post the journal in GA. Send the resulting entry from the Intercompany Outbox if it was not automatically sent.
6. In GAA, accept the incoming intercompany journal transaction into the designated journal batch, review the proposed entries, and post them.
7. Check that the allocated expense appears in GAA and that the due-from / due-to intercompany balances agree.

4. Validation and Reconciliation

Both invoice and journal processing require validation, including reviewing how manual versus automatic sending affects the process. Finance teams should perform a cross-company check after posting, rather than merely confirming that a transaction reached the Inbox.

Limitations and Key Considerations

Intercompany removes duplicate entry, but it does not remove the need for accounting judgment, partner setup, and review controls.

Business Impact

For the multi-entity charging scenario, the standard Business Central workflow provides a clearer hand-off from the company initiating a recharge to the company that owns the final expense. The approach can offer the following operational benefits:

The extent of these benefits depends on the organization’s transaction volumes, account mappings, and review processes.

Frequently Asked Questions

Conclusion

Intercompany functionality in Microsoft Dynamics 365 Business Central offers a practical way for related legal entities to transact while preserving separate books. In the GA-to-GAA scenario, a source-company recharge could be processed through an intercompany sales invoice and received as a purchase invoice, while an intercompany general journal offered a lighter route for allocating individual costs.

The most important implementation lessons were not about turning on a single feature. They were about connecting each company correctly, mapping G/L accounts and dimensions, choosing the right transaction method, and preserving a controlled Inbox/Outbox review process. With those fundamentals in place, finance teams can reduce duplicate work and make cross-company costs easier to classify, review, and reconcile.