Guide · updated November 18, 2026
A crypto payment Excel your accountant can defend in a review
Your accountant does not argue that you got paid: they argue about which number goes in the books. A file with thirteen columns in the right place closes the month in an afternoon; a list of hashes in a chat turns it into three days of questions.
The problem is not the file, it is what the file is missing
Exporting something from your exchange at month-end is not enough: which invoice it was, how much was invoiced and at what price the money came in are all missing. What is left is a token amount, a date and an alias that does not match the client, and with that your accountant does not book, they guess. The fix is not a prettier PDF: one row per invoice, source data next to closing data, and the evidence linked.
The five things your accountant needs from every payment
- Date with time and zone: the moment it arrived, not the day you remembered to write it down.
- Identifiable counterparty: the client on the invoice, not the wallet alias.
- Invoiced amount in your books currency: the number you already declared, no recomputation.
- Dollar value at arrival, with source and time: without it the conversion is your own assumption.
- Verifiable evidence: network and hash, so anyone can go back to the chain and confirm amount and timing.
Without the fourth the entry fails the review; without the fifth it fails the audit.
The 13 columns in Cuadre's Excel
It comes from the same database as the PDF receipt, so nothing gets retyped. One row per invoice, quoted values, UTF-8:
factura— invoice id, the same one on the receipt.fecha— when it was issued.cliente— the client name you entered.concepto— the service description the client sees.monto_usd— the invoiced amount.token— USDC, USDT or ETH depending on the rail.red— base, ethereum or trc20.monto_token— what was received in token units.valor_usd_arribo— the dollar value at the instant of arrival.precio_fuente— literal price source:coingecko:ethereum/usdfor ETH, the declared 1.00 USD peg for stablecoins.tx— the transaction hash.estado— waiting, partial, paid, over or expired.pagada_utc— the instant the payment closed.
Invoiced and arrival value are separate on purpose: an ETH invoice can close paid in tokens while its dollar value is lower because the price moved. The file shows both numbers.
The five states, and why they matter in the file
State comes from tokens received versus tokens expected, with a 99% floor and a 105% ceiling:
- waiting: issued, unpaid. Not revenue yet.
- partial: something arrived below 99%. A balance is left and the receipt can already be issued.
- paid: inside the tolerance, the normal case.
- over: above 105%. Usually a client who added fees or paid two invoices at once.
- expired: lapsed unpaid. If money lands on that address later, the scanner still sees it.
Without a state column everything looks like collected revenue: that is where phantom income from expired invoices comes from.
Three things that break the close even when the Excel is perfect
- Editing the invoiced amount: once it changes it no longer matches the client's invoice or the receipt. Book the difference separately.
- Mixing transfers between your own wallets with revenue: moving USDC from one of your wallets to another is not a sale.
- Collecting into the personal wallet you also spend from: the balance stops meaning anything. One address per invoice and a separate business wallet solve 90% of it.
Checklist before you send the file
- Does every row have its evidence (network + hash) or the reason it does not?
- Are waiting and expired rows excluded from the period's revenue?
- Are partial rows noted with the outstanding balance?
- Does every amount carry a price source and a UTC timestamp?
- Does the total match what landed in the business wallet in that range?
With those five answers the close gets signed. Without the last one it is a wish list.
Frequently asked questions
Does the Excel have one row per payment or per invoice?
One per invoice. If the client pays in two parts the row stays the same: received goes up and the state moves to partial and then to paid, so your accountant sees the whole case.
Is the booked amount the invoiced one or the arrival one?
Both, in separate columns: monto_usd is invoiced, valor_usd_arribo is what the token was worth when the payment landed. Neither is rewritten into the other.
Why keep the hash column if the amount is already there?
So the evidence does not rest on your word: with hash and network anyone can open the explorer and check amount, time and counterparty. It is the same hash printed on the PDF receipt.
Can a hand-built Excel sheet do the job?
For a one-off cleanup, not for a monthly close: it goes stale with the first partial payment and records no price source. The exported file comes from the same data as the receipt.
If you want the system to do this
Cuadre does that on its own — invoice, address, matching, price with source and time, receipt and Excel with these columns — for US$29/month, US$24 for life for the first 10 accounts.
Reserve founder seat · US$24 See pricing in detail
Read next: how to reconcile USDC payments against your invoices · which USD rate applies when a client pays in crypto · one deposit address per invoice · what reconciliation costs at Request Finance.