Invoices are Flint's receivables resource. Every invoice is backed by an order: create one from an existing open order, or use quick pay input and Flint creates the backing order internally. When you send an invoice, Flint freezes the customer-facing billing content into a snapshot, issues a stable hosted invoice link, and emails the recipient.
An invoice moves from draft to open on send, then to partially_paid or paid as money comes in, or void if you cancel it. Collection can be online (an invoice-owned hosted checkout session for card payment) or offline via manual payments for checks, cash, wires, and other external methods. Delivery attempts, reminders, lifecycle events, and PDFs are all tracked on the invoice itself, and payment activity publishes webhook events.
See the Invoicing guide for an end-to-end walkthrough, and Payment links vs checkout sessions vs invoices for choosing the right collection surface.
