Crypto Accounting for Business: Records You Can Reconcile

What should you keep for a crypto sale?

You need a record someone else can follow. Start with the order reference, the agreed terms, the invoice or payment request, the coin and network, and the company wallet or account the payment should go to. Add the payment reference and evidence of its status.

The parcel record matters too, so a reviewer can connect the payment to the goods supplied, an open order or a later return. Our Bitcoin acceptance guide covers what to decide before you release goods against a payment.

For UK limited companies, GOV.UK's guidance (read on 18 October 2026) calls for records of receipts, spending, assets, debts, stock, and goods bought and sold, with supporting documents. It also keeps company finances apart from the owners' own.^[1] So keep the business purpose, and the fact that the funds are the company's, clear when a director helps manage a wallet. This is general information, not legal advice.

Any correction goes alongside the original record, with the reason for the change and who approved it. That way a later customer return traces back to the existing order, and the payment history that first supported the sale stays intact.

Which accounting rules apply to your business?

Which rules apply depends on your company, your reporting basis, the period and how you hold the assets. Work those facts out with your accountant before you copy an online crypto accounting method. The UK Endorsement Board describes its role as deciding which international accounting standards are adopted for UK use, so a standard published internationally doesn't by itself tell you which text applies to your company.^[2]

The example below assumes UK-adopted international accounting standards for a made-up reporting period. That says nothing about whether a real private company must or may use them, so ask your adviser which framework and requirements apply before you prepare accounts.

The IFRS Interpretations Committee's June 2019 decision covers a narrow group: a cryptographically secured digital currency on a distributed ledger, with no issuer and no contract between the holder and another party. For that group, it points to IAS 2 when holdings are for sale in the ordinary course of business and IAS 38 otherwise.^[3]

A balance held with a payment service may be a claim against that service instead. A token backed by an issuer can raise contract questions the decision leaves out. Our USDT and USDC comparison shows why the particular asset and setup matter. A token's name or how a wallet displays it won't tell you how it's classified.

Give your accountant a plain description of what the business holds, why, who can spend it and what restricts access. They need that to work out how to record, measure and disclose it.

When does the payment become a sale in the books?

That depends on your accounting policy and the commercial facts, not just a timestamp. A customer ordering, an invoice, a confirmed payment and goods being handed over each answer a different question.

The IFRS Foundation's revenue overview ties recognition to transferring the promised goods or services and the customer obtaining control. It doesn't make blockchain confirmation a universal revenue trigger.^[4]

1. 
   01

   Collect the evidence

   Gather the terms, orders, payment requests, wallet records, delivery records, costs and customer emails. Hold on to the source files, and note anything missing.

2. 
   02

   Match the sale and payment

   Connect the coin, network, receipt and who controls the wallet to the order. Record token units and their accounting-currency values on their own lines, each with its evidence.

3. 
   03

   Reconcile what happened later

   Match wallet movements, costs, conversions, returns and period-end differences. Give every open item an owner instead of forcing a balancing label.

4. 
   04

   Settle the policy questions

   Ask your accountant to write down the accounting, valuation, tax and reporting decisions. Find out what more evidence they need before you close the period.

How do you match an invoice to a wallet receipt?

Each payment you receive should match a specific request, using the destination, coin, network, token units and transaction evidence. A buyer saying they've paid is where you start looking, not a finished match. The Bitcoin developer guide tells a broadcast transaction apart from a verified payment and describes linking payment requests to receiving addresses.^[9]

Follow the confirmation and exception rules of whoever runs your checkout. If a payment is short, late, too large, a duplicate or on the wrong network, sort that out before the books look settled. The gateway workflow guide walks through those stages.

Each receipt needs its transaction identifier kept with it. A Bitcoin transaction can have several outputs, so its total movement may not be your customer's payment to the company.^[11]

If another message about a payment arrives, compare it with what you've already recorded before logging a second receipt. When a transaction is replaced or a reference is corrected, keep the link so a reviewer can see why the identifier changed and doesn't find a second sale.

Which value should you record in pounds?

Record the token units and the accounting-currency value side by side, along with what the valuation is for, the method, the source, and the time and time zone it applies to. A checkout quote, a later market price and a completed conversion are different pieces of evidence.

The IFRS Foundation describes functional currency through the business's economic environment, and its IAS 21 overview treats functional and presentation currencies as two different things.^[5] Our example assumes GBP for both. Switching a software display to pounds doesn't decide that for a real company.

For UK tax calculations involving business exchange tokens, HMRC's CRYPTO40100 discusses converting at the time of the transaction, using a consistent valuation method and keeping records of it, alongside the relevant accountancy and legal adjustments. We read that guidance on 18 October 2026.^[6] It doesn't make every dashboard price an acceptable valuation, or settle every financial-reporting measurement.

Today's price isn't the whole history, so your accountant will want evidence for the original sale, the asset received, any later disposal and what's left at period end. If you change a valuation method, keep the earlier price records with the reason and who approved it.

How do fees, transfers and later conversions fit together?

Three figures need to stay distinct: the gross sale, any charges you can evidence, and the amount that arrived. For each charge, note who incurred it, how it was paid and what record supports it. Don't assume a customer's sending cost is the company's expense, or that a missing amount was a network charge.

Bitcoin's transaction documentation separates outputs returned as change from payments to another recipient, and describes the network fee on its own.^[11] When you review a company transfer, find the destination and any change coming back before you label the movement. Token units spent on costs also need their own purpose and valuation evidence.

You also need to know who controls both ends. When you move funds between the same company's wallets, match the outgoing and incoming records, confirm both belong to the company and note any cost before calling it an internal transfer. A change in control or ownership needs attention even when the software has already filled in a convenient category.

A later conversion or disposal needs its own record, linked to the original: what left, what you received, who the other party was, the costs and the timing. If another national currency is involved, ask your accountant to split any foreign-exchange effect from changes in the crypto asset's value, because not every price difference is the same kind of gain or loss.

How you receive payment changes this job. A crypto payment gateway can bring in a contractual claim or a conversion step, while receiving straight into a wallet leaves a different set of records. Neither one puts cash in your bank by itself.

How should customer returns stay linked to the sale?

Treat what the customer is owed, its value, the funding, the approval and the customer receiving the money as five milestones. Start from the lawful return policy that applies and the circumstances of the case. The ecommerce guide explains how a returned parcel, a refund label and money returned differ in practice.

First, work out what the customer is owed. Before you promise a token quantity or deduct a charge, work out the agreed return value and its currency under the policy that applies, with proper advice. Then write down the basis and the time you used to translate that value into the coin the customer will receive.

Use a destination address the customer has confirmed for themselves, suitable for the coin and network. The Bitcoin developer guide warns that if you infer the destination from the original sending transaction, you can send the return somewhere the customer doesn't control.^[9]

BTCPay's refund documentation shows the same kind of staging: a customer claim, approval, signing and broadcast come first, and the refund counts as complete on-chain only after confirmation.^[14] That describes the software, not the hypothetical company's setup or a completed real return.

What should you check at period end?

Reconcile your holdings and obligations to the evidence, and leave open accounting questions visible. That means matching opening records, receipts, outgoing movements, costs and the token units still held, and reviewing outstanding orders, returns and movements still in progress alongside them.

Seeing a wallet isn't the same as being able to spend from it: Bitcoin's wallet guide describes receiving, monitoring and signing as functions that can be split up.^[10] A read-only view lets whoever does your books investigate without being able to spend, but it doesn't prove the company owns the wallet or give you full evidence of control.

Look for missing history and unexplained access limits too. BTCPay's wallet documentation, for instance, describes missing earlier transactions after importing a previously used wallet, and settings that affect what the wallet shows.^[12] So find out what an export covers before assuming a displayed balance is complete.

Your accountant can tell you which valuation, impairment, disclosure and subsequent-event questions remain under your framework. If access is restricted, record the notice, the affected asset or claim and its current status; a balance still showing on screen says nothing about whether it's available or recoverable. The BTCPay review explains how wallet and server setups change the evidence you need.

Are accounting records the same as tax and VAT records?

They overlap, but doing one doesn't do the others. HMRC's business-income guidance, as we read it on 18 October 2026, discusses exchange tokens received from customers or used to pay suppliers as part of trading profits, and bases the tax result on the holder's activities.^[7] Ask your tax adviser how the events and your financial accounts feed into the calculation, and don't assume one capital or revenue result for everyone.

HMRC's VAT guidance says goods and services sold for exchange tokens stay subject to the normal VAT rules, with the taxable supply valued in sterling at the transaction point. Supplying the token itself is treated differently.^[8] None of this settles the example company's registration position, product rate, tax point or reporting duties.

Your adviser will need records of the sale, later token movements and returns. Before you change software, check the reporting and retention rules, including any reason the old records must stay available. A wallet report isn't tax clearance, and nor is any supposed crypto exemption.

Can software do the reconciliation for you?

Software can organise and match records, but you still have to find out what it covers and how it reads things. BTCPay's reporting documentation draws a useful line: wallet-report rows describe on-chain transactions, while payment-report rows describe accounted invoice payments.^[13] Import both without understanding how they relate and you can count the same event twice.

Before you buy, ask the vendor for an export specification covering the fields, token denominations, time zones, date coverage, corrections, returns and duplicate handling, plus how you can get back to the source documents and what you can still reach when the subscription ends. We haven't tested an accounting package, export or live integration.

The WooCommerce and Shopify guides cover how each platform handles orders and returns, which differ. Go by your own installed setup rather than assuming a status means the same thing on another platform. When you pick a provider, include the access and exports your bookkeeper needs in your processor selection.

Limit who receives customer data and wallet-history access. The ICO's data-minimisation guidance, read on 18 October 2026, says personal information should be adequate, relevant and limited to what you need it for, and it flags that the guidance is under review.^[15] Work out what access is proportionate and how long you'll keep things, instead of sharing everything by default.

This guide rests on public documents and a hypothetical workflow, so it doesn't certify anyone's books, software, eligibility or completed payments. Our methodology explains the limits of that kind of evidence.

Crypto accounting FAQ