DEV Community: KitDesk

Net 7 vs Net 30: pick a due date finance can actually honor

KitDesk — Wed, 16 Sep 2026 13:14:33 +0000

“Net 30” sounds professional. For a solo freelancer, it often means you finance the client for a month and then spend another week chasing.

The due date on your invoice isn’t a vibe. It’s the day you agreed cash should clear — and it only works if both sides can honor it.

What Net 7 and Net 30 actually mean

Net 7: payment is due 7 days after the invoice date.

Net 30: payment is due 30 days after the invoice date.

Not “I’ll start thinking about it in 7 days.” Not “ASAP.” A calendar date you can put in a reminder sequence.

If your agreement says Net 14 and the invoice only says “due upon receipt,” you’ve handed AP an ambiguity. Write the date.

Why freelancers default to Net 30 (and why that’s often wrong)

Net 30 is corporate muscle memory. Big companies run pay cycles. Your rent does not.

A practical way to choose

Ask one question before you send terms: Who is paying, and how do they run AP?

Solo founder / small shop / new client: Net 7 or Net 14. Deposit before kickoff. Final files after balance clears.
Mid-size with a real AP inbox: Net 14 is a common compromise. Confirm the billing contact and whether they need a PO.
Enterprise that only pays Net 30 / Net 45: Either accept it and raise the price / use milestones so you’re not floating the whole project, or walk. Don’t pretend Net 7 will survive their pay calendar.

Also match terms to project shape: milestone invoices (due Net 7 each) beat one giant Net 30 at the end when all leverage is gone.

Make the due date operable

Whatever you pick:

Put it in the agreement and on the invoice as a real date
Send to the billing contact, not only your day-to-day contact
Reuse the same Day 0 / 7 / 14 reminders after that date — process, not pep talks
Pause new work only if you already wrote that right before you needed it

A due date finance can’t honor is decoration. A shorter Net term plus a deposit usually beats a polite Net 30 you can’t afford to wait for.

I keep agreement, SOW, invoice, and those reminder emails in one $5 starter pack here: https://kitdesk.carrd.co
For new or small clients, long terms increase:

Your unpaid exposure while you keep delivering
The chance the invoice gets buried in a monthly batch
The awkwardness of follow-ups that start a month late

Net 30 can be fine for trusted retainers or enterprises that will not pay faster — if you priced the wait into the fee and you can float the cash. It is a poor default for first projects with strangers.

Buy Freelancer Kit ($5) — contract, SOW, invoice templates + payment emails: https://workspace50.gumroad.com/l/cpzjm

The four documents I send before freelance work starts (so the invoice isn’t a surprise)

KitDesk — Wed, 16 Sep 2026 12:11:52 +0000

Most freelancers obsess over the invoice.

That’s backwards.

By the time you send an invoice, the money conversation should already be finished. The invoice is a receipt for something both sides already agreed — not a hope that finance will invent a due date for you.

I wrote separately about what to do when payment is already late. This post is the stack that makes “late” less common: four boring documents you send before kickoff.

1. A short services agreement (not a novel)

You don’t need twenty pages of recycled legalese. You need clarity on:

Who the parties are (legal names)
What you’re selling at a high level
Fee, currency, deposit, when you invoice, due dates (Net 7 / Net 14 beats “ASAP”)
What happens if they cancel mid-project (kill fee)
Whether you can pause work if payment is overdue
When IP transfers (usually on full payment) and portfolio rights

Keep it plain English. If the project is large or regulated, get local counsel. For everyday freelance work, a short agreement beats a vague chat t
“Homepage + four inner pages in Figma, two revision rounds, stock photos provided by client” is scope.

When something new appears mid-project, you don’t argue vibes. You point at the SOW and quote a change order.

3. An invoice template finance can actually pay

Blank or half-finished invoices create delay. AP pays what they can process.

Minimum fields I reuse every time:

Your legal / business name and contact
Client name and project name (matching the agreement)
Invoice number, issue date, due date
Line items tied to the SOW (not vibes)
Payment methods that work for them
A one-line reference to the agreement / late fee if you use one

I keep the same invoice in Word, Excel, and a simple HTML version for email. Matching the client’s preferred format removes one excuse.

4. Payment follow-up emails written when you’re calm

When money is overdue, emotion is expensive. Process is cheap.

I reuse the same sequence:

How the four fit together

Agreement + SOW before work.
Invoice that matches those documents.
Follow-ups that don’t invent new rules mid-chase.

If you only fix one thing this week: send the agreement and SOW before kickoff, and put a real due date on the invoice. That alone beats another round of “just circling back.”

I packaged the templates I actually use (agreement, SOW, invoice formats, and those Day 0/7/14 emails) into a $5 starter pack here: https://kitdesk.carrd.co

Steal the process even if you write your own files. The win isn’t the PDF — it’s sending the right paper before the work starts.

Day 0 overdue: polite reminder + invoice reattached + payment details
Day 7: firmer note that references the payment terms you already agreed
Day 14: pause-work / final notice — only if your agreement allows it

Write these once. Reuse them. You’re not being cold; you’re being consistent.hread.

Buy Freelancer Kit ($5) — contract, SOW, invoice templates + payment emails: https://workspace50.gumroad.com/l/cpzjm

2. A one-page scope of work (with out-of-scope)

This is where unpaid “one more tweak” dies — or thrives.

Good SOW lines look like: deliverables, formats, revision rounds, assumptions, timeline dependencies on client feedback/assets, and a short out-of-scope list.

“Website redesign” is not scope.

Late Invoices Aren’t a Personality Problem — They’re a Process Problem

KitDesk — Wed, 16 Sep 2026 09:30:22 +0000

If you’ve freelanced longer than a month, you’ve stared at an unpaid invoice and wondered what you did wrong.

Usually nothing. The client isn’t evil. You’re not “bad at business.” What’s missing is a repeatable process that makes payment the default outcome—not a hope.

This is the system I use when money is late (or about to be).

The invoice is too late to be your first document

Most freelancers treat the invoice like the start of the money conversation. By then, scope is fuzzy, due dates live in Slack, and “Net 30” means “whenever finance gets to it.”

Send three things before meaningful work starts:

A short services agreement — who the parties are, what’s being bought, payment timing, late fees (if any), kill fee / pause-work language, IP ownership in plain English.
A one-page scope of work — deliverables, what’s out of scope, revision rounds, assumptions. This is what stops “one more tweak” from becoming free labor.
Invoice timing in writing — deposit (e.g. 50% up front), milestones, or Net 7 / Net 14. If it’s only verbal, it’s optional in the client’s calendar.

When those three exist, the invoice isn’t a surprise. It’s a receipt for something already agreed.

What belongs on the invoice (so AP can pay you)

A blank or half-finished invoice creates delay. Finance teams pay what they can process.

Minimum fields:

Your legal / business name and contact
Client name and project name
Invoice number, issue date, due date
Line items tied to the agreed scope (not vibes)
Payment methods that actually work for them
A one-line late-fee or reference to the agreement, if you have one

I keep the same invoice in Word, Excel, and a simple HTML version for email. Matching the client’s preferred format removes one excuse.

Don’t send only a PDF with no context. Pair it with a short payment email: what’s due, by when, how to pay, and a calm “reply if anything’s unclear.”

A boring late-payment sequence beats improvising angry

When an invoice is overdue, use the same sequence every time. Emotion is expensive. Process is cheap.

Day 0 overdue: polite reminder + invoice reattached + payment link/details.
Day 7: firmer note that references the payment clause in the agreement.
Day 14: pause work / final notice — only if your contract allows it. Don’t invent leverage you didn’t negotiate.

Write these emails once. Reuse them. You’re not being cold; you’re being consistent.

Sample Day 0 tone (adapt freely):

Hi {{name}}, quick note that invoice {{#}} for {{project}} was due {{date}}. I’ve reattached it here with payment details. Happy to confirm receipt or answer any AP questions.

Sample Day 7 tone:

Hi {{name}}, following up on invoice {{#}} (due {{date}}). Per our agreement, payment was due on that date. Please confirm when it will be processed, or let me know if you need a different format.

Why late pay keeps happening (even with “good” clients)

Scope lived in chat, so disputes feel legitimate.
No deposit, so you’re financing their project.
Due date was “ASAP.”
You waited two weeks to follow up because it felt awkward.

Awkward is cheaper than unpaid. Follow up on the schedule you wrote when you were calm.

Soft tools, not a sermon

You don’t need a course. You need documents you can send the same day: agreement, SOW, invoice, and a small set of payment follow-ups.

If you want a ready-made pack (Word + Excel + HTML invoice, contract + SOW, and 12 payment emails), I put mine in Freelancer Kit for $5: https://workspace50.gumroad.com/l/cpzjm

Steal the process even if you write your own templates. The win isn’t the file—it’s sending the right paper before the work, and the same reminder after the due date.

Checklist you can use today

[ ] Agreement signed (or at least emailed and acknowledged) before kickoff
[ ] SOW attached with out-of-scope listed
[ ] Deposit or clear Net terms
[ ] Invoice fields complete + due date visible
[ ] Reminder emails drafted for Day 0 / 7 / 14
[ ] Pause-work rule written before you need it

Late invoices feel personal. They’re usually procedural. Fix the procedure once, then reuse it.

Buy Freelancer Kit ($5) — contract, SOW, invoice templates + payment emails: https://workspace50.gumroad.com/l/cpzjm