Multi-Entity Treasury: Running Accounts Across Group Companies

A multi-entity treasury should centralise visibility and control without combining the assets or records of separate legal companies. Give each entity distinct fiat accounts, stablecoin wallets, approvals and accounting exports. Document every intercompany transfer according to its legal purpose, post both sides consistently, and consolidate balances only in group reporting. This preserves ownership boundaries while letting treasury manage liquidity across fiat, USDC and USDT.

Separate legal ownership from group-wide visibility

A subsidiary is not simply a department or cost centre. It has its own books, creditors, directors, tax obligations and potentially different regulatory requirements. Its treasury structure should make that legal distinction visible at account, wallet and transaction level.

Each operating company should normally have its own fiat accounts or virtual account details where available, separate USDC and USDT wallets for each network used, named authorised users, entity-specific approval limits, beneficiary records and accounting exports. Corporate cards should also be issued and reconciled under the entity responsible for the expenditure.

The parent or central treasury team can still have consolidated access. The distinction is between centralised operation and commingled ownership: the same team may administer several entities, but each balance and payment should remain attributable to its legal owner.

For stablecoins, using separate wallets is as important as using separate bank accounts. If two subsidiaries share one wallet, the blockchain shows the wallet’s aggregate balance but does not establish which company owns each token. An internal spreadsheet may help allocate activity, but it is weaker than maintaining separation at source.

Stablerail supports a single business account environment for USDC and USDT treasury with entity-level balances, approvals and signing quorum, corporate cards, global payouts, fiat off-ramp access and exportable audit evidence. Availability of accounts and payment rails still depends on each entity’s jurisdiction, industry and KYB review.

Complete onboarding for every legal entity

Approval of the parent company does not automatically approve its subsidiaries. Each company opening an account must complete the applicable know-your-business review, even when ownership and directors overlap.

Finance teams can reduce repeated requests by maintaining a group onboarding pack containing:

• Certificates of incorporation and constitutional documents.
• Registered and operating address evidence.
• Directors, authorised signers and ultimate beneficial owners.
• A dated ownership chart connecting the parent and subsidiaries.
• A description of each entity’s business, expected activity and payment corridors.
• Source-of-funds or source-of-wealth evidence where requested.
• Licences or registrations relevant to regulated activities.

Map each document to the entity it supports. A group chart explains the relationship, but it does not replace entity-specific incorporation records, authority documents or financial information.

Choose the payment route by entity and purpose

The fastest route is not always the most appropriate. Treasury should consider the sending entity, destination ownership, currency, asset, network compatibility, cut-off time, counterparty acceptance, fees and evidence produced by the route.

Stablecoin compatibility must be checked at the asset-and-network level. USDC on Base, for example, should not be sent to an address that the recipient supports only for USDC on Ethereum. The address format alone may not reveal the mismatch. Confirm the token, network and destination ownership through a trusted channel, and use a small test transfer when the destination or route is new.

Treat intercompany transfers as legal transactions

An intercompany transfer is not an informal movement inside one corporate wallet. Before sending funds, determine whether it is an intercompany loan, capital contribution, dividend, shared-cost recharge, invoice settlement or cash-pool movement. That classification determines the agreement, approvals, tax analysis and accounting entries required.

For example, an intercompany loan will usually create a receivable for the lender and a payable for the borrower. A capital contribution affects equity rather than an intercompany payable. Exact treatment depends on the applicable accounting standards, company law, transfer-pricing rules and executed documents.

Intercompany transfer checklist

1. Confirm the purpose. Link the payment to an agreement, invoice, board approval or treasury instruction.
2. Verify authority. Check that the transfer is permitted under the entity’s mandates, approval limits and any cash-pool or loan agreement.
3. Validate ownership. Confirm that the bank account or wallet belongs to the intended receiving entity.
4. Select the route. Compare fiat, on-chain and conversion routes using total cost, timing and evidence requirements.
5. Approve from the sender. Apply the sending company’s approval workflow and signing quorum rather than a generic group approval.
6. Capture execution data. Retain bank references or transaction hashes, wallet addresses, token, network, amount, fees, exchange rate and timestamp.
7. Post both sides. Record equal and opposite intercompany entries using the same reference and investigate any difference.

For stablecoin conversions, record more than the token amount. Finance needs the fiat amount, accounting timestamp, rate source, conversion charge, network fee and the asset used to pay that fee. The blockchain transaction hash proves execution, but it does not explain the business purpose or accounting classification.

Consolidate reporting without consolidating custody

Group treasury reporting should aggregate information while preserving the underlying entity records. A CFO may need one liquidity view, while controllers and auditors need to drill down to the legal owner, account, wallet and transaction.

A useful group report shows balances by entity, currency, stablecoin and network; distinguishes available, committed and restricted funds; identifies intercompany receivables and payables; and includes upcoming payroll, tax, supplier and debt obligations. It should also expose unmatched intercompany entries instead of netting them silently.

Use a consistent chart of accounts, entity codes and transaction references across the group. For USDC and USDT, retain the network because the same ticker on different chains represents separate operational balances. Record internal wallet movements as transfers, not revenue or expense, while separately recording network and conversion fees under the group’s accounting policy.

At consolidation, matched intercompany balances and transactions are eliminated from group results. They remain in the individual legal entities’ ledgers because each company must still show its own receivable, payable, funding or distribution activity.

Run a repeatable month-end control process

A disciplined close is more reliable than reconstructing ownership and purpose after the fact. The finance team should:

• Export bank, card, conversion and blockchain activity for every entity.
• Reconcile each bank account and wallet to its entity ledger.
• Match intercompany entries by reference, amount, asset and date.
• Investigate timing differences, fees and exchange-rate variances.
• Revalue stablecoin and foreign-currency balances under the applicable accounting policy.
• Eliminate matched intercompany balances only in the consolidation layer.
• Archive approvals, agreements, invoices, bank references and transaction hashes.

Stablerail can provide approval histories, pre-send sanctions and address-screening records, and exportable audit evidence. Those records support review but do not replace intercompany agreements, invoices, board approvals, transfer-pricing analysis or tax documentation.

The durable model is simple: separate ownership and control at entity level, standardise data and procedures across the group, and consolidate only for visibility and reporting. That gives treasury the speed to move fiat and stablecoins while preserving defensible legal, accounting and audit boundaries.