Multi entity accounting software: what it is & when needed

Non-controlling interest

When a parent controls a subsidiary but owns less than 100% of it, the outside owners' share is reported as non-controlling interest (NCI). Consolidation still includes 100% of the subsidiary's assets, liabilities, income, and expenses, then attributes part of equity and net income to NCI.

For example, a parent owns 80% of a subsidiary that earns $100,000. Consolidated net income includes the full $100,000, with $80,000 attributable to the parent and $20,000 attributable to NCI.

Key components of entity management

Multi-entity accounting requires three structural elements:

1. Isolated ledgers per entity: Each legal entity maintains its own general ledger, its own chart of accounts, and its own transaction history. Nothing posts across entity boundaries without documentation.
2. Documented intercompany transactions: Every transfer, loan, management fee, or cost allocation between entities must be recorded in both ledgers at the point of execution, not reconstructed at month-end.
3. Approval rules per entity: Payment thresholds, role-based permissions, and audit trails apply within each entity.

A centralized chart of accounts helps keep intercompany balances traceable by matching every "due-to" in Entity A to a corresponding "due-from" in Entity B.

Multi-entity vs. single-entity workflows

Single-entity accounting assumes one ledger, one set of books, and one audit trail. Multi-entity accounting assumes none of those things.

Multi-entity closes need staged reviews: entity close first, then intercompany reconciliation, then consolidation. A checklist that does not account for entity sequencing will create rework at the consolidation stage every month.

Structural patterns for global finance

Global finance teams manage multiple legal entities across tax jurisdictions, currencies, and regulatory regimes. The process is further complicated when only some of the entities are wholly owned, or when the entities use different general ledger systems, record in multiple currencies, and face different tax rules such as VAT. These structural differences compound reconciliation complexity.

Foreign-currency translation

Each entity records transactions in its functional currency, which is the currency it mainly earns and spends in day to day operations. When a subsidiary's functional currency differs from the group's presentation currency, the group translates that subsidiary's statements before consolidating them, following IAS 21 or ASC 830. Assets and liabilities are translated at the closing rate, and income and expenses at the transaction-date rate or a period average. The resulting translation differences go to other comprehensive income, not profit or loss.

A foreign-currency transaction inside one entity, such as a EUR invoice in a USD ledger, is remeasured instead, and the gain or loss goes to profit or loss. Hyperinflationary economies follow separate rules. Translation also feeds intercompany mismatches: if two entities record the same transaction at different rates, the balances won't eliminate cleanly until the rate difference is resolved.

Transfer pricing across tax borders

Transfer pricing is the price one entity charges a related entity for goods, services, loans, or intellectual property, and it is a common area of tax scrutiny. For US federal income tax, related-party prices must meet the arm's length standard under 26 CFR 1.482-1. Other countries apply their own transfer pricing rules, so confirm them with a local tax adviser.

The arm's length standard asks whether unrelated parties would have agreed the same price in comparable circumstances. For charges such as management fees, finance teams typically record the pricing basis, for example a cost-plus markup or a comparable market rate, alongside the invoice, so the same figure appears in both ledgers and supports the tax position.

Approval workflows across entities

Internal controls should include structured approval workflows and audit trails that track transactions across entities. Set approval policies for each entity and department: who can propose a payment, who can approve it, and the amount above which a second approver is required. Keep the preparer and approver of a payment separate, and record the approver and the date against every payment so the trail survives an audit.

Tax filing rules for multi-entity groups

For US federal income tax, each entity has its own tax obligations, but not always a separate return. A single-member LLC is usually disregarded for US federal income tax, and a US affiliated group with 80% of the vote and value can file one consolidated federal return under IRC 1504 using Form 851. Where an entity is taxed as its own taxpayer, missing documentation, inconsistent pricing, or reconciliation gaps expose the structure to penalties and audit risk. Other countries set their own entity tax and group filing rules, so confirm them with a local tax adviser.

Isolating ledgers for each entity

This workflow depends on keeping each entity's ledger isolated while giving operators a single login. The practical test is whether one set of credentials opens a separate workspace per entity, each with its own accounts, approval rules, and records, so the team can move between entities without merging the books.

Post eliminations in the consolidation layer or group journal process so the entity ledgers stay unchanged and only the group figures carry the adjustment. That separation lets an auditor review each entity's books on their own.

Tracking intercompany payments

Intercompany transactions are where multi-entity accounting breaks. Elimination entries, transfer pricing, and settlement timing must be documented at the point of execution, not reconstructed at month-end.

Consolidated statements zero out internal fund transfers, sales, loans, management fees, inventory movements, and other related-party dealings among group companies to reflect only external transactions and prevent double counting that would overstate revenue, assets, and liabilities.

Closing books for multiple legal entities

Locking the accounting period only after every key reconciliation is completed and signed off stops reconciling items from rolling forward unresolved. An item left open in one month tends to cause errors in the next. Checkflow's month-end close checklist describes this control.

Managing multi-entity elimination flows

Elimination entries strip the effect of dealings inside the group out of consolidated results, so only transactions with outside parties remain. Classify each internal item first: a receivable or payable balance, a sale between group companies, a charge, a loan, a dividend, or profit not yet realized on inventory still held within the group. Then decide whether the full amount can be eliminated in the current period.

Worked example: A US parent bills its UK subsidiary $10,000 for shared services, and the subsidiary hasn't paid by period end. Each entity records its own side, and the elimination is posted only in the consolidation layer.

After the elimination, consolidated revenue, expenses, receivables, and payables carry none of the internal charge. If the UK subsidiary had paid the invoice before period end, each ledger would settle the receivable and payable, and only the revenue and expense lines would still need eliminating.

The case finance teams struggle with is a currency difference. Suppose the UK subsidiary books the $10,000 charge in GBP at the rate on the day it approves the invoice, while the US parent booked the receivable at the rate on the invoice date. If the two rates differ, the subsidiary's payable, once translated into USD, no longer equals the parent's $10,000 receivable.

The elimination leaves a residual balance until the team traces the gap to the rate difference and records it. Under IAS 21 or ASC 830, that difference is a foreign-currency effect. A payable the subsidiary owes in USD but records in GBP is remeasured, with the gain or loss in profit or loss, and the subsidiary's translated statements add a translation difference in other comprehensive income. See "Foreign-currency translation" above for how each is treated.

Intercompany settlement workflow

Before producing consolidated financials, reconcile each intercompany balance and eliminate it. Compare what entity B owes entity A with what entity A shows as receivable from entity B. Trace any gap to a timing difference, an FX rate difference, or a missing entry, and clear it before the period locks.

Cutoff differences between periods cause many intercompany mismatches. Entity A invoices Entity B for a management fee on March 30 and books the revenue in Q1. Entity B approves the invoice on April 3 and books the expense in Q2. Each entry follows its own entity's cutoff, yet at the Q1 elimination, A's receivable has no matching payable on B's ledger. Account mismatches occur when entities use different general ledger accounts for the same transaction.

Reconciliation finds the gaps, and settlement clears the balance. An intercompany settlement is the payment that clears a receivable in one entity and the matching payable in another. Each entity records the cash movement in its own ledger, ideally on the same date and at the same amount, so both balances go to zero. Bank fees and FX differences on the payment can leave a residual, so finance teams document both sides at the point of execution and pair them before the period locks. Settling a balance doesn't remove the need for elimination entries, which are still posted in the consolidation layer for any revenue and expense between the entities.

Centralizing audit-ready reporting

Centralizing audit-ready reporting starts at the entity level. Every transaction, approval, and supporting record must be traceable from execution to ledger entry within each entity, so an auditor can review each entity on its own books without manual reconstruction. The group also consolidates: a parent that controls subsidiaries must present consolidated statements with intercompany balances eliminated (IFRS 10, ASC 810-10-45-1), as PwC's guidance on intercompany transactions describes.

Data errors in manual entity reporting

Inconsistent intercompany handling and incomplete documentation tend to show up as mismatches during the close. The team then spends time tracing balances and correcting entries. With dozens or hundreds of entities, small gaps multiply quickly. Citrin Cooperman's intercompany accounting guidance describes these close-process failures.

Bottlenecks in month-end reporting

Context-switching between payment platforms, bank portals, and ERPs adds time to every close cycle. Each system has its own data format, so reconciliation is manual by default, and one entity that finishes late holds up intercompany reconciliation and consolidation for the whole group.

Audit trail gaps across entities

Ad hoc payments that bypass the approval chain are a control failure. Every payment execution must be documented. Approval workflows must produce records that satisfy internal audit and external review.

Benefits of running multiple entities on Altitude

Beyond the accounting sync, a company with several entities gets three practical benefits from the account itself:

• Payment rails for each entity: every workspace can use ACH, same-day ACH, US domestic wire, SEPA, SWIFT, and stablecoin transfers, so each entity pays suppliers and contractors on the rail that fits its corridor. Rail availability varies by country, and every business goes through verification.
• Free intercompany transfers: transfers between your Altitude accounts carry no Altitude fee and settle instantly, so funding one entity from another doesn't wait on a banking cutoff.
• One login, separate cards and access: Altitude is available in 200+ countries, with product availability varying by country, so entities in different countries can sit behind one login. One email address opens up to five workspaces, and each workspace has its own accounts, cards, approval rules, and role-based permissions (Propose, Approve, Submit, Read Only). A finance lead can move between entities without sharing credentials across them.

Accounting syncs to QuickBooks Online and Xero

Accounting syncs to QuickBooks Online and Xero and syncs:

• Bank deposits and payments: ACH, wire, SWIFT and SEPA
• USDC and EURC deposits and transfers
• Transfers between your Altitude accounts
• Card activity, once your Cards account is mapped

Granular user permissions by entity

Permissions are set per workspace, so each entity has its own role-based permissions (Propose, Approve, Submit, Read Only) and configurable thresholds. Those are the operational alternative to routing every payment through a single founder or hiring a dedicated finance team.

Payment rail fees on Altitude

ACH, same-day ACH, US domestic wire, SEPA and supported stablecoin transfers carry no Altitude fee, so transfers between entities on those rails add no Altitude cost. Outbound SWIFT costs $35. Under the OUR convention, the sender covers the known fees, though some intermediary banks can still deduct charges. Stablecoin transfers settle outside banking hours, and Altitude's payments documentation shows settlement windows by rail.

Do I need separate accounts for each entity?

Yes. Each legal entity needs a self-contained set of accounts for external reporting, which typically means maintaining its own ledger, chart of accounts, and approval rules. Separate bank accounts also keep each entity's cash, tax obligations, and audit trail distinct, so transactions between entities can be recorded on both sides and eliminated on consolidation.

How do intercompany transactions affect consolidation?

Intercompany transactions must be documented in both ledgers at the point of execution, then eliminated in the consolidation layer. See "Managing multi-entity elimination flows" for how elimination entries are classified and posted, with a worked example showing that each entity's books stay unchanged.

Can I add entities as my business grows?

Yes. A new legal entity needs its own ledger, chart of accounts, and approval rules from the day it starts transacting, so the group can add entities without restating the books of existing ones. Each new entity also adds intercompany balances to document on both sides and eliminate on consolidation, and one more set of timing differences to resolve before each close.

What's the difference between multi-entity and multi-currency accounting?

Multi-entity accounting treats each legal entity as a separate ledger. Multi-currency accounting treats each currency as a separate balance. A business can have multiple entities, multiple currencies, or both.