Being paid in Bitcoin can look straightforward until IR35, PAYE and the GBP valuation all need to line up. A contractor in England may want the flexibility of crypto, but HMRC will still expect the engagement, the paperwork and the tax treatment to be defensible. The real risk is not the coin itself; it is getting the contract or records wrong.
Yes, contractors & IR35: paid in BTC? A contractor can be paid in Bitcoin without changing IR35 status, because IR35 depends on the real working arrangement, not the payment currency. The key is to value the BTC in GBP at the correct point, keep evidence of the exchange rate and retain robust contractual and accounting records.
Can you be paid in bitcoin without changing IR35?
Yes, a contractor can be paid in Bitcoin without changing the IR35 analysis. The currency used for settlement does not decide whether the engagement is inside or outside IR35. HMRC looks at the real relationship, then asks whether it looks like employment or genuine self-employment.
What matters first is the contract and the day-to-day reality. A BTC payment can sit inside a compliant contractor structure, but it does not cure disguised employment. If the working practices point to employment, the tax treatment follows that reality.
The cleanest way to frame the issue is this: Bitcoin is a payment method, not an IR35 shield. That line holds across limited company, agency and umbrella setups. It also applies whether the work started in a previous year, in 2026, or this year.
IR35 tests still come first
Control remains one of the most useful signs. If the client decides how, when and where the work gets done, the risk rises. If the contractor controls delivery and can substitute another suitably skilled person, the position usually looks stronger.
Mutuality of obligation matters too. A contract that looks open-ended, with a steady stream of work and no real right to refuse future tasks, can point towards employment. BTC does not change that analysis.
The error most people make at this point is simple. They focus on the payment rail and forget the status test. That leads to neat invoices and messy tax outcomes.
Crypto does not override status
A payment in digital assets does not rewrite the legal facts. If the role is inside IR35, HMRC can still expect PAYE and National Insurance contributions on the relevant income. If the role is outside IR35, the company can still be paid in BTC, provided the contract and records support that position.
A contractor can therefore receive Bitcoin and still be outside IR35. A contractor can also receive Bitcoin and still be inside IR35. The payment medium changes less than many assume.
Contract title does not decide status. HMRC looks at control, substitution and mutuality of obligation, then compares them with the real working practices.
What HMRC will actually examine
HMRC will ask who directs the work, who can send someone else, and whether the client has a genuine obligation to offer work and the contractor an obligation to accept it. It will also look at invoices, emails, internal instructions and how the job ran in practice.
The Off-Payroll Working rules, as set out by HMRC and the Finance Act 2019, make that focus very clear. The payment currency never replaces the status test.
A useful point for advisers is this: the blockchain transfer proves a transfer happened, but it does not prove the right tax treatment. That distinction matters in every enquiry.
HMRC treats BTC income as sterling income first
HMRC generally wants the contractor’s income measured in GBP, even when payment arrives in BTC. The sterling amount is the figure that matters for income tax, corporation tax, PAYE and record keeping. Crypto does not remove the need to state a pound value.
This is where many records fail. The crypto amount gets recorded, but the GBP value gets guessed or applied inconsistently. That creates risk later, especially if the exchange rate moved sharply between invoice date and payment date.
The better approach is boring but defendable. Fix a method, use it every time and keep the evidence.
Income tax versus capital gains tax
The original receipt for services is usually taxed as income, not as a capital gain. If the BTC is later sold, swapped or spent, any later increase or decrease in value can create a separate capital gains tax outcome under the Taxation of Chargeable Gains Act 1992.
That split is often missed. The income arises when the contractor is paid for work. The later gain or loss arises only if the BTC moves in value after receipt and before disposal.
Payment in kind and sterling value
Where BTC is used as settlement, the payment can function like a payment in kind in commercial terms, even though the tax analysis still depends on the facts. The key point is the sterling valuation on the relevant date and time.
A practical rule works well here. Record the BTC amount, the GBP equivalent, the source used for the exchange rate and the exact timestamp. If the invoice says £10,000 and the agreed settlement is 0.18 BTC, the file should show how that number was reached.
The data points point in one direction. Missing pound values are one of the fastest ways to create HMRC questions later.
Off-Payroll working rules in practice
The Off-Payroll Working rules in England mean the client, agency or fee-payer may carry payroll duties if the engagement is inside IR35. If a contractor is paid through an umbrella company, the umbrella normally sits in the PAYE chain and handles the payroll deductions.
BTC does not remove that chain. If the arrangement requires payroll treatment, the person who runs payroll still has to operate it correctly in GBP terms. That is true even when the contractor wants the final settlement in crypto.
HMRC’s own guidance on employment status and off-payroll working is built around the real relationship, not the label on the invoice.
HMRC guidance on checking employment status for tax
The route matters: limited company, agency or umbrella
The payment route changes the tax mechanics even if the contractor still receives Bitcoin in the end. A direct limited company arrangement, an agency chain and an umbrella company structure each create different duties for PAYE, NICs and reporting.
This is where the practical detail lives. What looks like the same BTC payment on the blockchain can sit in three very different tax setups.
Limited company, agency, umbrella
A limited company can invoice in GBP and settle in BTC if the contract allows it. The company then records the sterling value in its books and deals with corporation tax, director payroll or dividends as normal.
An agency chain is more awkward. If the agency is the fee-payer under off-payroll rules, it may need to process the payment through payroll before any crypto settlement happens. That can mean converting the amount into GBP first, then paying out after the deductions are made.
An umbrella company is usually the most rigid route. The umbrella runs PAYE, deducts employer and employee NICs where due, and pays the contractor net pay. If BTC enters that chain, the umbrella still has to report the sterling payroll figure correctly.
| Setup |
Who pays whom |
Main tax duty |
BTC risk point |
| Limited company |
Client to company |
Corporation tax and proper bookkeeping |
Wrong GBP valuation or weak contract wording |
| Agency chain |
Client to agency to contractor |
PAYE may apply under off-payroll rules |
Crypto may arrive after payroll has already been processed |
| Umbrella company |
Client or agency to umbrella to worker |
PAYE and NICs on gross pay |
Net pay in BTC still needs a sterling payroll trail |
Who bears PAYE and NICs risk
PAYE and NICs risk usually sits with the party that has the legal payroll obligation. In an inside IR35 case, that can be the fee-payer or umbrella. The contractor still needs the figures to be right, but the operational duty may sit elsewhere.
One case comes up often: a contractor agrees a £600 daily rate, then asks for BTC at settlement. The client accepts the idea but forgets payroll. Three weeks later, the payroll team is trying to rebuild the sterling value from an exchange screenshot that no one saved properly.
That is avoidable. It usually is.
Comparative matrix for each setup
The simplest way to think about the structures is this: limited company gives the most room to arrange crypto settlement, umbrella gives the least, and agency sits in the middle. That order can change if the contract is inside IR35 or the agency insists on payroll first.
| Structure |
BTC feasible? |
Payroll impact |
Records needed |
| Limited company |
Usually yes |
Company records sterling value |
Invoice, wallet, exchange rate, contract clause |
| Agency chain |
Sometimes |
PAYE may be triggered before settlement |
Agency terms, fee-payer records, valuation evidence |
| Umbrella company |
Often difficult |
Net pay and PAYE must still be correct |
Payslip, payroll trail, BTC settlement proof |
The route can decide who has to process the tax first. In practice, that often matters more than the wallet address.
1. Contract says BTC is allowed
Settlement terms set the currency, the date and the exchange-rate source.
2. Work is checked for IR35
Control, substitution and mutuality decide the status, not the token used.
3. GBP value is recorded
Invoice, timestamp, wallet and exchange evidence support the sterling figure.
4. Payroll or company accounts follow
PAYE, NICs, corporation tax or later CGT are handled from that base.
Under a limited company route, BTC can work as settlement only if the contract clearly states the fee is in GBP and the crypto is simply the payment rail. For example, a client may approve a £1,000 day rate, the contractor invoices in sterling, and the company accepts 0.02 BTC at an agreed exchange rate captured at the time of settlement. The company then books the sterling value, keeps the wallet transaction, and retains invoice records with the exchange rate evidence.
Where an agency is involved, the fee-payer may need to complete the PAYE and National Insurance step first before any onward crypto transfer. With an umbrella, the contractor may receive net pay after deductions, so the BTC element must never blur the PAYE trail or the gross-to-net calculation.
Valuing bitcoin in GBP needs one fixed method
A contractor should value BTC in GBP using one consistent and defendable method. HMRC does not reward improvisation. It rewards records that show a sensible rate, applied in the same way each time.
The exchange rate should be taken from a reputable source and tied to a specific date and time. If the business uses closing prices, it should use the same closing source every time. If it uses transaction-time pricing, the system should capture the timestamp too.
That sounds obvious, yet many files miss it. The blockchain shows movement. It does not show the sterling value used for tax.
Choosing an exchange rate source
A sensible source is one that is public, repeatable and easy to explain if asked. Many contractors use a major exchange price or an index from a known provider, then keep a screenshot or export for the record.
A rate lifted from a random social post is weak. So is an unlabelled chart saved weeks later. If the source can be challenged, the valuation can be challenged.
HMRC cryptoassets manual
Recording timestamp and transaction hash
The timestamp and transaction hash anchor the valuation to a real event. Without them, a later spreadsheet entry is only a guess with tidy formatting.
The best file usually shows the invoice date, the agreed BTC amount, the wallet address, the tx hash and the exchange rate used. If there is a delay between invoicing and payment, that gap should also be clear.
A clear record often saves 3 to 7 days of back-and-forth later. That is the sort of small delay that becomes a large problem if HMRC asks questions.
Accounting for fees and volatility
Fees should be shown separately where possible. If the contractor pays a network fee or exchange fee, that cost should not blur the gross fee for work.
Volatility needs a contract clause too. If the BTC falls between invoice date and settlement date, someone has to carry that risk. If the contract says nothing, the argument often becomes expensive and slow.
For HMRC purposes, the safest approach is to fix the GBP valuation point in advance and use it consistently. Many contractors choose the invoice timestamp, the payment timestamp, or a published exchange rate from a major platform, but whichever method is chosen should be applied every time and supported with exchange rate evidence such as a screenshot, CSV export or statement. If the BTC settles late and the price has moved, the sterling amount still needs to reflect the agreed valuation date.
That matters for income tax, corporation tax and, where the coins are later sold, for any separate capital gains calculation. A clear file should show the BTC amount received, the pound figure, the source of the rate and the exact time of the transaction so the crypto income position is defensible.
Contract clauses should say exactly how BTC is paid
A crypto payment clause should say when payment is legally made, which GBP rate applies and who carries the exchange-rate risk. It should also explain whether BTC is the settlement currency or only a way to transfer value after the GBP fee has been fixed.
Without those words, both sides can think they agreed something different. That is a common source of avoidable disputes.
Payment currency and settlement date
The clause should say whether the fee is denominated in GBP and settled in BTC, or denominated directly in BTC. Those are not the same thing.
If the agreement says the fee is £8,000, the contract should also say whether payment is due in the BTC equivalent at the spot rate on invoice date, payment date or another agreed date. If that is left open, the sterling value can drift.
Exchange-rate risk allocation
The contract should say who bears the risk if BTC rises or falls before settlement. If the client bears the risk, the contractor wants a fixed GBP equivalent. If the contractor bears the risk, the file should show that clearly.
This point is often overlooked until the market moves. Then everyone becomes very precise about words they ignored on signing day.
Crypto-specific invoice wording
The invoice should identify the GBP amount, the BTC equivalent and the rate source. It should also state the wallet address used for payment and the due date.
A simple example works well:
text
Invoice amount: £7,500
Settlement method: BTC equivalent at the Coinbase spot rate at 15:00 UK time on the invoice date
Wallet address: [insert address]
Tx hash: [insert hash after payment]
Rate source: [insert source and screenshot reference]
Indemnities and compliance wording
Some contractors add wording that each party remains responsible for its own tax compliance. That does not remove HMRC’s powers, but it helps define who is expected to operate payroll, bookkeeping and reporting.
The stronger drafting also confirms that BTC settlement does not alter status under IR35. That sentence is short, but it closes a very common argument before it starts.
The best clause is plain. It says the GBP fee, the BTC rate, the settlement date and who takes volatility risk.
Crypto-specific drafting should go beyond saying ‘payment in Bitcoin allowed’. A stronger contract makes clear whether the contractor is a limited company contractor or working through an agency chain, whether substitution clause rights remain intact, and whether the client retains the right to direct the work in a way that would affect the IR35 status analysis. It should also state who bears settlement risk if the BTC price moves between invoice and payment, who is responsible for any banking or exchange conversion fees, and whether the contractor can demand sterling instead of Bitcoin if the payment is delayed.
Those points help keep the contractor engagement commercially workable without creating uncertainty over off-payroll working, PAYE or the tax trail.
Keep proof for the tax position, not just the transfer
HMRC checks work better when the file shows the whole path from contract to cash equivalent. A wallet transfer alone rarely tells the full story.
The practical file should match the contract, the invoice and the tax return. If those three disagree, the weaker one usually loses.
Contract and SOW
Keep the signed contract, statement of work and any change orders. Those documents show what was agreed, who controlled the job and whether substitution or deliverables were real.
If a payment clause was added later by email, keep that email too. Small wording changes can matter in a status review.
Invoice and wallet proof
Keep the invoice, the wallet address, the tx hash and any exchange confirmation. The invoice should show the GBP figure even if the client pays in BTC.
A screen capture of the received coins can help, but it should sit beside formal records. Alone, it is thin evidence.
Exchange-rate and timestamp evidence
Keep the exact source of the sterling conversion. A screenshot, CSV export or account statement is usually stronger than a memory or a note made after the fact.
The file should also show the UK time used. That matters when price swings are sharp and the payment lands close to a rate change.
Payroll or company records
If payroll applies, keep payslips, RTI records and the workings behind the gross and net figures. If the work runs through a limited company, keep the bookkeeping entry and the corporation tax support.
The records must line up. If the accounts show £9,800 but the contract says £10,000, the gap needs a reason.
A clean audit trail is not a luxury in crypto payments. It is the difference between a defendable return and a weak one.
Common mistakes that create HMRC risk
The biggest mistake is assuming crypto payment changes status. It does not. A second mistake is assuming the blockchain record is enough. It is not.
A third mistake is letting the exchange rate float without control. That turns a normal contractor fee into a valuation dispute.
Assuming BTC changes status
BTC settlement can sit inside or outside IR35. It does not move the line by itself.
If the role looks like employment, the contractor still faces inside IR35 treatment. If the role looks genuinely self-employed, BTC payment does not spoil that on its own.
Using unsupported GBP rates
Using a rough rate from memory is weak practice. So is using one rate for invoices and another for bookkeeping without a paper trail.
The rate must be defendable and consistent. That is what HMRC will test if the figures look odd.
Ignoring later disposal gains
If BTC is kept after receipt, later gains or losses can arise when it is sold or spent. That can create a separate capital gains tax point.
This matters when the contractor receives the coins and leaves them sitting on an exchange for weeks or months. The tax story does not end at receipt.
Missing umbrella or agency duties
An umbrella company or agency may still need to run PAYE correctly even if the final settlement is in crypto. Assuming they can skip payroll because the payment is in BTC is a mistake with real cost.
One practical warning stands out. Some contractors think the agency can pay in BTC “off the books” and everything stays clean. It does not. That route can create PAYE, NICs and reporting trouble for everyone involved.
Frequently asked questions about BTC pay and IR35
Does being paid in BTC increase IR35 risk?
No, the payment currency does not increase IR35 risk by itself. The risk comes from the working relationship, not the coin used. If the contractor is managed like an employee, BTC will not help. If the engagement is genuinely outside IR35, BTC can still be used, provided the contract and records are tight.
Can a contractor inside IR35 be paid in bitcoin?
Yes, but payroll still has to work in GBP. Inside IR35 status can trigger PAYE and National Insurance contributions, and the employer or fee-payer must handle those correctly. BTC can be the settlement method, but it cannot replace payroll duties where they apply.
How should a limited company record BTC income?
The company should record the sterling value at the agreed time and keep the exchange-rate evidence. The BTC receipt then sits in the books as income or a receivable at GBP value, while later changes in value may create a capital gains point if the coins are disposed of later.
What evidence does HMRC accept for BTC valuation?
HMRC will want a sensible, consistent and auditable method. A public exchange rate, a timestamp, the tx hash, the wallet address and the invoice all help. A lone blockchain record is rarely enough on its own.
Does an umbrella company have to use PAYE on BTC
Usually yes, if the arrangement is inside the payroll chain. The umbrella still has to calculate pay, tax and NICs in sterling terms. BTC may arrive later as settlement, but the payroll figures still have to be right first.
Is BTC payment better than PAYE for contractors?
Not if the role is inside IR35. BTC may give more flexibility for settlement, but it does not remove tax or status rules. For outside IR35 contracts, BTC can work well if the valuation and contract terms are properly set out.
What is the safest contract wording for crypto
The safest wording says the fee is in GBP, the BTC rate is fixed by an agreed source, the settlement date is clear and exchange-rate risk is allocated. It should also say that crypto payment does not change employment status under IR35.
This guidance does not fit every reader. It is not for people who are not contractors, are not working under off-payroll rules, or are only buying Bitcoin as an investment. It is also not the right frame if the payment is a one-off personal transfer rather than a business fee for services.
What to do before you accept BTC payment
The safest move is to treat BTC as a settlement method and lock down the tax facts before payment starts. That means checking IR35 status first, agreeing the GBP value method, and making sure the contract says who carries volatility risk.
If the engagement sits inside IR35, payroll and NICs need to work properly even if the final settlement uses crypto. If it sits outside IR35, the company still needs a clean GBP valuation, good records and a contract that matches the working reality.
One short rule covers most cases: agree the pounds first, then settle the coins. That keeps the tax trail clearer and reduces the chance of disputes later.
Before signing, review the contract wording, the invoice format and the record-keeping process together. If those three line up, BTC can be workable. If they do not, the risk usually lands on the contractor.
