Payment terms are the single most negotiated clause on a freelance invoice — and most freelancers get them wrong. They either default to Net 30 because it "sounds professional," or write "Due on Receipt" because they want to get paid fast, not realizing that neither approach is optimized for actually getting paid.
The difference between good and bad payment terms isn't just about cash flow. It signals how you run your business. A freelancer with clear, enforced payment terms gets paid faster, attracts more serious clients, and spends less time chasing invoices than one with vague or inconsistent terms.
This guide breaks down every common payment term pattern — Net 30, Net 15, Net 7, Due on Receipt, and 50% upfront — with honest pros, cons, and when to use each. Plus: how to write late payment clauses that actually work.
The Four Main Payment Term Patterns
Before picking a term, understand what each one signals to the client — because they read these differently than you might expect.
| Term | Days to pay | What clients think | Best for | Verdict |
|---|---|---|---|---|
| Due on Receipt | Immediate | "Pay now" — often treated as Net 7 | Small, one-time, low-value work | Use sparingly |
| Net 7 | 7 days | Fast turnaround expected | Quick deliverables, known clients | Good option |
| Net 15 | 15 days | Professional, standard | Most freelance work — the default | Recommended |
| Net 30 | 30 days | Corporate standard, expected | Large clients with AP departments | Only if required |
| Net 45 / Net 60 | 45–60 days | Enterprise billing cycle | Large corporations, government | Avoid if possible |
| 50% Upfront | Deposit now, balance on delivery | Serious vendor, standard practice | New clients, large projects | Always for new clients |
Net 30 vs Net 15: The Real Difference
Most payment terms debates come down to this one. Net 30 is what large companies default to. Net 15 is what freelancers who care about cash flow should default to.
30 days
- + Expected by enterprise clients
- + Rarely questioned in corporate environments
- − 30-day cash gap on every invoice
- − Late payers become 45–60 day payers
- − Compounds badly across multiple clients
15 days
- + Faster cash flow on every project
- + Rarely pushed back on by smaller clients
- + Late payers become 20–25 day payers
- + Signals you run a tight business
- − Some enterprise clients will require Net 30
The practical takeaway: start every new client relationship at Net 15. If a large client pushes back and explicitly requires Net 30 as a condition of doing business, accept it — but don't volunteer it. Most clients never ask. They pay what the invoice says.
The average freelance invoice gets paid 8–12 days after the due date — not on it. On Net 30 terms, that means 38–42 days to payment. On Net 15, it's 23–27 days. The difference is two weeks of working capital on every invoice, compounding across every client.
Due on Receipt: When It Works and When It Doesn't
"Due on Receipt" sounds like the fastest payment term, but it's actually one of the least effective — because most clients don't take it literally. When a client sees "Due on Receipt," they mentally translate it to "pay sometime soon," often treating it like Net 7 at best.
The problem isn't the intent — it's that "receipt" is ambiguous. Did the client receive the email? Open the invoice? Download the PDF? That ambiguity gives clients cover for delay.
Due on Receipt works in these cases:
- Small, sub-$500 services where immediate payment is genuinely expected (emergency edits, rush work, one-off consultations)
- Returning clients you have an established payment history with
- Services where you're delivering something the client needs immediately (a license key, a file, access to something)
Due on Receipt fails in these cases:
- Large projects where the client's AP department handles payment — they'll ignore "receipt" and pay on their cycle anyway
- New clients who don't have your banking details set up yet
- Any work where the client's internal approval process adds days to payment
If you want fast payment without the ambiguity of "Due on Receipt," use Net 7 with an exact due date. "Due May 12, 2026" is clearer and harder to ignore than "Due on Receipt."
The 50% Upfront Pattern
A deposit isn't a payment term — it's a business practice. But it belongs in this conversation because it changes your cash flow more than any net term can.
Requiring a 50% deposit before starting work does three things: it proves the client is serious, it covers your costs if the project stalls, and it psychologically commits the client to completing the project (people are less likely to ghost when they've already paid half).
When to always require a deposit
New clients you haven't worked with before. Any project over approximately $1,000. Work with significant upfront research, strategy, or planning time. Projects with unclear or evolving scope.
Standard deposit structures
50/50: Half upfront, half on delivery. Simple, cleanest for projects under $5,000. 30/30/40: Start, milestone, delivery. Better for longer engagements where you want to confirm commitment at the midpoint.
How to present it without awkwardness
"My standard terms are 50% to start and 50% on delivery. I'll send the first invoice when we confirm the scope — you can pay by card or bank transfer." Matter-of-fact tone, no apology. Most clients expect it.
Net terms on the balance
The deposit invoice is typically Due on Receipt or Net 7. The final balance invoice gets your standard Net 15. Clients who paid the deposit promptly usually pay the balance just as fast — you've established the payment relationship.
Set payment terms once, enforce automatically
IndieOps embeds your payment terms on every invoice and sends automatic reminders on the due date, at day +3, and day +7 — so you get paid without writing a single follow-up email.
Try IndieOps freeHow to Write Late Payment Terms That Actually Work
Most freelancers either skip late fees entirely or mention them vaguely in their contract and then never enforce them. Neither approach helps. The right play is to state your late fee policy explicitly on every invoice — and then actually mean it.
Late fees have two functions: deterrence and enforcement. The deterrence value is highest — clients who see a specific late fee clause pay earlier than those who don't. The enforcement value is secondary, but important when you have a repeat late payer.
Late fee language that holds up
1.5% per month is the standard rate — it's high enough to motivate payment without being punitive. The collections mention is optional but effective for larger invoice amounts.
Include this language in two places: your contract (so it's agreed to before work starts) and on the invoice itself (so there's no "I didn't know" when the due date passes).
When to actually enforce the fee
The honest answer: enforce it selectively and deliberately. For a client who's always paid on time and is two days late, waiving the fee is a reasonable relationship decision. For a client who is consistently 15+ days late and you've sent multiple reminders, the fee is leverage — and not charging it signals that it was never real.
The moment you decide to enforce a late fee, send a revised invoice with the fee added and a clear subject line: "Updated Invoice #042 — Late Fee Applied." Keep the tone matter-of-fact. You're not angry; you're applying the terms you both agreed to.
Matching Payment Terms to Client Type
Not all clients are the same, and your payment terms shouldn't be either. Here's how to adjust based on who you're working with:
| Client type | Recommended terms | Notes |
|---|---|---|
| New client, unknown history | 50% upfront + Net 15 on balance | Non-negotiable for projects over $500 |
| Established client, good history | Net 15 | Can relax to Net 30 if they request it |
| Small business / startup | Net 15 | Cash-constrained; shorter terms help both sides |
| Mid-size agency | Net 15–30 | Depends on their AP cycle; ask upfront |
| Enterprise / large corp | Net 30 (accept Net 45 if required) | Their AP cycle is fixed; negotiate rate, not terms |
| Chronic late payer | 100% upfront or stop working with them | Past behavior predicts future behavior |
The Exact Date Rule
The highest-leverage change most freelancers can make to their invoices: replace your net term with an exact due date.
"Net 15" requires the client to calculate when the invoice is due. "Due: May 20, 2026" does not. The difference sounds minor but it's not. Vague terms get processed when someone gets around to it. A specific date creates a deadline.
Include both: "Net 15 — Due May 20, 2026." The term is there for the record; the exact date is what gets paid. You can see how this applies to the full invoice structure in our guide on how to invoice clients as a freelancer.
Freelancers who switch from "Net 30" to "Due: [specific date]" report average payment times dropping by 5–8 days without changing anything else. The explicit deadline creates urgency that an abstract term doesn't.
Putting It Together: Your Payment Terms Policy
You should have a written payment terms policy — even if it's three sentences — that you use consistently across all clients. Consistent terms signal that you run a professional operation, not a one-person project.
Here's a template you can adapt:
State this when you send your project proposal — not when you send the invoice. Clients who know the terms upfront are far less likely to push back or pay late.
If you're still building out your invoicing process from scratch, the free invoice template guide covers the full field-by-field structure of a professional freelance invoice.