Skip to main content

Invoices

Send a structured invoice to a customer (line items, due date, the works), then watch it move from draft → unpaid → paid. URL: /invoices.

If you just need to charge a fixed amount with minimal ceremony, use a Payment request instead — it's a single shareable link, no invoice.

Page layout​

The page has three regions, top to bottom: action bar, Overview cards, list.

Action bar​

  • New invoice button (top right) — opens the create flow.

Overview cards​

Three KPI cards summarize the account's invoice state at a glance:

CardShows
OverdueTotal amount + count of overdue invoices
UnpaidTotal amount + count of outstanding (sent but not yet due) invoices
DraftsTotal amount + count of unsent drafts

List ("All invoices")​

Below the Overview is the full list, with these controls:

  • Search — text box "Find an invoice" (matches by invoice number, customer, etc.).
  • Status filter.
  • Date Created filter.
  • Show archived toggle — by default, archived invoices are hidden.

When the list is empty, you see "No invoices found — Create and send an invoice in minutes" and the action defaults you to New invoice.

Document list columns

Once there's at least one invoice in the account, capture the column set and re-list it here. Likely candidates: number, customer, amount, status, due date, created.

Invoice statuses​

Inferred from the Overview cards — confirm the full set:

  • Draft — created but not yet sent.
  • Unpaid — sent, awaiting payment, not yet past due.
  • Overdue — past the due date, still unpaid.
  • Paid — fully settled.
Confirm full status set

Are there others (Partially paid, Voided, Failed)? Send the list.

Create an invoice​

  1. Click New invoice (top right).
  2. Fill in customer, line items, due date.
  3. Save as draft, or send immediately.
Document the create flow

Walk through New invoice and capture: required fields, customer picker behavior, line-item editor, tax handling, currency, attachment support, schedule/recurring options.

What happens after sending​

When the customer pays, a transaction is created and the invoice flips to Paid. The transaction surfaces in Transactions with a link back to the invoice.

Confirm post-payment flow

Document: receipt sent automatically? PDF emailed? Webhook fired (invoice.paid)? Behavior on partial payment?

Archive​

Use Show archived on the list to bring archived invoices back into view. To archive an invoice, open it and use the archive action.

Confirm archive semantics

Is archive reversible? Does it affect the invoice's contribution to KPI cards? Document the unarchive flow.