Direct answer

Terms agreed before the work, repeated on the invoice, with the clock starting at acceptance. That is what gets invoices paid on time.

Most late payment is not malice; it is ambiguity with a due date missing. An invoice that says a total and little else gives the client's accounts side nothing to act on: no calendar date to schedule, no stated consequence to prioritise against, and no agreed answer when someone raises a query and the whole amount quietly waits. Payment terms fix that, but only when they are agreed before the work starts and then repeated, word for word, on the invoice itself. Terms that appear for the first time on an invoice are a surprise, and surprises get disputed. This page gives you the five lines that do the work, the reason the payment clock should start from the client's acceptance of the delivery rather than from the moment you happened to send the invoice, and a complete terms block you can copy onto your next quote and invoice unchanged.

See the instrument first: the live demo runs one real call and hands you its verifiable receipt, no signup.

Updated November 16, 2026. First published November 16, 2026. The records quoted below are real and public, read back from the live service on November 16, 2026.

Step 1. Agree the terms before the work, then repeat them on the invoice

Payment terms have two homes and they need both. The first is the quote or agreement, before any work exists, where the client accepts the terms as part of accepting the price. The second is the invoice, where the same terms are printed again next to the amount, so whoever processes payment sees the date and the rules without hunting for a contract. Terms living only in the agreement get forgotten by the person who actually pays; terms living only on the invoice were never agreed, and a client can fairly say so. The agreement version can be one short paragraph, the five lines in step 2, and the invoice version is the same paragraph copied, not paraphrased. Consistency is the point: when a payment is late, you are not arguing about what the terms should have been, you are pointing at words the client accepted twice.

Step 2. The five lines that do the work

Line one, the amount and what it is for: the total, the job or stage it covers, and the delivery it pays for, named so the payer can match the invoice to accepted work in seconds. Line two, the due date as a calendar date: a term such as net 14 is a duration, not a date, and durations get counted from different starting days by different people, so the invoice states both, payment within 14 days of acceptance, due 30 November 2026, with the actual date filled in. Line three, a stated late consequence: a fee or interest figure, modest and real, whose main job is not the money but the priority it gives your invoice inside a payment run. Line four, a dispute window: queries about an invoice are raised in writing within a stated number of days, and any undisputed part is still paid on the due date, so one questioned line can never hold a whole invoice hostage. Line five, a pause right: if an invoice passes its due date unpaid, further work pauses until it is settled, stated calmly at agreement time so using it later is procedure, not escalation. Five lines, each answering the exact question a payer or a late payer would otherwise improvise an answer to.

Step 3. Start the clock at acceptance, so the due date rests on a fact both sides can check

Terms need a starting event, and the weakest one is the day you sent the invoice, because sending is your act, arrival is arguable, and neither says anything about whether the work was accepted. The strongest starting event is the client's acceptance of the delivery: a dated decision, by a named side, over a stated set of work. The record format is AER-1, published as an IETF Internet-Draft (draft-zambo-aer1-26), created by Brennan Zambo, and each step carries a verifiable receipt: a receipt proves the saved result was not changed since it was saved. The two public records below show what an acceptance fact looks like:

Accepted: the decision is on the record

Pending: checked, and still waiting on a decision

Read the accepted record as the model: status accepted, decided by the client, on a stated date, over 4 steps, all checked. An invoice whose terms run from that date has a due date neither side has to take on trust, and a dispute window that opens and closes on the record. The pending record shows the gap to close before invoicing where you can: work checked, no decision yet, which means the clock has no agreed start and the invoice will float. Where a client will not accept formally, invoice anyway with the delivery date as the stated start, but know which of the two you hold: a clock started by a shared fact collects noticeably better than a clock started by your say-so.

Step 4. Match the strictness of the terms to the client in front of you

The five lines are constant; their settings are not. For a new client, keep the clock short, 7 or 14 days, and take a deposit before the first stage, because you have no payment history to lend against. For a large company, expect their payment run to be the real clock whatever your invoice says, so the work that matters is getting the invoice complete and correct for their process, purchase order number, exact matching details, and the named approver, early enough to make the run. For a long-standing client who has always paid, longer terms cost you little and buy goodwill, and the late consequence can sit unused for years doing its quiet job. What never changes with the client is the structure: a calendar due date, a dispute window with the undisputed part payable, and the pause right. Loosen the numbers for clients who have earned it; never loosen the structure, because the structure is what you fall back on the one time a good client's payment goes wrong.

Honest limits

This page is general information about invoice terms, not legal advice: late fee and interest enforceability varies by place and by what was actually agreed, and statutory rules in some places set defaults or caps that override private terms, so a large contract deserves a local review once. Terms also do not manufacture money in a client who has none; they remove ambiguity, which is the cause of most late payment, not all of it. A verifiable receipt proves the saved result was not changed since it was saved; it does not prove an invoice was paid, which is why the acceptance record and the payment record stay separate and linked. Zambo never holds funds and cannot collect an invoice for you; it makes the delivery and its acceptance checkable, which is the fact your terms start from.

The terms block, ready to copy

Paste this onto your quote, and again onto the invoice, filling the brackets once per job. Payment is due within [14] days of your acceptance of the delivery, by [calendar date]. The amount covers [job or stage] as delivered and accepted. A late fee of [1.5 percent per month] applies to amounts unpaid after the due date. Queries about this invoice are raised in writing within [7] days of the invoice date; any undisputed part remains payable on the due date. If an invoice is unpaid after its due date, further work pauses until it is settled. Deposits and stage payments already made are credited on the invoice they belong to. Six sentences carrying all five lines. Print it where the payer will see it, near the total and the due date, not in a footnote, and keep the wording identical from job to job, so the day you need it, it is the wording the client has already accepted several times before.

Frequently asked questions

What payment terms should I put on my invoices so clients pay on time?

Five lines, agreed before the work and repeated on the invoice: the amount tied to the named delivery it pays for; a due date written as a calendar date, not only a duration, counted from the client's acceptance of the delivery where you can; a stated late consequence, modest and real; a dispute window requiring queries in writing within a set number of days, with any undisputed part still payable on the due date; and a pause right if an invoice passes its due date unpaid. Then set the numbers to the client: short clocks and a deposit for new clients, completeness for a large company's payment process, longer clocks for clients with a payment history. Terms remove the ambiguity most late payment feeds on; they work because the client accepted them twice, at the quote and again on the invoice.

Should my payment clock start when I send the invoice or when the client accepts the work?

At acceptance, where you can arrange it. Sending is your act and arrival is arguable, so a clock started at sending rests on your say-so. Acceptance is a dated decision by the client over a stated set of work, which both sides can check, so the due date and the dispute window run from a shared fact. Where a client will not formally accept, deliver, invoice with the delivery date as the stated start, and keep the delivery record attached, so the start date is at least evidenced rather than remembered. The pattern to avoid is invoicing long after delivery with no stated start at all, which hands the payer a fresh excuse to count the days from whenever the invoice happened to surface.

What late fee should I put on my invoices?

A modest, stated one that you would actually apply: 1 to 1.5 percent per month on the overdue amount is a common shape, or a fixed administration fee where that is normal in your trade. The fee's real job is priority, not income: an invoice with a stated consequence gets scheduled ahead of one without, inside a payment run. Two cautions keep it honest. Enforceability varies by place and by whether the client agreed the term before the work, which is one more reason the terms live in the quote, not only on the invoice. And a fee you never apply teaches clients it is decoration, so apply it once, calmly, the first time it is earned, or remove it from your terms.

How do I stop one disputed line from holding up my whole invoice?

With the dispute window line, agreed in advance: queries are raised in writing within a stated number of days of the invoice date, and any undisputed part remains payable on the due date. That single sentence changes the shape of a dispute. Without it, a question about one line freezes the whole amount while the question drifts. With it, the client pays the undisputed balance on time and the questioned line is argued on its own, with a deadline for raising it that stops fresh objections appearing month by month. When you invoice a job in stages, the same effect comes free: each stage invoice is small, tied to its own accepted delivery, and a dispute touches one stage instead of the whole project fee.

How does a job record help my invoice terms actually work?

It gives the terms their starting fact. When the work runs through Zambo, built by Brennan Zambo, every job lands on its own record with a verifiable receipt for each step under AER-1, published as IETF Internet-Draft draft-zambo-aer1-26, and the client accepts the delivery on that record with a date and a release state, so the due date counts from a decision both sides can open, the dispute window opens against a stated set of steps, and the undisputed part is easy to identify because the stages are itemised on the record. Every tool free once a day, plus 3 continue calls. One free wrap-up handover per day, and pickup is always free. For $0.99, deliver your next job on one record, so the terms on its invoice start from an acceptance you can point to instead of a date you have to argue for: get the Day Pass. A Day Pass is unlimited for 24 hours, no subscription. Ongoing use is the Zambo Pass at $29 a month, $19 a month for $ZAMBO holders, or Lifetime at $250 one time.

Related