A cash drawer can balance while the exchange is still financially wrong. A customer’s crypto balance may be posted as revenue, a bank transfer may sit in suspense for days, or an employee settlement may never reach the correct ledger. These are not small bookkeeping issues. They affect liquidity, customer obligations, daily profit and loss, and the confidence of management and auditors.
This guide to exchange chart accounts explains how to build an accounting structure that reflects the reality of crypto, fiat, and multi-asset exchange operations. The objective is not to create more accounts. It is to create a controlled system where every transaction has a clear financial destination, every asset is traceable, and every daily report can be trusted.
What an exchange chart of accounts must do
A chart of accounts is the organized list of ledgers used to record financial activity. For a general retail business, it may be enough to separate cash, sales, expenses, and tax. An exchange needs more precision because it holds customer funds, manages multiple asset inventories, processes settlements through several channels, and often operates across branches, currencies, and counterparties.
A useful exchange chart of accounts must distinguish between company-owned assets and customer liabilities at all times. It must also show where funds are held, who controls them, what stage of settlement they are in, and whether a balance is available, restricted, pending, or under investigation.
When that structure is missing, teams compensate with spreadsheets, manual journals, and informal reconciliation notes. Those workarounds become difficult to control as transaction volume rises. They also make real-time P&L reporting unreliable because the underlying balances are not consistently classified.
Start with the accounting equation, not account names
The strongest charts are designed around the transaction lifecycle. Before creating accounts, document how value moves through the business: customer deposit, trade or exchange, fee collection, payout, bank settlement, treasury transfer, and reconciliation.
Every event should produce balanced dual-entry postings. If a customer deposits USD into a bank account, the business receives an asset, but it also owes the customer that value. The bank balance belongs in an asset account; the customer balance belongs in a liability account. Treating the deposit as revenue would immediately overstate income and hide the company’s obligation.
This principle applies across all supported assets. Bitcoin held in a company wallet, physical cash in a branch vault, gold inventory, and oil positions may all be assets. Customer balances associated with those holdings remain liabilities until the customer trades, withdraws, or otherwise settles their position.
Account names should make this distinction obvious. “BTC Wallet” is too broad if it combines treasury holdings with customer-backed holdings. “Customer BTC Liability,” “Company BTC Treasury,” and “BTC Settlement Receivable” are more useful because they describe both ownership and purpose.
Build the core account groups
Most exchanges need a numbered structure that keeps reporting consistent as operations expand. The exact numbering can vary, but the account categories should be stable.
Assets: where the exchange holds value
Asset accounts record resources controlled by the business. For an exchange, these may include operating bank accounts, branch cash, cash in transit, crypto wallets, stablecoin wallets, payment processor balances, receivables from counterparties, and company treasury positions.
Separate accounts by asset type and custody location when the distinction matters operationally. A USD balance at Bank A should not be blended with USD at Bank B if each balance has a different settlement risk, access process, or reconciliation owner. The same logic applies to hot wallets, cold wallets, and third-party custodians.
Use clearing accounts for funds that have moved economically but are not yet fully settled. For example, an outgoing bank wire can move from available bank cash to “Bank Transfers Pending” until confirmation arrives. This prevents the same funds from appearing available in two places and gives operations a visible queue for follow-up.
Liabilities: what the exchange owes
Customer balances are usually the most important liability group. Create separate liability accounts for each material asset or currency, such as customer USD balances, customer EUR balances, customer BTC balances, and customer USDT balances.
Other liabilities may include accounts payable, taxes payable, employee expense advances, partner commissions payable, or funds received pending identification. The final category is particularly valuable for deposits that arrive without a usable reference. Rather than forcing them into a customer account, hold them in an identified suspense liability until operations can match the payer and apply the funds correctly.
A suspense account is not a place to leave uncertainty permanently. It is a controlled exception queue. Assign an owner, define an aging threshold, and require documented resolution.
Equity: capital and retained results
Equity accounts capture owner contributions, retained earnings, distributions, and other capital movements. Keep them separate from operating income and expenses. When an owner funds a new branch or adds liquidity, the entry should be visible as capital, not hidden within revenue.
This separation gives finance leaders a clearer view of whether growth is being funded by profitable operations, outside capital, or short-term obligations.
Revenue: what the exchange has earned
Revenue accounts should record earned fees, not exchanged principal. Common examples include trading fees, spread income, withdrawal fees, remittance fees, custody fees, and service charges.
The right level of detail depends on management needs. A startup may only need trading fees and withdrawal fees. A multi-branch operation may need revenue by product, branch, currency corridor, or counterparty. Do not create dozens of accounts simply because a report might be useful someday. Use dimensions, tags, or reporting fields when your accounting system supports them, and reserve separate ledger accounts for distinctions that require independent control or financial statement treatment.
Expenses: what it costs to operate
Expenses may include payroll, rent, security, banking charges, blockchain network fees, liquidity provider costs, software, compliance services, marketing, depreciation, and foreign exchange losses.
Be precise with costs that are directly tied to customer transactions. Network fees, payment processor charges, and remittance costs often need their own accounts because they materially affect margin. If they are mixed into general operating expense, management cannot see the true profitability of each service line.
Design accounts around control points
A practical guide to exchange chart accounts is incomplete without operational controls. The chart should support the people who reconcile balances, approve adjustments, monitor cashier activity, and investigate exceptions.
Create dedicated accounts for situations that require review: cash over and short, unallocated deposits, pending withdrawals, inter-branch transfers, counterparty settlements, and wallet reconciliation differences. These accounts should not normalize errors. They should expose them quickly.
For example, a branch cash transfer should not be recorded as an expense when cash leaves one location. It should move into an inter-branch transit account and clear only when the receiving branch confirms delivery. The transit balance then becomes a daily operational control: any aged amount demands an explanation.
Role-based permissions matter as much as account design. Cashiers may need to initiate or record transactions, while finance staff approve journal adjustments and administrators control account mapping. No single user should be able to create, approve, and conceal a material adjustment without review.
Keep asset, currency, and location separate
Multi-asset exchanges often make one of two mistakes. They either create one account for every possible combination of asset, branch, customer type, and transaction channel, or they combine everything into broad balances that cannot be reconciled.
The better approach is controlled granularity. Separate the general ledger by factors that change financial ownership, custody, settlement status, or regulatory reporting. Use operational dimensions for branch, employee, customer segment, or product channel when those details are needed for analysis but do not require a distinct balance sheet account.
For instance, separate customer USDT liabilities from customer BTC liabilities because they are different obligations. Separate cash in Branch A from cash in Branch B if each branch performs its own close. But you may track the responsible cashier through transaction-level reporting rather than creating a ledger account for every employee.
Establish daily reconciliation rules before go-live
A chart of accounts only works when balances are verified against the real world. Every material account should have a reconciliation source and a named owner. Bank accounts reconcile to bank statements or feeds. Wallet accounts reconcile to wallet balances. Customer liabilities reconcile to the customer subledger. Cash accounts reconcile to physical counts. Counterparty receivables and payables reconcile to settlement confirmations.
Set a daily close process that identifies unmatched items, aging exceptions, unusual manual journals, negative balances, and differences between customer liabilities and safeguarded assets. The process should produce evidence, not just a verbal confirmation that everything looks right.
Automation reduces risk here, but it does not remove accountability. Automated dual-entry accounting can post transactions consistently at scale, while finance teams focus on the exceptions that require judgment. That is a better use of skilled operators than rebuilding the ledger in Excel each evening.
Make migration a controlled accounting project
When moving from spreadsheets or generic accounting software, do not copy every historical inconsistency into the new chart. Map existing balances to the new structure, reconcile opening balances by asset and liability class, and document any adjustments required to correct prior classifications.
Test a representative set of transactions before full migration: fiat deposit, crypto deposit, customer trade, fee collection, withdrawal, bank wire, branch cash movement, and counterparty settlement. If each scenario posts correctly and reconciles to the expected account, the chart is ready for operational use.
Siferex gives exchange teams one secure accounting operating system for this work, with automated dual-entry postings, multi-asset records, role-based access, and real-time reporting in a single platform.
The right chart of accounts gives every dollar, token, bar, and settlement a defined place to land. Build it around ownership, custody, and daily reconciliation, and your finance team can spend less time explaining balances and more time controlling the business.