Sell on terms, and actually get paid.

Terms that are a setting, not a spreadsheet

Let approved buyers check out on invoice and pay later. Terms are any whole number of days from 0 to 365 — 0 means due on issue — with a default you choose and per-customer overrides for the accounts that get something different.

When the order is placed, the invoice freezes its term and records where it came from. Edit the customer next month and last month’s invoices keep the due dates the buyer actually agreed to.

The right term wins

A term can come from four places, and Throttle resolves them in order:

1. a term negotiated on an accepted quote,
2. the customer’s own term,
3. a term set on the cart,
4. your default.

A signed deal outranks a standing default — so an order quoted at Net-60 is never invoiced at the customer’s usual Net-7.

Accepted, on the record

With the invoice-terms connector on, buyers accept your terms at checkout, and Throttle stores a fingerprint of the exact text they accepted alongside the order.

Receivables, in one place

• An aging report buckets what’s outstanding into 0–30, 31–60, 61–90, and 90+ days past due.
• Overdue reminders go out automatically at 1, 7, 14, and 30 days past due, each one emailing the buyer and firing an invoice.past_due webhook — skipping disputed and zero-balance invoices.
• Invoice PDFs download from the dashboard or the API, and invoices can be resent.
• Payments that arrive outside checkout — a wire, a cheque — are recorded against the invoice so the books close.
• Notes and dispute flags keep the context with the invoice.

One invoice list for your buyers

Card captures, terms invoices, and subscription charges appear in a single per-buyer invoice list. The @usethrottle/invoices React package drops it into your own customer portal.

Good to know

• Overdue reminders run in production only.
• There’s no write-off flow, and a single invoice can’t be paid in parts yet.
• An overdue invoice doesn’t block the buyer from placing new orders.