United States / Case studies

Case study · SaaS Technology

Two ledgers, one set of numbers: running a group after it goes multi-entity

A SaaS company added a holding structure to reach international investors and customers — and inherited two ledgers, two currencies and a set of intercompany balances that had to agree with each other every month. The structuring decision is a one-time project; keeping the consolidated numbers honest afterward is a recurring discipline, and it is the discipline an investor or acquirer will test first.

The engagement

What was broken

A SaaS startup serving international clients wanted to expand into new markets. Overseas investors had expressed interest in the company, but the existing corporate structure created challenges for foreign investment, intellectual property ownership, and international contracting. The founders needed a scalable structure without disrupting existing operations.

What we did

Working alongside international legal and tax advisors, CapEasy designed a holding company structure that aligned with the founders' expansion plans. We advised on cross-border regulatory compliance, shareholding arrangements, intellectual property ownership, and inter-company agreements while ensuring compliance in the operating jurisdiction. The founders were also guided on future fundraising implications and operational governance.

Where it landed

The company successfully established an international corporate structure that improved investor confidence, simplified overseas contracting, and positioned the business for global fundraising while maintaining compliant operations.

The United States playbook

A holding structure is a decision; consolidation is a monthly job

Standing up a parent entity over an operating subsidiary is a project with a start and an end date — the agreements get signed, the cap table reflects the new layer, and the structure is done. What does not end is the accounting: from that point forward, every month produces two sets of books that have to be combined into one number a US investor, lender or acquirer will actually rely on. A group that treats consolidation as an annual scramble before the audit is the group whose diligence takes weeks instead of days.

The gap shows up first in intercompany transactions — a management fee from the parent to the subsidiary, a cost reimbursement the other way, an IP licence between the two. Each leg of that transaction is booked twice, once in each entity's ledger, in two different charts of accounts and, if one entity is Indian, in two different currencies. Left alone, those two legs drift: a $12,000 charge recorded in one ledger and a slightly different rupee-converted figure in the other, both technically "booked," neither actually agreeing.

Eliminations: why the group total is not the sum of the parts

A consolidated set of financials is not simply the parent's numbers added to the subsidiary's. Intercompany balances and transactions — the management fee, the intercompany loan, the IP licence royalty — sit on both entities' books and have to be eliminated on consolidation so the group does not report revenue or expense to itself, or an asset and a liability that are really the same obligation counted twice. That elimination step is exactly what a related-party filing forces a US-connected group to already be tracking: Form 5471 requires certain US officers, directors and shareholders in foreign corporations to report the relationship, and its Schedule M specifically calls for transactions between the foreign corporation and related persons — the same intercompany lines a clean consolidation eliminates. A 25%-foreign-owned US corporation, or a foreign corporation running a US trade or business, faces the analogous requirement on Form 5472, which exists precisely because the IRS wants visibility into related-party dealings between a US entity and its foreign affiliate.

The practical implication for a founder is that the intercompany schedule is not paperwork you build once for a lawyer — it is the same schedule your bookkeeping needs every month to eliminate correctly, and the same schedule Form 5471 or 5472 will ask about at filing time. Building it once, for both purposes, beats reconstructing it twice from two currencies and two email chains a year later.

Currency translation is a concept, not a plug

When the group includes an entity that keeps its books in a currency other than the parent's reporting currency — rupees under an Indian subsidiary, US dollars at the parent — combining the two requires translating one set of financials into the other's currency before they can be added together. That translation is governed by FASB's foreign currency guidance (ASC 830, Foreign Currency Matters), which sets out how a functional currency is determined and how balance-sheet and income-statement items get translated for consolidation, plus how the resulting translation adjustment is presented. The rule itself did not change; what changes month to month is the exchange rate applied, and a rate picked inconsistently — spot rate for some accounts, an average rate for others, without a documented policy — is what produces a "plug" line nobody can explain in the consolidated statements.

The discipline that holds up under scrutiny is a documented rate policy applied the same way every period: which rate for balance-sheet accounts, which for income-statement activity, and the translation adjustment tracked as its own line rather than absorbed into an unrelated account to make the total balance. CapEasy prepares that translated, eliminated consolidation on a maintained schedule; the accounting conclusions on functional currency designation and any related tax positions run through your CPA and legal advisors.

One close calendar across every entity in the group

A multi-entity group that closes each entity on its own schedule — the US parent on the 5th, the Indian subsidiary whenever its team gets to it — cannot produce a reliable intercompany elimination, because one side of every intercompany entry is closed and the other is not yet final. The fix is a single close calendar that every entity in the group follows in the same order and on the same dates: reconciliations first in each entity, then the intercompany schedule reconciled entity-to-entity before either set of books is called final, then the translation and elimination that turns two ledgers into one consolidated set.

That calendar is the artefact a board, an investor or an acquirer's diligence team actually reads for confidence — not the fact that a structure exists on paper, but that every month since it was formed has produced a consolidated number both entities' books can be traced back to.

What to take from it

  1. A holding structure is a one-time legal project; consolidating it correctly every month is the discipline that follows and never ends.
  2. Intercompany balances must be eliminated on consolidation — and the same schedule that supports the elimination is what Form 5471 Schedule M or Form 5472 will ask about at filing time.
  3. Currency translation needs a documented, consistently applied rate policy under ASC 830 — an inconsistent rate is how an unexplained "plug" line ends up in the consolidated statements.
  4. A group cannot eliminate intercompany entries correctly if its entities close on different calendars; put every entity on one close sequence.
  5. What diligence actually reads is the monthly consolidation trail, not the existence of the structure on paper.

Primary sources

The same discipline, on your books.

A named accountant, the grinding automated, licensed partners where the law wants them.

Book a fit call