Can Business Central manage multiple companies and currencies?

What does multi-company management mean in Business Central?

A group needs to see both the performance of each legal entity and the position of the whole business. These are related requirements, but they should not be confused. Separate companies preserve the accounting records of each entity. Group reporting brings selected results together using an agreed reporting structure and accounting policy.

Business Central can support this arrangement. The implementation decision is how to structure it so finance can work reliably without creating unnecessary duplication. Begin by listing the entities, ownership relationships, trading currencies, reporting obligations and people responsible for each close. Business Central implementation and support should be scoped against this operating model. Adding companies to software is easier than correcting a poorly defined group structure after transactions have started.

When should we create a separate company rather than a dimension?

A separate legal entity usually requires separate books, while a department, channel or cost centre may be better represented through dimensions within an existing company. The decision should follow accounting and operational requirements. It should not be based simply on how the management dashboard ought to look.

For example, a group with two subsidiaries might use two companies, while each subsidiary uses dimensions for locations or departments. If every branch becomes a company without a clear reason, reporting and intercompany administration can expand considerably. Work with your finance adviser to confirm the boundary. Business Central finance implementation can then align posting rules, dimensions and reporting with that agreed structure rather than trying to repair the distinction through spreadsheets later.

Can every entity share the same chart of accounts?

A common chart of accounts can make group analysis easier, but it is not always practical to force every entity into an identical structure. Acquired businesses, local reporting requirements and different activities may justify differences. The important requirement is a controlled mapping to the group reporting view.

Define the purpose of each group account and identify which local accounts feed it. Avoid broad catch-all mappings that hide useful detail or make a profitable business appear loss-making. Treat new account creation as a governed change: someone must consider the effect on local reports and consolidated results. Keep a mapping register with owners and review dates. It should be possible to explain a group figure without relying on one person's memory.

How does financial consolidation work?

Business Central provides consolidation tools for transferring financial information from business units into a consolidated company. Microsoft documents support for different account structures, fiscal years and currencies, including business units in different environments. The configuration determines how the source information is translated and represented in the group view.

See Microsoft's financial consolidation guidance for the product capability. Your finance team still needs a close timetable, approved mappings, exchange-rate treatment and a method for handling adjustments. First prove the process using one completed historical period. Compare the outcome with the previously approved group accounts and investigate differences before relying on the new report.

Does consolidation automatically eliminate intercompany transactions?

No. Microsoft identifies consolidation eliminations as a manual process. Combining the subsidiary figures does not by itself remove every internal sale, balance or profit that needs adjustment. Finance must identify the relevant transactions and post the appropriate elimination entries using its approved accounting policy.

Create an elimination register explaining the source balances, calculations, journal references and reviewer. Pay particular attention to timing differences and transactions recorded differently by the two parties. An intercompany sale might be invoiced by one entity before the receiving entity records it. The right response is to investigate the underlying event, not to conceal the difference in an unexplained group adjustment. Keep ownership clear throughout the close.

What is the difference between intercompany processing and consolidation?

Intercompany processing supports transactions between entities, while consolidation produces a combined reporting view. A well-designed intercompany process can reduce rekeying, but does not remove the need to match balances, resolve disputes or assess elimination entries. They are separate controls serving different purposes.

Map a typical transaction from the originating purchase or sale through the receiving company's acceptance, posting and settlement. Agree matching references and how rejected transactions return to the sender. Include service charges, stock transfers and centrally purchased costs if those apply. For trading groups, Business Central supply chain and distribution can help connect these accounting decisions to actual goods movements. A physical transfer between warehouses must be distinguished from a sale between different legal owners.

How does Business Central handle foreign-currency transactions?

Business Central lets a company transact in currencies other than its local currency. Currency setup includes the relevant codes, rates and accounts used for exchange differences. A foreign-currency invoice therefore needs both its transaction amount and its accounting representation in the company's local currency.

Microsoft's currency exchange-rate guidance explains the distinction between updating rate data and adjusting posted entries. These are different activities. Finance should agree which source supplies rates, who checks the import and when adjustments run. An apparently successful daily rate update does not prove that month-end revaluation has been completed correctly.

Who should own the exchange-rate policy?

Finance should own the policy, with appropriate accounting advice where needed. The implementation team can configure it, but should not decide the business's accounting treatment by default. Specify the source, effective date, rate precision and permitted exceptions for ordinary transactions, settlement, revaluation and consolidation.

Different purposes may require different treatments. A purchasing forecast rate is not necessarily the correct rate for a posted supplier invoice or a group balance-sheet translation. Label them clearly in reports. Record who may amend a document rate and require a reason where an override is material. A controlled policy makes results explainable when a director asks whether a margin change reflects trading performance, currency movement or an inconsistent conversion assumption.

How do realised and unrealised exchange differences affect reporting?

An unpaid foreign-currency balance can change in local-currency value before cash moves. This creates a different reporting issue from the exchange difference established when a payment settles the balance. Staff need to understand both so they do not treat every exchange movement as a bank reconciliation error.

Use a simple training scenario: post a supplier invoice, revalue the open amount at month-end, then pay it in a later period. Follow the related entries and compare them with the approved accounting policy. Avoid importing rates and adjustments from another system without checking whether Business Central has already performed the same work. Double adjustments can be harder to detect than a missing transaction because individual entries may each look plausible.

Can we manage bank accounts in several currencies?

A multi-currency bank setup must reflect how the business actually receives, holds and pays money. Document each account's entity, currency, access rights and reconciliation owner. Confirm how bank feeds or statement imports identify the account and how fees, transfers and conversions are recorded.

Do not assume the rate implied by a bank transaction will match a published reference rate. Banks may apply spreads and charges, and transfers between currency accounts can involve several accounting components. Test a real example with sensitive information removed. Reconcile in the bank account's currency while also checking the local-currency accounting effect. Where additional applications exchange banking information, include the relationship in system integration services design and make duplicate import prevention an explicit requirement.

How should we report group performance without losing local detail?

Start with the questions directors and entity managers need answered. Group revenue, cash, working capital and profitability may require a common definition, while local teams still need operational measures. Agree how internal trading, currency conversion and shared costs affect each measure before building a dashboard.

Power BI consultancy can help combine and present information once those definitions are stable. Keep entity, period, currency basis and refresh time visible. A useful report should let the reader distinguish local-currency performance from the group reporting view. Avoid adding together amounts carrying different currencies simply because their columns share a name. Reconciliation back to approved company accounts should be part of the reporting design and its ongoing review.

What changes when the group includes overseas companies?

Currency capability is only one part of overseas operation. Each entity may have different requirements for tax, invoicing, banking, statutory reporting, language and data handling. Confirm the available localisation and any partner application needed for the specific country and process. Do not assume a UK configuration can simply be copied everywhere.

Create a country requirements checklist with a local finance owner and obtain suitable professional advice. Separate mandatory local requirements from group preferences. Confirm how local changes will be tested before updates are deployed. A manufacturing subsidiary may also have different operational requirements from the UK head office; Business Central for manufacturing should be evaluated against the actual production process rather than a generic group template.

How should access work across companies?

People should receive access according to their role and responsibilities in each company. A group finance manager may need broad visibility, while a local purchasing user may need access to one entity and a narrower set of functions. Convenience alone is not a reason to give every employee full group access.

Document company access, sensitive permissions and the process for starters, movers and leavers. Review accounts used by integrations separately from ordinary employees. managed IT support can support identity and device controls around these users, while application owners confirm Business Central permissions. Include an explicit check for staff changing roles across entities. An employee leaving one subsidiary should not retain access simply because another group account remains active.

How do we keep shared data consistent without copying mistakes?

Agree which data should be shared, which remains company-specific and who approves changes. Items, customers and suppliers can look similar across entities while having different tax details, bank information, terms or local responsibilities. A shared name does not establish that every field should be identical.

Where automation distributes master data, build in validation and a way to handle exceptions. Power Platform consulting may be suitable for supporting approvals or notifications, depending on the requirement, while more complex synchronisation may need dedicated integration work. Test an amendment and a rejection, not just the first record creation. Keep the receiving company's responsibility visible so centrally distributed data does not become a source of unchallenged errors.

What should a multi-company month-end checklist contain?

Create one timetable covering local closes, intercompany matching, currency adjustments, consolidation, eliminations and management review. Every step needs an owner, a due date, evidence of completion and a rule for reopening it. The order matters because a late subsidiary adjustment can change the group result after reporting appears complete.

Use control totals and documented sign-off rather than a verbal assurance that an entity is finished. Track unresolved items separately and assess whether they affect release of the group report. If supporting systems or reporting workloads use cloud infrastructure, include their availability and maintenance windows in managed cloud services planning. A predictable close depends on operational coordination as well as correct accounting configuration.

What should we test before adding another company?

Test one complete period rather than only creating a company and posting a sales invoice. Include opening balances, local transactions, foreign-currency settlement, intercompany rejection, period-end adjustments, consolidation and eliminations. Confirm that restricted users see only the information intended for them.

A useful acceptance pack includes the expected entity trial balances, intercompany matches and group result. Have finance explain how each reported total was produced. For a retail subsidiary, include returns and settlements from selling platforms; Business Central for retail can help connect those operational events with the group reporting design. Record defects with owners and retest them before the company begins live trading. Do not rely on launch-day corrections for core accounting controls.

How should we approach an acquisition or a phased rollout?

A newly acquired company rarely needs every historical transaction migrated immediately. Decide what is required for current trading, comparative reporting, audit access and legal retention, then choose an appropriate migration or archive approach. Preserve enough detail to support opening balances and outstanding transactions.

For phased rollouts, maintain a consistent group reporting contract while allowing sensible local differences. Reuse the tested template, but review assumptions each time rather than cloning it unquestioningly. Ask the acquired finance team where its current processes differ and which spreadsheets keep the business running. Those conversations often reveal requirements that a purely technical migration plan misses. Keep the first close within the project scope so the team proves the full reporting cycle.

How should we compare local-currency growth with group-currency growth?

A subsidiary can improve its local trading performance while reporting lower revenue in the group's currency because exchange rates moved. Management needs to see both effects clearly. Agree whether reports present actual translated results, a consistent-currency comparison or both, and explain the calculation alongside the figures.

Use a simple worked example agreed with finance before building the report. Hold the commercial volumes and prices constant, change the rate, and confirm that the report isolates the intended currency effect. Keep management analysis distinct from statutory accounting outputs so a useful comparison is not mistaken for the approved reporting treatment.

Document which rate applies to each scenario and preserve prior versions where budgets or forecasts change. Without this discipline, two teams can produce different growth figures from the same transactions and both appear reasonable. The purpose is to make management decisions clearer, particularly when assessing an overseas acquisition, pricing changes or a subsidiary's performance against targets.

What evidence should we retain for a group close?

Keep the source entity reports, reporting periods, mappings, rate tables, consolidation results and adjustment references used for the approved close. Add sign-off showing who prepared and reviewed each material stage. Evidence should be organised so a reviewer can follow a number from the group report back to its source without asking staff to recreate the process months later.

Record changes after initial sign-off, including their reason and the reports affected. If an entity reopens a period, assess whether group reporting needs to be rerun and whether previously distributed information should be replaced. A version label alone is insufficient unless the team knows which version is approved and what changed.

Agree retention, access and responsibilities with the relevant finance and information owners. Limit unnecessary copies containing sensitive data. The objective is a reproducible reporting trail that supports review and continuity when personnel change. This is particularly valuable for smaller finance teams, where one experienced colleague may otherwise become the only source of knowledge about how consolidation actually works.

What should we do before committing to a multi-company project?

Prepare an entity map, currency list, reporting calendar, intercompany transaction examples and a description of current reconciliation problems. Select a small set of genuine scenarios for the demonstration, including a foreign-currency invoice and a disputed intercompany balance. Ask suppliers to identify what is standard, configured, extended or dependent on another application.

Build the business case around practical outcomes such as a more controlled close, fewer duplicated transactions and clearer group reporting. Set a baseline before claiming savings. To explore the fit, contact NetMonkeys with your group structure and the reporting tasks that consume the most time. A disciplined design makes Business Central useful across entities without replacing financial judgement or the controls that protect each company's accounts.