heshi_
← Back to blog

Intercompany Accounting for Multi-Entity Crypto Groups

Heshi Team··4 min read
guide
intercompany
multi-entity
transfer-pricing
crypto-accounting

If your crypto project has more than one legal entity — and most serious ones do — intercompany accounting is one of the most error-prone areas of your financial operations.

A typical crypto group structure looks something like this:

  • Foundation (Cayman Islands) — token issuance, treasury, grants
  • OpCo (Singapore) — development, operations, employment
  • Marketing Co (UAE/ADGM) — marketing, business development, regional operations
  • IP Co (BVI or Ireland) — intellectual property holding

Each entity transacts with the others: the Foundation pays the OpCo for development services, the OpCo licenses IP from the IP Co, the Marketing Co charges the Foundation for marketing services. These intercompany transactions must be properly recorded, priced at arm's length, and eliminated on consolidation.

The Three Intercompany Challenges

1. Recording

Every intercompany transaction needs to be recorded in both entities' books — as a receivable in one and a payable in the other, with matching amounts. In crypto, this gets complicated because:

  • Payments may be in tokens (not fiat) — requiring FX conversion at the transaction date
  • Timing differences: on-chain transfers settle instantly but may not be recorded in both GL systems on the same day
  • Token-denominated invoices change value between issuance and payment

2. Transfer Pricing

Intercompany transactions must be priced at arm's length — meaning the price should be what unrelated parties would agree to in comparable circumstances.

Common intercompany transactions in crypto groups:

  • Development services (OpCo → Foundation): typically cost-plus markup (5-15%)
  • IP licensing (IP Co → OpCo): royalty based on revenue or cost-sharing arrangement
  • Management fees (OpCo → Foundation): allocation of shared overhead
  • Marketing services (Marketing Co → Foundation): cost-plus or fixed fee
  • Treasury management (Foundation → OpCo): management fee for token operations

Each needs documented pricing methodology (CUP, TNMM, cost-plus, etc.) and comparable analysis.

3. Elimination on Consolidation

For consolidated financial statements, all intercompany transactions must be eliminated:

  • Intercompany receivables net to zero against intercompany payables
  • Intercompany revenue nets against intercompany cost
  • Intercompany profits in inventory or assets must be eliminated

Practical Steps

Step 1: Map Your Intercompany Flows

Document every type of transaction between entities. Create a matrix:

From To Transaction Type Frequency Currency Method
Foundation OpCo Development services Monthly USD Cost + 10%
Foundation Marketing Co Marketing services Monthly USD Cost + 8%
IP Co OpCo IP license Quarterly USD 5% of revenue
Foundation OpCo Grant funding As needed ETH/USDC At fair value

Step 2: Standardize Invoice Templates

Create standard intercompany invoice templates that include:

  • Both entity names and jurisdictions
  • Service description matching the transfer pricing documentation
  • Period covered
  • Amount in agreed currency
  • Payment terms
  • Reference to the intercompany agreement

Step 3: Monthly Matching

At each month-end, match intercompany balances across all entities. Every receivable in Entity A should have a corresponding payable in Entity B. Investigate and resolve any mismatches before close.

Step 4: Quarterly Transfer Pricing Review

Review that actual intercompany charges are within the arm's length range documented in your transfer pricing policy. Adjust if markups or fees have drifted.

Step 5: Elimination Entries on Consolidation

Prepare elimination journal entries:

Account Entity Debit Credit
Intercompany Revenue OpCo X
Intercompany Cost Foundation X
Intercompany Payable Foundation X
Intercompany Receivable OpCo X

Crypto-Specific Complications

Token payments for intercompany services: If the Foundation pays the OpCo in ETH for development services, the FX rate at the payment date may differ from the invoice date. This creates FX gains/losses that need to be recorded in both entities.

Treasury token movements: Tokens moving between Foundation wallets and OpCo wallets must be carefully classified — is it an intercompany loan, a grant, a service payment, or a capital contribution? The classification affects tax treatment in both jurisdictions.

DAO governance payments: If a DAO treasury pays contributors who are employed by the OpCo, this may create intercompany obligations that need to be recorded.

Automation Is Essential

Manual intercompany accounting across 3-5 entities, potentially with token-denominated transactions across multiple chains, is a recipe for errors. Heshi automates the matching, flags mismatches in real-time, and generates elimination entries automatically.

Multi-entity crypto group struggling with intercompany accounting? Book a demo — we'll map your intercompany flows and set up automated matching.