My client is always late paying. How do I get paid faster?

Treat chronic lateness as a queue problem: your invoice waits behind every question the client's side must answer internally. Review the receipt and actual deliverable before accepting a handover.

Last updated: 2026-10-17

Some clients are late to everyone, and their lateness has structure: invoices sit while an approver hunts for confirmation the work arrived, matched the brief, and was the agreed price. Each hunt can take weeks inside a busy firm, and your invoice competes with every other supplier's hunt. The freelancer whose delivery answers all three questions on one link, with the acceptance already recorded on it, is processed first because processing is trivial.

The rest of the system is timing and terms. Invoice on acceptance day, not at month end, because queues are processed in arrival order more often than in fairness order. Set the due date from the acceptance, with a late step named in the agreement (a fee where your market supports one, or an explicit pause on new work, which large clients feel more). Send the day-one reminder with the record attached, so even the reminder is verification-complete.

Where lateness persists after the system is fair, price it honestly: deposits for new work, shorter windows, or a late-payer premium folded into the next quote. A client who is late and objects to every remedy is giving you information about the relationship's real terms; the record at least ensures the lateness is about cash, not about doubt.

Checklist: the late-payer system

1. Delivery as a record, acceptance recorded on it. 2. Invoice issued the day of acceptance, record link on the invoice. 3. Terms: due date counted from acceptance; late step named (fee or work pause). 4. Day 1 past due: reminder with the record and the acceptance date. 5. Day 7: firmer reminder naming the late step now in effect. 6. New work: deposit or shorter terms until the pattern breaks. Keep every artefact in the job folder; the pattern, documented, is what changes behaviour.

Worked example

The acceptance this system runs from is visible on public records like https://zambo.dev/handover/45434a17-4afc-486a-9646-e689bcee4297 , where the client's decision sits on the delivery itself. An invoice issued against a state like this leaves the payer nothing to hunt for, which is the queue-jump in its entirety.

Frequently asked questions

Is it risky to charge a late fee to a big client?

The late step works even when never collected, because it changes the invoice's priority inside their process. Name it in the agreement before work starts, apply it calmly, and waive it strategically once, in writing, when payment lands.

The client is late because their own clients pay late. Does the system still help?

It moves you to the front of the queue they pay from when money arrives, which is the realistic prize. Verification-complete invoices are the ones a stretched payer clears first, because clearing them costs no internal effort.

Should I stop working with chronically late clients?

After the system has run fairly for two or three cycles, the remaining lateness is a price signal: raise the price to carry it, take deposits, or exit. Decide from the documented pattern, not from the frustration of one bad month.

By Brennan Zambo, founder of Zambo.

Last verified: 2026-10-17.

Invoice the next acceptance the same day, record attached: https://zambo.dev/demo/ .

Try a handover

A handover gives your client one proof link with verifiable receipts to review, then Accept or Flag.

try it: say 'use zambo to hand this over to <client>' in your ai

Add Zambo · Handover docs · Real public handover · AER-1