Skip to content

Intercompany

Prepare paired drafts and verify exact due-to and due-from evidence without creating bank movement.

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.

Do both companies support the same internal transaction?

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

Due to / due from
Reciprocal payable and receivable positions between entities; each side belongs to its own books.
What it works with
Paired Legal Entity drafts, due-to/due-from account mappings and explicit currency authority where required.
What you get
A reviewable relationship that exposes a one-sided or partially posted state.

How the work progresses

Who uses it

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

  1. Prepare the paired entity context and eligible due-to/due-from mappings.
  2. Review each side with explicit currency authority where needed.
  3. Verify actual posting evidence on both sides and retain partial states until the relationship is supported.

A concrete example

Illustrative, not customer data.

Do both companies support the same internal transaction?

A $12,000 parent charge needs corresponding evidence in the subsidiary. One posted side is not presented as a fully balanced relationship.

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 intercompany

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 paired Legal Entity drafts, due-to/due-from account mappings and explicit currency authority where required. 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.