Multi-entity finance operations

Manage Expense Workflows Across Multiple Subsidiaries

Standardize shared expense steps across subsidiaries without losing entity-level ownership, account mappings, approval authority, currency, or settlement context.

The approach

A multi-subsidiary process must preserve which legal entity incurred and recognizes a cost while making common submission and review steps understandable. Do not infer entity ownership solely from an employee's location or manager. Define how entity, account, department, and project are selected; name owners for mappings and exceptions; and record a supported basis for shared costs. Reconcile expenses and obligations within each entity before reviewing cross-entity allocations and consolidated totals.

A practical process

Set an entity assignment rule

Document how the responsible entity is determined for each expense type and who resolves uncertainty. Capture the source amount and currency alongside required accounting dimensions so entity-level records remain explainable.

Govern common and local mappings

Maintain controlled mappings for categories, accounts, dimensions, approvers, and settlement routes. Record owners and effective dates; reuse shared definitions only where local processes genuinely align.

Route by the right authority

Assign reviewers according to entity and delegated decision rights, with a conflict route when a submitter is also the usual approver. Keep policy authorization separate from finance's validation of coding and documentation.

Reconcile entity books before consolidation

Match expenses, card balances, employee obligations, and settlements within each entity. Then investigate shared costs and intercompany balances using the documented allocation basis and retain links to the source record.

Worked example

Illustration only—not a real customer case or measured outcome: a shared software service supports employees in two subsidiaries, while one employee submits the invoice. Finance confirms the entity assignment and applies the organization's documented allocation basis, checks each entity's account mapping, and records any needed intercompany treatment. The original amount and invoice remain linked to both resulting records; the cost is not split merely to make reports appear balanced.

What to avoid

  • Do not assign a cost to an entity using employee location alone.
  • Do not assume identical expense categories map to identical accounts across entities.
  • Do not consolidate before reviewing entity-level transactions and open exceptions.