Crypto Payroll Compliance: FMV, Payslips, Remittance, Audit Log (2026)

Payroll·

Crypto Payroll Compliance: FMV, Payslips, Remittance, Audit Log (2026)

Running payroll partly in crypto does not remove the payroll obligations — it adds a valuation and a multi-jurisdiction layer on top. The compliance spine is FMV at pay date, compliant payslips, fiat tax remittance, and an audit log, applied per jurisdiction. What stays the same and what crypto adds.
Author avatar Wag3s TeamEditorial team specializing in Web3 finance, crypto tax, and DAO operations. Based in Zurich, Switzerland.

Reviewed by Wag3s Editorial Team — verified against the crypto-payroll compliance spine (FMV at pay date, compliant payslips, fiat remittance, audit log) and its multi-jurisdiction application · Last reviewed May 2026

Crypto Payroll Compliance: FMV, Payslips, Remittance, Audit Log

"We pay in crypto" gets treated as an exit from payroll. It is the opposite: the same obligations, plus a valuation layer and a multi-jurisdiction problem on top. This article sets out the compliance spine that does not change when pay is denominated in crypto, the two pieces that get added, and what that looks like in several specific countries. The narrower withholding mechanics behind one pay event, sell-to-cover and the FMV-at-vest determination, are covered in the token compensation tax withholding guide.

The compliance picture in brief

  • Crypto payroll does not remove payroll obligations. It adds a fair-market-value-at-pay-date step and a fiat-remittance step on top of the same duties.
  • The spine, applied per jurisdiction, runs from FMV at the pay date, to a compliant payslip, to fiat remittance of withholding and social contributions, to an audit log.
  • Multi-jurisdiction is the hard part: the taxing point, rates, social contributions, payslip format and deadlines are all per-country, and special regimes such as the French BSPCE layer on top.
  • The FMV must be captured with a defensible source and timestamp, since it sets the base and drives any sell-to-cover.
  • Keep per-event and per-employee records, plus the payslip and an audit log.
  • Confirm the rules per jurisdiction with an adviser; a single global payroll assumption is non-compliant for everyone outside the assumed country.

What does not change

Paying in crypto generally adds a valuation and currency layer to the same payroll obligations: the employer still owes compliant payslips, the correct withholding and social contributions, fiat remittance to the authority, and reporting. The crypto element mainly introduces an FMV-at-pay-date determination and the fact that tax is remitted in fiat, not tokens (see token-comp withholding). Crypto changes the mechanics, not the existence, of the obligations, and that misconception is the costliest one.

The compliance spine

Four elements, applied per jurisdiction:

ElementWhat it is
FMV at pay/receipt dateThe valuation base for income and withholding
Compliant payslipRequired local format
Fiat remittanceWithholding and social contributions to the authority (funded via sell-to-cover if paid in tokens)
Audit logEvery element, reconcilable

These are the same payroll fundamentals as fiat pay, with the FMV and fiat-remittance steps added.

Multi-jurisdiction is the hard part

Web3 teams are often distributed, and payroll obligations, the taxing point, rates, social contributions, payslip format and reporting deadlines, are strictly per-country, with special regimes such as the French BSPCE layered on. A single global payroll assumption is non-compliant for everyone outside the assumed country. Each employee's jurisdiction has to be applied individually. This is the dominant crypto-payroll compliance challenge and a strict YMYL caution: confirm per jurisdiction, and never globalise one country's rule.

FMV at pay date

The crypto element is generally valued at its fair market value on the relevant date (pay or receipt), and that value is the base for income and withholding. It must be captured with a defensible source and timestamp, because it is volatile, and the same FMV drives any sell-to-cover amount. An undocumented or hand-picked rate is a compliance weakness, the same fair-value discipline as in token-comp withholding.

Records and defensibility

Per pay event and per employee, retain the FMV with its timestamp and source, the gross, the withholding and social contributions, the fiat remitted, the net delivered (fiat and/or tokens), the jurisdiction basis, and the compliant payslip, all on an audit log. Crypto payroll is only defensible if every figure is reconcilable to a documented basis: the audit-trail discipline, applied to payroll.

Jurisdiction-specific rules: key examples

France

France applies specific rules to employee compensation in crypto assets under the broader regime for non-cash remuneration (avantages en nature). The FMV at the date of attribution is the taxable value. Withholding (retenue à la source) for employees is required at the French progressive income-tax rates, and social contributions (CSG/CRDS, cotisations sociales) apply to the same base. France also has specific rules for BSPCE (bons de souscription de parts de créateur d'entreprise) and BSA (bons de souscription d'actions) — startup warrant schemes. Token grants that resemble BSPCEs may qualify for preferential tax treatment at disposal (flat 30% PFU) rather than as employment income, but the eligibility conditions are strict and the token must be a qualifying equity-equivalent. Confirm with a French payroll adviser; the distinction between employment income (taxed immediately) and a qualifying BSPCE/BSA (taxed at disposal) can be substantial.

United Kingdom

HMRC treats crypto payments as employment income taxable under PAYE. The employer must calculate the sterling equivalent of the crypto received using the market exchange rate at the date of receipt, apply the correct income-tax band and National Insurance contributions (both employee and employer), and remit via Real Time Information (RTI) reporting on or before the payment date. If the crypto is not in pounds sterling, HMRC accepts an exchange rate based on a "reputable exchange" — a documented source is required. Stablecoins (e.g. USDC) are still subject to PAYE treatment in the same way, with the sterling equivalent confirmed at the date of receipt.

United States

The IRS treats cryptocurrency wages as ordinary income measured at the fair market value in USD on the date received. Employers must withhold federal income tax, Social Security (FICA), and Medicare on the FMV of the crypto. The withholding is remitted in USD using EFTPS; if the employee is paid in tokens, the employer must typically arrange sell-to-cover to fund the withholding obligation. W-2 reporting must include the crypto wages in Box 1 (wages) at the USD FMV. Some crypto-native companies have attempted to characterise crypto wages as non-taxable or deferred; IRS guidance (Notice 2014-21 and subsequent FAQs) is clear that this is incorrect.

Switzerland

Switzerland treats crypto salaries as employment income (Erwerbseinkommen) subject to withholding tax for employees without B/C permit status and ordinary assessment for residents. The FMV in CHF at the date of receipt is the taxable value. Social contributions (AHV/IV/EO and ALV) apply to the gross salary in CHF equivalent. The Swiss Federal Tax Administration has specific guidance on crypto assets as part of the Rundschreiben on cryptocurrencies (ESTV circular). Employees who receive tokens that later appreciate will recognise capital gains on disposal if they hold as private assets — which are generally not subject to federal income tax in Switzerland (a significant advantage for Swiss-resident employees versus the UK or France).

Common payroll compliance errors

Applying the FMV at the end of the month for monthly payroll, not at the actual payment date. For volatile assets, a one-day difference can create a material discrepancy. The FMV must be captured at the actual payment/receipt date with a timestamp from a documented source.

Not withholding because "the employee will sort it out in their tax return." Employer withholding obligations do not disappear because the employee is responsible for filing a return. In most jurisdictions, the employer is a separately liable withholding agent and can face penalties for under-withholding regardless of whether the employee later pays the correct tax.

Paying contractors in crypto without employee vs contractor classification. The compliance obligations differ substantially between employees (withholding, payslips, social contributions) and independent contractors (typically no withholding, 1099-NEC or equivalent reporting). Misclassifying an employee as a contractor in order to avoid withholding obligations is a significant compliance failure in every jurisdiction.

Not maintaining payslips in the required local format. Many jurisdictions (France, Germany, UK) require payslips to show specific line items — gross pay, deductions by type, net pay — in the local language. A simple email noting "we sent you 0.5 ETH" is not a compliant payslip.

Practical guidance

  1. Reject the idea that crypto removes payroll: the obligations are the same, plus FMV and fiat-remittance.
  2. Run the four-element spine per jurisdiction.
  3. Apply each employee's jurisdiction individually, with no global assumption.
  4. Capture the FMV, timestamp and source defensibly at the pay date.
  5. Keep special regimes (such as the French BSPCE) separate from generic crypto payroll.
  6. Retain per-event and per-employee records, the payslip and the audit log, and confirm with a payroll adviser.

Configuring a crypto-payroll tool

A crypto-payroll platform can run the spine, but the obligations it is meeting are set by each country's law, so the configuration to check is whether the tool applies the right rules and captures a defensible valuation. When you assess one, confirm that it:

  • applies the correct rules per jurisdiction and per employee, rather than one global default;
  • captures the FMV, timestamp and source at the pay date in a form you could defend;
  • retains the full per-event record, the compliant local payslip and the audit log.

Platforms such as Toku and Liquifi provide multi-jurisdiction token and fiat payroll with FMV handling, sell-to-cover, payslips and audit logging. The platform runs the spine; the obligations themselves are jurisdiction law.

How Wag3s supports the spine

Wag3s HR records the FMV, timestamp and source per pay event, the gross, withholding and net split with the fiat remittance, the jurisdiction basis per employee, and the payslip data on an audit log. That is the reconcilable spine behind compliant crypto payroll. Because payroll obligations are strictly jurisdiction- and employer-specific, Wag3s supports a qualified payroll or tax adviser's determination per country rather than replacing it. See the HR product page.


Further reading

Sources

  • IRS (United States) — Notice 2014-21: cryptocurrency wages are ordinary income at the US-dollar fair market value on the date received, subject to federal income tax withholding, FICA and FUTA, and reported on Form W-2. See also the Digital assets hub.
  • France — see the BSPCE vs token grants article and its BOFiP and Légifrance sources, which document the distinct French regime referenced above.
  • IFRS — IFRS 2 Share-based Payment and IAS 19 Employee Benefits, where the crypto-pay element interacts with share-based-payment or employee-benefit accounting.

The UK PAYE/RTI treatment, the Swiss withholding and social-contribution treatment, and the per-country payslip and reporting requirements described above are each set by national rules; confirm the specifics per jurisdiction with a local payroll or tax adviser. The compliance spine (FMV at pay date, compliant payslip, fiat remittance, audit log) is the operational discipline that satisfies, but does not replace, those obligations.

Editorial disclaimer
This article is informational and does not constitute payroll, tax, or legal advice. Payroll obligations are strictly jurisdiction- and employer-specific. Confirm with a qualified payroll/tax adviser per jurisdiction.