The Crypto Contractor Agreement: Clauses, Rate Locks, and the Invoice That Survives an Audit

A contractor invoices you for 4,000 USDT. You send 4,000 USDT. Everyone’s happy until March, when your accountant asks what the deductible expense was in dollars, on what date, at what rate, and from which source — and nobody wrote it down. Now you’re reconstructing a price for a token on a specific afternoon eight months ago, and the number you land on determines both your deduction and, if the contractor is a US person, what goes in box 1a of their 1099-NEC.

That’s the small version of the problem. The large version is that an invoice in USDT is, in the EU, not a valid VAT invoice at all.

Most of what goes wrong with contractor payments in stablecoins goes wrong at the paperwork layer, not the payment layer. The transfer works fine. It’s the six lines of contract language and the eight fields on the invoice that decide whether the arrangement holds up when someone examines it. Here’s what those should say.

Rule one: never denominate in the token

Set the fee in a fiat currency. Name the stablecoin as a settlement method. Never write “Fee: 4,000 USDT” in a contract or on an invoice.

There are three separate reasons, and each is sufficient on its own.

Tax. Under IRS Notice 2014-21, digital assets are property. A contractor includes in income “the fair market value of the virtual currency, measured in U.S. dollars, as of the date that the virtual currency was received.” If the contract is denominated in tokens, the dollar figure is whatever the market says at an arbitrary moment, and both parties are exposed to a valuation dispute over a number neither of them chose.

VAT. Article 226(8) of Directive 2006/112/EC requires an EU invoice to state the taxable amount per rate, and the Court of Justice requires that amount to be capable of expression in monetary terms; Article 230 — while permitting the invoice amounts to be in any currency — requires the VAT amount to be expressed in the member state’s national currency. An invoice denominated purely in USDT doesn’t satisfy either. The taxable amount rule has a helpful backstop: under Article 73, where consideration is non-monetary, the taxable amount is the subjective value the parties actually attributed to it — established in Naturally Yours Cosmetics (Case 230/87) and Argos Distributors (C-288/94). In plain terms, the agreed euro fee is the taxable amount, not some retrospective token valuation. But you only get that benefit if the agreed euro fee exists in writing.

Practical. A fiat-denominated fee makes the payment auditable in one step. “€3,500 invoice, settled in USDC at the ECB rate for the invoice date” is a complete story. “4,000 USDT” is the beginning of a research project.

So: Fee: USD 4,000. Settlement: USDT (TRC-20) to the address specified in Schedule A. Two lines, and most of the downstream mess disappears.

The six clauses that matter

Everything else in a services agreement stays the same. These are the ones that change when settlement moves onto a blockchain.

1. Currency of account and currency of settlement

Separate them explicitly. The currency of account is the fiat currency the fee is expressed in and the obligation is measured in. The currency of settlement is the token. State that a shortfall in fiat value at the moment of settlement remains payable, and that a surplus is not a gift. Otherwise you’ve created an argument about whether an off-peg moment discharged the debt.

2. Rate source and rate lock

This is the clause people skip, and it’s the one that generates disputes. Specify:

• Which rate. A named exchange’s daily close, a named index, or the ECB euro reference rate for USD conversion. Pick one and name it in the agreement.
• Which timestamp. Invoice date, payment initiation, or block confirmation. Block confirmation is the cleanest because it’s independently verifiable by both parties, but invoice date is simpler for monthly retainers.
• How long the rate holds. A rate lock of 24 or 48 hours from invoice issue is standard practice for volatile assets and mostly ceremonial for stablecoins. Until it isn’t. USDC traded to $0.87 during the Silicon Valley Bank weekend in March 2023. A rate lock clause costs nothing to include and covers the one weekend a decade when it matters.

HMRC’s position reinforces the point for UK payers: CRYPTO40100 requires conversion to sterling “at the appropriate rate at the time of each transaction,” using “a consistent methodology,” with records of the valuation methodology retained. HMRC doesn’t tell you which source to use. It tells you to pick one and be consistent, which is a policy decision you make once and then never revisit.

3. Network, address, and who pays gas

Name the network in the agreement, not just in an email. USDT on Ethereum and USDT on Tron are different assets operationally: sending to the wrong chain’s address is how funds get permanently lost. Specify:

• The network (TRC-20, ERC-20, and so on)
• That the address is set out in a schedule and can only be changed by a signed amendment or a defined verification procedure
• Who bears network fees. Default should be the payer. Gas deducted from a contractor’s fee is, in the US, an argument about whether they received the full contracted amount, and if the person turns out to be an employee, fees that reduce effective pay below minimum wage are an independent violation.

The address-change clause is not paranoia. Business email compromise targeting payment details is one of the most common ways companies lose money in this workflow, and “our banking details have changed, here’s a new wallet” is a much easier fraud than intercepting a wire. Require out-of-band verification for any address change, in writing, in the contract.

Our comparison of ERC-20 vs TRC-20 covers which network to specify for which payment size.

4. When the obligation is discharged

Define the moment of payment. Options: on broadcast, on first confirmation, on N confirmations, or on the funds being spendable by the contractor. Pick confirmation on-chain, because it’s the only one both parties can verify independently.

Then add the clause nobody thinks of until they need it: what happens if the transfer is frozen. Tether can blacklist any USDT address, and does so constantly. Its own April 2026 disclosure put the cumulative total at over $4.4 billion frozen across more than 2,300 cases. If a contractor’s address is blacklisted after you send, the payment is on-chain, unrecoverable, and hasn’t reached them. Who bears that? State it. The defensible answer is usually that a payment to an address that is validly blacklisted at the time of sending discharges nothing, and a payment to an address blacklisted afterwards does.

5. Screening and cooperation

Give yourself the contractual right to screen the destination address and to withhold payment pending an alternative address if the screen returns high risk. Without it, refusing to pay a contractor whose wallet has mixer exposure is a breach of contract argument you’d rather not have.

Frame it as a compliance obligation, because that’s what it is. OFAC enforcement is strict liability: a US person can be liable “even without having knowledge or reason to know,” with the IEEPA civil maximum at $377,700 per violation or twice the transaction value, as of the January 2025 adjustment. ShapeShift settled for $750,000 in September 2025 over 17,183 apparent violations, with OFAC’s finding turning on its failure to use the IP-geolocation data it already held to screen for users in sanctioned jurisdictions. Exodus Movement settled for $3.1 million in December 2025 over 254 apparent violations, a non-custodial provider whose support staff helped users in Iran, including by suggesting a VPN.

We’ve covered how that check works in cryptocurrency address screening.

6. Classification language that means something

Every services agreement says the contractor is an independent contractor and not an employee. Courts and revenue authorities ignore that sentence. What they look at is the substance: who controls how the work is done, who bears financial risk, whether the worker has other clients, whether there’s an ongoing integrated relationship.

What you can usefully put in the agreement is language that matches the substance you actually have, the contractor supplies their own equipment, sets their own hours, may accept other engagements, invoices for deliverables rather than time, bears the cost of correcting defective work. If those statements aren’t true, don’t write them. A false recital is worse than no recital.

The stakes are asymmetric with crypto settlement. Section 3509 puts employer liability on reclassification at 1.5% of wages plus 20% of the worker’s FICA share, doubling to 3% and 40% where the required information returns weren’t filed, with no reduced rates at all where the failure was due to intentional disregard. And here’s the multiplier: under 29 CFR 531.27(a) the FLSA requires minimum wage and overtime “in cash or negotiable instrument payable at par.” Crypto is neither. So a reclassified contractor who was paid entirely in USDT is owed the full cash wage again, in dollars, and the tokens you already sent offset nothing.

The EU applies the same substance-over-form doctrine, and Directive (EU) 2024/2831 on platform work adds a presumption-of-employment mechanism that member states are transposing by 2 December 2026.

Model clause language you can copy

Search for a crypto contractor agreement and you will not find one. You will find blog posts describing what the clauses ought to say. Here is the actual drafting language, written to sit inside a standard services agreement. Adapt the bracketed terms, have your own counsel look at it, and stop rewriting it from scratch every engagement.

Currency of account and settlement

The Fee is denominated in [US dollars / euros] (the “Currency of Account”). The Client may discharge the Fee by transfer of [USDC / USDT] on the [Ethereum (ERC-20) / Tron (TRC-20)] network (the “Settlement Asset”) to the address set out in Schedule [A]. The quantity of Settlement Asset transferred shall be calculated in accordance with clause [X] below. Any shortfall between the Currency of Account value of the Settlement Asset received and the Fee remains payable by the Client; any surplus shall be credited against the next invoice and shall not be treated as a gratuity or a waiver.

Rate source, timestamp and rate lock

The applicable conversion rate shall be [the European Central Bank euro reference rate / the daily closing mid-rate published by [named exchange]] as at [the date of issue of the relevant invoice]. That rate shall be binding on both Parties for [48] hours from invoice issue. Where payment is not initiated within that period, the rate shall be recalculated on the same basis as at the date of payment initiation. Neither Party shall be entitled to reopen a completed payment on the basis of subsequent movement in the value of the Settlement Asset.

Network, address and fees

The Contractor’s settlement address and network are set out in Schedule [A]. The Contractor may substitute an address only by written notice signed by [an authorised signatory], confirmed by the Client by a separate channel of communication not used to transmit the notice, and acknowledged by the Client in writing. The Client shall bear all network and gas fees, which shall not be deducted from the Fee.

Discharge of the payment obligation

The Client’s payment obligation is discharged upon [confirmation of the transaction on the relevant network] to the address specified in Schedule [A]. Where that address is subject to a freeze, blacklisting or blocking action by the issuer of the Settlement Asset, by a competent authority or by operation of law at the time of transfer, the obligation is not discharged and the Client shall re-transfer to an alternative address nominated by the Contractor. Where such action is taken after the transfer has confirmed, the obligation is discharged and the resulting loss lies with the Contractor.

Screening

The Client may screen the Contractor’s settlement address against applicable sanctions lists and for exposure to sanctioned entities, illicit finance and high-risk services before each payment. Where screening returns a result that in the Client’s reasonable opinion presents a compliance risk, the Client may withhold payment and shall promptly request an alternative settlement address. Withholding under this clause shall not constitute late payment or breach, provided the Client requests an alternative address within [3] business days.

Wrong-network transfers

Where the Client transfers the Settlement Asset on a network other than that specified in Schedule [A], and the assets are not recoverable by the Contractor, the payment obligation is not discharged and the Client shall re-transfer on the correct network. Where the Contractor supplied an address that was incorrect, incomplete or on a network other than that specified, the payment obligation is discharged to the extent of the transfer and any loss lies with the Contractor.

That last clause exists because the failure is common and the money is usually gone. Which brings us to the thing nobody writes about.

When the payment goes to the wrong chain

USDT on Ethereum and USDT on Tron are separate tokens on separate ledgers that happen to share a ticker. Send one to an address formatted for the other and the outcome depends entirely on who controls the receiving address, which is not something either party thinks about until it happens.

Recoverable, usually. Contractor gave you an Ethereum address; you sent USDT on BNB Smart Chain or Polygon. Both are EVM chains, the address format is identical, and the same private key controls the address on every EVM network. The contractor adds the network to their wallet and the tokens appear. Cost: an evening of confusion.

Recoverable, painfully. You sent to a deposit address at an exchange, on a network that exchange supports for a different asset. Most large exchanges run a recovery process for this. It takes two to six weeks, often carries a fee, and some exchanges decline below a minimum value.

Gone, if the address was never theirs. Ethereum address, Tron network, or the reverse. The address formats differ, but the cryptography doesn’t: Tron uses the same secp256k1 curve and Keccak-256 hashing as Ethereum, so one private key controls the matching address on both chains. A contractor who holds their own key imports it into a Tron-compatible wallet and the tokens appear. It is genuinely unrecoverable where the receiving address was custodial and the key was never theirs to import.

The prevention is procedural rather than clever, and it costs nothing. Ask every contractor to confirm their deposit network in writing once, store it against their record rather than in an email thread, and send a test transfer of a few dollars before the first real payment. That single test has saved more money across this workflow than any clause in this article. Our comparison of ERC-20 vs TRC-20 covers which network to use in the first place.

The invoice: eight fields, no exceptions

An invoice for a crypto-settled engagement needs everything a normal invoice needs, plus four things it doesn’t.

Field 8 is the whole trick. The invoice says €3,500. It does not say “3,500 USDC” as the price.

After payment, three more items attach to the record: the transaction hash with sending address, receiving address, network and token contract address; the block timestamp and the rate as at that timestamp from the named source; and the screening result for the destination address, dated.

Which rate, at which moment

The rate question has four defensible answers and one indefensible one. Pick a row, write it into the agreement, and never vary it.

Block confirmation is the cleanest default because both sides can verify it against a public ledger and a public rate. Invoice date is simpler and fine for stablecoins on a monthly cycle.

What the audit file needs to contain

If an examiner picks one payment at random, this is what should exist for it. The list is short and the failure is almost always that it’s scattered across four systems.

Before payment: signed W-9 or W-8BEN / W-8BEN-E, unexpired; a written statement of where the services are performed; the fiat-denominated services agreement; the screening result for the destination address.

At payment: the invoice; the USD or EUR fair market value at the payment timestamp with the rate source named; the transaction hash and both addresses; your basis in the tokens disposed of.

After year end: the 1099-NEC (US payee at or above $2,000 for tax year 2026, due 31 January), or the 1042-S and 1042 (US-source payments to foreign persons, due 15 March), or a written note of why neither was required.

That last item deserves emphasis. “We filed nothing because the services were performed in Manila and we hold a valid W-8BEN signed 12 March 2026” is a complete answer that ends the conversation. “We didn’t think we needed to” is the answer that starts an examination.

Two things people underestimate. First, the payer has a disposal to account for. Paying a contractor in tokens is simultaneously an ordinary §162 deduction at fair market value and a disposition of property producing capital gain or loss against basis. For a stablecoin bought near $1.00 and spent near $1.00 that’s approximately nothing, but it isn’t automatically zero, there’s no de minimis exemption in current law, and Treas. Reg. §1.1012-1(j) requires wallet-by-wallet basis tracking for acquisitions and disposals from 1 January 2025 with no stablecoin carve-out, and Rev. Proc. 2024-28 is the transitional safe harbor for allocating basis held before that date. UK payers face the same structure through a different door: HMRC treats the payment as a barter transaction, so tokens are disposed of for corporation tax or CGT purposes.

Second, withholding is always a fiat obligation. Backup withholding at 24% where a US payee’s TIN is missing or incorrect, chapter 3 withholding at 30% on US-source payments to foreign persons without a valid treaty claim. You cannot remit tokens to a revenue authority. If you pay entirely in stablecoins, keep a fiat reserve sized to the withholding you might owe, and keep it before the payment goes out.

The full reporting mechanics are in 1099 for foreign contractors.

Where the contractor’s own rules bite

A clause that works for you can create a problem for them, and a contractor who gets into trouble with their own tax authority stops being your contractor.

India is the hardest. Export-of-service proceeds must be realised through an Authorised Dealer bank within nine months for exports made up to 30 September 2026, and within fifteen months once the FEMA (Export and Import of Goods and Services) Regulations, 2026 take effect on 1 October 2026, evidenced by a FIRC. A wallet transfer produces none, which also puts GST zero-rating at risk. Tax runs in two stages: slab rates on receipt as professional income, then a flat 30% under section 115BBH on any conversion gain, with no expense deduction and no loss set-off.

The Philippines is straightforward for a freelancer under ₱3m gross receipts: elect the 8% flat option in lieu of graduated rates and the 3% percentage tax, convert through a BSP-licensed VASP, no FX surrender requirement. Above ₱3m, VAT zero-rating on exported services needs a Certificate of Inward Remittance that a wallet transfer doesn’t generate.

Brazil brought virtual assets inside the FX regime from 2 February 2026 under central bank Resolutions 519–521: cross-border payments settled in virtual assets are FX operations, only BCB-authorised PSAVs may intermediate, a restriction that bites from 30 October 2026 when the authorisation window closes, and there’s a USD 100,000 per-transaction cap where the counterparty isn’t authorised for FX.

Inside the EU, USDT is the wrong choice regardless of the contractor’s country. It’s a non-compliant e-money token under MiCA, ESMA required EU service providers to complete a sell-only wind-down by 31 March 2025, and the transitional period ended 1 July 2026. Use USDC or EURC, EURC additionally removes the FX conversion from the equation entirely, which makes the invoice and the settlement the same number. Our MiCA guide has the framework.

Ask contractors what their accountant needs. Most of the time the answer is a properly formatted invoice in a fiat currency plus proof of the transfer, which costs you nothing beyond doing what’s described above anyway.

Making it operational

None of this is hard for one contractor. It gets hard at forty, across three continents, twelve times a year, when the invoice lives in email, the screening result lives in a compliance tool, the transaction hash lives in a block explorer tab somebody closed, and the ledger entry lives in accounting software that has never heard of a wallet address.

The fix is structural rather than clever: put the invoice, the screening result, the payment and the ledger entry on the same record, and give the person who builds a payment run different permissions from the person who approves it. Write the six clauses once. Build the invoice template once. After that the work is just running it.

Frequently Asked Questions

Should a contractor invoice in USDT or in dollars?

In dollars, or euros, or whatever fiat currency the fee is agreed in. The token amount appears on the invoice as a derived settlement quantity, not as the price. Invoicing directly in USDT creates a valuation dispute and, in the EU, fails the Article 226 requirement that the taxable amount be expressed as a monetary amount and the VAT amount in the member state’s national currency.

What should a crypto contractor agreement include that a normal one doesn’t?

Six additions: separate currency of account from currency of settlement; a named rate source, timestamp basis and rate-lock period; the network, destination address and who bears gas fees, with an out-of-band verification requirement for address changes; a definition of when the payment obligation is discharged, including what happens if the address is frozen; a right to screen the destination address and withhold pending an alternative; and classification recitals that match the actual substance of the relationship.

What exchange rate should I use for a crypto contractor payment?

Whichever one you name in the agreement and then apply consistently. HMRC requires “a consistent methodology” with records of it retained, and doesn’t prescribe a source. For euro conversions, the ECB euro reference rate for the relevant date is defensible and independently verifiable. The important thing is documenting the policy once and not varying it between payments.

Is a crypto invoice legally valid?

Yes, provided it meets the same requirements as any other invoice in the relevant jurisdiction. For EU cross-border B2B that means the Article 226 fields, sequential number, issue date, both parties’ details and VAT numbers, description and date of supply, taxable amount as a monetary amount, and the VAT amount or reverse-charge annotation. The crypto-specific fields sit alongside those, not instead of them.

Who should pay the network fee on a contractor payment?

The payer, in almost all cases. Deducting gas from the contractor’s fee raises the question of whether they received the contracted amount, and if the relationship is ever reclassified as employment, fees reducing effective pay below the minimum wage are an independent violation. Network costs are small on every chain in normal conditions: well under a cent on Polygon, roughly $2 on Tron since Proposal #104 cut the energy price, and about ten cents on Ethereum at current gas levels. That is a reason to specify the network rather than to shift the cost.

What happens if the contractor’s wallet gets frozen after I send?

Contractually, whatever your agreement says, which is why it should say something. Tether’s blacklist function reverts all transfers from a listed address, and recovery is unusual: BlockSec’s on-chain analysis found 3.6% of blacklisted USDT addresses unfrozen in 2025, with a median release of 18.2 days, and over the same period the volume of USDT permanently destroyed ran at about 56% of the volume newly frozen. The defensible default is that a payment to an address validly blacklisted at the time of sending discharges nothing, while a subsequent freeze is the contractor’s risk.

Does paying a contractor in crypto affect whether they’re classified as an employee?

Legally, no. Neither the IRS common-law test nor the FLSA economic-reality test lists the medium of payment as a factor. It sits inside the IRS’s financial control category as a minor evidentiary point. What crypto changes is the cost of a reclassification: crypto counts as zero toward minimum wage and overtime under 29 CFR 531.27(a), so you’d owe the cash wage again in dollars on top of what you already paid.

What happens if I send USDT on the wrong network to a contractor?

It depends on the pair. Between EVM chains, Ethereum, BNB Smart Chain, Polygon and Arbitrum, the same private key controls the address on all of them, so the contractor adds the network in their wallet and the tokens appear. To an exchange deposit address, most large exchanges run a recovery process taking two to six weeks, usually for a fee. Between Ethereum and Tron the address formats differ and no key spans both, so the tokens are unrecoverable. Send a test transfer before the first real payment.

Can a contractor refuse to be paid in crypto?

Yes, unless they’ve agreed otherwise in the services agreement. Consideration is a term of the contract, so a contractor who signed up to be paid in USDC has agreed to it, and one who didn’t hasn’t. This is why the settlement clause belongs in the agreement rather than in an email, and why changing the settlement asset mid-engagement needs a written amendment.

What records do I need to keep for a crypto contractor payment?

Ten items: the signed W-9 or W-8, the place-of-performance statement, the fiat-denominated agreement, the pre-payment screening result, the invoice, the fair market value at the payment timestamp, the named rate source, the transaction hash with both addresses and the network, your token basis for the disposal, and the year-end filing or a written note of why none was required. Withholding agents should retain information returns, or be able to reconstruct them, for at least three years after the reporting due date. See crypto bookkeeping for the ledger structure.

Take your current contractor template and add six clauses to it: currency of account separate from settlement asset, a named rate source with a timestamp basis, network and address with out-of-band change verification, the moment of discharge including the frozen-address case, a screening right, and wrong-network allocation. Copy the drafting language above, fill in the brackets, and send it to counsel once rather than per engagement. Then fix the invoice template so the fee reads in euros or dollars and the token amount reads as arithmetic underneath it. Before the first payment to anyone new, screen the address and send a test transfer of a few dollars on the network they named. That sequence, done once, is the difference between a five-minute answer to an examiner and a three-month reconstruction. VaultNow keeps the invoice, the AML screening result and the payout on the same record, with batch payouts of up to 100 recipients at $0.50 per transaction plus gas, so the audit file assembles itself instead of being rebuilt from a block explorer in April. The operational walkthrough is in paying contractors in USDT, the rail comparison in paying international contractors, the employee boundary in paying employees in cryptocurrency, and the books side in crypto accounting for business.

General information on how these rules work, not legal or tax advice. Positions are stated as at 26 August 2026; rates, thresholds and filing dates change, and the right answer turns on facts specific to you. Check the current text of anything cited here with your own adviser before acting on it.