Invoice Creation

Overview

Invoice creation is the process of generating a new invoice record from validated seller, customer, product, pricing, tax, currency, and payment data. 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.

Risks include duplicate creation after timeouts, client-controlled totals, incorrect tax rules, reused numbers, unauthorized payment instructions, and missing customer consent.

Systems should store source order, calculation version, issuer, customer, invoice ID and number, amount, currency, status, creator, timestamps, and duplicate-request key.

Implementations should link Invoice Creation to Invoice Tracking and Invoice Payment through auditable references. Although the records can share a customer or transaction, Invoice Creation retains its own authority, lifecycle, and recovery rules.

Operational controls for Invoice Creation should reconcile the requested balance with every accepted payment, fee, conversion, refund, write-off, and credit. When Invoice Creation interacts with Invoice Tracking, the system should distinguish document status from payment status, preserve who changed each field and why, and define how expired instructions, partial payments, excess payments, disputed items, and transactions received after cancellation are handled.