Invoice payment tips: 24 practical levers (before, during, and after you send)

These invoice payment tips are written for people who are tired of “send earlier” and “be nicer” as the only advice. They are grouped by phase of the receivable, so you can scan for “before you invoice” versus “this is already 20 days late.” The tips are numbered for quick copy into internal playbooks. Not every tip applies in every market; B2B with AP is different from B2C card payments, and the tips say so where it matters.

Before you invoice: align the deal with how money actually moves

1. Put standard payment terms in the signed quote or order acceptance, not only on the back of the invoice footnote.
2. Name the legal entity that matches your bank account and the customer’s vendor file; a subtle mismatch is a 30-day delay for free.
3. Agree in writing what “done” is for a milestone, so a silent customer cannot hide behind scope fog.
4. Set internal rules for deposits or retainers in industries where that is the norm, so you are not 100% exposed before trust is built.
5. Decide in advance if you will accept card fees absorbed or passed through; that argument should not happen on the day they pay.
6. Clarify currency if you are cross-border; FX surprises are a classic reason a wire bounces or sits in an exception queue.
7. Name an AP contact in writing on large B2B deals, not only the buyer who loved the pitch.
8. For subscription-style work, align invoice calendar to their real payment runs (e.g. biweekly AP cycles).

The invoice itself: make entry into their system boring

1. One obvious invoice number, one obvious due date, and one amount due. Nothing clever.
2. Repeat remittance and entity details in the body of the email, not only the PDF footer.
3. Put the purchase order, project, or cost center where their portal’s upload form expects it.
4. For partial payments, make partial balances explicit on every subsequent invoice or statement.
5. If you are VAT- or sales-tax-registered, show the right registration numbers; AP sometimes rejects on compliance alone.
6. PDF file names that are boring: INV-2026-00042.pdf, not final_final2.pdf.
7. A clear late-fee or late-term line only if your contract supports it, not as an empty threat.
8. A single place for “if anything is wrong, reply to this address” so disputes route correctly.

After you send: timing, nudges, and tone

1. Send a pre-due nudge 3–5 business days before the date; it is a scheduling aid, not a nag.
2. On the due date, only ping if the amount is large or the customer is new; otherwise, wait a short business-day buffer.
3. On overdue, restate numbers and ask for a status and a pay date, not a lecture.
4. Never send the same paragraph twice; the second touch should add a new fact, deadline, or next internal step you already said in the contract.
5. For repeat late payers, attach a one-line “we will apply our policy on X date” that matches what you have already put in the contract.
6. If you use automation, keep human-readable signatures so the customer knows a person is accountable.
7. For emotional buyers, a short call often beats a long email; for AP queues, a narrow portal question often beats a call.
8. When a promise date is set, do not nudge the day before; check in on the day after if cash has not hit.

Tools and metrics: one number to watch without dashboard theater

Days sales outstanding, rolling 90 days, is enough for many teams if you use one definition: invoice date to cleared cash. A sudden jump in a single large customer’s balance often matters more than a one-point DSO wobble. For deeper playbooks, use get invoices paid faster and the guide on how to get clients to pay invoices on time as siblings to this one.