Treat Lightning and on‑chain Bitcoin receipts the same for revenue: record the GBP value at the time of receipt. Lightning adds timing, routing and reconciliation work that finance must track.
Lightning Payments vs On-chain: quick comparison
For a quick choice, Lightning offers speed but requires more reconciliation; on‑chain offers simpler reconciliation but slower settlement.
| Criterion |
Lightning |
On-chain |
When to choose |
| Speed |
Near instant settlement off-chain |
Settlement depends on block confirmation time |
Use Lightning for micropayments and fast retail flows |
| Fees |
Small routing fees and channel costs |
Miner fees variable by congestion |
Choose on-chain for high-value settled receipts |
| Accounting complexity |
Higher: channel opens, closes, routing and rebalancing |
Lower: single on-chain receipt per sale |
Use on-chain if avoiding off-chain reconciliations |
| Custody option |
Non‑custodial or custodial wallets possible |
Non‑custodial or custodial wallets possible |
Choose based on treasury and AML controls |
| Tax treatment impact |
Same HMRC revenue rules but extra timing items |
Direct revenue recognition at receipt |
Either is fine if processes capture GBP values |
Businesses that need speed and micropayments should favour Lightning. Businesses that want simpler flows and fewer reconciliation items should favour on‑chain.
Review controls and logs weekly to reduce audit risk.
On-chain payments when to choose and how to record
Use on‑chain receipts for higher values and simpler reconciliation. Record the GBP value when funds are received.
The business recognises revenue in GBP at that spot rate. If the firm holds Bitcoin, recognise gains or losses on later disposal or conversion.
Example numeric worked sale:
- A UK shop sells goods for £120 on 01 March 2026.
- The spot rate when the on-chain tx confirmed is £40,000 per BTC.
- BTC received = 0.003000 BTC.
Typical journal entries for on-chain receipt when the business holds crypto:
-
When goods are sold and BTC is received
-
Dr Debtors or Cash equivalent (BTC wallet at GBP value) £120
-
Cr Sales revenue £120
-
To record crypto asset at spot
-
Dr Crypto asset — BTC (nominal ledger) £120
-
Cr Debtors or Clearing account £120
-
When the business converts BTC to GBP later at a different rate
-
Dr Bank (GBP) £115
- Dr Loss on crypto FX £5 OR Cr Gain on crypto FX if positive
- Cr Crypto asset — BTC £120
These entries show revenue separate from later gains or losses on the asset. They keep sales and FX effects distinct for tax and audit.
Set a written FX and GBP conversion policy. Name your spot rate sources and timestamp rules.
Cover batched receipts and a weighted average rule for batches. State revaluation frequency for retained balances.
For example: a sale on 10 April 2026 results in 0.004 BTC received. The firm records revenue using the PSP spot = £45,000/BTC → GBP sale £180.
If on 12 April the firm converts 50% of the holding at £50,000/BTC it will bank £100. It recognises a realised FX gain of £10. The remaining 0.002 BTC is revalued at period‑end at £52,000/BTC to a carrying value of £104.
Document whether gains and losses flow to profit and loss or a revaluation reserve. Also state whether hedging derivatives are allowed.
This reduces audit queries and helps keep HMRC tax computations consistent.
Lightning payments when to choose and how to record
Use Lightning for instant low‑value sales and subscriptions; ledger treatment must capture channel opens, routing fees and unsettled balances.
Record revenue in GBP when the invoice is settled by the payer via Lightning. Capture the PSP spot or node rate at that time.
Worked numeric example:
- Sale value £5 on 02 March 2026. Spot rate at receipt £50,000 per BTC. BTC received 0.0001.
- Routing fee 0.000001 BTC (equivalent £0.05). Channel open fee cost 0.00002 BTC (£1).
Core journal entries when holding BTC:
-
On sale and receipt (immediate economic receipt):
-
Dr Crypto asset — BTC £5
-
Cr Sales revenue £5
-
To record routing fee deducted en route
-
Dr Routing expense £0.05
-
Cr Crypto asset — BTC £0.05
-
If the business opens a channel (cost charged on-chain)
-
Dr Channel setup cost (expense or capitalised minor cost) £1
-
Cr Crypto asset — BTC £1
-
When revaluing at period end (example quarter-end)
-
If BTC value falls and unrealised loss £0.50 then:
- Dr Unrealised loss on crypto £0.50
-
Cr Crypto asset — BTC £0.50
-
When closing channel and converting to GBP later
-
Dr Bank £X
- Dr Loss on conversion £Y or Cr Gain on conversion £Y
- Cr Crypto asset — BTC £Z
These entries cover the cash, expense and revaluation effects specific to Lightning. They also show how routing fees reduce the asset base.
💡 Advice
Use a separate ledger account for Routing fees. Use a dedicated clearing account for unsettled channel balances.
Lightning Payments vs On-chain: how to choose for your firm
When choosing a flow, the key difference is reconciliation effort and FX timing. If the firm will keep BTC on the balance sheet, Lightning requires more subaccounts and daily monitoring.
If the firm wants to avoid holding crypto, a fiat‑settling PSP removes crypto accounting and shifts the cost and control to the PSP.
Decision criteria checklist:
- Volume and ticket size: Lightning for many small transactions under £10. On‑chain for larger single payments.
- Treasury capacity: choose on‑chain if treasury cannot manage channel liquidity.
- AML and PSP constraints: use a fiat PSP if the regulatory burden must be minimised.
- Audit readiness: pick the flow that matches existing bank reconciliation processes.
⚠️ Attention
Recognising income only when crypto is converted to GBP misstates revenue timing: HMRC requires revenue to be measured in GBP at the time of receipt.
Review controls and logs weekly to reduce audit risk.
What nobody tells you about practical costs and controls
Routing fees and channel opens create recurring micro‑costs. Industry estimates show these costs often range between 0.1% and 1% of transaction value.
On‑chain miner fees vary much more. They could range between £0.10 and £10 per transaction depending on congestion.
Another hidden cost is staff time for reconciliation. Lightning requires matching many small routing events with sales. For many UK firms that cost exceeds the fee savings for micropayments.
Practical controls for auditors:
- Maintain a channel ledger with opening tx id, capacity and counterparties.
- Reconcile daily unsettled channel balances to node backups.
- Log every routing fee against a sale or expense.
- Keep exported node and wallet proofs for the audit trail.
HMRC checklist for accepting Bitcoin in the UK
Follow these items to ensure records and tax positions are correct.
- Record GBP revenue at time of receipt using a reliable spot rate source and timestamp. See HMRC guidance for record keeping at the link below.
- Keep separate ledger accounts for crypto assets, routing fees, channel setup costs and unrealised gains and losses.
- Retain evidence: exchange rates, transaction ids, node logs and PSP settlement reports for at least 7 years for corporation tax records.
- If using a PSP that settles in GBP, check contractual terms to confirm whether the firm ever holds crypto.
External references:
A practical regulatory checklist complements HMRC record‑keeping. Firms must assess whether activities require FCA cryptoasset firm registration.
They must also comply with the Money Laundering Regulations 2017. Keep KYC thresholds and SARs processes in writing.
Map each product to its regulatory perimeter and retain AML evidence for 5–7 years. Review FCA guidance annually.
Reconciliation template and audit controls
Export a simple ledger weekly for reconciliation. The export must show sale details, fees and settlement.
- Date
- Sale ID
- GBP sale value
- BTC amount received
- Spot rate at receipt
- Routing fee BTC and GBP
- Channel open/close tx id and cost
- Settlement to bank (if converted)
- Gain/Loss on conversion
Use a dedicated clearing account for unsettled Lightning receipts. Reconcile it to node balances daily.
Visual flow
Sale → Receipt (Lightning/on-chain) → Crypto asset ledger → Revaluation → Conversion or hold
Reconcile daily
A filled reconciliation example makes operational control clear. The example below shows weekly Lightning sales and clearing movements.
Example weekly snapshot: three Lightning sales on 01 May: Sale A £3 (0.00006 BTC), routing fee 0.0000006 BTC (£0.003); Sale B £5 (0.0001 BTC), routing fee 0.000001 BTC (£0.005); Sale C £2 (0.00004 BTC), routing fee 0.0000004 BTC (£0.002).
Book at receipt: Dr Clearing account — Lightning receipts £10; Cr Sales revenue £10.
When payments settle into the node and routing fees are realised, post these entries. Dr Crypto asset — BTC £9.99; Dr Routing expense £0.01; Cr Clearing account — Lightning receipts £10.
If the node batches and converts total 0.0002 BTC to GBP two days later at a rate that yields £9.80 after conversion fees, post: Dr Bank £9.80; Dr Loss on conversion £0.19; Cr Crypto asset — BTC £9.99.
The reconciliation row for each sale should show Sale ID, GBP value, BTC amount, routing fee, clearing movement, settlement tx id and final bank amount. This filled example shows how small routing fees and settlement timing feed the clearing account and the crypto asset ledger.
Review controls and logs weekly to reduce audit risk.
Lightning Payments vs On-chain: which minimises VAT headaches
In the context of VAT, the tax depends on the supply, not the payment method. Value the supply in GBP at the time of supply.
The VAT due is calculated on that GBP value. Using a GBP‑settling PSP simplifies VAT because the VAT point and consideration are in sterling.
Lightning Payments vs On-chain: which minimises capital gains tax
In the context of capital gains, gains apply when the business disposes of crypto or converts to fiat. Converting immediately on receipt leaves little scope for large gains or losses.
Holding crypto exposes the firm to corporation tax on gains on later disposals. For small merchant receipts converted same day, CGT exposure is minimal.
What hidden costs arise from Lightning versus on-chain
Lightning needs channel management, routing fees and reconciliation headcount. On‑chain costs include higher miner fees at peak times.
PSPs that settle in GBP shift many of these costs off the firm. They charge a conversion fee for that service.
FAQ
What is the difference between Lightning and On-chain?
Lightning is an off‑chain payment layer built on top of Bitcoin that settles through payment channels. On‑chain payments are recorded directly on the Bitcoin blockchain with block confirmations.
Lightning suits low‑value, instant payments. On‑chain suits large, directly verified receipts.
Should a UK business use On‑chain?
On‑chain is appropriate where the firm wants fewer reconciliation items and direct settlement proof on the blockchain. It reduces the need for channel accounting.
Choose on‑chain if transaction volumes are low and ticket sizes are high.
How many transactions can Lightning Network handle?
The Lightning Network can route many more small transactions than Bitcoin on‑chain because it uses off‑chain channels. Exact throughput varies by topology and channel capacity.
In practice, Lightning handles thousands of payments per second in theory, though network topologies limit real world routing capacity.
How to accept crypto payments as a business in the UK?
Settle policy first: decide whether to hold crypto or settle to GBP. Implement AML checks and choose custody.
Create ledger accounts for sales, crypto asset, routing fees, channel costs and unrealised gains. Record GBP revenue at receipt and keep full transaction evidence for HMRC.
Lightning Payments vs On-chain: which simplifies bookkeeping and audits?
On‑chain generally simplifies bookkeeping because each sale maps to a single on‑chain receipt. Lightning increases bookkeeping complexity due to channel and routing events.
If the firm uses a fiat PSP, bookkeeping is simplified regardless of the underlying protocol as the firm only records GBP bank receipts.
What if a channel fails or a routing fee is refunded?
If a routing fee is refunded, credit the routing expense and debit the crypto asset. If a channel failure causes a temporary mismatch, use the designated clearing account and document the issue.
Maintain node logs and proofs for auditors to trace any reclaims.
Where to find HMRC guidance?
See the HMRC Cryptoassets Manual for tax treatment and record‑keeping rules. It explains that receipts should be valued in GBP at the time of receipt and that later gains or losses on holdings must be accounted for in tax computations.
