Being offered salary in Bitcoin, or already being paid in crypto, creates immediate PAYE and National Insurance exposure, valuation and timing risk, and increases the risk of penalties if payroll and reporting are incorrect.
Readers will get clear employer–employee workflows and numeric PAYE and Class 1 NIC examples. They will find ready contract clauses, consent templates and exact FPS/P11D entries. They will also find reconciliation methods and custody options to protect net pay.
Accepting Bitcoin as salary likely counts as receiving taxable earnings. The employer must operate PAYE and account for employer and employee National Insurance. The taxable amount is the GBP market value at payment.
HMRC expects payroll reporting by FPS and P11D where needed. To avoid fines, get written terms or insist on GBP payment. Alternatively, ensure the employer runs correct payroll and valuation.
Receiving bitcoin as payroll: PAYE and NI risks
This section lists the variables that determine tax, timing and operational risk when salary is paid in Bitcoin. Each item must be agreed in writing. Each item must be recorded at the payment moment.
- Legal status of payment: whether the payment is employment remuneration, a genuine gift, or a reimbursement. Employment remuneration triggers PAYE and Class 1 NICs under the Income Tax (Earnings and Pensions) Act and SS contributions law.
- Valuation timestamp: the exact clock time the employer uses to value BTC in GBP. HMRC requires a documented source for the GBP conversion.
- Who funds PAYE/NICs: the employer normally remains liable to operate PAYE and pay employer NICs even for non‑cash pay. A contract clause cannot remove that statutory duty.
- Settlement method: whether the employer converts to GBP first, withholds GBP for tax, or transfers net crypto and expects the employee to fund tax later.
- Custody and liquidity: token liquidity affects whether conversion is feasible within payroll timing. Illiquid tokens raise compliance risk.
Immediate rule: treat crypto payroll as earnings valued in GBP at the time of payment. Keep an auditable screenshot or API record of rate and timestamp.
Cross‑border payroll: non‑residents, posted workers and NIC treaties
Crypto salary raises extra complexity for non‑UK residents and cross‑border workers. PAYE obligations depend on where work is done and the employment link. If duties are carried out in the UK, the employer usually has a PAYE duty.
The employee's UK tax residence does not by itself create employer obligations if all duties were performed abroad, but careful evidence is still needed.
National Insurance hinges on bilateral social security agreements and posted worker rules. Employees seconded to or from the UK may remain under their home system for a limited time and be exempt from UK Class 1 NICs.
Employers should check the employee's tax residence and days worked in the UK. They should also check for a social security certificate such as an A1. If treaty relief applies, the employee may claim it via self‑assessment.
Where crypto is paid internationally, consider currency conversion timing and the paying entity's UK PAYE setup, and be aware of the risk of creating a UK permanent establishment. Get country‑specific advice and document residency and secondment terms.
Employer pays part of salary in bitcoin, operational flow and numeric examples
The workflow below shows the lowest‑risk method and two alternatives. Worked numbers use the assumptions stated next.
Assumptions (example tax year): basic rate of income tax 20% (2026). Employee primary NIC 12% on the relevant band (2026). Employer secondary NIC 13.8% (standard rate, 2026). Personal allowance example £12,570 (2026). These figures show mechanics only.
First, the recommended low‑risk flow: run payroll in GBP, deduct PAYE and NICs, then offer conversion to Bitcoin after the payslip is issued. This leaves statutory duties unambiguous.
Example 1. Monthly salary £4,000; employer agrees 50% delivered in Bitcoin by value at payday.
- Taxable crypto element (GBP value at payment): £2,000.
- PAYE (20%): £400.
- Employee NIC (12%): £240.
- Employer NIC (13.8%): £276.
- Net cash-equivalent to convert into BTC for the employee: £2,000 − £400 − £240 = £1,360.
- Employer total cash cost for the crypto element if employer funds ER NIC: £2,000 + £276 = £2,276.
This shows two practical requirements. The payslip must show the GBP taxable amount and deductions. The employer must ensure the employee receives BTC worth £1,360 or pays the shortfall in fiat.
Example 2. Employer sells BTC to fund PAYE and NICs immediately; conversion costs are illustrated below.
If the employer must sell BTC to fund PAYE of £400 and ER NIC of £276, and the custodian charges a 0.8% sell fee, the sale required ≈ (£400+£276)/(1−0.008) ≈ £683.7 gross sale amount. The employer should budget for fees and spreads. Typical fees are 0.5–1.5% on major exchanges.
Warning: if the employer transfers gross BTC worth £2,000 and does not fund PAYE/NIC, HMRC will treat PAYE as unpaid. Liability, interest and penalties attach to the employer even if BTC later falls in value.
FPS entries and sample payroll text
An FPS must report GBP amounts. The employer should record the listed fields with an explanatory note. The note must state exchange rate source and timestamp.
- employeeId
- payPeriodStart
- payPeriodEnd
- taxablePayThisPeriod (GBP)
- taxThisPeriod (GBP)
- nicThisPeriodEmployee (GBP)
- employerNICThisPeriod (GBP)
- payslipNotes: "BTC payment; valuation source: [Exchange] at [ISO timestamp]; tx id [hash]"
Sample payslip line (example):
- Taxable pay (GBP): £4,000
- Tax deducted (GBP): £800
- Taxable crypto element (GBP): £2,000; tax deducted £400; employee NIC £240; employer NIC £276
This level of detail is essential. HMRC queries often begin by checking whether the FPS ties to exchange rate records.
Contract clause and employee consent text
-
Employment contract clause (short form): "The employer may discharge up to [x%] of gross salary in cryptocurrency. For PAYE and National Insurance purposes the GBP market value at the time of payment will determine taxable earnings. The employer will deduct PAYE and employee National Insurance from the GBP-equivalent and may retain or convert cryptocurrency to satisfy tax obligations. The employee consents to this treatment and accepts volatility risk."
-
Signed acknowledgement (one line): "The employee acknowledges receipt of the above clause and consents to valuation method and tax deductions on [date] — signature."
Save these templates in the employee file with the payslip and the rate snapshot.
Practical RTI steps and deadlines for crypto payroll
RTI obligations do not change when an employer adds a crypto element to pay. File a Full Payment Submission on or before payday. Ensure PAYE and NICs are paid to HMRC by the scheme's payment deadline.
Practical steps employers should follow:
1) Agree and record the valuation timestamp. Capture the exchange API snapshot. Enter the GBP taxable amounts into payroll.
2) Submit the FPS with taxablePayThisPeriod, taxThisPeriod and nicThisPeriodEmployee on or before the pay date.
3) Pay the PAYE bill to HMRC according to the payment schedule. Many electronic payments process by the 22nd of the month after the tax month.
4) If conversion of crypto to GBP completes after the FPS has been filed and payment is due, the employer must still pay HMRC on time from its own account, then post the conversion receipts into reconciliation.
If an amendment is needed within the same tax year, submit a replacement FPS for that pay period with corrected figures. For adjustments affecting earlier tax years, follow HMRC correction procedures and earlier year update routes.
Always keep conversion proof and make a short payroll journal entry. Link the FPS submission ID, payPeriodEnd and the custodian transaction ID so a late conversion ties to the original PAYE liability.
Brief clarification.
Contractor or freelancer offered bitcoin as payment, different rules and tests
If the payer and recipient are genuinely self‑employed the amounts are trading or professional receipts. The tax point is when the invoice is treated as received. NICs follow self‑employed rules and self‑assessment.
The distinction rests on employment status tests: control, substitution and mutuality of obligation. Misclassification risk creates PAYE fallout for the payer.
If a contractor invoices in Bitcoin and is genuinely self‑employed, the contractor reports trading income in GBP at the time of receipt. The contractor pays income tax and Class 2/4 NICs via Self Assessment.
Example (anonymised): a freelance developer invoiced £5,000 equivalent in BTC and declared it as trading income. The payer later sought to treat the payment as employment income. The resolution required a short contract review and evidence of substitution rights and retained overheads.
Practical detail from payroll desks: misclassification enquiries often start when RTI shows an identical pay‑pattern to employees but the payer has no PAYE deductions. Gathering records typically takes 3–4 weeks. If HMRC opens a formal compliance review, expect 6–8 weeks.
This section lists frequent errors and how to correct them quickly.
-
Error: assuming tax arises only on disposal. Correction: employment income is taxed when paid, not at disposal.
-
Error: believing payment in crypto removes employer PAYE/NIC responsibilities. Correction: statutory duties remain and the employer must operate PAYE.
-
Error: no documented valuation method or timestamp. Correction: immediately capture an API snapshot, exchange trade id or screenshot with ISO timestamp and store it.
-
Error: sending gross BTC without arranging GBP to remit to HMRC. Correction: if HMRC requests PAYE the employer must fund the shortfall. Consider voluntary disclosure and remedial PAYE return.
Exception: this guidance does not apply when the receipt is a genuine gift or loan not connected to employment. Documentation proving the gift nature, such as board minutes or a donor statement, must be retained.
Table: operational models comparison
| Model |
Compliance complexity |
Who bears volatility |
Typical cost items |
Recommended for |
| Convert to GBP first; run payroll in fiat |
Low |
Employer |
Conversion fees, custody fees |
Established employers, low risk appetite |
| Pay GBP via payroll; offer post-pay conversion |
Low |
Employee (optional) |
Administrative, optional conversion fees |
Startups offering crypto benefits |
| Transfer net crypto; employee sells for tax |
Medium–High |
Employee |
Employee conversion fees, potential employer enforcement risk |
High-risk employers or contractors |
| Third‑party crypto payroll provider |
Low–Medium |
Depends on contract |
Provider fees, KYC/AML controls |
Employers who lack custody expertise |
Valuation, volatility handling and reconciliation rules
HMRC treats crypto salary as earnings valued in GBP at the time of payment. The valuation source must be credible and kept with payroll records. Recommended sources include major exchange mid‑market rates such as Coinbase Pro, Kraken and Bitstamp.
HMRC guidance and the Cryptoassets Manual reference market value principles. The Chartered Institute of Taxation technical briefs also discuss valuation approaches.
A practical rule of thumb: capture a timestamped API response or exchange trade id at payment. Retain that file in payroll records for at least 6 years.
Handling volatility between valuation and settlement requires clear contractual treatment. If the employer agrees to fund PAYE/NICs but conversion takes time, the employer should hold fiat reserves and aim to convert within 24–72 hours when possible.
In practice many custodians settle GBP within 1–3 working days. Employers should plan for 3–4 working days to complete conversion and reconciliation.
Reconciliations must show payroll valuation, actual conversion proceeds, fees and any shortfall. If conversion proceeds are lower than payroll valuation, the employer must decide who absorbs the loss and record the adjustment.
Numeric reconciliation example:
- Payroll valuation: £2,000.
- Conversion realised later: £1,920 after fees.
- Shortfall: £80.
If the employment contract places volatility risk on the employer, the employer should post an expense of £80. If the employee bears volatility the employer must document the shortfall and may deduct or invoice the employee. Without explicit consent the employer risks a dispute and an HMRC challenge.
Record-keeping checklist for HMRC queries:
- timestamped exchange rate snapshot or API output
- transaction hash and wallet addresses
- exchange or custodian receipts showing fees
- signed employee consent and contract clause
- FPS/RTI records and payslips showing GBP amounts
- reconciliation journal entries and board approvals for policy
Integrations, payroll operations and custody options, automation patterns
Aim to automate valuation, conversion, RTI submission, HMRC payment and reconciliation. Three common integration patterns exist for payroll teams.
1) Payroll-first, custodial conversion after payroll:
- payroll system calculates and deducts GBP amounts
- custodian sells or buys BTC to match sums
- custodian returns transaction proof to payroll for reconciliation
2) Custodian-as-payroll: a specialist provider performs valuation, conversion and issues payslips. They may file RTI for the employer. This reduces in‑house complexity. It requires due diligence on AML and security controls.
3) Employee-directed conversion: employer pays gross BTC and reports GBP value to HMRC. The employee must convert and pay any CGT on disposal. The employer still must operate PAYE in GBP.
Recommended vendors and tech notes (illustrative; perform due diligence): payroll platforms with RTI support include Sage, Xero Payroll and BrightPay. Custodians with UK operations include Coinbase, Bitstamp and Copper.
When integrating, require API logs, settlement proofs and a CSV export of conversion events for audit.
1
Agree valuation source & timestamp
2
Run payroll in GBP & record FPS
3
Convert or fund PAYE/NICs via custodian
4
Send net BTC to employee & keep tx proof
5
Reconcile conversion, record shortfalls
Operational controls for AML and KYC include wallet whitelists and sanctions screening. Employers that contract custodians should verify FCA registration where applicable. They should also request proof of cyber insurance and SOC reports.
Technical integration patterns: fields, webhooks and reconciliation keys
Crypto payroll needs an API contract between payroll software and the custodian or exchange. A minimal flow follows.
(1) The payroll system requests a valuation at the agreed ISO timestamp. The exchange returns a signed snapshot with rateSource, pair, midMarketRate, timestamp and tradeId.
(2) Payroll calculates GBP tax and instructs the custodian to convert the exact GBP amount to settle PAYE and employer NICs.
(3) The custodian returns a settlement webhook with txId, settledGBP, fees, grossCryptoSold and netCryptoTransferred.
(4) The payroll system ingests the webhook and writes a reconciliation record linking employeeId, payPeriodEnd, FPSSubmissionId and custodian.txId.
Key fields to map and store include payrollId, payPeriodEnd, taxableCryptoGBP, exchangeRateTimestamp, rateSource, FPSSubmissionId, custodianTxId, feesGBP, settledGBP, netCryptoSent and walletAddress.
For robust reconciliation use an immutable identifier such as custodianTxId combined with FPSSubmissionId and payPeriodEnd.
