Invoice
invoice_id,expected_usdc
FREE / BROWSER-LOCAL / ONE HUMAN ECONOMIC OWNER / AI-ASSISTED
One client invoice. One USDC receipt.
How many EUR actually reached the bank?
If your team receives USDC from customers and later off-ramps it into EUR, four separate records must reconcile: the invoice, the token-event export, the conversion receipt and the bank deposit. This free checker flags missing references, reported shortfalls, FX fee arithmetic, duplicates and pending steps using only what you paste in your browser.
Invoice → USDCUSDC → off-rampGross EUR − fees = net EUROff-ramp → bank
Try invented example ↓Reverse: fiat funding → crypto contractor payouts ↗
This is NOT settlement verification, accounting software, FX rate evidence, or proof of money received. All four datasets are visitor-supplied and potentially false. Never submit real personal/regulated records or wallet keys. The example is completely fictional.
Compare four CSV exports without sending them anywhere
Choose up to 300 rows / 80 kB per file, or paste data. Explicit reference IDs are required. This intentionally does not join records by guessed amount, wallet or timestamp. Only canonical Circle Base USDC is understood in the synthetic example; amounts are decimal-exact.
Reported token receipt
invoice_id,receipt_id,amount_usdc,chain,token,status
Reported EUR conversion
receipt_id,conversion_id,source_usdc,gross_eur,fee_eur,net_eur,executed_at_utc
Reported bank credit
conversion_id,net_eur,status,posted_at_utc
| CSV | Row | Issue | Meaning (illustrative only) |
|---|
The optional export contains only input category, row number and issue code; it intentionally omits invoice IDs, amounts and addresses. A zero-issue result only means that the four imported statements align syntactically.
Deliberate limits protect your accounting judgement
Token explorer ≠ invoice
The receipt CSV can be forged. We do not make RPC requests, inspect signatures, confirm token ownership, reconcile internal wallet transfers, or verify that an event settled on the chain. The Base token address field is compared with the canonical Circle contract string only.
Conversion quote ≠ historical FX source
Arithmetic checks are on *reported* gross EUR, fees, and net EUR; no implied ECB/interbank rate, fair value, spread benchmark, custody treatment or P&L is invented. Original exchange confirmations and accounting policy remain necessary.
EUR credit ≠ bank confirmation
reported_posted is merely an input label, not bank access. Pooled exchange credits, partial offramps, unrelated wallet receipts, chargebacks, netting and multiple conversions per transaction require explicit allocation and manual review.
Privacy-first by design
All parsing happens in this page after static assets load; Content-Security-Policy forbids network connections. No account, cookie, analytics, token, wallet, address capture, upload or payment is required. Do not paste client-confidential records into unapproved devices.
Need one source-format adapter instead of another spreadsheet?
The checker is completely free. For a concrete processor/exchange whose fictional or client-authorized redacted columns differ, we can discuss a conditional 49 native Base Circle USDC pilot: two nonsecret synthetic schema variations, offline source mapper, exact match/exception rules, deterministic tests, short handoff guide and one scoped correction. This is a proposal, not a checkout, customer order, price guarantee or accounting service.
Only want to share a missing field? Send free, fictional-example feedback ↗. Describe where the invoice, transfer, conversion ID, or EUR bank credit fails to join. The existing voluntary form asks for a reply email; please provide no real bank or customer records. No purchase is required.
Work begins only after one independent buyer and the lawful human payee agree in writing on precise fields, data rights, AI assistance, delivery, acceptance, IP, tax/KYC as applicable, chain/payment terms and cancellation/refund provisions. **No sale or customer is claimed.**
Request a conditional 49 USDC scope ↗ Give nonconfidential field-only feedback ↗