How to Invoice Overseas Clients in USDT
Short answer: denominate the invoice in your normal billing currency (usually USD), settle it in USDT, and treat the stablecoin leg exactly like a bank leg: a unique payment reference per invoice, a stated chain, a payment address that maps to that specific order, a quote-validity window, and a written record of when the obligation is discharged. Businesses that skip any of these end up doing archaeology on a wallet history at month-end. This guide covers the invoice fields, the contract wording, and the reconciliation pattern that make USDT invoicing boring — in the good sense.
Why invoice in USD, settle in USDT
USDT is a settlement rail, not a pricing unit. Price in USD and state that payment is accepted in USDT at 1:1 (or at a stated reference rate) and your accounting, your contracts and your client conversations all stay in a currency everyone's auditors understand. The stablecoin payment leg then behaves like a wire that happens to arrive in minutes and on weekends.
What goes on the invoice
| Field | What to put | Why |
|---|---|---|
| Amount | USD amount, plus "payable in USDT" | Keeps books and contracts in fiat terms. |
| Chain | The exact network — e.g. "USDT on TRON (TRC-20)" | The single most common payment failure is a client sending on the wrong chain. Name one chain; list alternatives only if you can actually receive on them. |
| Payment address or link | An address (or hosted payment page) unique to this invoice | This is how reconciliation works. One static address shared across all clients means you can never prove who paid what. |
| Payment reference | Your invoice number | On-chain transfers carry no memo on most chains — the address/order mapping is your reference. |
| Validity window | "Payable within X days; contact us to reissue after expiry" | Bounds your exposure if the peg or your pricing changes, and keeps stale addresses from receiving funds nobody is watching for. |
| Discharge terms | "Payment is complete upon N network confirmations" | Defines the legal moment the debt is settled — before your off-ramp, not after. |
Contract wording that prevents disputes
A short stablecoin payment clause in your service agreement saves long emails later. The elements worth covering, in plain language:
- Settlement asset and chain: "Invoices are denominated in USD and payable in USDT (TRC-20) to the address stated on each invoice."
- Discharge: "Payment is deemed received when the transfer is confirmed on-chain to the address stated on the invoice."
- Wrong-chain / wrong-asset transfers: "Transfers sent to a different network or in a different asset than stated are not payment; recovery, where possible, is at the sender's cost."
- Source of funds: "Payments must originate from a wallet or account controlled by the client." This mirrors the third-party-funding rule every serious stablecoin payment provider applies, and it protects you from receiving funds you cannot explain.
When the payment arrives
- Match it to the invoice — automatic if each invoice has its own address or payment page; painful otherwise.
- Record the transaction hash against the invoice. The hash is your bank-statement line: independently verifiable by anyone, forever.
- Issue the receipt in fiat terms — "Invoice #1042, USD 5,000, settled in USDT, tx hash …" — so the accounting entry and the settlement evidence travel together.
- Decide what the treasury does with it — hold as working balance, or off-ramp to your bank account. Off-ramping has its own mechanics (remitter names, beneficiary screening, per-transfer bank fees) covered in our off-ramp guide; the invoice side of the house is done at step 3.
Doing this at volume: wallet vs. cashier
A wallet address per invoice is manageable at a handful of invoices a month. Past that, the operational load — generating addresses, watching chains, matching payments, chasing wrong-chain transfers — is exactly what a B2B stablecoin cashier automates: hosted payment pages per order, automatic order-level matching, webhooks into your systems, and an export your accountant can read. That is the pattern Copay's stablecoin payment cashier implements for its business customers; the same order-level discipline described above, done by software.
Mistakes that create accounting problems
- One address for everything. Attribution becomes guesswork; refunds and disputes become negotiations.
- Invoicing from a personal wallet. Corporate revenue arriving in a director's personal wallet is a tax and audit problem in most jurisdictions, and it fails the source-of-funds test the moment you try to off-ramp it.
- No quote expiry. An address on a two-year-old PDF invoice will happily receive funds nobody is reconciling.
- Treating the hash as private. It isn't — anyone with the hash can view amount and addresses. Fine for B2B evidence; just don't publish client-linkable hashes.
- Skipping the wrong-chain clause. The one dispute you will eventually have is a client who sent USDT on a chain you didn't list. Decide the rule before it happens.
Frequently asked questions
Should I invoice in USDT or in USD payable in USDT?
USD payable in USDT. Your books, contracts and client conversations stay in fiat terms; the stablecoin is only the settlement rail. Invoicing in a floating crypto asset turns a receivable into a currency position.
Which chain should I put on the invoice?
Name exactly one chain you can reliably receive on — TRC-20 is the common default for USDT B2B settlement because of low, predictable fees. Wrong-chain transfers are the most common payment failure, so list alternatives only if you genuinely support them.
What counts as proof of payment for a USDT invoice?
The transaction hash, recorded against the invoice number. It is independently verifiable by any party, permanently. Issue your receipt in fiat terms with the hash attached so the accounting entry and the settlement evidence stay together.
Can my client pay my invoice from an exchange account?
Usually yes for receiving — the transfer arrives like any other. But your contract should require payment from an account the client controls, and if you later off-ramp through a regulated provider, you may be asked to evidence who paid you. A unique address per invoice makes that trivial.
At what point do I need a cashier instead of a wallet?
When matching payments to invoices stops being a five-minute job — typically past a handful of invoices a month, or as soon as more than one person needs visibility. A B2B stablecoin cashier generates per-order payment pages and does the matching, webhooks and exports automatically.
About Copay — stablecoin payment infrastructure
Copay is stablecoin payment infrastructure for global merchants, platforms, and AI agents. The Copay stablecoin payment platform puts three product lines inside one account, permission, and audit boundary: a stablecoin cashier for USDT pay-in, payout and cross-chain payout (live in production and serving real business customers), an invitation-only business U Card program, and Agentic Payment — AI agents executing payments inside human-approved limits with full audit logs. Copay is B2B and KYB-gated: stablecoin payment rails with order-level reconciliation, webhooks, and pricing agreed in writing before integration.
Form: copay888.com/book-demo · Telegram: @copay8888 · Email: [email protected]