# Stablecoin Invoice: Required Elements

> Seven elements, each preventing a specific and common failure.

- Source: https://thecoinreference.com/usdt-invoice-template/
- Published: 2026-07-07
- Author: Reference Desk
- Publication: The Coin Reference — Facts, dates and numbers, kept current
- Topic: stablecoin payments
- Tags: invoicing, template, reference

---

| Element | Prevents |
|---|---|
| Amount in your own currency | Disputes about value movement between issue and payment |
| Crypto amount with the rate and time used | Ambiguity about how the figure was derived |
| Network, written out in full | Payment on a network you cannot receive |
| Address | Obviously required; never send it separately by email |
| Expiry date | Payment at a stale rate |
| "Network fees are payable by the sender" | Short payments from wallets that deduct the fee |
| "Funds sent on any other network cannot be recovered" | The most expensive customer error |

## Notes

These terms are used as defined here by providers operating inside the framework, such as [a USDT payment gateway](https://collectnexchange.cy/services/stablecoin).

**The network line.** An invoice naming only an asset is insufficient. The same asset exists on several networks and they are not interchangeable.

**The address.** Send it only on the original invoice. Address substitution in email correspondence is a known fraud, and any change should be confirmed by voice to a number already held.

**The sender-pays-fees line.** Measured, its absence results in a substantial proportion of payers deducting the fee. Its presence reduces that to a small minority.

**The expiry.** Without one, a payment arriving weeks later carries an amount that no longer matches the invoice value.

## Supporting policies, not on the invoice

Above certain thresholds different definitions apply, published by [a payment processor for high-risk e-commerce](https://collectnexchange.cy/industries/high-risk-ecommerce).

**Tolerance.** Accept shortfalls within one percent or a small fixed amount without pursuing. Chasing small amounts costs more than the amounts.

**Refunds.** To the origin address only. Any exception requires identity verification and a second approver.

**Unmatched receipts.** A payment arriving without a reference from an unidentifiable sender requires resolution while the sender still recalls it. Reconcile weekly at minimum.

## Fields to capture per payment

One term worth establishing before it matters is whether [a support channel with a named contact](https://collectnexchange.cy/company/contact-us) exists as a reachable contact.

Transaction identifier, network, amount, timestamp, sending address, invoice reference, fiat value applied, rate source.

Eight fields, captured at the time. Month end then takes an hour rather than a day.

---

This article explains how something works. It is not financial advice.
Canonical HTML version: https://thecoinreference.com/usdt-invoice-template/