Content
Introduction
For multi-entity crypto companies, intercompany transactions are a routine operational reality, and a persistent accounting headache. As Web3 organizations scale across subsidiaries, DAOs, and digital asset funds, tracking, documenting, and eliminating intercompany transfers of crypto assets becomes exponentially more complex than in traditional finance.
The stakes are not theoretical. At FTX, transfers of funds among entities were not properly documented, "due to" and "due from" amounts did not reconcile across entities, and customer funds were commingled with corporate funds. Celsius faced similar structural failures. These cases did not fail because of the absence of a single accounting rule. They reflected deeper breakdowns in governance, internal controls, related-party documentation, reconciliation practices, and asset segregation across multi-entity groups. As the CPA Journal has noted, the crypto industry's lack of mature operational accounting practices amplified the risks in these structures. For finance teams at multi-entity crypto companies today, these cases illustrate what happens when intercompany accounting is treated as an afterthought rather than a systematic process.
What Are Intercompany Transactions?
Intercompany transactions are transfers of assets, services, loans, and settlements between entities within the same consolidated group. Under FASB Statement No. 57 (FAS 57), related party transactions include those between a parent company and its subsidiaries, between subsidiaries of a common parent, between an enterprise and trusts for the benefit of employees (such as pension and profit-sharing trusts managed by the enterprise's management), between an enterprise and its principal owners, management, or members of their immediate families, and between affiliates.
Critically, FAS 57 notes that transactions between related parties are considered related party transactions even when they are not given formal accounting recognition. For example, an enterprise may receive services from a related party without charge and never record receipt of those services. This is a common gap in crypto-native organizations, where informal transfers between entities are frequent and documentation is sparse.
Asset Classification Comes First
Before accounting for any intercompany crypto transfer, finance teams need to determine how the digital asset is classified for accounting purposes. Under ASU 2023-08, crypto assets that meet specific scope criteria — intangible digital assets without enforceable rights to underlying goods, services, or assets, among other conditions — are measured at fair value. However, not all digital assets fall within that scope. Wrapped tokens, certain governance tokens, NFTs, and stablecoins may each require different accounting treatment depending on their characteristics. Getting the classification right at the entity level is a prerequisite for recording intercompany transfers correctly and preparing supportable elimination entries at consolidation.
Types of Intercompany Transactions in Crypto Companies
The most common forms relevant to Web3 finance teams include crypto asset transfers between wallets controlled by different subsidiaries, stablecoin settlements for intercompany services, intercompany loans denominated in digital assets, token distributions from a parent entity to operating subsidiaries, and shared service allocations billed across entities.
Notably, most enterprise B2B crypto intercompany payments are conducted in stablecoins to reduce volatility exposure, making USDC and USDT the dominant settlement instruments in these structures.
Why Intercompany Accounting Is Especially Complex for Crypto Entities
Deloitte has characterized intercompany accounting broadly as "the mess under the bed," and a Deloitte poll of 4,127 accountants identified decentralized accounting systems as the top challenge in managing intercompany activity. In crypto, these challenges are significantly amplified.
Wallets are frequently commingled across individuals and entities without formal segregation. There is no native on-chain distinction between an intercompany transfer and an external transaction. Every transfer must be documented as a contribution, distribution, or sale for proper accounting treatment, and that documentation is often absent entirely.
In partnership contexts, crypto contributions and distributions affect capital accounts and outside basis, requiring coordination between digital asset lot tracking and entity-level accounting.
Crypto accounting software designed for multi-entity structures addresses exactly this operational gap by centralizing transaction data across wallets and entities, giving finance teams the visibility needed to document and reconcile intercompany activity as it occurs rather than reconstructing it at period end.
The FTX and Celsius Warning: What Undocumented Intercompany Transfers Cost
As documented in the FTX bankruptcy proceedings and analyzed by the CPA Journal, transfers of funds among entities were not properly documented, intercompany balances did not reconcile, and customer funds were commingled with corporate funds. These were not narrow compliance failures — they reflected systemic weaknesses in governance, reconciliation, and multi-entity controls. Finance teams at multi-entity crypto companies need systematic intercompany processes, not improvised ones.
How Cryptoworth Helps Multi-Entity Teams Manage Intercompany Accounting
Cryptoworth is a crypto accounting platform built for the operational realities of Web3 finance teams managing multiple entities and wallets. Rather than manually reconciling intercompany transfers across spreadsheets, Cryptoworth centralizes transaction data across wallets and entities, automates cost basis tracking, and generates the audit-ready documentation that intercompany accounting requires.
For teams preparing consolidated financials, Cryptoworth's crypto subledger capabilities and middle office reconciliation tools provide the foundation for supportable intercompany eliminations, ensuring that receivable and payable balances agree before consolidation rather than surfacing mismatches after. This is the kind of systematic infrastructure that turns intercompany compliance from a period-end crisis into a routine process.
The Accounting Standard You Need to Know: ASC 810-10-45
The governing standard for intercompany eliminations in consolidated financial statements is ASC 810-10-45. The language of ASC 810-10-45-1 is unambiguous:
"In the preparation of consolidated financial statements, intra-entity balances and transactions shall be eliminated. This includes intra-entity open account balances, security holdings, sales and purchases, interest, dividends, and so forth. As consolidated financial statements are based on the assumption that they represent the financial position and operating results of a single economic entity, such statements shall not include gain or loss on transactions among the entities in the consolidated group. Accordingly, any intra-entity profit or loss on assets remaining within the consolidated group shall be eliminated; the concept usually applied for this purpose is gross profit or loss."
This standard applies to intra-entity transactions within a consolidated group regardless of asset type, including crypto assets. While U.S. GAAP does not include a crypto-specific intercompany accounting standard, the consolidation elimination requirements of ASC 810 still apply directly.
ASC 805-50 and Common Control Transactions
Crypto corporate structures frequently involve entities under common control that transfer digital assets between themselves. Under ASC 805-50-30-6, when the receiving entity and transferring entity use different accounting methods for similar assets and liabilities, carrying amounts may be adjusted to the basis of accounting used by the receiving entity if the change would be preferable.
Any such change must be applied retrospectively, and financial statements presented for prior periods should be adjusted unless impracticable, per ASC 250-10-45.
Intercompany Journal Entries: Examples for Crypto Transactions
The following examples illustrate how intercompany crypto transactions are recorded. For each scenario, the first set of entries shows what each entity records on its own books. The elimination entries that follow are recorded only at the consolidation level — they do not appear in any individual entity's general ledger.
Example 1: Intercompany Crypto Transfer (No Gain or Loss Recognized)
Parent Entity A transfers 10 BTC to Subsidiary B at carrying value.
Entity-level entries:
Parent Entity A:
- Debit: Intercompany Receivable
- Credit: Crypto Asset (BTC)
Subsidiary B:
- Debit: Crypto Asset (BTC)
- Credit: Intercompany Payable
Consolidation elimination entry:
Because this is an intra-entity transfer within a consolidated group, no gain or loss is recognized at the consolidated level. The receivable and payable are eliminated in consolidation, and the crypto asset appears only once on the consolidated balance sheet.
Example 2: Intercompany Stablecoin Settlement for Services
Subsidiary A pays Subsidiary B 50,000 USDC for shared services rendered.
Entity-level entries:
Subsidiary A (buyer of services):
- Debit: Shared Services Expense
- Credit: Intercompany Payable (USDC)
Subsidiary B (provider of services):
- Debit: Intercompany Receivable (USDC)
- Credit: Service Revenue
Consolidation elimination entry:
Both the revenue on Subsidiary B's books and the expense on Subsidiary A's books are eliminated, along with the intercompany payable and receivable. The consolidated income statement reflects no net impact from this internal exchange.
Example 3: Intercompany Crypto Loan
Entity A lends 100 ETH to Entity B under a formal intercompany agreement.
Entity-level entries:
Entity A (lender):
- Debit: Intercompany Loan Receivable (ETH)
- Credit: Crypto Asset (ETH)
Entity B (borrower):
- Debit: Crypto Asset (ETH)
- Credit: Intercompany Loan Payable (ETH)
Consolidation elimination entry:
As interest accrues, Entity A records interest income and Entity B records interest expense on their respective books. Per ASC 810-10-45-1, both the loan balances and any accrued interest income and expense are eliminated at the consolidation level only. These intercompany journal entries must be documented with the underlying loan agreement to support the elimination.
Intercompany Eliminations: What Gets Removed in Consolidation
Under ASC 810-10-45, the following must be eliminated when preparing consolidated financial statements: intra-entity open account balances, security holdings, intra-entity sales and purchases, interest, dividends, and any intra-entity profit or loss on assets remaining within the consolidated group.
The standard notes this list is illustrative ("and so forth"), and the overarching principle is that consolidated statements shall not include gain or loss on transactions among the entities in the consolidated group. Consolidated financials represent a single economic entity, and internal transfers do not create real economic gains for that entity.
How to Eliminate Intercompany Transactions in Consolidation: Step by Step
Finance teams can follow this process to eliminate intercompany transactions in consolidation:
- Identify all intercompany transactions across entities for the period.
- Confirm that intercompany balances agree between entities. Receivables on one side must match payables on the other.
- Prepare elimination journal entries to zero out matched intercompany balances.
- Eliminate any unrealized profit or loss on intra-entity transfers of crypto assets still held within the consolidated group.
- Document all elimination entries with supporting transaction records.
Step two is where crypto teams most often encounter problems. Wallet commingling and absent documentation mean that intercompany balances frequently do not agree, making the elimination process difficult to execute and impossible to audit.
Intercompany Eliminations and the Arm's Length Principle
The CPA Journal notes that intercompany transactions should be supported by clear documentation and priced in a manner consistent with applicable tax and transfer-pricing requirements. That arm's-length concept is separate from the U.S. GAAP consolidation rules discussed above. From a practical standpoint, however, consistent pricing support and documentation make it easier for finance teams to reconcile balances, support related-party disclosures, and assess the tax consequences of intercompany crypto transactions.
Undocumented or informally priced intercompany transfers create downstream elimination and disclosure problems that compound at every reporting period.
Transfer Pricing, Tax, and Documentation Requirements
Note: U.S. GAAP consolidation and intercompany elimination rules (discussed above) are separate from transfer pricing, income tax, and indirect tax obligations. The requirements in this section arise from tax law and regulatory frameworks, not from the accounting standards governing consolidated financial statements. Finance teams should address both, but should not conflate them.
Intercompany transactions with related parties must comply with the arm's length standard under OECD guidelines on transfer pricing and applicable local rules. For crypto companies, this means maintaining documentation for service agreements, intercompany lending arrangements, and token transfers between entities.
Core documentation elements finance teams need include the scope of services, pricing methodology, allocation keys for shared costs, and settlement terms. For service agreements, this means defining cost pools, markups or fixed fee basis, measurable service levels, reporting and oversight provisions, and treatment of excess capacity costs. For lending arrangements, this means specifying principal amounts, interest rates, and repayment terms denominated in the relevant digital asset.
VAT requirements may also apply to intercompany transactions, depending on the jurisdiction and the nature of the supply. In many jurisdictions, intercompany transactions may fall within the scope of VAT even where no cash changes hands due to netting, but the treatment varies significantly by country and transaction type. Each intercompany transaction should be assessed for local invoicing and indirect tax obligations, and finance teams operating across borders should seek local tax advice to determine the applicable rules.
Transfer pricing adjustments relating to already-issued invoices generally need to be reflected through debit or credit notes referencing the original invoice.
Disclosure Requirements for Intercompany Transactions
Under FAS 57 / ASC 850, required disclosures for related party transactions include the nature of the relationship, a description of the transactions, dollar amounts of transactions for each period for which financial statements are presented, amounts due from or to related parties as of the date of each balance sheet presented, and the terms and manner of settlement.
Control relationships must be disclosed even when no transactions occur between entities, because the common control may result in operating results or financial position significantly different from what would have been obtained if the enterprises were autonomous.
For SEC registrants involved in specific structures — such as guaranteed-securities or collateralized-securities arrangements — Rules 13-01 and 13-02 under Regulation S-X require Summarized Financial Information to be presented on a combined basis, with intercompany eliminations among the obligor group applied. Intercompany amounts between the obligor group and non-obligors must remain and be separately identified. These rules apply in the context of those specific filing obligations and became effective January 4, 2021, with earlier compliance permitted. They are not general-purpose intercompany disclosure requirements for all public companies.
ASU 2024-03 (DISE) and Intercompany Activity
Finance teams preparing consolidated financials should also be aware of ASU 2024-03 (Disaggregation of Income Statement Expenses, or DISE). This is a disclosure standard that requires public business entities to provide more detailed breakdowns of certain expense line items in the notes to the financial statements. It is not a consolidation standard and does not change how intercompany transactions are eliminated.
However, in developing the standard, FASB acknowledged that consolidated reporting practices — including intra-entity cost allocations and shared service arrangements — can make exact disaggregation of expenses burdensome. The standard permits the use of reasonable estimates or approximations where transaction-level data is not readily available due to these factors. For multi-entity crypto companies with high volumes of intra-group cost allocations, this acknowledgment is worth noting when preparing the required disclosures, though it does not reduce or modify the underlying intercompany elimination requirements.
Income Tax Considerations for Intercompany Crypto Transfers
Note: The income tax treatment of intercompany transfers is governed by the Internal Revenue Code and applicable regulations, not by U.S. GAAP consolidation standards. This section addresses the financial reporting implications of those tax rules.
Before ASU 2016-16, when recognizing income on an intercompany sale or transfer of an asset, an entity had to record a journal entry to eliminate the income tax expense in the seller's jurisdiction and record an asset (such as a prepaid asset) for taxes paid. The entity also had to reduce the tax basis in the buyer's jurisdiction for financial reporting purposes so that no deferred tax asset was recorded for the difference between the buyer's tax basis and consolidated book basis.
Finance teams should also note the Form 1099-DA timeline. Brokers generally began Form 1099-DA gross-proceeds reporting for digital-asset transactions on or after January 1, 2025. Basis reporting is expected to expand for certain transactions beginning January 1, 2026, subject to final rules and IRS instructions. Self-custody wallets where users control private keys are not covered under the current rules. Teams managing intercompany transfers through custodial platforms should factor this reporting layer into their documentation workflows.
Best Practices for Managing Intercompany Crypto Transactions
Finance teams at multi-entity crypto companies should build intercompany accounting into their operational infrastructure, not their period-end close.
- Formally segregate wallets by entity. Never commingle across subsidiaries without documented intercompany agreements.
- Document every intercompany transfer at the time of transaction, specifying whether it is a contribution, distribution, loan, or sale.
- Maintain intercompany agreements that specify pricing methodology, settlement terms, and allocation keys.
- Reconcile intercompany balances between entities at each reporting period before consolidation, not after.
- Apply consistent cost basis tracking across entities so eliminations are mathematically supportable.
- Use a purpose-built crypto accounting platform to centralize wallet data across entities and automate the reconciliation and documentation workflows that manual processes cannot scale.
Conclusion
Intercompany transactions in crypto are governed by the same GAAP consolidation rules that apply to any asset type. ASC 810-10-45 is clear, and the elimination requirements are not discretionary. But the operational complexity of blockchain-based transfers, commingled wallets, and multi-entity crypto structures makes compliance significantly harder in practice than in traditional finance.
The finance teams that get this right treat intercompany accounting as a systematic process, built on documented agreements, reconciled balances, and consistent cost basis tracking across entities. Cryptoworth is built to support exactly this, automating the transaction data aggregation, cost basis tracking, and audit-ready documentation that multi-entity crypto accounting demands.
Disclaimer
The information provided in this article is for educational and informational purposes only. No legal, tax, investment, or other professional advice is being provided by Cryptoworth™ Corporation.
Tax rules and regulations vary across jurisdictions and individual circumstances.
We strongly recommend that you consult with a qualified tax advisor, accountant, or financial professional before making any decisions related to your specific situation. Your personal financial or tax outcomes may differ based on your location, portfolio, and reporting requirements.
Cryptoworth™ Corporation assumes no responsibility or liability for any decisions made based on the content of this article.