You finished the job in March. You invoiced in March. It is now May, the money is still “in process,” and the strangest part is how ordinary this feels — because net-30 quietly became net-45 became “we pay at sixty, sorry.” Late payment is the default setting of business-to-business life, but it is not a law of nature: a large share of it is caused by the invoice itself — when it was sent, what it says, and what happens the day it goes overdue. So why do some invoices get paid in nine days while identical work waits fifty? Here is what the fast-paid ones do differently.
The short answer: speed is decided before the invoice exists
The fastest-paid invoices are set up in the agreement, not the document: the price, terms and due date agreed in writing before work begins, a deposit collected up front, and the payment process designed so that paying you is the easiest thing your client does all week. The invoice then simply executes decisions already made. Everything below is that system, piece by piece.
What exactly belongs on the invoice?
More than most templates include, and every missing item is a reason for a payment department — or a procrastinating client — to set it aside. Your business name and contact details, the client’s correct legal name, a unique invoice number, the issue date, and the due date written as an actual date, not a term: “Due April 15,” never just “Net 30,” because a date can be circled on a calendar and a term must be calculated. Then the itemization: each service or product on its own line, described in the client’s language (the project name they use internally, the PO number they issued), quantity, rate, line total. Finish with the amount due in the largest type on the page, the taxes and fees itemized rather than buried, and exactly how to pay — link, details, the works. The US Chamber’s invoicing best-practice guide covers the same anatomy; the principle underneath it is friction: every question an invoice leaves unanswered is a day it sits unanswered too.
When should it be sent?
The same day the work is delivered or the milestone is hit — this is the single highest-yield habit in this article. An invoice sent while the client is still enjoying the result gets paid like a thank-you; the same invoice sent three weeks later gets processed like archaeology. For longer projects, invoice in milestones rather than one giant bill at the end: smaller invoices clear approvals faster, arrive while goodwill is fresh, and surface a payment problem at week two instead of month three. Recurring work should ride on recurring invoices generated automatically — the goal is that no invoice ever depends on you remembering, on a busy Friday, that it exists.
Who should the invoice go to — and does format matter to big clients?
Two addressing mistakes quietly delay more payments than any term you set. The first is sending the invoice only to the person who commissioned the work, when their accounts-payable department — a different human, in a different queue — is the one who pays. Ask at the start of every engagement: “Who should invoices go to, and is there an AP address I should copy?” The answer takes ten seconds at the start and saves ten days at the end. The second mistake looms with larger clients: many run strict intake rules — the invoice must quote their PO number, match the PO’s line amounts, and arrive as a PDF through their portal or AP inbox, and anything non-conforming is rejected without a phone call, discovered by you at day forty. Confirm the client’s invoicing requirements in the same conversation as the price. Conforming exactly to a big client’s boring process is not bureaucracy; it is the fast lane through it.
Should you offer an early-payment discount?
The classic term “2/10 net 30” — two percent off if paid in ten days — deserves arithmetic before adoption. Two percent for twenty days of speed annualizes to roughly 36 percent, which makes it some of the most expensive financing a business can offer; on thin margins it gives away the profit to buy back your own money slightly sooner. It can still be rational in narrow cases — a chronically tight cash position, a client whose payment you are deliberately prioritizing — but the cheaper levers come first: deposits, shorter terms, milestone billing and friction-free payment rails buy the same speed without the standing discount. Offer it deliberately, to specific clients, with the math in front of you — never as a default line on the template because a template suggested it.
How do terms and deposits change the outcome?
Shorten the window where you can: net-14 is unremarkable now in most service industries, and net-7 for small amounts is increasingly normal — every day removed from the term is a day removed from the average payment, because most clients pay a fairly fixed number of days around the due date you set. Take deposits on anything substantial: 30 to 50 percent up front both funds the work and psychologically commits the client to the project’s paperwork being in order. And state the late fee on the invoice itself — typically 1 to 1.5 percent per month — not because you expect to collect millions in fees, but because an invoice with a stated consequence is triaged differently from one without. (The FreshBooks guide to late fees covers the wording and the etiquette in useful detail.)
How easy is it to actually pay you?
Auditing this question honestly embarrasses many small businesses. The pay-now link on the invoice should complete in under a minute: card and ACH accepted, no account creation, no “please call for details.” Card fees of 2.9 percent sting until you price them against the alternative — fifty days of waiting and two hours of chasing — at which point they are among the cheapest money you spend. Offer the rails your clients already use, state them on the invoice, and never make a willing payer solve a puzzle.
What happens on day one overdue?
A system, not a mood. On the due date, an automated reminder for anything unpaid (many clients genuinely forgot, and a same-day nudge pays a surprising share). At seven days overdue, a personal, pleasant, specific message: the invoice number, the amount, the original date, the payment link again. At fourteen, a call — voice changes the priority of things in a way email cannot. At thirty, the late fee appears, stated calmly as the policy executing itself, and new work pauses until the account is current — said early, in the agreement, so it is never a threat invented mid-dispute. Notice what the sequence never contains: anger, guilt, or a fourth identical email. Firmness with courtesy resolves almost every late invoice that is resolvable; the small remainder are a client problem, not an invoice problem, and they get solved at the client level.
The tooling that makes all of this automatic
None of the above survives on memory, which is why the mechanics belong in software: invoicing built into your accounting tool, automatic reminders on a schedule, online payment links, and a weekly ten-minute review of one aging report — who owes what, since when. At some point the honest question becomes whether the system should be run by you at all — the analysis in is it worth hiring a bookkeeper for a small business weighs exactly that handover, and most owners who read their aging report weekly already know their answer before they finish it.
Questions owners ask about getting paid
Is it rude to charge late fees to good clients? It is businesslike to have a stated policy and merciful to waive it once, on the record, for a genuinely good client with a genuine problem. What is rude — to yourself — is financing other companies’ operations for free, indefinitely, without ever naming terms.
Should small invoices be chased at all? Yes, quickly and lightly, because small unpaid invoices are rarely about money — they signal a process gap (wrong contact, missing PO) that will recur on a large invoice if it is not fixed on the small one.
What if a client disputes part of an invoice? Ask them to pay the undisputed portion now and put the disputed lines in a separate, short conversation with a deadline. A single contested line should never hold the whole amount hostage — and a client who insists it does is telling you something important about every future invoice you will ever send them.
The bottom line
Payment speed is mostly designed, not deserved. Agree terms before the work, deposit up front, invoice the same day, write a date not a term, make paying take sixty seconds, and let a calm automatic ladder handle the overdue days. Do that and “net-30 became net-60” stops being weather that happens to your business and becomes what it should have been all along: a setting you control.
1 Comment