Industry

Multi-company groups

Sequence modernization across legal entities, shared services and local operations while preserving statutory and commercially necessary variation.

Page purpose

Start from the operating model in Multi-company groups, not a generic technology list.

Multi-company groups operate under pressure to close and consolidate on time, integrate acquisitions, control shared spend, and compare performance while each legal entity retains its own accountability. Currency, calendar, tax treatment, language, market, and business-model differences make group visibility and local operation a continuous balancing decision.

The operating sequence starts when an entity, branch, account, counterparty, employee, supplier, or item is created. It continues through local purchasing, sales, payroll, treasury, and journals; crosses entity boundaries through goods, services, loans, or allocations; and ends in matching, settlement, entity close, elimination, and consolidated review.

Operating pressures

Where fragmentation creates operating cost.

  • A new or acquired entity is represented differently in banking, procurement, HR, sales, accounting, and reporting records.
  • The same supplier, customer, employee, item, or account cannot be followed reliably from one company's record into another's.
  • Sender and receiver disagree on period, currency value, quantity, charge basis, or reference, leaving balances open near close.
  • Close teams request late files and explanations because adjustments, settlements, and elimination reasons sit outside the transaction trail.

Sector priorities

What modernization success means in this context.

  • A visible operating calendar links company cutoffs, submissions, matching, settlement, adjustment, elimination, and consolidated review.
  • Each selected cross-company flow has named sender, receiver, amount or quantity basis, due date, dispute route, and close treatment.
  • Entity differences are recorded with their effect on daily work and period close, so the accountable owner can preserve, revise, or retire them.

Context-specific decisions

Questions inseparable from the sector context.

  • Which event creates the authoritative entity and counterparty relationship used in cross-company transactions?
  • Which differences must be resolved before close, which can be disclosed and carried, and who accepts each treatment?
  • Which recurring mismatch should be addressed at source, at the company handoff, or in the close process?

Modernization agenda

Maps that connect systems to work.

  • Entity factbook covering ownership, operating model, currency, calendar, language, accounts, cutoffs, responsible teams, and source records
  • Month-end operating calendar showing submissions, matching windows, settlement dates, dependencies, escalation points, and review meetings
  • Cross-company casebook for selected goods, service, loan, allocation, and correction scenarios with paired sender and receiver records
  • Aged exception ledger for master-record conflicts, unmatched balances, disputed charges, missing explanations, and unresolved ownership

Change sequence

Sequencing change around continuity and dependency.

  1. Reconstruct the last two close cycles from calendars, submitted files, journal timings, adjustments, disputes, and review notes.
  2. Trace paired sender and receiver records for representative goods, services, treasury, allocation, and correction transactions.
  3. Compare entity handling through concrete records and decisions, then document why each material difference exists and who owns it.
  4. Order corrective actions by recurring delay, financial or operating exposure, dependency, and the next close in which evidence can be observed.

Context risks

Generic assumptions that do not hold in this context.

  • A late adjustment may make consolidated totals appear complete while the underlying company records remain unexplained.
  • Currency, period, quantity, or counterparty differences may be netted away and recur in the next close.
  • A locally necessary treatment may be removed without understanding its legal, commercial, workforce, or operating consequence.

Operating performance

Operating results, not technology metrics alone.

  • Elapsed time from company cutoff to matched balances, completed eliminations, and consolidated review
  • Count, value, age, and owner of unmatched cross-company transactions and late close adjustments
  • Selected consolidated measures traced to entity records with consistent period, currency, account, counterparty, and explanation

Decision questions

Questions that start from the operating model.

Which company differences deserve attention first?

Prioritize differences that delay close, break a paired transaction, change a reported meaning, create repeated adjustment, or obscure responsibility. Preserve a necessary local treatment while its reason and downstream effect remain documented.

Where should investigation begin?

Begin with a recent close and a small set of high-friction cross-company records. They reveal the actual cutoffs, handoffs, mismatches, manual explanations, and owners more clearly than an abstract organization chart.

Related decision

Continue from Multi-company groups to another decision angle.