OHM · Workflows · Multi-entity groups
Multi-entity groups
Consolidation becomes arithmetic, because both sides already agreed.
Group consolidation is hard for one reason: two entities book the same transaction differently and both are right. Agreeing it at the point of entry removes the argument from the close entirely.
The same step, two ways
How it runs today
- Each entity books its side on its own timing, in its own way.
- Intercompany differences surface at consolidation, weeks later.
- Eliminations become a negotiation between controllers who have both moved on.
- A duplicate invoice booked in two entities reads as two legitimate bills.
With the team on it
- Counterparty entity, amount and date are agreed before either side posts.
- Eliminations are arithmetic because the numbers were reconciled at entry.
- Duplicates are caught across entities, not just within one.
- The group position is available without waiting for every entity to finish.
Who runs, and what they enforce
All of them, on the same group position, at the same time. Not a queue.
| Agent | What it enforces |
|---|---|
| Intercompany Agent | Counterparty entity agreed |
| Duplicate Agent | No second copy, across any entity |
| Reconciliation Agent | Sub-ledger agrees to the control account |
| Period Agent | Posted in the open period |
| Report Agent | Books ready to report |
Agents without a link yet are part of the team but do not have a page written up.
What lands in your ERP
A consolidated position where the eliminations were agreed transaction by transaction, so the number does not move when someone checks it.
Agreed
The stamp on a group position that cleared this step. It means every check ran and passed — not that a sample did, and not that it will be reviewed later.
See this step run on your last 90 days.
One export. No connector. We come back within a working day.
$Check your savings→