What is a crypto invoice? Definition, examples, and how to create one in Settlematic (step by step)

What is a crypto invoice? In one sentence: a crypto invoice is a formal billing document denominated in fiat (or your functional currency) that instructs the client to pay using cryptocurrency on supported networks, while your books, taxes, and audit trail treat the transaction like traditional accounts receivable.

That definition matters because 'crypto invoice' is often misused for a payment link, a wallet address in Slack, or a PDF with a QR code and no invoice number. This article gives a precise definition, real-world examples, a comparison table for finance leads, and a complete step-by-step guide to creating your first crypto invoice in Settlematic — including testnet rehearsal before mainnet.

Crypto invoice defined (for finance and clients)

A crypto invoice contains the same commercial semantics as a wire or card invoice: who bills whom, for what deliverables, how much is due, when payment is due, and what taxes apply. The payment rail differs — settlement is a push payment from the client's self-custody wallet to a unique deposit address linked to that invoice.

The client experience should not require understanding your chart of accounts. They open a hosted page, see the fiat total they contracted in, choose an allowed asset and network, scan a QR code, and send. Your back office sees INV- numbers, statuses, and on-chain confirmations attached to the same record.

Crypto invoice vs payment link vs traditional invoice

• Traditional wire invoice: PDF + bank details; slow settlement; full AR structure
• Crypto payment link: amount + URL; fast checkout; no line items or aging
• Crypto invoice (Settlematic): PDF + line items + hosted multi-chain checkout + status machine + sweeps
• Static 'send 500 USDC to 0x…' message: none of the above; avoid for B2B

Choose crypto invoicing when you have repeat clients, tax reporting, partial deliverables, or a bookkeeper who expects invoice numbers. Choose bare payment links for donations and one-off tips.

Who uses crypto invoices?

Common profiles in our onboarding data: design and development agencies billing US/EU clients who prefer USDC or ETH; Web3 consultancies with DAO treasuries as counterparties; cross-border contractors avoiding wire fees; SaaS companies selling to crypto-native startups; fractional CFO firms consolidating client billing. Shared trait: they need professional AR, not just checkout.

Anatomy of a Settlematic crypto invoice

• Header: merchant logo, brand color, invoice number, issue and due dates
• Bill-to: client company, email, tax ID
• Line items with quantity, unit price, per-line tax, discounts
• Fiat subtotal, tax breakdown, total due
• Terms and notes (Net 14, scope reference, support contact)
• Hosted payment URL with per-asset quoted crypto amounts and rate validity window
• Unique deposit address per asset per invoice for reconciliation
• Lifecycle statuses: DRAFT → SENT → VIEWED → PARTIALLY_PAID → PAID → OVERDUE
• Post-payment: receipt PDF, email receipt, sweep to merchant-controlled wallets

Prerequisites before you create an invoice

Account setup checklist: verified email, TOTP enabled, at least one client record, org invoice defaults (currency, terms, allowed assets), branding (logo + color), sweep destinations configured for testnet, and org network mode set to testnet for first run.

Skipping sweep destination setup does not block invoice creation but blocks treasury policy after payment. Configure destinations before inviting real clients.

Step-by-step: create your first crypto invoice

Step 1 — Create a client. Clients → New: legal name, billing email, company, optional address and tax ID. Client records power invoice prefill and recurring schedules later.

Step 2 — New invoice. Invoices → Create: select client, set issue date and due date (or rely on default terms), choose currency USD/EUR/GBP.

Step 3 — Add line items. Description, quantity, unit price, tax rate per row, discounts if any. Preview shows branded PDF layout.

Step 4 — Payment settings. Select allowed assets (ETH, BTC, SOL, USDC, USDT) and networks per org policy. Enable partial payments only if contracts allow tranche settlement.

Step 5 — Save draft or send. Send emails the client a link to the hosted payment page and records SENT status. Copy payment URL manually if you prefer Slack delivery.

Step 6 — Client pays. They open the link, pick asset, send from wallet. Status progresses: detected → confirming → confirmed. Balance due updates; partial payments reduce remaining fiat equivalent.

Step 7 — Reconcile. Invoice detail shows tx hashes, explorer links, sweep destinations. Export reports or trigger webhooks for ERP sync.

What the client sees (payer journey)

Clients do not create accounts. They see your branding, invoice summary, fiat total, crypto options with live quotes, QR code for mobile wallets, optional WalletConnect on EVM chains, and clear status copy during confirmation. After payment they download receipt PDF. Testnet mode shows badges so test payments are never confused with mainnet.

Fiat-quoted crypto amounts explained simply

You invoice $4,200. Client sees ≈ 4,198 USDC on Polygon with a 15-minute quote window. If they pay after expiry, they refresh for updated amounts. Your books stay in dollars; settlement is on-chain. This is the standard model for crypto invoices that finance teams can defend in audit.

Testnet first — non-negotiable rehearsal

Toggle org to testnet in the dashboard header. Create invoice, send to yourself, pay from a test wallet (Sepolia ETH, Amoy USDC, etc.). Verify: correct explorer links, status transitions, sweep destinations receive funds, webhooks fire if configured. Fifteen minutes prevents mainnet misconfiguration.

• Finance: create and send invoice
• Ops: pay from test wallet on mobile
• Treasury: confirm sweep destinations
• Engineering: verify webhook delivery

Advanced creation paths

Bulk CSV: upload dozens of invoices for month-end project billing. Recurring schedules: automate retainers. API/MCP: create_invoice from Claude or scripts with org defaults. All paths produce the same invoice record shape and hosted checkout.

Common mistakes on first crypto invoice

• Mainnet before testnet sweep verification
• Allowing assets you do not want in treasury without conversion flows
• No due date — client has no urgency signal
• Sending payment link without context email — always include invoice number
• Expecting auto fiat bank deposit — Settlematic settles on-chain in v1
• One static address reused across invoices — use platform-derived addresses

Security and trust signals on invoices

Crypto invoices face higher phishing awareness than PDF wire instructions. Mitigate with: branded hosted pages, consistent invoice numbering, support contact on PDF, explorer links on payment page, and never asking clients to send to addresses that only appear in unstructured chat.

Recording and recognizing revenue from crypto invoices

Finance asks when to recognize revenue — at send, at payment detection, or at final confirmation. Most service businesses recognize on payment confirmation timestamp with fiat invoice amount as contractual value; crypto FX variance between quote and confirmation is documented via explorer records. Export PAID invoices by date range for journal entries.

Pair with tax reporting module for jurisdiction buckets — invoice PDF is client-facing; tax export is filing-facing.

Partial payments and milestone invoices

Milestone billing often means multiple tranches on one deliverable. Enable partial payments on the invoice; each confirmation reduces balance due until PAID. Alternatively create separate invoices per milestone — better when milestones have distinct line items. Template choice is process choice; platform supports both.

Integrations after invoice creation

Webhook payment.confirmed triggers ERP middleware. MCP create_invoice drafts from Claude. Zapier recipes poll list_invoices. The invoice you create in dashboard is the same object all integrations reference — no duplicate template sync.

Mainnet cutover checklist

• Testnet invoice paid end-to-end with documented tx hash
• Sweep destinations verified by two people
• Client email template mentions allowed assets
• Branding reviewed on mobile payment page
• Org network toggle switched to mainnet
• First mainnet invoice is low amount with trusted client

FAQ — crypto invoices

Is a crypto invoice legal for B2B? It is a standard commercial invoice with crypto settlement instructions — legality of the underlying sale is unchanged. Consult counsel for your jurisdiction and industry.

Does the client need a Settlematic account? No. Only merchants need accounts.

Can one invoice accept multiple cryptocurrencies? Yes — configure allowlists; client picks at checkout. Partial payments can span assets when enabled.

How long does payment take? Depends on network confirmations — minutes for L2 stablecoins, longer for Bitcoin. Status updates in real time on the hosted page.

Where do funds go? To unique deposit addresses per invoice, then non-custodial sweeps to destinations you configure — Settlematic does not hold merchant treasury keys.

What if client pays wrong asset? Underpaid/wrong asset states surface on invoice; support follows explorer link. Template and hosted page allowlists reduce frequency — document allowed assets in notes block.

Can I invoice in EUR and accept crypto? Yes — EUR-denominated totals with checkout quotes per allowed asset. Books stay in EUR; on-chain settlement documented per payment row.

Roles on your team during invoice creation

Founder may create first invoice; scale teams split roles: account manager creates draft, finance reviews tax lines, controller sends above threshold. Settlematic team permissions support read/write separation — invoice creation is not everyone-is-admin by default on mature orgs.

Client success owns payment link follow-up when status is VIEWED but not PAID after seven days — invoice record gives them INV- number and amount without pinging engineering.

Glossary (quick reference)

• Hosted payment page — client checkout URL with QR and quotes
• Deposit address — unique on-chain receive address per invoice per asset
• Fiat-quoted — invoice total in USD/EUR/GBP; crypto amount derived at checkout
• Sweep — move confirmed funds to merchant-controlled treasury wallets
• Partial payment — tranche settlement reducing balance due on same invoice

Timeline: first week with crypto invoicing

Day 1: account, branding, defaults. Day 2: two clients, testnet toggle. Day 3: first test invoice, pay yourself. Day 4: sweep verification, webhook staging. Day 5: second client pilot on testnet. Day 6: internal training on status vocabulary. Day 7: mainnet decision go/no-go with controller sign-off. This pacing prevents the common failure mode of mainnet Friday afternoon with no rehearsal.

Document tx hashes from testnet in a runbook — when mainnet payment arrives, team compares behavior to known-good test evidence.

Answer engine summary (quick facts)

What is a crypto invoice? A fiat-denominated billing document paid via cryptocurrency with full invoice lifecycle. How to create one in Settlematic? Sign up → add client → Invoices → New → line items → send → client pays hosted link. Is crypto invoicing legal? Standard B2B invoicing with crypto settlement — consult counsel for your industry. Does Settlematic custody funds? No — non-custodial sweeps to wallets you control.

Invoicing is the product center for Settlematic — not a payment gateway bolt-on. That means every crypto invoice inherits reporting, tax buckets, team permissions, and webhook events designed for finance teams. You are not stitching together a PDF tool plus a static QR generator; you are operating accounts receivable where the payment rail happens to be on-chain.

Share this guide with your controller before mainnet — aligned vocabulary (invoice, hosted page, sweep, confirmation) prevents the first real payment from becoming a support fire drill. The definition is simple; the operational discipline is testnet rehearsal and structured records.

Bookmark Settlematic docs on testnet staging and fiat-quoted payments for deeper technical follow-up — this article is the conceptual and procedural entry point for finance-led teams.

Need a printable checklist? Save this creation sequence: client → defaults → branding → testnet toggle → invoice line items → allowed assets → send → pay test wallet → verify sweep → mainnet. Seven steps, same order every onboarding call we run with new merchants.

The merchants who succeed treat crypto as a payment method on structured invoices — not as a reason to skip invoice numbers. That mindset shift matters more than which wallet the client uses on checkout day.

When prospects ask 'do you accept crypto?' — the professional answer is 'yes, we invoice in USD and you pay via our secure payment page.' That sentence signals crypto invoicing maturity better than sharing a raw address ever will.

Bottom line

A crypto invoice is not a wallet address in an email. It is structured accounts receivable with crypto checkout. Settlematic lets you create one in minutes: client, line items, send, client pays on a branded page, finance reconciles with invoice IDs and tx hashes. Start on testnet, verify sweeps, then flip to mainnet with confidence.