Invoice Payment Terms That Get You Paid: The Exact Wording, Line by Line

An invoice is not a document. It is an instruction set for someone else's payment process, usually executed by a person who has never met you, has forty other invoices in the queue, and will park yours the moment anything requires a question. After twelve years in finance, reviewing thousands of invoices from both sides of the table, I can tell you that most late payment starts on the invoice itself, in the details that made the AP clerk hesitate.

Here is the line-by-line wording that removes every hesitation.

The due date: write the date, not the code

Weak: "Terms: Net 30." Strong: "Payment due: August 14, 2026 (Net 30)." Net 30 requires the reader to find the invoice date and do arithmetic; a printed date requires nothing, enters their system as a hard field, and cannot be misread. Every day of ambiguity you remove is a day of DSO you never have to chase. While you are at it, print the invoice date and the delivery or service period explicitly, because "what period is this for" is the most common silent parking reason in services businesses.

The late fee line: present, factual, unapologetic

"Balances unpaid after the due date accrue a late fee of 1.5% per month." One sentence, on every invoice, whether or not you ever charge it. The wording, the legality caps, and the enforcement strategy deserve their own discussion, which I wrote here, but the invoice line itself does most of the work: AP prioritization software and humans alike sort fee-bearing invoices ahead of fee-free ones. Silence about consequences is a discount you are giving away.

Payment methods: make the fastest way the easiest way

List exactly how to pay, in your order of preference, with the details inline: "Pay by ACH (preferred): [routing/account or payment link]. Card: [link]. Check: [payable-to and address]." Every method that requires the payer to email you for details is a built-in one-week delay. If you use a payment link, put it at the top as a button or bold line; the single biggest payment-speed upgrade for most SMBs is turning a two-step payment into a one-click one.

The references AP actually matches on

Purchase order number, if the client issued one, displayed prominently; an invoice missing its PO does not get rejected, it gets parked, which is worse because nobody tells you. The client's own contact or approver name ("Attn: Karen Wu, Accounts Payable") so the invoice routes on arrival. And your contact for questions, a real monitored inbox, phrased as an invitation: "Questions about this invoice? Reply to billing@yourco.com and we will resolve it same day." That line converts silent disputes into loud, fast ones, which is exactly what you want, because silent disputes age into ghosting.

The optional line that changes behavior

If cash timing matters more than margin: "Early payment discount: deduct 2% if paid within 10 days (by August 25)." The math on whether that trade makes sense is real and worth doing before you offer it; the annualized cost is steep, roughly 37 percent, so it is a tactical tool rather than a default. But when used, put it on the invoice itself with the calculated deadline date, because a discount the payer has to compute is a discount that does not exist.

The full block, ready to adapt

Payment due: August 14, 2026 (Net 30). PO: 4471-B. Pay by ACH (preferred) via [link], card via [link], or check to [details]. Balances unpaid after the due date accrue 1.5% monthly. Questions: billing@yourco.com, same-day response. Attn: Karen Wu, Accounts Payable.

Six lines. Every one of them is answering a question before it gets asked, because in accounts receivable, the invoice that raises zero questions is the invoice that gets paid first. Structure buys you the first 80 percent; the follow-up system, which is the part we automate at RevCollect (bias disclosed), collects the rest. But the order matters: fix the invoice before you fix the chasing, because the best reminder in the world is the one the invoice made unnecessary.

FAQ

What payment terms should a small business put on invoices? A printed due date with the terms code in brackets, at least two payment methods with details inline, a late fee sentence, the PO and approver reference, and a monitored contact for questions.

Is net 30 from the invoice date or delivery date? By default, invoice date, but say so explicitly ("Net 30 from invoice date") because clients occasionally assume delivery date or month-end conventions, and every assumption is a delay.

Should I put late fees on the invoice even if I will not charge them? Yes. The stated fee changes payment priority regardless of enforcement, and stating it preserves the option. Springing an unstated fee later is both weaker legally and worse for the relationship.

Does offering multiple payment methods speed up payment? Yes, with a caveat: list them in your preference order and make the preferred one one-click. Friction, not preference, is what usually decides how and when an invoice gets paid.