Multi-entity

Forty portcos. One bridge.

Entity, location, and department are first-class dimensions on every projection and every diagnostic. Per-entity visibility for location managers, consolidated rollup for sponsors and CFOs, intercompany eliminations attributed to a synthetic entity so the bridge stays auditable.

First-class dimensions

Locations are not a tag. Entities are not a tag.

Most accounting platforms treat multi-entity and multi-location as bolt-on attributes — tags slapped onto a single-tenant ledger. We treat them as first-class dimensions on every journal entry, every projection, every report.

01 · ENTITIES

Saved groups of portfolio companies.

Define an entity group once. Roll up the four restaurants. Roll up the fund's twelve portcos. Every scenario, every diagnostic, every report can be scoped to a single entity, a group, or the consolidated parent without re-saving anything.

02 · LOCATIONS

Hierarchical, with parent/child rollup.

Locations carry parent/child relationships you manage as real resources — not a free-text field your team typos differently every quarter. Houston rolls up to Texas. Texas rolls up to the brand. Every location-aware report respects the tree.

03 · DEPARTMENTS

Cost allocation across business units.

For DSOs running clinical / non-clinical splits, or franchises tracking back-office allocations, departments give you the dimension you need for cost allocation without inventing a new chart of accounts.

Consolidated EBITDA bridge

One waterfall. Per-entity attribution.

When scope is consolidated, the projector runs per-entity in parallel inside the same request — the per-entity slices are independent so this is safe — and aggregates with intercompany elimination hooks. The eliminations themselves are recorded as a special "elimination" synthetic entity so they show up in the bridge and remain auditable.

The drill panel adds an entity column showing which locations drove each bar. The Dallas Plano location is dragging this scenario. Houston Heights is the largest contributor. Eliminations took $11k off the consolidated total — here are the entries.

  • Same lever. Different scope. One entity, one group, or consolidated parent
  • Per-entity contribution surfaced on every bar of every bridge
  • Intercompany eliminations attributed to a synthetic entity, auditable like any other entity
  • Tornado charts can be sliced by location to show which units are most sensitive to which levers
  • RBAC scoping: PE sponsors see consolidated; location managers see their entity
Pro forma modeling

"Add five locations in Q3."

A scenario can include synthetic locations — entities with no historical actuals — whose ramp curve is borrowed from a chosen historical analog. Add Dallas Frisco, model the ramp on Plano's first nine months, project the consolidated EBITDA impact through year-end. Every pro forma is auditable to the analog it inherited its trajectory from.

  • Synthetic entities with chosen historical analog as the ramp source
  • Per-period scaling controls if you expect the new location to ramp faster or slower than the analog
  • Inherits the lever vocabulary of the analog — same drivers, same envelopes
  • Cleanly removable after the period closes; or "promote to real entity" when you actually open the doors
  • Same Goal Seek and What-If math; the pro forma units participate in the consolidated optimization
RBAC scoping: PE sponsors see consolidated; location managers see their entity. The same scenario looks different depending on who's logged in — not by hiding numbers, but by limiting the scope of the projector itself to what the role is permitted to see.
Multi-tenant from the ledger up

Stop signing contracts before you've seen your own numbers.

Connect your books in an afternoon. See the diagnostics and the first scenarios on your real data, the same week. No implementation fees, no six-month rollout, no SOW.

app.rollupbooks.ai Start free
Already a user? Sign in ↗