OdyCust/ GUIDE
УКР

Invoices

Check payment instructions and distinguish observations from payment.

Step by step

  1. Open Invoices to see a working list. Search covers the loaded page; Document status filters on the server. Previous/Next page retain that filter. Refresh starts at the first page.
  2. Select a record to see its name, reference, exact amount, UTC dates and full receiving address. Copy address copies its complete value. Technical references contains internal identifiers and the asset’s smallest units.
  3. Open, Expired and Cancelled describe the document. They do not mean unpaid or paid. Stored receipt observations do not synchronize the network.
  4. Available actions use the selected invoice. More tools → Advanced operations opens the full permitted tools for this section.
  5. More tools → Advanced operations → Sync invoice subscribes to background history and refreshes stored observations. It takes no scan-size input and does not scan blocks in the request. The separate worker fills history; before coverage is ready, syncing and unknown totals do not mean zero received or paid. No automatic payment, Ledger credit or repeated mutation follows.
  6. On a phone, selecting a row moves focus to its details. Back to list restores focus to the selected row.
  7. Create invoice offers Wallet Node address or Proved external account only when their required reads are available. A Node wallet must be active, platform-backed and owned economically by the issuing organization. Customer-owned funds cannot become merchant receipts.
  8. Choose an existing active receiving address or Create address. The latter completes the normal allocation and public admission flow first; select Done, then review the Invoice. Invoice submission never implicitly derives another address. Only current enabled tokens with known exact precision are offered, and the request uses either account_id or node_id plus allocation_id, never both.
  9. Node Invoice details remain receiving instructions, with Open, Expired or Cancelled document states. Stored observations are not paid status or accounting credit. External Payment verification and collection actions cannot accept this source; its future custody accounting linkage is not claimed by the interface.
  10. If an external Invoice has no eligible source, Set up external wallet opens ordinary setup in the same tab and organization. Return to invoice creation reopens the draft, then choose the receiving source again. Previously entered name, reference, expiry and same-network asset/amount stay in memory for up to 15 minutes; reload, sign-out or identity change discards them. The connection alone is not a confirmed external account, and no Invoice is submitted automatically.

Working details

To create an invoice, select an available receiving source: a Wallet Node address or a proved external account. Enter a name, unique reference, asset, positive amount in asset units and local expiry. The optional customer is the intended payer; you can create one without leaving the form. Review shows UTC, the exact receiving address and amount. Confirm the prepared Invoice; the backend may require your security key. Setup for a missing external source opens in the same tab; select the source again after returning. An unknown result preserves the original terms for inspection and never repeats creation.

Interface

Invoices — Illustration from an earlier CRM version with fictional training data. Layout may differ; the text describes current actions. This is not payment evidence.
Illustration from an earlier CRM version with fictional training data. Layout may differ; the text describes current actions. This is not payment evidence.

Related reading

OdyCust · User documentation2026-10-13

Search documentation

Search stays within this guide. It does not request console data.