Are pension trustees and scheme managers confident about documenting crypto exposure and meeting HMRC requirements? Many trustees and sponsors face uncertainty when adding Bitcoin or other crypto exposures to a pension allocation because standard pension governance and HMRC record-keeping practices do not yet cover the operational specifics of cryptoassets.
This guide provides HMRC-ready templates, precise steps to document Bitcoin transactions and cost basis, spreadsheet structures for capital gains and income tax, and audit-ready workflows for reconstructing missing data. It is written for trustees, scheme administrators, in-house counsel and advisers who must demonstrate compliant record-keeping for Pension Funds & Crypto Exposure.
Key takeaways: what to know in 1 minute
- Trustees must document rationale and custody when adding crypto exposure to a pension scheme; a board resolution plus due diligence file is essential.
- HMRC treats crypto differently depending on how exposure is held (direct holding, ETP, pooled fund); tax and reporting obligations vary accordingly.
- Maintain traceable transaction ledgers with wallet addresses, transaction IDs, timestamps (UTC), fiat equivalents and cost basis for each disposal—this is critical for CGT and income tax reporting.
- Use standardised spreadsheet templates to calculate realised gains/losses (pooling rules where applicable) and to separate capital versus income events for scheme accounts.
- Reconstruction templates and audit logs enable an HMRC-ready paper trail if exchanges or custodians do not provide full export history.
Why Pension Funds & Crypto Exposure needs bespoke record-keeping
Pension schemes operate under strict governance and reporting regimes. When crypto exposure is introduced—whether via a direct holding, an Exchange Traded Product (ETP) inside a SIPP wrapper for individual members, or via pooled investment vehicles—the usual fund accounting systems and trustee minutes must be supplemented with crypto-specific documentation.
HMRC guidance on cryptoassets emphasises transaction-level detail and supporting evidence. Refer to HMRC guidance for individuals and businesses at https://www.gov.uk/guidance/tax-on-cryptoassets for the core tax position and examples. For trustees, governance documentation should demonstrate fiduciary oversight, risk assessment and custody arrangements in addition to tax-related records.
Essential record-keeping templates for HMRC reporting
These templates form the minimum evidence set trustees and administrators should use when a pension scheme has crypto exposure.
Template 1: trustee resolution and investment policy amendment
- Date of meeting, attendees, quorum.
- Purpose: approve crypto exposure, define permissible instruments (direct bitcoin, ETPs, derivatives), allocation limits.
- Due diligence checklist: counterparty assessment, custody model, insurance cover, legal opinion.
- Operational approvals: authorised signatories, dealing limits, settlement instructions.
Template 2: custody and custody reconciliation log
- Custodian name, entity ID, SLA summary.
- Wallet addresses under custody, public key fingerprints, custodian wallet reference.
- Regular reconciliation schedule and sign-off (daily/weekly/monthly as appropriate).
Template 3: transaction register (master CSV)
- Columns: Date (UTC), Timestamp, Transaction ID (txid/hash), Wallet address (from/to), Exchange name, Trade pair, Quantity (crypto units), Price per unit (fiat), Fiat amount, Fee (crypto/fiat), Counterparty details, Purpose (buy/sell/transfer/staking/reward), Cost basis, Proceeds, Realised gain/loss, Notes.
- Each row is a single on-chain transfer or exchange trade.
Template 4: cost-basis ledger and pooling tracker
- Track initial acquisition cost, fees, and pooling adjustments.
- Apply HMRC pooling rules for Bitcoin (where applicable) and clearly annotate which pooling method used.
Template 5: supporting evidence folder index
- For each transaction row, include links to evidence: exchange CSV export, signed trade ticket, wire transfer receipt, custodian statement, wallet export, Etherscan/Blockchair link.
How to document Bitcoin transactions and cost basis
Trustees and administrators must record three core elements for every transaction: the identity of the asset, the acquisition/disposal details and the monetary value in GBP at the time of the event.
Step-by-step: what to capture at acquisition
- Record the exact on-chain transaction hash (txid) and wallet address used.
- Note the acquisition timestamp in UTC and the source of the fiat conversion rate (name of exchange or market data vendor) with a permalink to the historical price if available.
- Log all fees separately (network fee and custodian/exchange fee) and whether fees were paid in crypto or fiat.
- Calculate the effective cost basis in GBP including fees.
Step-by-step: what to capture at disposal
- Capture sale timestamp, txid and counterpart address (if external transfer) or trade ID (if via exchange).
- Record gross proceeds in GBP, fees, and net proceeds.
- Compute realised gain/loss as net proceeds minus cost basis allocated to the disposed units.
- Annotate allocation method if pooling or specific identification is used.
Cost-basis methods and HMRC position
- HMRC usually expects clear evidence of how cost basis is derived. For trustees, document the allocation method (pooling or FIFO if allowed) and include worked examples in the file.
- Where ETPs are used, the ETP supplier's contract and prospectus determine whether disposals create capital gains at scheme level or income distributions.
Templates to track wallets, exchanges and transaction history
A centralised mapping between wallet addresses, exchange accounts and custodial references prevents orphaned transactions.
Wallet and account master list (H3)
- Unique ID, type (hot/cold/custodial/segregated), custodian, public address, associated exchange account ID, KYC entity, purpose (settlement, treasury, liquidity).
- Last reconciled date and reconciler initials.
Exchange mapping and CSV import guide (H3)
- For each exchange, maintain the API exporting method used (CSV format, field mapping). Keep a documented sample file and mapping table to ensure consistent imports.
- Where possible, use signed export files or notarised snapshots and store hash of each export to prove integrity.
Using spreadsheets for capital gains and income tax
Spreadsheets remain the most practical tool for trustees to show HMRC the calculations that underpin any tax position. The key is standardisation and auditability.
Spreadsheet structure: recommended tabs
- Summary: key totals, realised gains, losses, taxable income, tax codes applied, notes.
- Transaction register: raw transaction rows imported from master CSV.
- FX rates: daily GBP exchange rates with source and permalink.
- Pooling ledger: track pool units, average cost and movements.
- Reconciliations: exchange balances vs on-chain balances per date.
- Audit evidence index: links to documents and file hashes.
- Use explicit formulas (avoid manual values). Example: Realised gain = (Proceeds GBP - Fees GBP) - (Allocated cost basis GBP).
- Timestamp conversions: use UTC timestamp field and VLOOKUP / INDEX match to the FX tab for the exact day rate.
- Keep a calculation tab with step-by-step worked examples for typical scenarios.
Record-keeping templates that meet HMRC self-assessment rules
HMRC expects that records are sufficient to enable the calculation of taxable amounts and to support those figures in an enquiry. For pension schemes this means records must be scheme-level and compliant with trustee reporting.
Minimum retention and provenance
- Retain transaction-level records for the period HMRC can open enquiries (typically up to 6 years for self-assessment issues; longer for record of trustees' decisions).
- Preserve original exports from exchanges/custodians alongside hashed snapshots and a verification manifest.
- Maintain CSV/CSVX exports as primary machine-readable records and PDF snapshots for signed documents.
- Ensure the master transaction register references the exact file name and file hash for each supporting document.
Reconstructing missing data: audit-ready crypto paper trail templates
When exchanges or wallets cannot provide a complete export, a reconstruction methodology must produce a defensible audit trail.
Reconstruction process (H3)
- Obtain available partial exports and identify gaps (missing dates, missing txids).
- Use bank wire receipts, exchange trade confirmations, custodian settlement advices and on-chain block explorers to rebuild missing rows.
- Record assumptions: where prices are not available, use the mid-market rate at 12:00 UTC from a named market data provider and document the rationale.
Reconstruction template fields (H3)
- Original evidence type, source URL, retrieval timestamp, reconstructed fields, justification, reviewer sign-off.
- Keep a redline version showing original data and reconstructed additions.
Practical example: worked calculation for a disposal inside a SIPP
- Acquisition: 10 BTC purchased across three buys; total cost including fees £140,000.
- Disposal: 4 BTC sold for gross proceeds £68,000 less fees £400 = £67,600 net.
- Allocated cost basis (pooling): pool average = £14,000 per BTC; allocated basis to 4 BTC = £56,000.
- Realised gain = £67,600 - £56,000 = £11,600.
- Record the trade tick, txid, exchange CSV row, bank receipt and custodian settlement note.
Comparative table: custody models for pension funds
| Custody model |
Pros |
Cons |
| Institutional custodian (segregated) |
Clear custody records; insurance options; reconciliations. |
Costly; operational SLAs to manage. |
| Third-party exchange custody |
Convenient trading; familiar CSV exports. |
Counterparty risk; export reliability varies. |
| Self-custody (trustee-held hot/cold) |
Full control; simpler provenance for on-chain transfers. |
Requires trustee expertise; key management and insurance concerns. |
Audit-ready record workflow
Audit-ready record workflow
🔎 **Source evidence** → 🧾 **Master transaction register** → 🔗 **Hash & store** → ✅ **Reconciliation & sign-off**
- Collect exchange/custodian exports, bank receipts and on-chain txid links.
- Import into transaction register and link to file hash.
- Reconcile balances daily/weekly and record exceptions.
- Sign-off by scheme accountant and trustee governance lead.
When to use pooled ETPs versus direct holdings for pension exposure
- Use ETPs when trustees prefer a regulated wrapper with daily liquidity, transparent fees and simplified custody. ETP documentation (prospectus and issuer disclosures) becomes part of the HMRC evidence pack.
- Use direct holdings when the scheme requires bespoke custody, clear segregation and potentially lower long-term costs, but only if trustees can demonstrate operational competence and robust controls.
Advantages, risks and common errors
Benefits / when to apply ✅
- Diversification: a small allocation to Bitcoin may improve portfolio diversification when documented as part of an agreed investment policy.
- Access: ETPs provide easy exposure without handling private keys.
- Transparency: institutional custodians supply reconciliations and audit reports.
Errors to avoid / risks ⚠️
- Poor evidence for price/time: failing to record the exact timestamp and FX rate used for valuation undermines any CGT calculation.
- Missing txids: absence of on-chain references makes reconstruction expensive and less persuasive to HMRC.
- Mixing personal and scheme wallets: strict separation is required to avoid benefit-in-kind issues.
Questions trustees will ask (and how to answer them)
- Is the scheme exposed to taxable events? Yes, disposals and income-like events (staking rewards, airdrops) can create taxable events at scheme or member level depending on structure and should be logged.
- How long should records be kept? Keep records for at least six years and longer where trustee decisions or pensions law considerations apply.
- What if an exchange fails to provide history? Use the reconstruction template and capture bank wires, on-chain evidence and third-party price data with documented assumptions.
Questions frequently asked
Frequently asked questions
Can pension funds hold bitcoin directly?
Yes, subject to trustee approval, investment policy amendment and appropriate custody. Document the decision and custody model in the trustee minute and due diligence file.
How should gains inside a SIPP be reported?
Gains within a SIPP are typically tax-advantaged for the member; however, the scheme must still maintain records to demonstrate the tax position. Where disposals occur outside tax wrappers, trustees must calculate realised gains for scheme accounts.
What proof does HMRC expect for a crypto disposal?
HMRC expects a transaction ID or exchange trade ID, timestamp, fiat value at transaction time, supporting exchange/custodian export and reconciliation evidence.
Are staking rewards taxable for pension schemes?
Staking rewards can be income-like. Trustees must treat them according to scheme rules and keep evidence, including proof of distribution to scheme accounts and the valuation method used.
What if an exchange CSV has inconsistent columns?
Document the import mapping and keep the original CSV. Use a field mapping table and preserve a sample mapping file as part of the evidence set.
Your next step:
- Create or update the trustee minute and investment policy to explicitly cover crypto exposure and custody requirements.
- Implement the master transaction register and import existing exchange/custodian exports; hash each file and store hashes in a verification manifest.
- Run a one-off reconstruction exercise for historic holdings using bank wires, on-chain explorers and the reconstruction template; obtain trustee sign-off.
