Invoice Lifecycle

Definition

Invoice lifecycle is the complete sequence of commercial and system states an invoice passes through from draft and issue to payment, closure, cancellation, credit, dispute, or write-off. It should be modeled separately from checkout and payment lifecycles, while maintaining explicit links between them. Each transition requires a responsible actor, timestamp, allowed predecessor, and audit evidence.

Overview

Meaning and scope

Mechanism and operation

A crypto invoice normally begins with a priced request naming an asset, amount, network and expiry. A monitor then detects transfers and checks their association with that request. The workflow can enter a confirming state while additional blocks accrue, then a paid or settled state after its policy passes. It can also expire, receive insufficient funds or require a refund; these branches need distinct records. Invoice Lifecycle systems should preserve the issued version, due balance, denomination, tax treatment, payment instructions, and every later adjustment or settlement event.

Practical payment example

An invoice progresses from issued to awaiting funds, detecting payment, confirming and settled. Support retains each timestamp so a late transfer is not mistaken for an unpaid order.

Operational checks

Every transition needs a triggering event, time, source of truth and allowed next states. If payment arrives after expiry, do not silently reopen a quoted invoice; enter an exception with the recorded transfer and the business decision required to settle, re-quote or refund it.

Distinctions and limits

A complete record for Invoice Lifecycle should show where it depends on Invoice Payment and how it differs from E-Invoice. Risks include invalid transitions, duplicate events, payment and invoice status disagreement, reopened closed invoices, and automated collection after cancellation.

Related definitions: Invoice Payment.

Example