Skip to content

Multi entity reporting

Compare and consolidate legal-entity reporting with traceable inputs, boundaries, and limitations.

Separate entities. Group visibility.Sample company

Northstar Parent

Revenue · separate USD ledger

$120,000

Northstar Services

Revenue · separate USD ledger

$80,000

Combined revenue

$200,000

Internal charge eliminated

−$12,000

External group revenue

$188,000

Derived report. Neither entity ledger is rewritten.

Can I compare the group and still inspect each entity?

Group visibility becomes opaque when legal-entity boundaries, paired intercompany activity, translation, and eliminations are buried in spreadsheets.

Consolidated reporting
A derived view of a defined group, subject to explicit translation and elimination rules.
What it works with
Selected Legal Entities, their reporting inputs and the supported consolidation scope.
What you get
Group context with visible entity boundaries and traceable reporting limitations.

How the work progresses

Who uses it

Group finance teams and controllers responsible for separate companies and consolidated reporting.

  1. Confirm which entities and reporting inputs belong in the group view.
  2. Compare entity-level evidence and the supported derived group result.
  3. Inspect differences, currency authority and eliminations rather than assuming the records have been merged.

A concrete example

Illustrative, not customer data.

Can I compare the group and still inspect each entity?

A controller checks the group result, then returns to the parent and subsidiary inputs rather than treating the group view as a merged ledger.

Explore the sample company

What still needs judgment

Different-currency activity requires explicit approved FX authority. Consolidation is derived reporting and never mutates member ledgers or creates a balancing plug.

AI can explain entity and elimination drivers, but cannot approve rates, post either side, change ownership, or override unsupported reporting.

Available workflows depend on your plan, permission scope, configuration and supported data. Compare plans before choosing.

Before you use multi entity reporting

Can I explore this before connecting company data?
The public demo is a fixed, read-only sample company. It illustrates supported product areas without creating an account or accessing customer data; it is not proof that every configured workflow is available in the tour.
What should I verify before relying on an output?
Confirm scope, source coverage and timing. For this capability, review selected Legal Entities, their reporting inputs and the supported consolidation scope. An operating status or AI explanation does not replace the required review of accounting evidence.
Does an explanation automatically authorize a financial action?
No. AI can explain entity and elimination drivers, but cannot approve rates, post either side, change ownership, or override unsupported reporting.

Continue the workflow

See the work in context.

Explore a read-only sample company, or start with your own supported data.