Multiple Wallets, Multiple Blockchains: How Do You Build a Usable Stablecoin Reconciliation?
A company may use several wallets and several blockchains while still needing one financial view of its stablecoin position. That is where reconciliation becomes difficult.
Adding up visible wallet balances is not enough. The company must be able to explain how each on-chain movement connects to an economic transaction and ultimately to the accounting records.
1. Define the reconciliation scope first
Before reconciling anything, identify which addresses, wallets, platform accounts and networks actually belong to the scope. A missing wallet creates a difference; an unrelated wallet can create a false position.
A practical starting point is an inventory covering the wallet or account, responsible entity, network, asset, business use and date of inclusion.
2. Reconcile by wallet and network
The same stablecoin may circulate across several networks. Identical ticker symbols therefore do not necessarily represent the same infrastructure or transaction history.
Keep at least the asset, network, address or account and transaction identifier. This level of detail prevents technically different positions from being mixed.
3. Reconstruct movements before consolidating
For each asset, wallet and network: OPENING BALANCE + INFLOWS − OUTFLOWS = THEORETICAL CLOSING BALANCE. Outflows include fees charged in that asset; do not deduct the same fee twice.
The equation only becomes useful once movements are classified. An inflow may be a customer receipt, an internal transfer or the output of a bridge. An outflow may be a supplier payment, another company wallet or a fee.
4. Neutralise internal transfers
A transfer between two company wallets creates an outflow in one wallet register and an inflow in the other. These are two movements to match, not necessarily two blockchain transactions. The internal transfer remains in each wallet's trail and is excluded from consolidated external inflows and outflows.
The reconciliation should pair the outgoing and incoming legs and identify them as one internal transfer.
5. Treat cross-chain activity separately
Moving from one network to another may involve several transactions, a bridge or service provider, delays and sometimes an intermediate asset. Reconstruct the full chain instead of reconciling each hash in isolation.
The goal is to connect several technical traces to one economic intention and document any quantity differences.
Distinguish a transfer within one network from a cross-chain process. For example, Circle's CCTP transfers native USDC through burn-and-mint. Retain source and destination transaction references, the protocol reference or attestation where relevant, completion status and any amount still in transit at the cut-off date.
6. Isolate fees
Identify network fees, platform fees and other charges, including the asset used to pay them and the operation concerned. On Ethereum, network gas is paid in ETH: it must not automatically be deducted from a USDC or EURC token balance. A fee charged directly in stablecoins does reduce the position in that asset.
7. Consolidate only after neutralisation
Build the consolidated position by asset after matching internal transfers, cross-chain activity and fees. Quantities in different stablecoins or fee assets remain separate. A single financial view then requires a documented valuation method and a common reporting currency.
A reproducible reconciliation register should retain the following fields:
Date and cut-off — event date and reporting period.
Asset — token and contract address where applicable.
Network — blockchain used.
Source wallet — address or platform account.
Destination wallet — address or platform account.
Technical reference — hash and event or movement identifier where needed.
Quantity — amount and unit.
Classification — receipt, payment, internal transfer, cross-chain movement or fee.
Economic reference — invoice, contract or approval.
Accounting reference — posting and documented valuation.
Illustrative example: an internal transfer changes wallets, not the total
Fictitious case, in units of a single stablecoin, with all transfers completed at the cut-off date: opening consolidated balance 10,000; customer receipts 2,000; supplier payments 1,500. A transfer of 3,000 between two company wallets creates a 3,000 outflow and a 3,000 inflow that cancel in consolidation.
Closing consolidated balance: 10,000 + 2,000 − 1,500 = 10,500 units. If 5 units of fees are charged in the same stablecoin and have not already been included in payments, the balance is 10,495. Network fees paid in another asset are reconciled separately.
8. Reconcile the consolidated position to accounting
Once the on-chain position has been reconstructed, compare it with the accounting records. A difference should not simply be adjusted; it should be explained.
Potential causes include an unrecorded transaction, a misclassified internal transfer, unrecorded fees, a cut-off issue, a wallet outside the perimeter or a quantity difference caused by a technical operation.
9. Preserve evidence that allows the reconciliation to be reproduced
A usable reconciliation is more than a table that balances. Another person should be able to understand the scope, retrieve the transactions, follow internal transfers, identify the economic documents and reach the accounting entries.
The method can be summarised as: SCOPE → WALLET/NETWORK → MOVEMENTS → INTERNAL TRANSFERS → CROSS-CHAIN → FEES → CONSOLIDATION → ACCOUNTING → DIFFERENCES.
Turning on-chain data into financial evidence
A blockchain explorer can retrieve a transaction. A usable reconciliation should allow another person to understand why that transaction exists, how it fits with the other movements and how the complete trail connects to accounting.
Further reading
Sources
Technical documentation consulted on 5 October 2026. The reconciliation sequence and register above are BECTRA methodological recommendations.
Comments