Business adminInvoicing

How invoicing works

Clients never guess the amount. Operator issues a USD invoice that matches the enrolled plan, lists payment rails (check, Zelle, ACH first; crypto on request), and stays free of EIN on client paper.

Client flow

  1. Enroll request — plan, people, retention, payment preference.
  2. Invoice issued — voided bill / billing templates · status OPEN.
  3. Client pays — check, Zelle, or agreed ACH; crypto on request with a fresh address per invoice.
  4. Proof — client sends tx hash or fiat confirmation to business email.
  5. Mark paid — on-chain / operator confirm → PAID stamp → work continues.
  6. Recurring — monthly invoices on period; annual as single yearly invoice.

Sample invoice (household of two · monthly)

Digital Alchemy Labs LLC
d/b/a GET_VOIDED
reports@getvoid.family
Jurisdiction: Oklahoma
Address: issued on live invoices when set

Invoice

INV-SAMPLE-0003-2026-07
Issued: 2026-07-30
Due: 2026-08-06
Period: 2026-08
Open
Bill to: Sample Household · Client 0003
Plan: total privacy package · data_retention: encrypted_keep
Description SKU Qty Amount USD
Total privacy package (household of 2), monthly care total_privacy_package 1 29.00
Total due $29.00
Payment instructions

Pay Digital Alchemy Labs LLC / GET_VOIDED as stated on this invoice. Primary: check, Zelle, or agreed bank transfer (details listed per invoice).

Crypto on request: USDT/USDC (or BTC/ETH). A unique receive address is issued with each invoice — not reused across clients. Send only to the address on this invoice. After send, email the transaction hash + invoice number to reports@getvoid.family.

We will never ask for seed phrases or private keys. EIN is not printed on client invoices.

Services are evidence-backed privacy operations. No permanent-removal guarantee. See service agreement and signed authorization on file.

Annual invoice shape

PeopleMonthlyAnnual (11×)You save
1$19$209 / yr$19
2$29$319 / yr$29
3$38$418 / yr$38
4$47$517 / yr$47

Annual = monthly × 11 from pricing/skus.yaml (Pricing v2). Site-lint enforces match.

Billing notes (client-safe)

  • Line items match enrolled plan and headcount
  • Boring payment methods listed first on every invoice
  • If crypto: fresh receive address on that invoice only
  • Never put EIN on client-facing HTML/PDF
  • Record tx hash / fiat proof when marking PAID
  • Late unpaid may pause new submissions
Client enroll path Pricing