Paying and getting paid in stablecoins: evidence, matching and controls

How to settle invoices in stablecoins cleanly: what proves payment, how to handle fees and short-pays, and the sanctions checks that apply.

2026-10-17 · 6 min read

Stablecoins make cross-border invoices faster, but the ledger still has to prove who paid what, for which invoice, at what value. Treat a stablecoin payment like a wire with extra evidence: a transaction hash in place of a bank reference, and a token you have to value and track.

First, what the stablecoin is on your balance sheet

This drives how the payment is recorded. Under IFRS, the Interpretations Committee concluded in 2019 that cryptocurrencies are not cash; its analysis covered tokens that give the holder no contract with another party [6]. Many fiat-backed stablecoins do give a redemption claim on the issuer, so they need their own analysis, and practice varies.

Under US GAAP, ASU 2023-08 fair value accounting only covers tokens that give no enforceable right to underlying goods, services or other assets [5], so redeemable stablecoins are generally outside it. In August 2026 the FASB proposed guidance on when certain digital assets can be cash equivalents. Its examples turn on an on-demand contractual right to redeem for cash, a direct redemption right with the issuer for known amounts, and segregated reserves of at least one-to-one in short-term liquid assets [1]. Comments are due November 19, 2026 [1]. As of October 2026 this is a proposal, not GAAP.

What counts as settlement evidence

For each stablecoin receipt or payment, keep a packet that someone outside the team could follow:

• The transaction hash, chain, token contract address, amount and block timestamp.
• The sending and receiving addresses, and how you know the counterparty controls theirs (a signed invoice showing the address, a verified address book entry, or a test transfer).
• The invoice or bill it settles, with the remittance advice that links them.
• The rate used to convert to your functional currency, if the token is not pegged to it, with source and timestamp.
• Approval evidence for outgoing payments, such as the multisig signatures.

Check the token contract address, not just the ticker. Look-alike tokens with the same symbol are common, and a payment in the wrong token is not a payment.

Matching payments to invoices

On-chain transfers rarely carry a reference. Matching works best when you design for it: give each customer a dedicated receiving address, or ask for a unique amount or a remittance email with the hash. Expect three recurring exceptions.

• Short-pays: the customer deducts their network fee or sends a rounded amount. Agree in the contract who bears fees, then book the gap as a fee or a dispute, not a silent write-off.
• Wrong chain or token: the same stablecoin can exist on several chains. State the accepted chain and contract on the invoice.
• Overpayments and duplicates: hold them as a liability to the customer until refunded or applied.

Peg, FX and tax

If your functional currency differs from the coin's peg, convert at the rate on the transaction date and record the source. If the coin trades away from its peg at the time, record the observed price rather than assuming par, and flag it for review.

For US tax, paying for goods or services with virtual currency is treated as disposing of property, with gain or loss measured against your basis [4]. With a stablecoin bought at par the result is usually near zero, but it still exists and should be computed by lot.

Sanctions and the travel rule

Sanctions apply the same way to crypto as to fiat. OFAC says US persons, explicitly including users of digital currencies, must block property of listed persons, and recommends a risk-based compliance program with screening [2]. OFAC publishes some wallet addresses on its sanctions list but warns the list of addresses is not likely to be exhaustive [2]. Blocked virtual currency must be reported within 10 business days [2]. Screen counterparty names and addresses before paying and before accepting a new customer's payment address.

The travel rule binds regulated firms rather than ordinary businesses, but it affects you when an exchange or custodian is on either side. FinCEN's 2019 guidance says crypto transmittals of $3,000 or more can trigger the Funds Travel Rule for money transmitters, requiring them to collect and pass on sender and recipient information [3]. Expect your custodian or exchange to ask for beneficiary details, and keep them ready on vendor records.

What to do

• Write accepted tokens, chains and contract addresses onto every invoice and vendor record.
• Verify new counterparty addresses with a test transfer or signed confirmation, and screen them.
• Agree in contracts who pays network fees, and how short-pays are handled.
• Store hash, timestamp, value source and invoice link for every settlement.
• Track the FASB cash-equivalents proposal and revisit stablecoin classification once it is final.

Sources

1. Proposed ASU, Statement of Cash Flows (Topic 230): Cash Equivalents - Disclosure Enhancement and Evaluation of Certain Digital Assets (FASB)
2. Questions on Virtual Currency (OFAC, US Treasury)
3. FIN-2019-G001: Application of FinCEN's Regulations to Certain Business Models Involving Convertible Virtual Currencies (FinCEN)
4. Frequently asked questions on virtual currency transactions (IRS)
5. ASU 2023-08 Intangibles - Goodwill and Other - Crypto Assets (Subtopic 350-60) (FASB)
6. Holdings of Cryptocurrencies - June 2019 (agenda decision) (IFRS Interpretations Committee)

General information for finance teams, current as of publication. Not legal, tax or accounting advice.

All Newsroom explainers