Multi-entity professional services firms carry a complexity that single-entity firms simply don’t: separate legal entities, cost centers mapped to different sets of books, consultants crossing company lines, and invoices going out in multiple currencies. Most PSA platforms are built around a single organizational unit. When you add a second entity through acquisition, a new regional office, or a shared-services structure, the financial logic starts to break. The right enterprise PSA platform doesn’t just accommodate multiple entities — it treats intercompany financial continuity as a design principle, not an afterthought.
Why Single-Entity PSAs Break at Scale
The problem isn’t that your existing platform can’t add a second company. It’s that the financial architecture underneath it was never built to handle the question: whose revenue is this, whose cost is this, and in which currency should each be recognized?
When a consultant from your UK entity works on a US project, that transaction touches two sets of books, two base currencies, and two taxing authorities. A platform without native intercompany logic forces your finance team to resolve this manually — through spreadsheet reconciliation, manual journal entries, or post-hoc GL corrections. By the time you have three or more entities, the reconciliation cost compounds geometrically.
Enterprise PSA platforms solve this at the architecture level. Each legal entity maintains its own base currency, its own tax settings, and its own GL mapping. When work crosses entity lines, the platform generates intercompany transactions automatically, routes them to the correct books, and applies the prevailing FX rate. Your finance team sees clean, auditable records — not a reconciliation backlog.
How Intercompany Billing Actually Works
The Hub-and-Spoke Model
For firms with three or more entities, the most scalable intercompany configuration routes all cross-entity transactions through a master company. Without this, every entity pair requires its own defined account mapping — and as the number of entities grows, the number of required mappings grows geometrically. A hub-and-spoke architecture collapses that complexity: transactions flow through a central node, whether that’s an operating holding company or a designated master entity, and the mapping overhead stays constant regardless of how many subsidiaries you add.
Currency Separation and FX Revaluation
Every entity in a multi-entity structure keeps its books in its own base currency. When a transaction crosses currencies — a EUR-denominated engagement delivered by a GBP-cost resource, for example — enterprise PSA platforms separate engagement currency from company currency and apply FX revaluation at the prevailing rate. This means your project financials stay accurate in the engagement currency your client is billed in, while your corporate consolidation reflects the correct functional currency for each entity’s books.
For example: a consulting firm with entities in the US, UK, and Germany might bill a German client in EUR, staff the project with a London-based consultant paid in GBP, and consolidate everything into USD for the parent company’s reporting. Each layer needs its own currency logic — and each needs to reconcile cleanly against the others at month-end.
Governance Across Entities Without Losing Visibility
Hierarchical Permissions and Data Separation
Multi-entity firms need finance directors in one entity to see everything relevant to their books and nothing they shouldn’t see in another entity’s. Enterprise PSA platforms govern this through role-based permissions tied to cost centers and organizational structures, not just user roles. A controller in your Singapore entity gets full visibility into Singapore project profitability, billing, and WIP — without access to the US entity’s rate cards or margin data.
Consolidated Reporting Across Entities
Separation of financial records doesn’t mean separation of visibility at the executive level. The most important capability for a COO or CFO managing multiple entities is a consolidated view: utilization across all practices, AR aging across all entities, and WIP balances that roll up to a single dashboard without manual assembly. Enterprise PSA platforms achieve this by maintaining a single data layer above the entity-level financial records — so you can drill down to Singapore’s DSO or roll up to the firm’s global profitability in the same system.
Rate Structures Across Practices and Entities
Different entities often serve different markets, run different billing models, or staff at different cost levels. A firm where the US practice bills T&M and the UK practice runs fixed-fee engagements needs rate management that can carry both models simultaneously, with the correct billing logic inherited at the engagement level rather than overridden manually.
Enterprise PSA platforms centralize rate card management while allowing entity-level and engagement-level overrides. Cost rates, bill rates, and blended rate targets are defined centrally and inherited downstream — so a Resource Manager staffing a cross-entity project is working with financially accurate data, not estimates.
- Rate cards can be maintained at the entity level, the practice level, or the individual engagement level.
- Intercompany cost rates govern what one entity charges another for shared resources — keeping transfer pricing consistent and auditable.
What to Look For in an Enterprise PSA
The right platform for a multi-entity firm gives you financial continuity across the full project lifecycle — from the moment a quote is issued to the moment cash is collected — across every entity, every currency, and every cost center. That means intercompany transactions handled automatically, FX applied at the correct rate, permissions scoped to the right organizational boundaries, and consolidated visibility available without a reporting sprint.
Financial precision at the entity level and operational visibility at the firm level aren’t competing goals. The right enterprise PSA platform delivers both from the same financial foundation.
