Stablecoin treasury management: what a CFO does with USDT once customers pay

When customers pay in USDT, stablecoin treasury management lands on the finance team as five jobs:

• Matching. Tie every incoming payment to an invoice.
• Suspense. Park anything that doesn't match.
• Holding or converting. Set a rule for how much USDT stays as USDT and how much becomes fiat.
• Custody. Keep the balance where one failure can't take all of it.
• Approvals. Decide who can send it out.

On top of that sits one risk a bank account doesn't carry: the issuer can freeze tokens at an address. Stablecoin payments for CFOs come down to these jobs plus one conversation with the accountant about the balance sheet.

This guide starts where checkout ends: the money has landed and someone has to own it. If you don't accept stablecoin payments yet, start with how a crypto payment gateway gets connected and what it really costs.

How to reconcile stablecoin payments with invoices and orders

A bank transfer comes with a payer name and a reference field. A USDT transfer has neither. On the blockchain you see a sending address (a string of letters and digits), an amount, a network, a time and a transaction hash, which is the transfer's unique receipt number. Nothing in it says "invoice 1043".

That gap is the main difference finance teams notice once they compare crypto payments with bank transfers on fees and speed. The fix is to link the payment to the order before the customer sends it, not after.

There are three common ways to do it:

• A unique address per invoice. The payment processor or wallet software creates a fresh receiving address for each order, so whatever lands there belongs to that order. This is the most reliable method and the one most payment processors use.
• One address per customer. Each regular customer gets a permanent deposit address. It works for B2B clients who pay monthly, but you still have to split one transfer across several invoices by hand.
• One shared address. Every customer pays to the same address and you match by amount and time. This breaks as soon as two customers pay 100 USDT in the same hour, so we don't recommend it beyond a handful of payments a month.

Whichever method you use, record the same five fields for every payment: order number, transaction hash, network, amount received and the time it was confirmed. The network matters more than it looks. USDT exists as separate tokens on TRON, Ethereum and other chains, so a transfer on the wrong network never reaches your address. Ops staff should know which USDT formats exist and which one the business accepts.

Gross, net and the fee in between

The customer pays 100 USDT, but your balance may show less. The payment processor takes its fee, and the network charges its own fee whenever you move the money on.

Book the sale at the invoiced amount and the processor's cut as a payment expense, the same way you treat card fees. Then the revenue line matches the invoice and the bank-style reconciliation still works. The pieces that make up the difference are explained in how network fees, gas and gateway fees work.

What your processor's data should give you

Any processor you use should send your system a status for each payment and a final amount credited after fees. Ask two questions: at which status is the money actually yours, and which field holds the net amount?

At CryptumPay, statuses come by webhook (an automatic message from the processor to your server): created → pending → crediting → finished. The income field, which is the amount credited after all fees, is present only in the finished webhook. So the rule for your ledger is simple: post the payment when finished arrives, and take the net figure from income.

What to do with a payment you can't match

Some payments won't line up with anything. A customer sends 98 USDT instead of 100 because their exchange took a withdrawal fee. Someone pays an invoice that already expired. A client pays two invoices in one transfer. Money arrives from an address nobody recognises.

Most of these start at checkout, and the usual causes of failed and short crypto payments are worth fixing there. Some will still reach finance, so write the handling down before the first one does:

1. Park it in a suspense account. A suspense account is a holding line in the ledger for money you've received but can't allocate yet. The payment is recorded, the order stays open, and nobody guesses.
2. Set a tolerance. Agree with your accountant on a small shortfall you'll accept and write off, so a customer isn't chased over a dollar. Anything above it goes back to the customer as a request to pay the rest.
3. Ask the customer for proof. The transaction hash and the order number are enough to match a transfer for certain. Don't match on "it's probably them".
4. Never refund to the sending address by default. Many customers pay from an exchange, and the sending address belongs to the exchange, not to them. Money sent back there can be lost. Refund only to an address the customer names in writing, on the same network.
5. Put a deadline on it. Decide how long an unclaimed payment stays in suspense and what happens after that. Ask the accountant, because unclaimed money has its own rules in many places.

Stablecoin treasury management: should you convert USDT to fiat right away or hold it?

USDT tracks the US dollar, so holding it isn't a bet on crypto prices. For a business that reports in dollars, a USDT balance behaves much like a dollar balance, with three extra risks: the issuer, the peg and the place you keep it.

For a business that reports in euros or pounds, holding USDT also means holding dollars. That exposure to the exchange rate is the same one you'd have with a USD bank account.

The case for converting quickly is simple: payroll, rent and tax are paid in fiat, and fiat in a bank carries none of those three risks. The case for holding is just as practical. Some businesses pay contractors or suppliers in USDT, and converting to fiat only to buy USDT back later costs two spreads. If that's you, look at whether suppliers abroad can be paid in stablecoins before you set the policy.

Most finance teams land on a middle rule:

• Keep a working buffer. Hold enough USDT to cover the outgoing payments you actually make in USDT over the next few weeks.
• Sweep the rest on a schedule. Convert everything above the buffer daily or weekly, so the balance at risk never grows with sales.
• Set a ceiling. Put a hard cap on the USDT balance. When it's crossed, someone converts, whatever the calendar says.

The stablecoin keeping its dollar value is an assumption, not a promise. Before you pick a buffer size, read what happens to a business when a stablecoin loses its peg, meaning its price slides away from one dollar.

What converting actually costs

Converting means selling USDT for dollars or euros on an exchange or through a broker, then withdrawing to the bank. You pay a trading fee or spread, a network fee to move the USDT, and sometimes a bank fee on the incoming wire. Those costs belong in the total cost of taking payments, next to what drives online payment fees and how businesses cut them.

Going straight to Tether, the company that issues USDT, is rarely an option for a merchant. Tether redeems only for verified customers, with a minimum of 100,000 USD and a fee of 0.1% or 1,000 USD, whichever is greater.

When customers pay in coins other than USDT

If your checkout also takes bitcoin and other coins, the first treasury question comes before any of this: how long does a volatile coin sit on your books before it becomes something stable? The shorter, the better, and the ways to protect crypto takings from market swings all come down to shrinking that window.

At CryptumPay, incoming payments are converted to USDT as soon as they arrive: "Converted as soon as it arrives, so your balance never sits in a volatile coin." For the finance team this means one asset to reconcile and one hold-or-convert policy, whatever the customer paid with.

Where should a company hold stablecoins?

There are four places a business can keep USDT. Each one carries a different counterparty risk, meaning the chance that whoever holds the money for you fails or blocks it:

• A crypto exchange account. Converting to fiat is quick and easy. But the balance is a claim on the exchange, and if the exchange fails, you're a creditor. Exchanges can also freeze accounts during a compliance review. In the EU, exchanges licensed under MiCA, the EU's crypto rulebook, no longer let EU customers trade USDT because Tether isn't authorised there. ESMA, the EU markets regulator, set that deadline for the end of the first quarter of 2025. Holding and transferring USDT is still allowed.
• A custodian. A regulated custodian holds the assets for you, usually separated from its own money, and adds insurance and audit reports. You pay fees and go through onboarding, and it makes most sense once balances are large.
• The payment provider's balance. It's convenient because money waits where it landed. But a payment provider isn't a bank, so the balance is only as safe as that company. Read its terms on withdrawals and freezes, and treat this as a transit account rather than a vault.
• Your own wallet. Self-custody means the company holds the private keys, the secret codes that authorise transfers. No third party can fail on you. But losing a key, or one employee holding it alone, can cost everything, and the company carries that operational risk itself.

A sensible setup for a growing business uses more than one of these. The provider balance is where payments land. A company-controlled wallet or custodian holds the working buffer. The bank holds the rest.

"Company-controlled" still leaves the main decision open: whether one person holds the key or several people must sign each transfer together. Two things settle it: how many people move money and how much sits in the wallet. Between them, they decide which crypto wallet setup suits a business of your size.

What happens to company funds if the issuer freezes the address?

The USDT smart contract, the program that keeps track of everyone's balances, lets Tether block a specific address. Once an address is frozen, tokens at that address can't be moved at all. Nobody at your company can override this, and neither can your wallet provider.

Tether's terms of service let it freeze tokens where the law requires it and where it decides freezing is prudent. In practice freezes follow sanctions lists and law-enforcement requests about stolen or criminal money. In the US, the GENIUS Act, signed on 18 July 2025, makes this an obligation rather than a choice. Every issuer of payment stablecoins, foreign ones included, must be technically able to freeze and seize tokens and must comply with lawful orders. The act takes effect no later than 18 January 2027.

For an honest merchant the realistic risk is indirect. A freeze targets an address, not a person. If a customer pays you with stolen funds and investigators trace the money to your receiving address, your address can end up on the list, along with every legitimate payment sitting there.

A few habits keep that risk small:

• Screen incoming payments. Blockchain analytics tools flag transfers from sanctioned or stolen-funds addresses, and some processors run this check for you. Ask yours whether it does.
• Move money off receiving addresses. Sweep regularly from the address customers pay into to a separate treasury wallet. Then one bad payment can't trap your whole balance.
• Split balances across addresses and custodians. No single address should hold more than you could afford to have locked for months.
• Keep your records. Order numbers, customer identity and transaction hashes are what you'll need to show Tether and your lawyers that the funds are legitimate. Getting frozen funds released is a request to the issuer, not a button you can press, and it takes time.

The same logic applies to issuer risk in general. A business that holds all its stablecoin reserves in one token depends on one company. That's one reason to understand how USDT and USDC differ as payment stablecoins, even if you only accept one of them.

Who in the finance team controls stablecoin wallets and approves withdrawals?

A crypto transfer can't be reversed or recalled. A bank can sometimes stop a wire sent by mistake, but a blockchain can't. So the controls that matter all sit before the money moves:

• Split the roles. One person prepares a withdrawal, a second approves it and a third reconciles it afterwards. This is the same segregation of duties you use for bank payments, applied without exceptions.
• Require several signatures. A multisig wallet needs, for example, two of three authorised keys to sign a transfer, so no single person can move funds alone. On Ethereum this is done with smart-contract wallets, and TRON has multi-signature permissions built into its accounts.
• Whitelist destination addresses. Withdrawals go only to pre-approved addresses, such as your exchange account or supplier wallets. Adding a new address takes its own approval and a small test transfer first.
• Set limits. Put a daily ceiling on withdrawals, and require an extra approver above a certain amount.
• Lock down API keys. If software withdraws automatically, give the key only the permissions it needs and restrict the servers it can be used from.
• Plan for people leaving. When someone with signing rights leaves, remove their key the same day and review every whitelisted address they added.

Ask any payment provider how withdrawals work and what protects them. At CryptumPay, withdrawals are available any time with no minimum amount, in manual and automatic modes. A manual withdrawal from the dashboard needs no IP allowlist. A withdrawal through the API (POST /v1/withdraw) requires an IP whitelist configured for the API key, so a stolen key alone can't send money from an unknown server.

How stablecoins land on the balance sheet, and what to settle with the accountant

The short answer for most businesses today: USDT is not cash on the balance sheet. Under US GAAP, the fair-value rules for crypto assets that FASB introduced in ASU 2023-08 leave out tokens that give the holder a claim on underlying assets. That's usually read as excluding fiat-backed stablecoins, so companies and auditors have to analyse each token, and practice still varies.

This is moving. On 18 August 2026, FASB, the body that writes US GAAP, proposed guidance on when certain digital assets can count as cash equivalents. A token would need a direct, on-demand right to redeem with the issuer for a known cash amount, backed by reserves held only in cash and Treasury bills of three months or less. Buying and selling on an exchange wouldn't be enough. Comments are open until 19 November 2026, and nothing is final.

Even if the proposal is adopted as written, USDT would not pass for any holder. Tether's reserves include bitcoin, gold and secured loans, not only cash and short Treasury bills. On top of that, Tether redeems only for its own verified customers, and the minimum and fee described above are the kind of restrictions the test rules out. How the rules work under IFRS is covered in the questions below.

This is general information as of September 2026, not legal, tax or accounting advice. Before year-end, settle these points with your accountant:

• Classification. What USDT is on your balance sheet under your framework, and how it's measured.
• The rate. Which price source and which moment you use to record a payment's value in your reporting currency.
• Fees. Whether revenue is booked gross with fees as an expense, or net.
• Tax. When receiving and converting USDT creates taxable income or a gain in your jurisdiction. In the US, the IRS treats digital assets as property, not currency.
• Proof of ownership. How you'll show auditors the company controls each wallet. A signed message or a small test transfer are the usual ways.
• Frozen or disputed balances. How any locked amount is shown and disclosed.

For the bookkeeper, most of these points turn into the same few entries made again and again. The payment goes in at its value on arrival, the fee is booked as an expense, and a later conversion is a sale with a gain or a loss. It helps to come to the year-end conversation already knowing how each crypto payment, fee and conversion is recorded in the books.

What it comes down to

Stablecoin treasury management is ordinary finance discipline applied to a payment rail with no reference field, no recall and an issuer that can freeze. Link every payment to an order before it's sent, and give unmatched money a written procedure. Hold only the USDT you'll spend, in more than one place, behind approvals no single person can bypass. Take the balance-sheet question to your accountant early, because the standard-setters are changing the answer right now.

Questions finance leads also ask

What is the stablecoin accounting treatment under IFRS?

IFRS has no standard written for stablecoins. In 2019, the IFRS Interpretations Committee concluded that crypto holdings are not cash and are usually intangible assets under IAS 38, or inventory under IAS 2 if the business holds them for sale in its ordinary course. A stablecoin that gives the holder a contractual right to redeem for cash may instead be a financial asset under IFRS 9, but the right has to belong to the holder, so the terms of each token matter. This reflects the position in September 2026; confirm it with your auditor.

What has the SEC said about stablecoin accounting?

The SEC doesn't write accounting standards for companies; in the US that's FASB's job. In April 2025, SEC staff said that "covered stablecoins", meaning dollar tokens backed by low-risk liquid reserves and redeemable one-to-one, are not securities. In February 2026, staff allowed broker-dealers to apply a 2% haircut to payment stablecoins in their capital calculations. Neither statement tells an ordinary business how to classify USDT on its balance sheet.

Is Tether USDT safe to hold?

USDT has held close to one dollar for most of its history, and Tether publishes quarterly reserve reports checked by an accounting firm. These reports are attestations, not full audits. In November 2025, S&P Global Ratings cut its assessment of USDT's ability to hold its peg to "weak", pointing to riskier reserve assets such as bitcoin and gold, and to gaps in disclosure. For a business, "safe enough" is a question of size: fine as a transit balance, riskier as the place you keep a quarter's cash.

What are the AML risks of accepting stablecoins?

The main risk is receiving money linked to sanctions, fraud or theft, which can bring a frozen address, a closed exchange account or questions from your bank. Anti-money-laundering (AML) duties such as customer checks and the travel rule, which requires sender and recipient details to travel with a transfer, fall mainly on crypto service providers. In the EU, the Transfer of Funds Regulation has applied the travel rule to crypto transfers since 30 December 2024. A merchant still has sanctions obligations of its own, so screening incoming payments and knowing who your larger customers are is worth the effort.