SME Fintech TaskforceFinance research for smaller businessesFINANCE / RESEARCH

SMALL BUSINESS FINANCE

Crypto taxes in 2026: how to keep records of recurring payouts

For UK miners, HMRC says the tax treatment of mining rewards depends on whether the activity amounts to a trade; where it does not, the sterling value of tokens at receipt is treated as miscellaneous income. A recurring pool payout therefore needs a record of the reward, its date and quantity, its GBP value, and the later wallet transfer. The EMCD Mining Pool publishes EMCD’s Bitcoin pool terms; those terms help identify reward and payout events in the account history.

Explore the finance guide

A record trail for recurring Bitcoin mining rewards

Use one linked record for each event in the asset’s path. The reward, sterling valuation, transfer, disposal and operating cost support different entries in the books.

A record trail for recurring Bitcoin mining rewards
EventRecord fieldsEvidence to retainWhat the entry establishes
Pool reward creditAsset, quantity, credit date, account and worker, reward method, deductionsDated pool statement or account exportWhat the pool credited for the recorded work period.
GBP valuationValuation time, source, currency pair, rate and calculationSaved price record and conversion inputsHow the sterling amount was reproduced.
Wallet payoutBroadcast time, BTC amount, destination, transaction ID, confirmationsPool payout history and wallet or explorer recordHow credited assets moved to the receiving address.
Later disposalDate, quantity, proceeds or value received, fees and destinationExchange statement, wallet export and transaction recordWhat happened to the asset after receipt.
Mining costsDate, supplier, amount, purpose and account treatmentInvoice, contract or payment recordThe operating cost and its separate accounting trail.

Map reward and payout events before classifying income

A pool reward and an on-chain payout are two records in one trail, not necessarily the same event. The pool may show accepted work, a reward credit, an available balance and a transfer after a threshold or scheduled run. The wallet then records a transaction broadcast to the network. Preserve each timestamp and the provider’s label so the books can distinguish what was credited from what left the account. EMCD’s payout guide describes its BTC threshold and usual payout window (EMCD Help Center: free mining payouts); check the account history for the event that actually occurred.

Save the time zone shown in each export. A pool may display UTC, local time or a date without a time, while a wallet explorer records a block timestamp. When a reporting period ends near midnight, those labels can place the same event on different calendar dates. Keep the original timestamp unchanged, record any converted time in a separate field, and state the conversion zone. This makes the sequence of reward, payout and confirmation readable without silently shifting an event into another day or accounting period.

For an individual miner, HMRC says whether mining is a taxable trade depends on factors including the degree of activity, organisation, risk and commerciality (HMRC Cryptoassets Manual: mining transactions). If the activity is not a trade, HMRC treats the pound-sterling value of tokens at receipt as miscellaneous income. Where it is a trade, tokens are trade receipts. These routes call for careful classification before totals are entered in a return; the existence of a mining pool statement alone does not decide which route applies.

Build a source-backed record for each pool credit

Use the pool’s own records to make a row for every credited reward or reward batch. Capture the provider, account and worker identifiers; the asset and quantity; the period covered; the date and time shown; the reward method; gross reward; deductions; net credit; and the statement or export filename. Keep a note when the interface groups several blocks or days into one line. A row should let another reviewer trace the reported amount to the source screen or downloaded statement without editorial it from memory.

If a pool export combines rewards, retain the original combined line and the period it covers. Do not split it into invented daily amounts. Where a separate provider report gives the underlying breakdown, link that report and retain the method used to reconcile its rows to the total. If the source provides no finer detail, keep the total as reported and make the missing granularity visible in the working file rather than manufacturing a precise timeline.

Record the transfer and sterling value separately

Add the wallet transfer as a linked but separate row: broadcast date, BTC amount, destination address, transaction ID, network and confirmation status. Match the transfer to the pool’s payout history, allowing for a pool fee or network-fee treatment where the provider specifies one. Do not add the transferred BTC to the reward total a second time if it represents an earlier credited balance; the two records describe reward recognition and movement of the asset, respectively.

HMRC’s public guidance says records for cryptoassets received (HMRC: records for cryptoassets received) should include the token type, date received, quantity, total holdings and sterling value; it also calls for bank statements and disposal details where relevant. For each mining receipt, store the GBP figure, the valuation timestamp, the exchange or pricing source, the currency pair and the calculation used to convert the token amount. Retain the raw source alongside the calculated value. A later reviewer should be able to repeat the conversion from those inputs.

A price quoted in dollars is not yet a sterling figure. Record the USD price and the GBP conversion separately if that is the available source, including the timestamp and both rates. Use a consistent, documented valuation method for the relevant event and keep enough precision to reproduce the reported total. If a data source revises historical observations, save the downloaded record or a dated copy of the response used for the calculation.

Keep valuation and disposal evidence reproducible

For recurring receipts, use the same documented valuation source and conversion steps where they are available, then record any exception rather than smoothing it away. Keep the source currency, quoted rate, conversion rate and resulting GBP amount in separate columns. This preserves the inputs if the reporting method is reviewed later and prevents a monthly total from concealing which individual observations were missing, delayed or corrected by the source.

The pool dashboard, wallet and bookkeeping system answer different questions. A pool statement shows the provider’s accounting for accepted work; the blockchain transaction shows a transfer; a wallet or exchange record helps identify the destination and any subsequent conversion. HMRC’s record-keeping guidance notes that exchange records may be retained only for a limited time, so download statements and transaction exports while they remain available. Keep originals read-only and make corrections in a separate working copy with a dated note.

Receiving a token and disposing of it later are separate tax events. If mining tokens have already been treated as income, HMRC says a later disposal may give rise to Capital Gains Tax on a subsequent increase in value. Preserve the quantity and GBP value recorded at receipt, then separately log each sale, exchange, gift or purchase made with the asset, including the disposal date, consideration and transaction costs. Do not overwrite the receipt valuation with the later sale price.

Separate operating costs from receipt reconciliation

Keep operating costs in their own ledger rather than subtracting them from the token’s recorded value. HMRC’s capital-gains manual says mining equipment and electricity do not count as allowable costs in respect of the tokens for CGT (HMRC Cryptoassets Manual: allowable expenses); some costs may be deductible against trading profits for Income Tax purposes. The applicable accounting follows the activity’s classification and the records for the business. Store electricity invoices, hosting charges, hardware purchases and financing costs with their dates and business purpose, then reconcile them under the appropriate accounts.

At month end, reconcile three totals without collapsing their meaning: rewards credited by the pool, transfers shown in the wallet, and token disposals or conversions. Investigate differences such as a pending balance, a payout below a wallet’s deposit threshold, a fee, a reversed transfer or a statement period crossing month end. Keep the pool statement, blockchain transaction ID, wallet export and valuation evidence together. The resulting trail supports bookkeeping and tax review while leaving the original provider records intact.

Close the period with a traceable evidence file

A compact working file can contain a reward register, a payout register, a disposal register, a GBP valuation log and a cost ledger. Give each event a stable reference and link the supporting files by that reference. Record the tax year and the date on which the file was closed. If an entry changes, preserve the old value, the replacement, the reason and the source that supports the correction; this makes the history legible when a return is reviewed months later.

Keep the registers in a format that can be exported without losing transaction IDs, full asset quantities, dates or source links. A spreadsheet summary is useful for review, but it should point back to the original provider statement, wallet export and valuation record. Use a stable file name with the period and provider, and avoid replacing an earlier export with a later download under the same name. This lets a reviewer distinguish a changed source file from a corrected bookkeeping entry.

The practical test is whether a reviewer can start with a line in the books and reach the source statement, then follow the same quantity to a wallet transaction or later disposal without counting it twice. If the pool exports do not expose the reward-credit date, retain the provider’s available account history and note which timestamp its terminology uses. Current account terms and HMRC guidance should be checked for the accounting period being reported, particularly when a provider changes its payout process.

Close the mining records for the period

  1. Save the pool statement and preserve the original reward credit and timestamp.
  2. Match each credit to a GBP valuation record with its source and conversion inputs.
  3. Link each pool payout to the wallet transaction without counting the same BTC twice.
  4. Record later disposals and operating costs in their own registers.
  5. List unresolved differences and retain the evidence needed to review them.
A mining reward ledger links pool credit, a sterling valuation and a later wallet transaction
Month-end reconciliation connects pool statements, wallet transfers, GBP values and disposal records

SME finance: common questions

Are pool rewards and Bitcoin payouts the same tax record?
They can describe different events. Record the pool reward credit and the later wallet transfer separately, then apply the correct tax treatment to the receipt under the miner’s circumstances.
What records should a UK miner keep for recurring rewards?
Keep the token type, receipt date, quantity, total holdings and GBP value, together with the pool statement, valuation evidence, wallet transaction details and any later disposal records.
Does every mining operation count as a trade for UK tax?
No. HMRC says the answer depends on factors such as the activity’s degree, organisation, risk and commerciality. The facts of the operation determine the classification.
Can electricity and mining hardware be deducted from a token’s capital gain?
HMRC says those mining costs are not allowable costs in respect of tokens for CGT. Some costs may be deductible against trading profits for Income Tax purposes, depending on the circumstances.