Invoice terms (Net-N)
How Throttle decides an invoice's due date, the four places that value can come from, and why a term is frozen onto the invoice at issue.
Net-N is how long a buyer has to pay after an invoice is issued. Throttle does not have a fixed Net-30 — the number is configurable per customer, and can be negotiated per deal. This page covers where that number comes from and what freezes it.
Where the number comes from
Four sources, checked in this order. The first one set wins:
| Precedence | Source | Where it’s set | Recorded as |
|---|---|---|---|
| 1 | Negotiated term | Accepted on a quote | cart_override |
| 2 | Customer default | net_n on the customer | customer_override |
| 3 | Cart term | Set on the cart | cart_override |
| 4 | Global default | DEFAULT_NET_N, falls back to 30 | global_default |
The resolved value and its source are both written onto the issued invoice, as net_n and net_n_source.
A negotiated term outranks the customer’s standing default, and that ordering is deliberate. A customer default describes how you usually bill an account; a term accepted on a quote is a specific agreement for one deal, with recorded evidence of the buyer accepting it. When the account default won instead, a quote issued and accepted at Net-60 was invoiced at the customer’s Net-7 — billing the buyer 53 days before they had agreed to pay.
Valid values
Any integer from 0 to 365. Zero is legitimate and means due on issue — useful for a deposit or a cash-on-delivery account, and it is not the same as leaving the field unset. Unset means “fall through to the next source”; 0 means “due now”.
Terms are frozen at issue
Once an invoice is issued it keeps the term it was issued with. Editing a customer’s net_n afterwards changes what their next invoice gets and leaves every historical invoice alone.
This is why net_n and net_n_source are stored on the invoice rather than looked up on read. A finance team reconciling a six-month-old invoice needs the terms that applied that day, not today’s. If you need to change the due date on an invoice that already went out, that is a new invoice or a credit, not an edit.
Setting a customer default
Leave netN unset or null on a customer and they inherit the global default. Set it and every invoice for that customer uses it, unless a quote negotiated something else.
curl -X PATCH https://api.usethrottle.dev/api/v1/customers/cus_51.../ \
-H "X-API-Key: $THROTTLE_SECRET_KEY" \
-H "Content-Type: application/json" \
-d '{ "netN": 45 }'null clears it back to the default rather than meaning zero. This is the distinction most likely to bite: 0 and null are different instructions, and only one of them means “due immediately”.
Who gets Net-N at all
Offering invoice terms is a credit decision, not a checkout setting — you are shipping goods before you have the money. Throttle gates it on an allowlist: a customer is either approved for Net-N or they are not, and the terms above only apply to customers who are. There is no per-customer credit limit today, only the binary allowlist, so an approved buyer can place orders of any size on terms.
If you are extending terms at meaningful volume, that gap is worth knowing about before it matters rather than after.
Where to look next
Issued invoices and what is outstanding live under Finance in the dashboard, with the aging report breaking receivables into standard buckets. Terms themselves are configured on the customer record, not per order.
Last updated August 9, 2026