Invoice Creation

Overview

How it works and why it matters

Creating an invoice turns commercial terms into a traceable obligation and payment request. The system should freeze or version price, currency, invoice ID, due date, recipient, accepted payment assets, network and late/partial-payment rules. An invoice is issued before any qualifying transfer necessarily exists.

Important technical and operational details

It assigns a unique identity and initial lifecycle state and can produce a document, API object, or hosted payment link. Creation should be server-authoritative, idempotent where retries are possible, and auditable from source order to issued invoice. When implementing Invoice Creation alongside Invoice Payment, a reliable invoice workflow links the document to payment evidence while keeping document status, payment status, and accounting status separately auditable.

The process can calculate line items, discounts, taxes, shipping, fees, due date, and payment terms. Draft invoices may allow edits, while issued invoices normally require controlled corrections or credit notes.

For crypto-enabled invoices, creation can store a fiat denomination and generate payment options later, or immediately generate an asset-specific quote and session.

Invoice number and internal invoice ID can serve different purposes. Numbers may follow legal sequences, while IDs are system identifiers and should remain globally unique within scope.

Related concepts

Invoice Tracking; Invoice Payment

Further reading

• docs.oxapay.com documentation