Use Case: Crypto

Invoice in crypto or in fiat — with the numbers your accountant needs

Exchanges, crypto payment processors, Web3 and SaaS products billing in stablecoins, OTC desks, mining and staking service providers, and agencies paid in crypto all need documents that hold up for tax and reporting. Space Invoices lets you price invoices, estimates, advance invoices, credit notes, and delivery notes directly in BTC, ETH, SOL, USDC, or USDT, or keep the document in fiat and add an optional crypto equivalent, wallet address, and payment type on top. Crypto-priced invoices always record the exchange rate to your local currency, so your accountant has what they need for tax and reporting. Invoices in a foreign fiat currency get a rate whenever one is available.

Start free sandbox View crypto docs

Who This Is For

You run an exchange, crypto payment processor, or Web3 product billing business customers

You want to issue invoices, estimates, advance invoices, credit notes, or delivery notes priced directly in BTC, ETH, SOL, USDC, or USDT

You want fiat invoices to also show a crypto equivalent for customers who prefer to pay that way

You need to record payments received in crypto and reconcile them against invoice balances

You want wallet addresses, transaction hashes, or on-chain references stored on the document, not just in a spreadsheet

Not A Fit

Your entity is registered in the UK; HMRC does not treat crypto as money, so UK entities cannot issue crypto-priced documents

You need to send a crypto-priced document as a structured e-invoice such as Peppol/UBL, XRechnung, NAV, KSeF, SdI, or French e-invoicing; those formats require an ISO 4217 currency, so use a fiat invoice with crypto equivalents instead

You need Space Invoices to accept, process, or custody crypto payments

You need automatic on-chain payment detection or confirmation tracking

You need crypto accounting, cost-basis reporting, or tax advice

What You Get

Crypto-priced invoices

Issue invoices, estimates, advance invoices, credit notes, and delivery notes with currency_code set to BTC, ETH, SOL, USDC, or USDT. Amounts use the asset’s own precision: 8 decimals for BTC and ETH, 6 for SOL, 2 for USDC and USDT. Switch on crypto invoicing in settings to show crypto currencies in the web app currency picker.

Crypto equivalents on fiat invoices

Opt in per entity and pick up to 3 assets from BTC, ETH, SOL, USDC, and USDT. Invoices, advance invoices, and estimates in a regular currency then carry a snapshot converting the total to each asset at the market rate for the document date.

Wallet addresses

Register one wallet per asset, each with an optional network label. A crypto-priced document stores and prints the company’s wallet for that asset; a crypto equivalent carries the same wallet alongside the converted amount.

Local-currency conversion for tax and reporting

A crypto-priced document also carries the exchange rate and the totals converted to the company’s currency. Fiscal and tax reporting, dashboards, and country fiscalization modules such as FURS, FINA, e-SLOG, UJP, and SAF-T all use the converted amount, the same way documents in a foreign currency already do.

Crypto payment type

Record payments received in crypto with a dedicated payment type, available on crypto-priced invoices or once crypto equivalents or crypto invoicing are switched on. Store the transaction hash in the payment reference field. On a crypto-priced invoice, payment amounts are in the asset itself.

Webhooks and reversals

Get webhook events for document and payment state, and use credit notes for reversals instead of rewriting a finalized invoice.

First Sandbox Milestone

Prove a crypto-priced invoice with converted totals

Before shipping UI, validate that an entity can enable crypto invoicing, that a BTC-priced invoice shows the right BTC amounts, wallet, and converted EUR totals on the PDF, and that a crypto payment reconciles the balance.

Create a sandbox entity

Add a BTC wallet to the entity settings

Create an invoice with currency_code set to BTC

Check the PDF shows the BTC amounts, the wallet address, and the converted EUR totals for tax purposes

Record a payment with type crypto and the transaction hash as the reference

Entity Setting

Enable wallets, equivalents, and crypto invoicing

entity settingsJSON

{
  "crypto_wallets": [
    {
      "code": "BTC",
      "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh",
      "network": "Bitcoin"
    }
  ],
  "crypto_equivalents": {
    "enabled": true,
    "codes": ["BTC"]
  },
  "crypto_invoicing": {
    "enabled": true
  }
}

Invoice Response

A BTC-priced invoice, with converted totals

invoiceJSON

{
  "currency_code": "BTC",
  "total_with_tax": 0.0122,
  "exchange_rate": {
    "rate": 74462.51,
    "quote_currency": "EUR"
  },
  "total_with_tax_converted": 908.44,
  "issuer": {
    "crypto_wallet": {
      "code": "BTC",
      "address": "bc1qxy2kgdygjrsqtzq2n0yrf2493p83kkfjhx0wlh",
      "network": "Bitcoin"
    }
  }
}

Operational Gotchas

A crypto-priced document requires an available market rate for the asset; without one, Space Invoices rejects the document

Crypto-priced documents never carry a payment QR code

UK entities cannot issue crypto-priced documents; use crypto equivalents on a fiat invoice instead

Crypto-priced documents cannot be sent as structured e-invoices such as Peppol/UBL, XRechnung, NAV, KSeF, SdI, or French e-invoicing; those formats require an ISO 4217 currency

The customer’s actual transfer amount can differ from a crypto-equivalent snapshot if the price moves between document date and payment; record the amount actually received

Always double-check the network label on a wallet before sharing it; a mismatched network can send funds somewhere unrecoverable

Use credit notes for refunds and reversals rather than editing a finalized invoice

Compliance Notes

UK entities cannot issue crypto-priced documents, because HMRC does not treat crypto as money. Use crypto equivalents on a fiat invoice instead.

Crypto-priced documents cannot be sent or exported as structured e-invoices, including Peppol/UBL, XRechnung, NAV (Hungary), KSeF (Poland), SdI (Italy), or French e-invoicing, because those formats require an ISO 4217 currency. Use a fiat invoice with crypto equivalents where a structured format applies.

Slovenian and Croatian fiscalization (FURS, FINA), e-SLOG and UJP, Portuguese SAF-T, and accounting exports all use the document’s converted local-currency amounts, whether the document is priced in crypto or in fiat.

A crypto-priced document requires an available market rate; without one, Space Invoices rejects the document. Crypto-priced documents never carry a payment QR code.

Space Invoices does not accept, process, or hold custody of crypto, does not detect on-chain payments automatically, and does not provide crypto accounting, cost-basis, or tax advice; treat the crypto amounts as what they are and reconcile payments yourself.

See crypto use-case guide See webhook patterns

Start with one workflow, not a whole rewrite

Free sandbox with no time limit. Prove one entity and one invoice flow before deciding how much UI, compliance, and rollout surface you want to own.

Start free sandbox See platform architecture