Bitcoin and Stablecoin Payments for Tax & CPA Firms: A 2026 Compliance Guide

Every busy season, more CPA firms field the same calls. A client who reported $40,000 in capital gains wants to settle the fee in USDC. A boutique preparer in Miami gets asked by an offshore client whether the firm can invoice in stablecoins instead of waiting on a wire. By 2026, the IRS digital asset question on Form 1040 has been in place for seven filing seasons.

This guide is for partners, sole practitioners, and operations managers at CPA, tax preparation, and accounting practices weighing crypto fee invoicing. We cover the IRS and AICPA framework, the volatility-versus-reasonable-fee tension, custodial and non-custodial gateways, and a four-step setup. None of it substitutes for your state board of accountancy’s ethics opinion.

The CPA market shift: crypto-native clients and Web3 tax demand

The IRS first added a digital asset question to the 1040 in 2019 on Schedule 1. By tax year 2022 it had moved to the front of the form, broadened to cover receipts, sales, exchanges, and gifts, and become mandatory for every filer. That change put crypto inside the workflow of every U.S. tax preparer.

The downstream effect is concrete. CoinTracker and Koinly each report user bases in the seven figures, and most of those users still bring their reports to a human preparer. DeFi yield, NFT royalties, staking income, and airdrops generate reportable events that consumer software handles imperfectly. CPAs then reconcile cost basis lots, classify hard-fork receipts under Revenue Ruling 2019-24, and prepare the Form 8949 entries the tools missed.

Those clients then ask whether they can pay in the same assets. For a client whose treasury sits in USDC on a hardware wallet, paying a $4,500 invoice on-chain takes minutes. Wiring the same fee from an exchange off-ramp to a U.S. bank takes three to five business days and $25 to $40 in wire fees.

Three reasons tax firms are adding crypto invoicing in 2026

The drivers behind firms accepting crypto fees over the past two filing seasons are practical.

Cross-border and Web3-heavy client bases prefer stablecoin settlement

Firms with niches in token issuance, fund formation, or expat filings now field engagements from clients who hold most of their working capital on-chain. Those clients would rather wire USDC from a multisig treasury than off-ramp through Coinbase, transfer to a domestic bank, and ACH the firm. For an $8,000 international engagement, accepting USDC directly removes three intermediaries and shortens collection from a week to under an hour.

Disputed retainer chargebacks during tax season

Firms accepting credit card retainers sometimes encounter clients who dispute the charge after the return is filed. Visa and Mastercard chargeback processes generally favor the cardholder in service disputes, and the firm bears the documentation burden. During the February-through-April crunch, defending a chargeback while finishing fifty other returns is the wrong use of a partner’s time. Crypto transactions, once confirmed on-chain, are not reversible by the network. That removes one channel that bypasses the firm’s fee dispute process.

Reduced reliance on banks for offshore client billing

Firms serving U.S. expats, foreign nationals with U.S. tax obligations, or international fund clients find correspondent banking slower than five years ago. Stablecoin transfers do not eliminate the firm’s KYC, AML, or 1099 obligations, but they cut the bank-side delay and FX spread on small-to-medium engagements. A $3,500 invoice to a São Paulo client clears in minutes, with single-digit network costs rather than $40 in wire fees plus 1.5% to 2.5% in FX spread.

AICPA and IRS framework for accepting crypto fees

The regulatory picture has two sides: federal tax law on the income side, AICPA professional conduct rules plus state board regulations on the practice side. Neither is hostile to crypto fee acceptance. Each imposes documentation and conduct standards to internalize before going live.

IRS Notice 2014-21: income recognition at fair market value on receipt

The foundational guidance is IRS Notice 2014-21, which classifies virtual currency as property for federal tax purposes. The practical implications:

• The fee is ordinary income at the fair market value of the cryptocurrency in U.S. dollars on the date of receipt.
• If the firm later sells or converts, the difference between disposition price and value at receipt is a capital gain or loss.
• The firm must keep records of receipt date, fair market value at receipt, and disposition date and price for each crypto fee, on a per-lot basis.

Holding received cryptocurrency for any meaningful period creates a small but real second-order bookkeeping burden. Firms that prefer simplicity convert stablecoins to dollars promptly after receipt, keeping gain or loss exposure close to zero.

Form 8300 reporting threshold for cash and digital asset receipts

The Bank Secrecy Act requires a trade or business that receives more than $10,000 in cash in a single or related transactions to file Form 8300 within fifteen days. The Infrastructure Investment and Jobs Act of 2021 amended Section 6050I to extend that requirement to digital asset receipts above the same threshold. Treasury and IRS issued transitional guidance in Announcement 2024-4 deferring the digital-asset obligation pending final regulations. As of early 2026 the framework is still in active rulemaking. Cash receipts above $10,000 still trigger a Form 8300 filing. Digital asset receipts above $10,000 should be tracked with the same rigor in anticipation of final rules.

State CPA board ethics rules and the AICPA Code of Professional Conduct

The AICPA Code does not address cryptocurrency fee acceptance directly. The relevant standards are general: integrity and objectivity, restrictions on contingent fees, and the expectation that fees be reasonable and disclosed. Several state boards have published informal guidance through CPE materials, but the state-by-state picture varies. California is more permissive than New York, for example, but neither has issued a binding rule. Treat your state board’s posture as the binding constraint and the AICPA Code as the floor underneath. If your state board has issued a position paper, follow it. If not, document a firm policy that satisfies the general AICPA standards and have it reviewed before launch.

Why stablecoins resolve the volatility-versus-reasonable-fee tension

The biggest professional-conduct concern with accepting Bitcoin or Ether for fees is volatility. The AICPA’s reasonable-fee standard, mirrored in most state board rules, holds that a fee cannot become unreasonable simply because the underlying asset appreciated between receipt and earning. A $5,000 invoice paid in BTC on January 15 that doubles by April 15 raises an obvious question about whether the firm is collecting a reasonable fee or a speculative windfall.

Stablecoins side-step that problem. USDC and USDT are dollar-pegged tokens designed to hold a 1:1 relationship with the U.S. dollar. A $5,000 invoice paid in USDC is, for practical purposes, $5,000, minus de minimis depeg risk that historically holds within fractions of a percent for major issuers.

Fee economics matter too. A typical credit card processor charges roughly 2.9% plus a fixed per-transaction fee, with cross-border surcharges raising the effective rate to 3.5% or higher. Aurpay charges 0.8% per transaction with no monthly minimum, no setup fee, and no FX spread on stablecoin payments. On a $5,000 invoice that is roughly $40 in network costs versus $145 to $175 on a credit card. The difference bears on the reasonable-fee analysis on its own.

Non-custodial vs custodial models for client trust accounts

Read this carefully if your firm holds client funds in trust. That comes up in M&A advisory, transaction-fee escrow, or tax controversy work involving IRS deposits on the client’s behalf.

A custodial crypto gateway receives the client’s payment into the gateway’s own wallets, holds it through a settlement window, and forwards it later. From a fiduciary-segregation perspective, that raises questions. Whose property is it during the window? What happens if the gateway becomes insolvent? Is the structure consistent with the firm’s duty to safeguard client funds?

A non-custodial gateway routes payment directly from the client’s wallet to a wallet the firm controls. The gateway generates addresses, watches the chain, and sends a webhook, but never takes possession. The firm holds its own private keys. No third-party balance, no settlement queue, no withdrawal limits.

For CPA firms that handle client trust funds, the non-custodial model maps more cleanly onto fiduciary-segregation doctrine. Earned amounts route to the operating wallet. Unearned or escrowed amounts sit in a segregated trust wallet, the same flow as a wire received into a segregated bank account, on different rails. For a deeper architectural comparison, see our walkthrough of non-custodial versus custodial gateway trade-offs.

U.S. trust account doctrine for accountants was written for fiat in domestic bank accounts, and most state board guidance lacks explicit rules for cryptocurrency held in trust. Do not treat any crypto gateway, including a non-custodial one, as a turnkey trust-account solution. The firm remains responsible for a documented policy that satisfies its state board.

Setting up crypto invoicing at your firm in 4 steps

The technical setup is the easy part. Most firms can send their first crypto invoice within an afternoon. The harder work, drafting the engagement letter language and receipts policy, sits with the partners and should be done first. For comparable thinking on stablecoin invoicing in adjacent practices, see our stablecoin invoicing guide for solo practitioners and consultants.

Step 1: Choose how clients will pay

Three patterns cover most use cases:

• Crypto Invoice by email or SMS link. The firm sends an invoice as a link, the client opens it, picks a currency, and pays from their own wallet. Funds settle directly into the firm’s wallet. Best for tax preparation engagements, advisory retainers, and milestone billing.
• Hosted Checkout page. A no-code payment page shared by URL. Useful for one-time work such as a Form 1040X amendment, an offer-in-compromise filing fee, or an audit representation deposit.
• WordPress and WooCommerce billing portal. For firms running a client portal on WordPress with WooCommerce for productized billing (flat-fee S-corp formations, bookkeeping subscriptions, expat tax packages), the Aurpay WooCommerce plugin adds crypto as a checkout option alongside existing methods.

Step 2: Set up your wallets

Two wallets are typical: an operating wallet for earned fees and a segregated trust wallet for retainers, escrow deposits, or advisory-engagement client funds. Both should be firm-controlled with documented signatory access, ideally under multi-signature controls if the firm already uses multisig for its bank signatories. Extend internal controls documentation to cover wallet custody, signatory rotation, and partner departures.

Step 3: Connect the gateway and configure currencies

In Aurpay’s merchant dashboard, connect the operating wallet and configure which currencies to accept. A practical default for most CPA firms in 2026:

• USDC (ERC-20). Dollar-pegged, most commonly held by U.S. corporate clients and digital-asset fund treasuries.
• USDT (TRC-20). Dollar-pegged, most commonly held by international and Asia-based clients, with lower network fees than the Ethereum version.
• BTC. Optional, where firm policy permits non-stablecoin fee receipts.

Many firms limit the early supported list to USDC and USDT. Dollar-pegged stablecoins sidestep the reasonable-fee volatility issue. Aurpay’s full list includes BTC, Bitcoin Lightning, ETH, USDT (ERC-20 and TRC-20), USDC (ERC-20 and TRC-20), DAI (ERC-20), and BNB. Setup is instant onboarding without bank-style verification; the firm remains responsible for client KYC where applicable.

Step 4: Document the policy and update engagement letters

Before the first crypto invoice goes out, update the engagement letter template to address: which currencies the firm accepts, how the fee is valued (typically U.S. dollars at the time of receipt, citing Notice 2014-21), how refunds of unearned amounts are handled, and any state-specific disclosures. Have your firm’s general counsel or an external ethics consultant review this language first.

Tax season operations: bulk invoicing, refunds, year-end reconciliation

For a firm preparing 200+ individual returns in a season, operations matter as much as policy.

Bulk invoicing. Firms with high-volume repeat clients issue invoices in batches once the engagement letter is signed. The Crypto Invoice product supports individual payment links per client. WooCommerce-based firms get the crypto option automatically on each invoice. Some firms use the REST API to generate payment links from the same workflow that sends the engagement letter.

Refunds for over-billed clients. When an estimated fee exceeds actual time billed, refund the difference. Crypto transactions cannot be reversed by the network, but they can be sent back: the firm initiates a new transaction to the client’s wallet. Document the refund decision, rate used, and matter or invoice number as you would a refund check. For recurring clients, crediting the over-billed amount to the next engagement avoids a second on-chain transaction and cost-basis event.

Year-end reconciliation in QuickBooks or Xero. Book crypto fees as income at fair market value in dollars on the date of receipt, recording receipt date, asset, on-chain transaction hash, and dollar value. If the firm holds crypto rather than converting promptly, gain or loss on subsequent disposition is a separate entry tagged to the same lot. Add a dedicated income account and an asset account per wallet so on-chain reconciliation is straightforward at year end.

What this guide does not replace

This article is informational content for decision-makers at CPA, tax preparation, and accounting firms. It is not legal advice, tax advice, or an ethics opinion. It does not certify any gateway, including Aurpay, as compliant with any state board’s conduct rules, the AICPA Code, or trust-account expectations. Consult your state CPA board’s ethics opinion before going live. This article is general guidance, not legal advice. For the law-firm equivalent including the state-bar trust analysis, see the legal services version of this playbook. For broader gateway selection criteria, see our crypto payment gateway comparison guide.

Disclaimer: This article is informational content for CPA, tax preparation, and accounting practices evaluating crypto payment acceptance. It is not legal advice, tax advice, or an ethics opinion. AICPA professional conduct rules and state board regulations vary by jurisdiction, and the federal framework for digital-asset reporting under Section 6050I remains in active rulemaking. Consult your state board’s guidance and your firm’s general counsel before accepting cryptocurrency for professional fees. Tax treatment described here is based on IRS Notice 2014-21, Revenue Ruling 2019-24, and Announcement 2024-4 as of the publication date; consult a qualified tax advisor for application to your specific facts.