How to Write a Payment Terms Section Clients Actually Read

You wrote payment terms into your contract. They are in there, somewhere around clause nine, in the same paragraph as the bit about governing law. The client signed it. And then the invoice went thirty-eight days past due anyway, and when you finally asked about it, they said something like "oh, I thought we were on net 60."

It is a maddening moment, because you did the responsible thing. You put it in writing. What you are running into is not a contract problem so much as a reading problem: terms that are legally sound but practically invisible. Nobody argues with a section they never absorbed — they just operate from whatever assumption they walked in with.

This post is about writing that section so it actually lands: where it belongs, the phrasing that removes wiggle room, and the decisions to make before you write a line. None of it needs a lawyer, and all of it is fixable in an afternoon.

Why good payment terms still get ignored

Start with the scale of the gap. Xero's US small business data puts the average wait on an invoice at about 29 days in 2026, with payments landing roughly nine days later than agreed. QuickBooks' 2026 late payments report found 59% of small businesses now carrying invoices 30 or more days overdue, up from 47% the year before. Stated terms and actual behaviour have drifted a long way apart.

Some of that is genuine cash-flow pressure on the client's side, and no amount of drafting fixes that. But a meaningful share is simpler: the person paying your invoice is often not the person who read your contract. Your agreement was signed by a project lead; the invoice is processed by someone in finance who has never seen it, working from the invoice and whatever their default assumption is.

So the section has two jobs, and most contracts only do the first. It has to be enforceable, and it has to be transmissible — plain enough that whoever signed it can repeat it accurately to whoever pays it. Terms that cannot survive being explained in one sentence over Slack will not survive an accounts department.

Decide the terms before you write them

Writing is the easy part. Most vague payment sections are vague because the decision underneath was never made. Settle these five questions first:

• How long the client has. Net 30 is borrowed from enterprise procurement, not something you owe a small client. Net 14 or Net 15 is entirely reasonable for a service business, and it is where a lot of freelancers land after one bad quarter.
• Whether the clock starts at invoice or delivery. Different dates, sometimes weeks apart. Pick one and name it.
• What you take up front. For project work, 25–50% before you start is standard, and it does more than protect you — it tells you early whether the client's payment process actually functions.
• Whether there is a late fee, and what it is. A common figure is 1.5% per month on the overdue balance. You cannot apply one retroactively, so this is a write-it-now-or-never decision.
• Which payment methods you accept, and who covers the fees. Especially internationally, where a wire fee can quietly eat a chunk of a small invoice.

Still weighing the first question? Our breakdown of Net 30 versus due on receipt covers how each behaves in practice, and if the deposit is the part making you uneasy, we covered the language in how to ask new clients for a deposit.

Put it where people actually look

The highest-leverage change most people can make is positional. Terms buried in the back half of a contract, between indemnity and termination, are functionally invisible. Move them forward: in a proposal or statement of work, the payment section belongs immediately after scope and before anything procedural, because that is where the reader is still paying attention.

Then repeat it. The terms belong in three places, at three different lengths:

• The contract or SOW — the full version, with the late fee, payment methods and anything conditional.
• The invoice itself — one line, with the due date as an actual calendar date. "Due 14 September 2026" beats "Net 14" because it needs no arithmetic and no shared view of when the clock started.
• The kickoff email — one plain sentence confirming the arrangement, so there is a searchable record in the client's inbox that is not a PDF attachment.

That third one matters more than it sounds. When finance asks "what are we paying and when," the project lead searches their email, not the contract folder.

Write it in sentences a busy person can parse

A payment terms section does not need to sound legal to be enforceable. It needs to be specific and unambiguous — a different quality entirely, and one plain English is very good at.

Compare these. First, what most contracts say:

"Payment shall be rendered by the Client within a reasonable period following receipt of invoice, subject to approval of deliverables."

Three escape hatches in one sentence: "reasonable period," "following receipt," and "subject to approval." The last is the worst, because it hands the client an unbounded internal review as a legitimate reason not to pay. The same clause with the hatches closed:

"Invoices are due 14 days from the invoice date. Payment is due on completion of the work described in this agreement, not on internal review or sign-off. Overdue balances accrue a late fee of 1.5% per month. Accepted methods: bank transfer or card; the client covers any transaction fees on international payments."

Four sentences, no defined terms, nothing that needs a definitions page. A project manager can read it once and relay it accurately. That is the test.

The phrases worth removing

A few bits of standard language do more damage than their length suggests:

• "Upon receipt." Sounds urgent, means nothing. Receipt by whom, on what date? Replace it with a number of days from a named starting point.
• "Subject to approval." Ties your cash flow to someone else's calendar. If a review step really exists, cap it: "the client has five business days to raise revisions; the invoice is due regardless."
• "Promptly" and "as soon as practicable." Polite ways of saying whenever.
• "Net 30" with no date on the invoice. The term is fine; the missing date is the problem.
• Terms split across two clauses. If the timeline is in one place and the late fee in another, the reader absorbs one and misses the other.

What to do when the client pushes back

Occasionally a client reads your terms carefully enough to negotiate them, which is a good problem to have. Some larger organisations have a real policy floor and cannot pay faster than net 45 without an exception process — that is not them being difficult.

Trade rather than concede. Longer terms for a larger deposit. Net 45 for a milestone schedule instead of one invoice at the end. Or the longer window on condition that the late fee stays exactly as written — a client confident they will pay on time has no reason to object.

What to avoid is quietly dropping the section because it felt awkward to defend. The awkwardness is coming either way; the only question is whether it happens now, over a document, or in six weeks when the money has not arrived.

Clear terms make the follow-up easier, not unnecessary

Here is the part that is easy to get wrong. Well-written terms do not stop late payments; they change what a late payment means. When the terms were vague, a follow-up is a negotiation — you are re-litigating what was agreed. When they were specific, it is a reminder of a date you both already know, which is a far easier message to write and to receive.

So the two work together: clear terms plus a consistent follow-up rhythm is the whole system, and neither half does much alone. If the rhythm is the piece that keeps slipping — and for most people it is, because it has to happen while you are busy with actual work — that is the gap DueDrop was built to close, sending the friendly nudges on schedule so you are not the one remembering to write them. And if you have been wondering whether to add a late fee at all, we looked at whether they actually change behaviour rather than just sitting on the page.

Frequently Asked Questions

How long should a payment terms section be?

Four to six sentences in the contract, one line on the invoice. Anything longer is usually boilerplate the client skims or edge cases better handled in a separate clause. The constraint is useful: if you cannot state your terms in six sentences, some part of the arrangement is still undecided.

Is Net 14 too aggressive for a new client?

It is not, and it is increasingly common for service businesses. Net 30 is a convention inherited from enterprise procurement, not a standard you are obliged to match. Most small and mid-sized clients pay on whatever schedule you state, as long as you state it up front rather than introducing it later. Larger corporate clients may have a policy floor — a conversation for the proposal stage, not the first invoice.

Can I add a late fee to an invoice if my contract does not mention one?

No. A late fee has to be disclosed before the work is done, which means it belongs in the signed agreement and, ideally, on the invoice too. Applying one retroactively is generally unenforceable and reliably damages the relationship. If your current contract is silent, add it to the next one rather than to the outstanding balance. Caps on late fees vary by jurisdiction, so check what applies where you operate.

Should the payment clock start at invoice date or delivery date?

Invoice date is cleaner: it is one unambiguous moment both sides can see on the document. Delivery date invites debate about what counts as delivered. What matters most is picking one and naming it explicitly — "14 days from the invoice date" — rather than leaving it implied.

What if the client's finance team never sees my contract?

Assume they will not. That is why the invoice needs a calendar due date on its face and the kickoff email should restate the terms in one plain sentence. Treat the contract as the enforceable version and the invoice as the operational one — the invoice is what the person paying you is actually looking at.

The short version

• Terms have to be enforceable and repeatable — if your client cannot relay them in one sentence, their finance team will never hear them.
• Decide the timeline, start date, deposit, late fee and payment methods before you write; vague clauses are undecided clauses.
• Move the section forward, then restate it on the invoice as a calendar date and in the kickoff email as one plain sentence.
• Cut "upon receipt," "subject to approval," and "promptly" — each hands back the certainty you were trying to create.
• Clear terms do not eliminate late payments; they turn the follow-up from a negotiation into a reminder.