USDT invoicing: the rules worth knowing before you send one

The same USDT balance can sit on TRON TRC20, Ethereum ERC20 or BNB Smart Chain BEP20, and each has its own address format and fee profile. If your invoice says only USDT, a client may send on a chain your wallet does not watch.

VegaPal keeps the network attached to the saved wallet, so it prints next to the address on the PDF and on the payment page rather than living in a separate message you forgot to send.

Because USDT tracks the dollar, a 2,400 USDT invoice should land as 2,400 USDT. Network fees are paid by the sender, but it is still worth writing on the invoice that the amount received must match the amount due, so nobody nets the fee out of your payment.

If your books run in AED, EUR or another currency, record the fiat equivalent on the day the payment lands — that figure, not the invoice date rate, is usually what your accountant needs.

A USDT invoice is still an invoice: sequential number, issue date, due date, itemised work, totals and tax where it applies. Getting paid on-chain is not a reason to keep looser paperwork than a bank-paid client would get.

Store the transaction hash with your copy of the invoice. It is the crypto equivalent of a bank reference and answers most questions before they are asked.

Suppose Northwind Studio in Dubai delivers a website audit for a client in Istanbul. The invoice reads: tax invoice INV-2026-0087, issued 4 March, due 18 March, one line item 'Technical SEO audit and report — 1 × 2,400.00 USDT', amount due 2,400.00 USDT.

The payment block reads 'USDT on TRON (TRC20)' above the receiving address, with a single sentence underneath: network fees are paid by the sender, so the amount received must equal 2,400.00 USDT. When 2,400 USDT arrives, Northwind files the transaction hash next to its copy of the invoice, marks the document paid, and records the AED equivalent using the rate on 11 March, the day the payment landed.

Writing only 'USDT' with no network. This is the expensive one: a client sends on BNB Smart Chain to an address you only monitor on TRON, and the balance sits somewhere you may not be able to reach. Name the asset and the network together, every time.

Letting the client net the network fee out of the payment. If you invoice 2,400 USDT and receive 2,398.20, you now have a partial payment and an awkward email. One sentence on the invoice prevents it.

Copying an address from a chat thread instead of your saved payment methods. Truncated addresses, autocorrected characters and stale wallets all come from the same habit. Save the wallet once and select it.

Losing the invoice-date and settlement-date exchange-rate records. Keep both and let your accountant apply the appropriate reporting treatment and any exchange difference.

VegaPal creates the document and publishes your payment instructions on a PDF and a public page. It does not hold your USDT, convert it or act as an escrow, and there is no wallet connection or signature request anywhere in the product. On Pro it reads the public TRON, Ethereum and Polygon blockchains to confirm USDT invoices paid on those networks.

The payment goes wallet to wallet. On Pro, a payment of the exact amount on TRC20, ERC20 or Polygon marks the invoice paid after the network's confirmations (20 on TRON, 12 on Ethereum, 64 on Polygon), usually within minutes. Any other amount waits for your OK. On Free, or on other networks, you check your wallet and mark the invoice paid yourself.