HIVE80lab — Ops notes

Overdue Invoice Collection Ladder for Small Teams

The work is not done when the deliverable ships. The work is done when the money lands. Small teams are good at the first half and quietly terrible at the second, because chasing money feels rude — but it is only rude when it is improvised. A client who receives a calm, scheduled, professional reminder at day 1, day 7 and day 14 thinks they have their act together. A client who receives one furious email at day 45 thinks they are unprofessional and desperate. The difference is not the client; it is the ladder. This page is the ladder: five steps, pre-written, tone rising on a schedule, run in fifteen minutes a week by one named owner.

1. The clock — starts at the due date, owned by one person, read every Friday

Collection fails first as a bookkeeping failure: nobody knows which invoice is how overdue. So the ladder starts with a view, not an email — one page listing every open invoice with five columns: client, amount, due date, days overdue, and the next action with its date. One person owns the page (in a five-person team, that is the founder or the ops person — collection is a founder-adjacent job, not a task you delegate to whoever is least busy). The ritual is fifteen minutes every Friday: read the list, send this week's rungs, write next week's actions. The aging buckets decide where attention goes: 0–30 days is process (invoices are simply late, not at risk), 31–60 is friction (something is wrong — find it), 61–90 is relationship (a call, not an email), 90+ is decision (the write-off math in step five). The month-end close already produces the raw material — this is where the aged invoices actually get worked, weekly, while they are still conversations and not confrontations.

2. The five steps — pre-written, tone rising, never improvised

The entire trick is that the emails are written before they are needed, so the Friday pass is copy-paste-send, and the tone rises on schedule instead of with your mood.

Day 1 past due — the friendly nudge. Assume process failure, not bad faith, because day-1 late is process failure 90% of the time. One short email: "Hi Sam — invoice #142 for $2,800 was due yesterday. Probably just slipped; here it is again attached. Could you confirm it's in your next payment run?" The attached invoice matters more than the sentence: a third of all "late" payments are literally a lost email. This step collects a shockingly large share of aged receivables by itself.

Day 7 — the firm reminder. Still polite, now specific and dated: restate the amount, the original due date, and ask for one thing — a payment date, not a payment intention. "Could you confirm the date it will be paid?" is the question that converts "yes, it's coming" into a calendar entry. A promise with no date is the most common way late invoices become 90-day invoices.

Day 14 — the phone call, and the real question. Email replies slow down precisely when something is actually wrong; the phone finds out what. The question that matters is not "where is our money" but "who processes this payment on your side?" — because late payments hide behind exactly three blockers (next section). Fifteen minutes on a call routinely beats six more emails.

Day 30 — the formal notice. Tone flat, not angry; facts, not feelings. Restate the amount, the dates, the two prior reminders, and invoke the clauses that were written into the contract at signing (step four): the late fee and, where the contract allows it, the pause of ongoing work until the account is current. The pause clause is only usable if it was agreed at the start — which is precisely why it must be in the template contract, not invented during the argument.

Day 60 — the final notice and the decision. A dated final notice stating the amount and a deadline, and then the write-off math from step five: collections agency or small-claims (usually 25–50% of the amount either way), or a professional write-off that converts the loss into the deposit policy that prevents the next one. What never happens is the silent 90+ bucket — an invoice you have stopped looking at but not decided about.

3. The three blockers most late payments hide behind

Nearly every overdue invoice is one of three things, and each has a script. "We never received it" — the lost-invoice third of all late payments; response: resend to the named person plus their AP inbox, and from now on send every invoice to two addresses (the client and their accounts mailbox) with the number in the subject line. "We dispute the work" — rare but real; response: stop the ladder's tone escalation for this invoice and move it to a human conversation about scope, because chasing harder on a disputed invoice burns the client; if the dispute is legitimate, credit it fast and fix the scoping process; if it is not, the paper trail you kept (approved scope, delivered work) is what settles it. "Our client hasn't paid us" — the one small teams forgive too easily; response: genuine sympathy, a specific date, and a new rule going forward: your terms are not collateral for their cash flow. A client who is chronically "waiting on their client" pays the vendors who invoice early and deposit-first, not the ones who wait politely.

4. Prevention beats collection — the clauses and habits that make the ladder rare

The best collection call is the one you never make, and it is purchased at the contract stage, not the overdue stage. Four habits do most of the work. Deposit first: 50% up front on all new-client work — a client who resists a deposit is telling you, before you have done a hour of work, exactly how they pay; believe them. Terms earned, not assumed: new clients start at Net-15; Net-30 is a reward earned by six months of on-time payment, not a default. Two clauses in every contract: a late fee (1.5% per month or a flat late charge — stated plainly, enforced evenly; a clause you never invoke trains clients that your terms are decorative) and a pause clause (ongoing work pauses when an invoice is 30+ days past due). Invoice the day work ships, not at month-end — every day between delivery and invoice is a day you donated to their cash flow. A team that does these four things rarely climbs past step two of the ladder; the ladder exists for the exceptions, and the exceptions are mostly new clients who have not yet learned your terms.

5. The write-off decision — made with math, once, in writing

At 90+ days, stop escalating and start deciding. The math is short: a collections agency or small-claims route recovers, historically, somewhere between half and three-quarters of what it chases, minus a third of it in fees, plus weeks of founder attention — so a $1,200 invoice is usually not worth it and an $18,000 one usually is. The honest part is the rule, decided in a calm week and written in the decision log: "we pursue debts over $X and write off under it, once, with a lesson." The write-off is not a failure; the failure is having no deposit policy when the client was signed. The invoice that gets written off should change one thing — the deposit percentage, the client vetting question, or the pause clause — or you have paid tuition twice for the same course. What a write-off is not: a reason to stop the ladder for everyone else, which is the quiet way a $2,000 loss becomes a $20,000 accounts-receivable habit.

A worked example: $14,200 aged, one Friday ritual, three weeks

A five-person studio runs its first honest aging list at a runway review — the runway page's "dunning pass" is this page, systematized. Six invoices, $14,200 total: two at 0–30 ($3,900), two at 31–60 ($5,400), one at 61–90 ($2,600), one at 97 days ($2,300, a client who went quiet). The Friday ladder runs three weeks: the day-1 and day-7 emails collect both young invoices in eleven days (one was a lost email, resent to the AP inbox, paid in four days). The day-14 calls surface the real blockers on the mid bucket — one client's AP had the wrong tax ID and quietly sat on it for six weeks, the other's "client hasn't paid us" turns into a split payment plan: half now, half in three weeks, both dated in writing. The 97-day invoice gets the final notice; the client pays $1,300 within a week of the pause clause being invoked, and the remaining $1,300 goes to the write-off line with the lesson — that client had resisted the deposit at signing, and next time the 50% deposit is a condition of starting, not a negotiation. Net: $12,850 recovered in twenty-one days for roughly forty-five minutes of scheduled email. The studio's decision-log entry: "the ladder is now a Friday habit; awkwardness was costing us $5,000 a quarter."

Related pages

An invoice is not revenue until it is cash, and cash comes to the team that asks on a schedule. Own the aging list, one person, fifteen minutes every Friday; send the pre-written reminders at day 1, 7, 14, 30 and 60 with tone rising on schedule; treat every late payment as one of three findable blockers; write the deposit, earned-terms, late-fee and pause clauses into the contract before the work starts; and make the write-off decision with math, once, in writing. Small teams that chase politely and predictably get paid — and stop financing their clients' cash flow for free.

  • Failed Payment Recovery Sequence — when the "late payer" is an expired card on a subscription, not an invoice

    • The cheapest overdue invoice is the one you never invoice: quotes that close on the day-8 deadline (see the quote follow-up sequence) get deposit invoices out immediately, and deposits rarely age.

    This playbook is part of the Hive80 Lab ops kit line — field-tested, instantly downloadable: The ladder works hardest on invoices that were never collected up front — the upfront deposit checklist moves half the invoice to signature day so the ladder has less to climb.