Crypto Payroll Hub · Compliance
Stablecoin payroll compliance: MiCA, the IRS, and the hybrid gross-to-net model.
Stablecoin payroll is no longer an edge case — US and EU employers now run it at scale. This guide covers the four things a compliance team needs to get right before the next pay run: the hybrid gross-to-net ledger, IRS W-2 reporting, MiCA EMT vs ART classification, and the documentation an auditor will ask for.
Section 1 · Operating model
The hybrid gross-to-net model.
Most teams that pay in stablecoins have already settled on a hybrid ledger: the pay slip is denominated in a USD-equivalent so the employee can read their gross and net against a familiar yardstick, but the on-chain transfer is denominated in the chosen stablecoin. The two ledgers stay in sync at the moment of payment; they diverge the moment the conversion rate moves. That distinction is the spine of the whole compliance posture.
Why two ledgers, not one
The employee's offer letter, W-2, and severance calc all run in a fiat currency — usually USD, EUR, or GBP — because tax authorities and labor law operate in fiat. The on-chain payment, on the other hand, settles in USDC, USDT, DAI, or a token-native asset like ETH. A single ledger can't do both jobs without contorting the legal language, so the cleanest setup is to record the gross obligation in fiat, the on-chain transfer in the chosen token, and the delta as a conversion gain or loss.
Net amount equals gross minus withholdings
Withholdings for income tax, social contributions, and benefit premiums are calculated on the fiat-equivalent gross and then netted against it. The on-chain transfer delivers the net figure converted at a quote captured at the moment of payment. The employer records both the fiat-net and the token-net on the pay register — never only the on-chain number — so a tax authority can reconcile the two without a forensic reconstruction.
Conversion timing on pay date
The conversion rate should be captured at a single, repeatable moment on each pay date — the same time, the same provider, ideally the same venue. Many teams use a 4pm UTC snapshot on pay date or a TWAP over the prior 24 hours; what matters most is that the rate is reproducible after the fact and that the choice is documented in the employer's payroll policy. The same rate is used both to convert the net owed to the employee (so the on-chain transfer matches the pay slip) and to book the wage expense the employer recognizes.
Section 2 · United States
IRS treatment and W-2 reporting for US teams.
The IRS treats crypto — including stablecoins — as property, not as currency. Notice 2014-21 is the foundation; Rev. Rul. 2023-14 (cryptocurrency staking) and subsequent guidance extend the same property framing to compensation paid in digital assets. For payroll, the practical consequence is that any compensation paid in stablecoin is taxed as ordinary wages, valued at the USD spot rate at the moment of receipt, and reported on a W-2 in USD.
W-2 Box 1 and the wage base
Box 1 of the W-2 captures federal taxable wages in USD — the figure the employee will compare to their final pay stub. When the wages are paid in stablecoins, the USD-equivalent at the moment of payment becomes both Box 1 and the basis for federal income tax withholding. The employer does NOT report the on-chain token amount on the W-2; the W-2 reflects USD figures only. The token amount and the conversion rate live in the employer's pay register and are retained with the rest of the wage records.
Social Security, Medicare, and FUTA
Wages paid in stablecoin are also subject to FICA withholding under the same rules as fiat wages. Box 3 (Social Security) and Box 5 (Medicare) on the W-2 are keyed off the same USD-equivalent gross used for Box 1, and FUTA applies up to the per-employee wage base. The employer remits the withholding in USD — the payroll tax system has no on-chain settlement option — so the employer converts the withholding amount at the same spot rate used for the on-chain transfer to the employee's wallet.
Year-end payroll register reconciliation
At year end, the employer's payroll register should reconcile line by line with the W-2 totals. Each pay run needs a captured per-row record: (a) the USD-equivalent gross, (b) the conversion rate and source, (c) the on-chain token amount and destination wallet, (d) the withholdings and net, and (e) the on-chain transaction hash. The class-action risk in this space is real — the 2022 IRS John Doe summons to Kraken and the contemporaneous whistleblower enforcement actions both targeted inadequate recordkeeping — so the register is the surface a regulator opens first.
Recordkeeping floor
Retain per-row pay records — conversion rate, on-chain hash, wallet attestation, withholding USD figures — for at least four years from the pay date. Treat them as time-stamped wage records, not as ordinary receipts.
Section 3 · European Union
MiCA in the EU: EMT vs ART classification.
The EU's Markets in Crypto-Assets Regulation (MiCA) — Regulation (EU) 2023/1114 — splits fiat-referenced tokens into two categories. How a token is classified determines who can issue it, who can hold reserves on its behalf, and what redemption rights the holders enjoy. EU employers that pay wages in stablecoins should know which side of that split their rail sits on before they pay the first euro-equivalent.
What most payroll operators will hold
Most EU payroll operators settle in an electronic money token (EMT) — typically a euro-denominated token like EURCV, a regulated issuer's USDC variant on an EU-authorized issuer, or a domestic token issued by an EU credit institution. EMTs are issued by an authorized credit institution or e-money institution, carry a 1:1 reserve in fiat and highly liquid assets, and confer an unconditional redemption right at par against the issuer. For payroll, that means the employer can settle wages in EMT and have a clean story for the auditor: the rail is regulated, the redeemer is solvent, and the token is backed euro-for-euro.
When ARTs complicate things
Asset-referenced tokens (ARTs) cover stablecoins pegged to a value other than a single fiat currency — algorithmic stablecoins, multi-currency baskets, or baskets of crypto assets like ETH plus US Treasuries. ARTs require a Crypto-Asset Service Provider (CASP) authorization under MiCA Title III and follow a more involved whitepaper, governance, and reserve disclosure regime. An employer that pays wages in an ART-class token takes on the CASP due-diligence burden at every pay run — and the whitepaper "redemption at fair market value" language can't be substituted for the par-value redemption an EMT provides.
| Dimension | EMT | ART |
|---|---|---|
| Reserve backing | 1:1 fiat currency; highly liquid assets at par. | Reference value of one or more fiat, commodities, or crypto assets; can be a basket. |
| Issuer authorization | Authorized credit institution or e-money institution under EU rules. | CASP authorization under MiCA Title III; whitepaper approval. |
| Redemption right | Unconditional at par against the issuer, on demand. | At fair market value of the reference asset; terms in the whitepaper. |
| MiCA reference | Title IV, Articles 43–54. | Title III, Articles 17–42. |
| Suitable for payroll | Yes — cleanest story; par-weight payout reconciles with W-2 / payslip. | Possible but heavier — CASP due diligence per pay run, FMV redemptions. |
Algorithmic stablecoins used as ARTs require CASP authorization and a published whitepaper before they can be redeemed at scale. Employers paying in those tokens should retain the whitepaper reference as part of the per-pay-run audit trail.
Section 4 · Audit posture
Employer documentation checklist.
The single most useful exercise before scaling stablecoin payroll is to assemble an audit-ready documentation binder. The list below covers the artefacts a tax authority, regulator, or external auditor will ask for — and the order the team can build them in a single quarter.
What to have on file
- Wallet attestation at onboarding. Each employee signs a written attestation that the wallet they provide is theirs, that they have sole custody of the seed phrase or an equivalent control, and that they understand the employer will only send wages to that address. Retain with the employment file.
- On-chain transaction receipts, ≥ 5-year retention. For every pay run, archive the explorer screenshot, the transaction hash, the block confirmation depth, the sender/receiver addresses, and the token-denominated amount. Treat these as time-stamped wage records.
- FX rate source for the pay date. Document the source — exchange midpoint, a published index, a TWAP — and capture the quote at the moment the rate is "locked" for the pay run. Store a copy of the quote alongside each pay register row.
- W-2 / payslip issued in USD-equivalent. Whether the employee is paid in USDC or USDT, gross and withholdings on the W-2 and payslip are in USD. The on-chain transfer reconciles to the net in USD. Never a token-denominated payslip.
- Jurisdiction-specific AML / KYC record. For each payee, archive identity proof and address proof consistent with the employer's local AML regime. In the US, this aligns with BSA recordkeeping; in the EU, with the AMLD5 / AMLD6 recordkeeping rules.
- MiCA whitepaper reference if paying in an ART. If the rail is an asset-referenced token, retain the approved whitepaper (URL, version, issuer entity) and the CASP authorization reference at the time of each pay run.
- Conversion-rate policy in the employer handbook. Publish the "how we lock the rate" rule in the employee handbook. Anchor it to a single timestamp per pay date and a single source. Avoid using exchange-by-exchange averages without an explicit policy.
- Backup rails and contingency plan. Document the backup pay rail — usually a same-day wire or a US ACH transfer — and the trigger for invoking it. Stablecoin rails occasionally stall for chain-level reasons; the contingency keeps the W-2 timing intact.
- Annual reconciliation of tax filings and pay registers. Reconcile 941s / W-3 totals to the underlying pay register row by row. Sign and date the reconciliation; retain with the year-end file.
- Data-retention schedule. Define the retention horizon — typically four years for US wage records and five to seven years for EU payroll and AML records — and the destruction policy. Stale records are a discovery liability; missing ones are worse.
Hiring in stablecoins? Start with the board.
Coincruit’s /jobs and /gigs boards already index listings on USDC, USDT, DAI, ETH, and BTC rails. If you publish your first listing this quarter, the documentation in this guide covers the compliance posture the listing will need.