Late Payment Is Designed In Before the Invoice Leaves, Not Fixed by Chasing

Ask an owner who is chronically late getting paid what they are doing about it, and the answer is almost always about chasing: a firmer email, a call on the right day, a difficult conversation they have been putting off. Chasing works up to a point, and it is the most expensive and least pleasant lever in the whole business. Nearly everything that determines when the money arrives was settled well before the invoice went out, in decisions that felt like paperwork at the time and were actually the design of the thing.

Terms Are a Choice, and Net Thirty Was Somebody Else's

Most small businesses use net thirty because it appeared on an invoice template they downloaded, and it came from a world of mailed checks and monthly accounting cycles rather than from any analysis of their own situation. Due on receipt is entirely normal for consumer work. Net fifteen is unremarkable for small commercial customers. Net thirty belongs where you are invoicing a company whose accounts payable function genuinely runs a monthly cycle, and even then it is worth knowing when that cycle closes, since an invoice arriving the day after a cutoff waits an extra month whatever the terms say.

Two questions to a new commercial customer before the first job handle most of this. What is your payment cycle, and what does an invoice need on it to be processed without a query. A purchase order number, a project code, a named contact. Getting those right the first time prevents the most common cause of delay, which is not reluctance to pay at all but an invoice sitting in a queue waiting for a missing field that nobody has told you about.

Deposits, and the Number That Actually Matters

A deposit does two jobs at once: it covers your material outlay so you are not financing somebody else's project, and it converts a maybe into a commitment. The useful sizing rule is that the deposit should cover the direct costs you will incur before you next invoice. If a job requires buying materials up front and the work runs three weeks, a deposit smaller than the material cost means you are lending the customer money for three weeks at your own expense. Deposits on residential work are capped in some states, and a few also dictate what the contract must say once one has been taken, which is worth checking before setting a policy rather than after.

Progress Billing on Anything Longer Than a Fortnight

A single invoice at the end of a two month job is a design flaw rather than a preference. It concentrates the entire risk at the moment your leverage is lowest, because the work is finished and the customer already has everything they wanted from you. Breaking it into stages tied to observable milestones rather than to dates fixes that: on materials delivery, on rough in completion, on substantial completion, with a final retention amount at closeout. Each stage is smaller to approve, and a payment that does not arrive tells you about a problem at the halfway point rather than at the end.

Making Payment Easier Than Not Paying

A surprising share of late payment is simply friction. The invoice arrived as a printed attachment requiring somebody to type details into a bank portal, so it moved to the bottom of a pile. Remove the friction wherever it costs less than the delay does. Send invoices electronically with a payment link. Accept cards and price for the processing fee rather than refusing the method that pays you the same day. Put the total, the due date and the payment method at the top, where they are visible without scrolling. Then send it the day the work finishes, while the customer still remembers being pleased, because an invoice sent within a day gets paid noticeably faster than the identical one sent a fortnight later.

A Follow Up Sequence Written Once

Chasing works far better as a schedule than as a reaction, because a schedule removes the decision about when it has become awkward to ask. Three days before the due date, a short reminder framed as a courtesy. The day after, a brief note that the invoice appears outstanding with a copy attached again. On day seven, a phone call to a person rather than an email to an address, asking whether the invoice was received and approved, which is a question rather than a demand and frequently surfaces the real reason. On day fourteen, a written notice referencing your terms and any late fee the contract provides for, with a specific date. On day thirty, stop work on anything ongoing.

Write those as templates once and send them on schedule, because consistency does most of the work: a customer who learns that your day seven call always comes starts paying on day five. Some customers were always going to be late, and the signals show early, in hard negotiation on price followed by more of it after the work, or a first payment that arrived late. The response is structural rather than personal, meaning a larger deposit, shorter terms, progress billing, and no new work started while an invoice is outstanding. Setting terms once and writing them down is the unglamorous groundwork the Small Business Administration spends much of its guidance on.

Businesses that get paid on time are rarely the ones with the best chasing scripts, and the owners running those businesses do not spend much time thinking about collections at all. They shortened the terms, took a real deposit, billed in stages, sent the invoice the same day, and made paying take under a minute. The chasing that remains is a short list rather than a weekly occupation, which is the actual prize here and the reason the design work is worth an afternoon.