Reconciliation guide · updated November 17, 2026
How to reconcile USDC payments against your invoices
Getting paid in USDC is easy. What breaks is the month-end close: money landed and you don't know which invoice it belongs to. This is the method that gives every payment a name, without asking the client to learn anything new.
Why one shared address breaks reconciliation
If every client pays the same address, at month end your only clues are amount and date. That works for four payments; it collapses at twenty:
- The transfer carries no memo. A USDC payment on Base or Ethereum moves an amount, a destination and a hash — the invoice number in the client's email does not travel with the money.
- Amounts repeat. Two clients paying US$500 the same week leave two identical transfers: assigning them is a guess.
- The payer is not always the client. When they withdraw from an exchange, the sending address is the exchange's.
- Partial payments don't fit the sheet. Half an invoice matches no expected amount and sits there as unowned surplus.
The method: one deposit address per invoice
Every invoice is created with its own address, so the payment is identified by its destination instead of by whatever the client types. The loop is short:
- You create the invoice in dollars (or euros) with a client name and a description.
- The system hands you a unique address derived from your extended public key: it is watch-only. The private key is not on the server, so the software reads the chain but cannot move funds.
- The client pays the amount in USDC on Base or Ethereum — or sends native ETH — from whatever wallet or exchange they use.
- The payment matches itself and the state changes: waiting, partial, paid or over. Default tolerance is 1%.
- Out come the receipt and the CSV: a PDF with hash, network, token amount and fiat value at arrival, plus one row per invoice.
Which dollar rate goes into the entry
USDC is a dollar by design, but the entry still needs the exact token amount and the arrival time. When the client sends native ETH the rate actually moves the result, and it has to be written down:
- The rate that counts is the one at the instant the payment arrived, not the month-end rate.
- The receipt stores the price source and the observation time: if the accountant asks where the number came from, it is on the document.
- It is not the rate of the exchange where the client bought: that is their cost, not your revenue.
The five states and what to do with each
- Waiting: nothing has landed yet; the link can be resent without touching the amount.
- Partial: less than expected arrived and the difference stays visible; the receipt covers what actually landed. This is a normal state, not an error to fix by hand.
- Paid: the amount arrived within the 1% tolerance.
- Over: more than expected arrived; you decide whether it is a credit or a refund, and it stays on record.
- Expired: the due date passed with no payment, without deleting the invoice or the history.
What your accountant needs to accept the CSV
They don't ask for “the wallet history”: they ask for one row per invoice with invoice number and client, dollar amount and token amount, token and network, transaction hash, arrival date and time, the price used with its source, and the payment state. Miss one column and they will ask for it anyway — that is where retyping starts and cent-level errors are born. The PDF has to say exactly what that row says.
Month-end checklist
- Filter by date range and look at partials first: those are the open balances.
- One entry per invoice, not per transfer: two instalments still make one invoice.
- Send the CSV as it is, with no amounts retyped.
- Settle overpayments before closing and write the decision down.
FAQ
Does it work if my client pays from an exchange?
Yes. The transfer comes from the exchange address, not the client wallet; with a unique address per invoice the match depends on destination and amount, not on who signed.
Do I have to ask them to include the invoice number?
No. A USDC transfer carries no memo field that reaches the chain; the invoice's own deposit address is what identifies it.
What if they pay half?
The invoice goes to partial, with the difference visible and a default 1% tolerance. The receipt covers what really arrived and its dollar value at arrival.
Does Cuadre move or custody my USDC?
No. It only reads the blockchain: addresses come from your extended public key and private keys are never on the server. It is not a gateway, exchange or off-ramp.
If you want the system to do this
Cuadre creates the unique address, matches the payment, builds the receipt and exports the CSV: US$29/month, US$24/month for life for the first 10 founding accounts. Non-custodial — we never hold your money.
Claim founder price · US$24 See full pricing
Keep reading: how Cuadre works in five steps · what the plan includes and what it doesn't · the technical card for agents.