Payment Terms That Get You Paid — The Late-Invoice System for Solo Businesses
Late payments are not bad luck — they are the predictable result of weak terms, vague invoices, and chase sequences that start too late and escalate too gently. One-person businesses feel every late invoice personally, so the system has to work without your constant attention.
This guide sets up that system: terms that filter slow payers before they hire you, invoice mechanics that get paid faster, a four-step chase sequence with exact scripts, and late-fee language that is enforceable rather than decorative.
The short answer
- Invoices sent within 24 hours of delivery get paid roughly twice as fast as invoices sent "when there’s time".
- Net-14 with a deposit outperforms Net-30 on both speed and write-offs for solo service businesses.
- Automated reminder at 3 days before due date cuts late payments by a third — most lateness is forgetfulness, not malice.
Who this playbook is for
Built for solo founders tired of chasing invoices and floating client costs from their own pocket.
Step 1: Set terms that assume money now, not money later
Default terms: 50% deposit to book the work, 50% on delivery; or monthly-in-advance for retainers. Offer Net-14, not Net-30 — Net-30 is a corporate convention that punishes small vendors. Put terms on the proposal, the contract and every invoice; consistency is what makes them feel non-negotiable.
Step 2: Make the invoice frictionless and specific
Every invoice: itemized scope reference, PO number if they use them, correct legal entity name, payment link, and due date in words ("due 14 March 2026"). Invoices bounce in AP departments over missing details — one rejected invoice costs you 30 days. Ask AP contacts early exactly what they need to pay you.
Step 3: Automate the friendly layer before due date
Reminder at 3 days before due ("heads-up, invoice #204 is due Friday — link here"), on the due date, and at 3 days past. Automated, warm, two lines each. This layer alone resolves most late payments because forgetfulness, not dispute, causes the majority.
Step 4: Escalate on a fixed schedule with a human voice
Day 7 late: personal email — "invoice #204 is a week past due; is it stuck in approvals? Happy to call your AP contact." Day 14: pause new work clause activates. Day 21: late fee applies per contract, and a final notice with a payment plan offer. Every step scripted in advance so chasing never depends on your mood.
Step 5: Screen new clients for payment behavior
Before onboarding: deposit paid on time? Contract signed without edits to payment clauses? If a client negotiates the deposit down before work starts, you have previewed the entire relationship. Trust the preview — slow-payer patterns appear before the first invoice, every time.
Your weekly operating rhythm
| Day | Action | Time |
|---|---|---|
| Daily | Send invoices within 24h of any delivery milestone | 10 min |
| Monday | Review AR aging; trigger this week’s chase steps | 20 min |
| Per deal | Confirm AP requirements (PO, portal, entity details) at kickoff | 15 min |
| Monthly | Review write-offs and adjust deposit percentages | 30 min |
KPIs that tell you it is working
| Metric | Healthy target | Why it matters |
|---|---|---|
| Average days to payment | Under 14 | The system’s headline number |
| % invoices paid late | Under 15% | Driven mostly by deposit policy and reminder automation |
| Write-offs per year | Zero to one | More means deposits are too low for your client mix |
| Invoice rejection rate | Under 5% | Rejected invoices are self-inflicted 30-day delays |
Common mistakes to avoid
- Net-30 with no deposit. You become a free lender to companies that would never lend to you; deposits flip the risk before work begins.
- Stopping work on late payers without saying so. The contract clause plus one clear email — "work resumes when #204 clears" — is both fair and effective; silent resentment pays nothing.
- Sending invoices late because delivery felt like the finish line. The invoice is part of delivery; automate it into the completion checklist.
A tool stack that fits a one-person budget
| Tool | Where it fits |
|---|---|
| Stripe / Wise invoicing | Payment links, automatic reminders, partial payments |
| Bonsai / Dubsado | Contracts with late-fee clauses wired to invoicing |
| Google Sheets AR aging | One tab: invoice, client, age, next action |
| Calendar | Escalation reminders at day 7/14/21 — no memory required |
Keep going
Use these internal references while implementing this guide:
- One Person Company Hub
- How to Start a One Person Company
- Solopreneur Operating System
- Money-Back Guarantees for Service Businesses
- Scope Creep Contract Language
- A Pro Bono Policy for Solo Founders
FAQ
Q: Are late fees actually enforceable?
Yes when they are in the signed contract, reasonable (commonly 1-1.5% per month or a flat amount), and consistently applied. Fees rarely get collected in full — their real power is motivational: clients pay on time to avoid them, which is the point.
Q: Should I stop work when a client pays late?
For overdue past a grace window you defined in the contract, yes — with notice. "Per section 4.2, work pauses on invoices 14+ days overdue" is professional, not aggressive. Working for free while chasing teaches clients that your deadlines are decorative.
Q: What payment terms should international clients get?
Same terms, plus clarity: who pays transfer fees (specify OUR/SHA), currency, and any portal requirements. International does not mean special — it means the invoice details matter even more because AP friction multiplies across borders.
Q: How big should my deposit be?
30-50% for projects, 100% for engagements under $1,500, first-month-in-advance for retainers. Scale deposits with client risk: new client and big project means higher deposit, not lower.
Get the weekly operating brief
Every Monday: 3 moves, 5 minutes. Actionable strategy for your one-person company — no fluff, no filler.