Guide · updated November 18, 2026
Which USD rate applies when a client pays in crypto
The invoice says dollars, the client sends tokens, and every month-end brings the same question: at what price did that money actually come in? It depends on the rail. What matters is that the price is written down with a source and a timestamp.
The invoice is in dollars; the payment is in tokens
An invoice starts with a dollar amount: that is what you bill and what lands in your books. The payment itself moves on-chain in its own unit. To join both ends you need a price per token, and it gets used twice: at issuance, to tell the client how much token to send; at arrival, to tell how many dollars actually came in. Two moments, two possible numbers.
The price observed at issuance
When the invoice is created, the system reads the token price and computes the expected amount: dollars billed divided by unit price. That amount is what the client sees on the public page (/i/<id>) and what decides whether the payment is complete. The reading is stored with its source and observation time. If it fails, no price is invented: the invoice is issued without an expected amount.
The price applied when the payment lands
When the scanner detects the payment on the invoice address, it reads the price again and multiplies it by what arrived. That product is the dollar value at arrival, and it goes on the PDF receipt alongside the hash, the network, the pair used, the price source and the UTC observation time. Your accountant sees which price was applied and where it came from.
A stablecoin is not the same as native ETH
- USDC and USDT: 1.00 USD per unit, assumed because it is a stablecoin and declared as such in the source. There is no market to query, not on Base, not on Ethereum, not on Tron. In practice there is no price risk between issuance and payment: a hundred dollars billed is a hundred tokens.
- Native ETH: market price, read from a public source at issuance and again at arrival. Here the gap between quoted and collected is real, and the observation timestamp stops being a detail.
The peg is an assumption, not magic: if USDC trades at 0.97, the receipt will still say 1.00 because that is what is declared, and it reads that way on purpose.
What happens when the price moved between invoice and payment
Status is decided on tokens, not dollars: received versus expected, with a 99% floor and a 105% ceiling. Below is partial, above is overpaid, in between is paid.
With ETH that can produce an awkward, well-documented combination: the client sends the exact ETH quoted, the invoice is marked paid, and the dollar value at arrival is lower because the price fell along the way. Cuadre does not hide the difference or adjust the invoiced amount: it leaves it on the receipt so you decide whether to absorb it or rebill it. With stablecoins the scenario does not arise.
How to defend this to your accountant
- Invoiced amount and arrival value: two separate fields, not one rewritten field.
- Price source and time: printed on the PDF, not buried in an email thread.
- Transaction hash: lets anyone go back to the chain and check amount and time.
- Closing Excel: carries amount, token, dollar value, status and hash into the spreadsheet.
Frequently asked questions
What exchange rate applies to a USDC invoice?
An assumed one: 1.00 USD per USDC. The receipt prints the literal source (stablecoin peg assumed at 1.00 USD) and the UTC timestamp of the observation, so your accountant can see it did not come from a market feed or an invented average.
What if the invoice is in native ETH?
Then there is a real market price: ETH/USD is read from a public source when the invoice is issued, the expected ETH amount is computed from it, and it is read again when the payment lands to record the dollar value at arrival. Both timestamps stay on the record.
Does the invoice close on the dollar amount or on the token amount?
Status is decided on tokens received versus tokens expected, with a 99% floor and a 105% ceiling. The dollar value at arrival is stored separately, so a price drop shows up as a visible difference on the receipt instead of being hidden inside the invoice status.
Who absorbs the difference when the price moved?
That is your call: Cuadre does not convert, does not charge an exchange fee and does not adjust the invoiced amount. What it does is leave the number documented — expected, received, price and timestamp — so the decision is written down instead of buried in a chat.
If you want the system to do this
Cuadre issues the invoice, derives its address, matches the payment, stores the price with source and time, builds the receipt and exports the Excel: US$29/month, US$24 for life for the first 10 founding accounts.
Reserve founder seat · US$24 See pricing in detail
Read next: how to reconcile USDC payments against your invoices · one deposit address per invoice · the crypto payment Excel your accountant accepts · what the plan includes and what it does not.