From the Halvern blog

Small-business collections: a healthy process, what the law lets you send, and when splitting a bill beats full payment.

A working playbook for freelancers and very-small-business owners — a healthy collections cadence, the legal ground rules for reminders and final notices, and when it's smarter to split a bill than push for full payment.

Published August 11, 2026 · Last updated August 11, 2026

A healthy collections process isn't a single stern email — it's a cadence. The shape is roughly the same at every scale, but at the one-to-five-person business it gets compressed into a few minutes of attention most weeks instead of a workflow. Day 3: a light nudge that the invoice is past due with the payment link attached (not a bare 'just following up' — that habit nobody responds to). Day 7: a friendlier reminder with a specific date for action. Day 14: a firmer note that names the next step. Day 21: a final notice before the file goes outside. Day 30 and beyond: a real escalation path. The cadence is yours, but it should be consistent — a customer you chase this week and forget next month has learned that silence works, and a customer you never chase has learned that your invoices are negotiable. Almost no one at this scale keeps that cadence by hand; almost everyone loses real cash to the slip.

What the law lets you send is straightforward, and the right tone is even more straightforward than people think. Reminders are not collections notices. They can state the amount due, when payment became overdue, the original payment terms, and what you'll do next — but they should not accuse, threaten an action you wouldn't actually take, or borrow the language of consumer debt collection. The federal consumer-protection rules don't apply to most B2B invoices, but the underlying norms are worth following anyway: no repeated calls at inconvenient hours, no abusive or profane language, no disclosure of the debt to third parties, and no false claims about legal action. They keep the relationship intact if the customer comes back. A final notice is owed when you intend to escalate — it should state specifically what is about to happen (a formal demand letter, a small-claims filing, a third-party referral) and when, and it should not be sent repeatedly. Below the small-claims threshold in your jurisdiction, pulling in counsel is almost never worth it; the cost of a lawyer's letter is often larger than the invoice.

Splitting a bill is, more often than people expect, the right move. The cues are simple: the customer replies and clearly intends to pay but cannot hit the original date; the customer asks for a date you can actually plan around; or your own cashflow needs the confirmation of payment-as-it-arrives rather than the lump. A split that pairs each installment with a specific purchase order line — and tagged notes on the books — closes cleanly and reconciles on the customer's side too, so neither side has a mystery at month-end. Two failure modes worth naming: offering the split yourself before the reply (which reads as if you weren't expecting them to pay in full), and the vague 'pay what you can' without a date or amount (which extends the silence). Either way, you don't get the cash; you do get the awkwardness.

An AI silent colleague picks up the thread where the cadence tends to break — the day-7 reply that needs a thoughtful answer, the quiet installment proposal, the four-line negotiation the owner would handle if they had a quiet hour. Halvern does this work in your voice. It reads the reply, classifies intent (will pay, disputes, gone silent, needs time), proposes dates or splits, and only loops you in when the decision is yours to make — a large refund, a chargeback dispute above your own threshold, a customer asking for something your policy doesn't cover. Routine nudges, installment splits, and the first three turns of negotiation never interrupt you. The relationship is preserved because the email still reads like the business — same from-name, same domain, same voice — rather than like a system. That's the line dunning software habitually crosses: a templated blast is unidirectional and tone-deaf, and the customer reads it as a signal that your business has given up on them.

The visible half of the same loop is a Monday-morning report: what was collected this week, what slipped, what Halvern negotiated and what got escalated to you, and what's projected by Friday. That report is what makes the rest of the work feel legitimate — it's the receipt for the cadence, and the only way the chain becomes a system instead of a habit. If this is the kind of work you'd rather not run by hand, the rest of the site sketches out how it works on your books, or you can email us directly and we'll set up a sandbox account within the week.