When a professional services firm operates across multiple legal entities, getting the financials right across those boundaries becomes one of the more complex problems in the back office. Resources from one entity work on projects owned by another, costs cross currency lines, and finance teams end up reconciling intercompany transactions by hand at month-end. Enterprise PSA platforms address this directly, treating inter-company billing as a structured accounting event rather than a manual workaround. The result is a system where cost-plus charges between entities are calculated, routed, and posted automatically, without a reconciliation sprint at the end of every period.
What Is Inter-Company Billing in PSA?
The problem: most multi-entity firms don’t have a single mechanism to price and record the transfer of services between their own companies.
When a US-based entity staffs a consultant onto a project owned by a UK entity, two things need to happen: the cost has to land on the right company’s books, and the borrowing entity has to be billed at an agreed rate, often cost plus an agreed markup. Without a dedicated system, finance handles this through manual journal entries, export-and-reimport cycles between GL systems, or elaborate spreadsheet models that introduce lag and error into the close process.
Enterprise PSA platforms resolve this by modeling each legal entity as a distinct company within the platform, each with its own GL accounts, currency, and tax profile. When a resource from one company logs time on a project belonging to another, the platform automatically generates the corresponding intercompany transaction, applies the configured cost-plus rate, and posts both sides of the entry to the correct books. The margin between cost and the transfer price is recognized by the supplying entity; the receiving entity sees the cost it actually owes.
Enterprise PSA platforms that support multi-entity structures can also route all intercompany transactions through a designated master company, which functions as a financial hub. This simplifies the accounting configuration significantly, particularly once you have three or more entities, because it replaces a geometric expansion of entity-to-entity account mappings with a single hub-and-spoke model.
How Does Cost-Plus Markup Get Calculated?
The problem: transfer pricing rules differ by entity pair, by resource type, and sometimes by contract.
Cost-plus billing between entities typically needs to reflect an agreed internal rate, not just the raw cost of the resource. That rate may vary based on the department the resource belongs to, their role or title, the type of work being performed, or the specific relationship between the two entities involved.
Enterprise PSA platforms govern this through a rate management layer that separates external billing rates from internal cost rates. The platform holds both figures for each resource or role and calculates the markup differential automatically when a cross-entity transaction is generated. Finance can define the markup rules once, at the organizational level, and the platform applies them consistently every time a qualifying time entry crosses a company boundary. There is no manual step required to price the transaction.
For example: A 200-person engineering firm with entities in the US, Germany, and Australia regularly seconds resources from the German entity to projects run out of the US entity. Finance has agreed on a 15% markup on German cost rates for any such intercompany transfer. Rather than calculating and entering that markup manually each month, the platform applies the 15% rule automatically at the point of time entry, generating the transfer invoice and both GL postings in the correct currencies as part of the standard billing cycle.
What Happens When Currencies Are Involved?
The problem: cross-entity work often crosses currency lines, which creates FX exposure that has to be captured accurately on both sets of books.
When the supplying and receiving entities carry their books in different base currencies, the intercompany transaction needs to be converted and recorded accurately on both sides. Manual FX conversion introduces inconsistency: the rate used may differ from the period rate used in the GL, creating reconciliation gaps that compound over time.
Enterprise PSA platforms that support multi-currency operations handle this by separating the transaction currency from each entity’s book currency. When a cross-entity charge is generated, the platform applies the prevailing exchange rate to convert the transaction amount into each entity’s base currency, and the resulting amounts are posted to the respective GL accounts accordingly. Both entities end up with an accurate, auditable record in their own currency, based on the same rate, applied at the same point in time.
What About FX Revaluation at Period Close?
Currency positions on open intercompany receivables and payables need to be revalued at period end as exchange rates move. Enterprise PSA platforms that manage multi-currency intercompany billing will include an FX revaluation mechanism that recalculates open balances at the closing rate and posts the resulting gain or loss to the appropriate accounts. This keeps the balance sheet current without manual adjustment and eliminates one of the more error-prone steps in the multi-currency close process.
How Are Intercompany Invoices Generated?
The problem: generating, approving, and matching intercompany invoices manually adds significant administrative overhead to the billing cycle.
In a manual process, the supplying entity prepares an invoice, sends it to the receiving entity, and someone on the receiving side matches it to the expected charges before approving it for payment. When this happens across multiple entity pairs, the volume of coordination required makes it a consistent bottleneck.
Enterprise PSA platforms automate the invoicing step as a direct output of the time and expense approval process. Once time entries are approved, the platform can generate intercompany invoices for the relevant entity pairs based on the configured billing rules, without requiring a separate manual request. Both the receivable on the supplying entity’s books and the payable on the receiving entity’s books are created from the same source record, which means matching is automatic and the audit trail is complete.
- The invoice reflects the actual approved hours and the configured cost-plus rate.
- The GL postings on both sides trace back to the originating time entries.
Does This Scale Across Many Entities?
The problem: intercompany billing complexity grows geometrically as entity count increases, and most manual processes cannot keep pace.
A firm with two entities has one intercompany relationship to manage. A firm with five entities potentially has ten. The number of account mappings, rate agreements, and invoice flows required to run intercompany billing manually across that structure becomes unmanageable quickly.
Enterprise PSA platforms address this through the hub-and-spoke architecture described above, combined with a centralized rate and account configuration model. Finance defines the rules once, at the organizational level. The platform enforces them across every entity combination, every billing cycle, and every currency, without requiring per-transaction intervention. As your firm acquires additional entities or opens new offices, the same configuration model scales to cover them.
