Crypto Month-End Close: An 8-Step Checklist for Finance Teams

Month-end close for a crypto-heavy company is not the same close as a traditional one. You have more variables, less reliable data, and no standard playbook that most junior accountants have seen. The close runs longer and breaks in new ways.

This is the 8-step process finance teams use when they have to close books with crypto on the balance sheet. It works for a single treasury wallet or a hundred operational wallets. The order matters. Skipping steps will cost you time on the back end.

Why crypto close is different

A traditional month-end close is mostly about matching bank statements, AR and AP aging, and accrual true-ups. A crypto close adds:

• Wallet balances that move every block, not every day
• Exchange data that is incomplete without API pulls
• Cost basis math that changes with every trade
• Tokens that do not have a clean USD market price
• DeFi positions that do not fit a standard chart of accounts category
• Transfers between owned wallets that look like sales if you do not tag them

The result is that a two-day close in a traditional SMB becomes a five- to ten-day close if crypto activity is not tracked throughout the month. A subledger running in parallel with your books flips that back to two days.

Step 1: Freeze the balance snapshot

Pull every wallet and exchange balance at 23:59 UTC on the last day of the month. This has to happen fast because the balances keep moving. Custodial exchanges will let you export an end-of-day balance through the API. On-chain wallets require pulling via block explorer or a node. Tag the snapshot with the exact timestamp so you can defend it to an auditor.

For Ethereum and Solana wallets, record the block height at UTC midnight, not the balance at the time your script ran. That distinction matters when an auditor asks you to reproduce the number six months later.

Step 2: Reconcile transaction count

Count every transaction on every wallet and match against your subledger or spreadsheet. A number mismatch means a transaction was missed or double-counted. A balance match with a transaction count mismatch is a bigger red flag than a balance mismatch. It means your books look right by accident.

Common gaps:

• Internal transfers between owned wallets (often mislabeled as sales)
• Failed transactions with gas fees still charged
• Airdrops the wallet received passively
• Staking rewards that accrued but did not show as transactions
• Contract interactions with no token movement (approvals, cancels)

Our DeFi reconciliation checklist covers the DeFi-specific version of this step.

Step 3: Classify every transaction

Each transaction needs a category:

• Purchase (token acquired, cost basis established)
• Sale (token disposed, realized gain or loss calculated)
• Transfer (between owned wallets, no P&L impact)
• Income (staking, airdrops, liquidity rewards)
• Expense (gas fees, service payments in crypto)
• Swap (one token exchanged for another, treated as sale plus purchase)
• DeFi position (liquidity provided, lent, staked)

Transfers between wallets you control should NOT create a realized gain or loss. Many spreadsheet systems mishandle this. If you see unexpected gains in a month with no selling activity, transfers are the likely cause.

Step 4: Apply cost basis

Pick your method once and stay with it. FIFO and HIFO are the common choices. HIFO gives the lowest tax bill in most up-market conditions. FIFO gives the simplest audit trail. Our HIFO vs FIFO guide covers the tradeoffs.

Apply the method at the wallet level, not the aggregate level. The IRS allows per-wallet tracking starting with the 2025 tax year and many state rules now require it. Aggregating across wallets creates reconciliation issues when one wallet is sold, audited, or transferred to another entity.

Step 5: Price unpriced assets

Some tokens do not have reliable market data. A wallet holding a governance token with $50k daily volume on one DEX needs a pricing rule. Pick a source per token and document it:

• CoinGecko for mid-cap tokens with multi-exchange data
• CoinMarketCap as a backup
• On-chain DEX price (Uniswap, Raydium) for low-liquidity tokens, with a note on slippage
• Cost basis value for tokens with no market (internal governance tokens, airdrops to closed wallets)

Document the source for each token in your accounting policy. Auditors will ask. Consistency across months matters more than which source you picked, as long as it is defensible.

Step 6: Record gains, losses, and revaluation

Once classifications and basis are set, calculate:

• Realized gain or loss on every sale and swap
• Unrealized gain or loss on remaining positions (if applying ASC 350-60 fair value)
• Income recognition at fair value on the date received (staking, airdrops)
• Fee expense from gas and exchange fees

For companies applying ASC 350-60 (fair value through net income for crypto assets), revaluation runs every month. See our ASC 350-60 guide for the mechanics and a worked example.

Step 7: Post journal entries

Everything above has to land in your general ledger. The typical entries for a month with trading activity look like:

• Dr. Cash / Cr. Crypto Asset for sale proceeds
• Dr. Realized Loss or Cr. Realized Gain for P&L from sales
• Dr. Crypto Asset / Cr. Cash for purchases
• Dr. Unrealized Loss or Cr. Unrealized Gain for fair value adjustments
• Dr. Gas Expense / Cr. Crypto Asset for fees paid in crypto
• Dr. Crypto Asset / Cr. Staking Income for rewards received

A crypto subledger posts these automatically to Xero or QuickBooks with the transaction-level detail preserved. Manual entry at volume is the single biggest source of close errors we see in client books.

Step 8: Review, document, and sign off

The final step is the one most teams rush. Before you close the month:

• Run a trial balance and match every crypto-related line to the subledger
• Check that ending wallet balances tie to GL balances for each token
• Review unusual items: large losses, new tokens, first-time DeFi positions
• Document valuation sources and cost basis method in the close memo
• Get sign-off by a senior reviewer with date and scope

Auditors trace back to this document in year one of any crypto audit. Make it complete the first time.

Common close blockers

Missing API keys. A wallet someone forgot to add halfway through the quarter. Add every wallet to the subledger at creation time.

Token price gaps. A small-cap your team started trading with no configured pricing source. Set up pricing at first transaction, not at close.

Transfer mislabels. The most common cause of phantom gains or losses. Tag at the time of transfer.

DeFi position drift. Liquidity pool shares that changed value due to impermanent loss, not trading. Classify these monthly.

Lost wallets or keys. Account for every asset, including the ones you cannot move. They still sit on the balance sheet until written off with proper documentation.

FAQ

Q: How long should a crypto month-end close take? With a subledger running through the month, two to three business days. Without one, five to ten. The variable is how much reconciliation you push to the end versus running continuously.

Q: Do I need to revalue crypto at month-end? Under ASC 350-60 (effective for fiscal years beginning after December 15, 2024), yes. Fair value through net income every reporting period. Before ASC 350-60, cost-less-impairment was the rule and revaluation was only downward.

Q: How do I handle wallets across multiple entities? Each wallet belongs to one legal entity. Transfers between entities are intercompany transactions with full double-entry treatment in both sets of books.

Q: What about staking rewards received mid-month? Income at fair value on the receipt date. Track the date, the USD value at that block time, and the quantity. Apply the company's revenue recognition policy for the category (ordinary income in most cases).

Q: Should I close crypto first or last? First. Crypto activity often feeds into other accounts (AP for vendors paid in crypto, AR for USDC invoices). Close crypto first so downstream accounts have the right inputs. Our invoice closure guide covers the downstream side.

Q: Can my GL software handle crypto without a subledger? Yes, with heavy manual work. Xero and QuickBooks have no native crypto accounting. Every journal entry comes from a spreadsheet or a subledger. At meaningful volume, a subledger pays for itself in saved hours within two months.

Bottom line

Crypto month-end close is a discipline problem, not a math problem. Teams that run a subledger continuously through the month close in two days. Teams that batch reconcile at month-end close in ten. Everything in the 8-step process above is more valuable when it runs daily rather than monthly. See how Breezing handles it across 40+ chains on pricing.