Skip to content

Legal entities

Define legal entities as the accounting and reporting scope while preserving the workspace collaboration boundary.

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.

Which company's books does this record belong to?

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

Legal Entity
The company or organization that defines an accounting and legal reporting boundary, distinct from the shared software workspace.
What it works with
Workspace Legal Entities and their own accounting and reporting configuration.
What you get
Separate accounting scopes within a shared collaboration boundary.

How the work progresses

Who uses it

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

  1. Define the company's entity boundary inside the authorized workspace.
  2. Configure its supported accounting and reporting scope.
  3. Select that entity for controlled work without treating other entity records as its own.

A concrete example

Illustrative, not customer data.

Which company's books does this record belong to?

Northstar Parent and Northstar Services share a workspace, but each retains its own journal and reporting scope.

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 legal entities

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 workspace Legal Entities and their own accounting and reporting configuration. 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.