A daily close is not a report you run at 6:00 p.m. It is the operational point at which an exchange confirms that every asset movement, customer balance, cash drawer, bank transfer, and trading result is supported by the ledger. Knowing how to close daily books consistently protects margins, exposes shortages early, and gives management a number they can rely on before the next trading day begins.
For crypto and multi-asset exchanges, the process must cover more than fiat receipts and payments. Digital wallets, stablecoins, precious metals, remittances, branch cash, bank accounts, and employee activity can all affect the same day’s financial position. A strong close turns those moving parts into one controlled, reviewable record.
Define the daily close before transactions begin
The best daily closes are designed before the first customer transaction is processed. Set a clear business-date cutoff, identify the teams responsible for each reconciliation, and define which reports must be reviewed before the day can be locked. Without these rules, each branch or cashier may close at a different point, creating timing differences that look like accounting errors.
Your cutoff should reflect actual operations. An exchange that trades around the clock may use a fixed UTC cutoff for global reporting, while a branch-based operation may need local branch cutoffs for cash accountability. Either approach can work. What matters is that every transaction is assigned to one business date, and late postings are visible as exceptions rather than silently changing yesterday’s numbers.
A daily close policy should also state who can post adjustments after close, who can approve them, and how the adjustment is documented. Reopening a closed day may be necessary when a bank reversal or blockchain confirmation arrives late. It should never happen without an audit trail.
Capture every movement in the right ledger
Daily books can only be as accurate as the transaction records feeding them. Each customer trade, fee, spread result, deposit, withdrawal, transfer, expense, and counterparty settlement must create the correct dual-entry accounting impact. Manual journals can resolve limited exceptions, but they are a poor foundation for high-volume exchange operations.
Review transactions that commonly create incomplete or duplicated entries: canceled trades, partial fills, failed payouts, internal wallet transfers, chargebacks, cash corrections, and transactions entered by multiple staff members. These items often explain why an operational total differs from the general ledger.
Asset classification matters just as much. Do not treat all holdings as a single balance merely because they appear on one dashboard. BTC, USDT, USD cash, bank-held USD, gold inventory, and oil positions require separate asset-level records. Their valuation methods, settlement timing, and custody evidence may differ, even when they are part of one exchange operation.
Reconcile balances before you close daily books
The central task in how to close daily books is reconciliation. You are proving that the ledger agrees with independent evidence, not simply confirming that totals look reasonable.
Start with physical and bank-based fiat. Count each cashier drawer, verify branch cash on hand, and compare the results with expected cash balances. Review bank statements, payment processor activity, incoming wires, outgoing remittances, and pending transfers. A transfer initiated today but settled tomorrow should be recorded according to your accounting policy and clearly marked as pending.
Then reconcile digital assets. Compare each wallet’s on-chain or custodian balance with the corresponding ledger account. Separate hot wallets, cold wallets, treasury wallets, customer custody wallets, and operational wallets. Internal transfers can cause false discrepancies when the sending wallet is reduced but the receiving wallet is not recorded correctly, so confirm both sides of every transfer.
For gold, oil, or other non-cash assets, reconcile the accounting balance to custody records, warehouse statements, supplier confirmations, or inventory logs. The evidence varies by asset, but the standard does not: the closing ledger must be supported by a verifiable external or operational record.
When a difference appears, do not force the balance to match with a broad adjustment. Investigate the source. It may be a missing fee entry, an incorrect exchange rate, an unposted withdrawal, a duplicate trade, a cashier shortage, or a timing difference. A documented exception is safer than an unexplained journal entry.
Verify rates, revenue, and daily P&L
A balanced ledger is necessary, but it does not automatically produce accurate profitability. Exchange operators need to verify that conversion rates, trade prices, commissions, spreads, and realized gains or losses were applied according to policy.
Review daily P&L by asset, branch, counterparty, and business line where applicable. A sudden increase in revenue can be a strong trading day, but it can also signal a rate configuration issue. A negative margin may reflect market movement, yet it may also point to an incorrectly priced transaction or a fee that was waived without authorization.
Use an approved pricing source and a consistent valuation timestamp for assets that must be marked to market. This is particularly important when digital asset prices move quickly near the daily cutoff. If rates are corrected after close, preserve both the original valuation and the approved correction so reviewers can understand the change.
Review exceptions and employee activity
Daily close is a control process, not only an accounting process. Finance leaders should review exception reports alongside the core reconciliations. Focus on unusual transactions, manual journal entries, voids, reversals, high-value payouts, negative balances, rate overrides, and transactions posted after the designated cutoff.
Employee activity should be attributable to a named user with an appropriate role. Cashiers may need to create transactions, branch managers may need to approve cash counts, and finance teams may need to post controlled adjustments. Those responsibilities should not be blurred by shared logins or unrestricted access.
Segregation of duties depends on team size. A smaller exchange may not be able to assign a separate person to every step, but it can still require secondary approval for high-risk activities. The key is to make responsibility visible: who entered the transaction, who reviewed the discrepancy, who approved the adjustment, and when each action occurred.
Approve, lock, and preserve the close package
Once reconciliations and exceptions are resolved or documented, generate the closing package. At a minimum, it should include the trial balance, asset and liability balances, customer balance reports where relevant, reconciliation evidence, daily P&L, exception logs, and approved adjustments.
The reviewer should not merely sign off on the package. They should compare key balances with the prior day and ask practical questions. Why did wallet inventory decline? Why is a branch cash balance higher than expected? Why did fee income change? Why are pending bank transfers accumulating? This comparison catches operational issues that a single-day reconciliation may miss.
After approval, lock the business date. Locking does not mean pretending the day can never change. It means any later correction is posted through a controlled process with a timestamp, user record, explanation, and approval. That discipline protects audit readiness and prevents yesterday’s financial position from changing without management awareness.
Build the process into one operating system
Spreadsheets can work for a low-volume operation with one cashier and a few assets. They become fragile when multiple branches, wallets, currencies, and users are involved. Version conflicts, delayed updates, and manual formulas create a close that depends on individual effort instead of defined controls.
A specialized exchange accounting platform such as Siferex centralizes multi-asset records, automated dual-entry accounting, real-time P&L, user permissions, and daily operational reporting in one secure platform. That reduces the need to assemble evidence from disconnected tools and makes it easier to identify an exception before it becomes a month-end problem.
Automation should not remove review. It should remove repetitive data handling so finance and operations teams can focus on the decisions that require judgment. The right workflow lets users reconcile quickly, route exceptions to the right approver, preserve the evidence, and close with confidence.
Make daily close a management habit
A reliable close should be fast enough to happen every day and detailed enough to stand up to scrutiny. Track how long each branch or team takes to close, how many exceptions recur, how often late adjustments are posted, and where reconciliation breaks down. Those measures show whether the process is improving or merely being completed.
The practical goal is simple: begin each new business day with confirmed balances, visible risks, and a ledger your team trusts. When daily books are closed with discipline, the exchange gains more than clean records. It gains control when market conditions, transaction volumes, and customer expectations are moving fastest.