The invoice is forty days old. A collection sequence that stays civil

Late payment is handled worst by the people it hurts most. A small business owner waits, feels awkward, waits longer, then sends something sharper than intended at day sixty. That sequence produces slow payment and damaged relationships at the same time.

A fixed sequence applied to every customer identically fixes both problems, because it removes the decision about whether to chase this particular person, which is the decision that causes the delay.

Before anything: make the invoice easy to pay

A surprising share of late payments are administrative rather than deliberate. The invoice went to the wrong person, lacked a purchase order number the customer's system requires, or arrived without a way to pay that suits them.

So: send it the day the work finishes, not at month end. Address it to the person who approves payment, having asked who that is. Include whatever reference their system needs. State the due date as an actual date rather than as terms. And offer a payment method that takes thirty seconds, because a customer who has to write a check will do it on the weekend, or not.

Day one after due: the automated reminder

A short automatic message noting the invoice is now due, with the invoice attached and a payment link. No tone at all. Most accounting software sends these and turning the feature on collects a meaningful share of late invoices with no human involvement.

The value of it being automatic is that it is not personal. Nobody is offended by a system.

Day seven: a short personal email

Two sentences. "Invoice 1043 for $2,850 was due on the fourth and I do not think it has come through yet. Could you let me know when it is scheduled?"

Asking when it is scheduled is better than asking for payment, and it is the most useful sentence in this whole sequence. It assumes good faith, it is easy to answer, and the answer tells you which situation you are in: an administrative problem, a cash flow problem, or an unspoken dispute about the work.

Day fourteen: a phone call

Email is easy to defer and a call is not. Call the person who approves payment, be pleasant, and ask the same question. Establish a specific date.

Then confirm it in writing straight afterward: "Thanks for the call, noting the payment is scheduled for the twenty-second." That converts a verbal commitment into a record, which matters if the date passes.

If the reason turns out to be a dispute about the work, you have now found it, and that is a different process which should be dealt with on its merits rather than as a collection matter. Ask exactly what the issue is, in writing, and resolve or reject it explicitly.

Day thirty: a formal letter with a deadline

Now the tone changes, once. A written notice stating the invoice number, the amount, the original due date, any late fee your terms provide for, and a deadline for payment. One sentence saying what happens after the deadline, and only something you will actually do.

Send it by a method that produces proof of delivery, and copy the person you have been dealing with as well as their accounts function.

This letter collects a large share of what has survived the earlier steps, because it is the point at which the file stops looking routine to whoever is deciding which invoices get paid this week.

After the deadline: the options that remain

Stop work if any is ongoing, and say so in advance rather than simply disappearing. Continuing to work for someone who has not paid the last invoice increases the amount at risk and signals that the terms are optional.

For a construction related debt, find out whether a mechanics lien is available and what its deadlines are, because they are strict and they run from dates that have already passed. This is the strongest remedy in the trades and it is lost by missing a filing window.

Otherwise: small claims court for amounts within your state's limit, or a collection agency for larger ones, which takes a substantial percentage and generally ends the relationship. Decide which before threatening either.

Preventing the next one

Most of this is avoidable at the point of sale. Deposits on larger jobs. Progress payments on longer ones. Stated terms on every invoice including a late fee, so that the fee is enforceable rather than invented at day forty. A credit check on any new commercial customer taking significant work on terms.

And keep the sequence identical for everyone. Applied uniformly it is a process, and nobody takes a process personally. Applied selectively it is a judgment about a particular customer, and that is the version that costs you the relationship.