Skip to content

Freelance payment terms explained: Net 15, Net 30, deposits & milestones

By the Billebly team · Published 10 June 2026 · Last updated 22 August 2026

Ask five freelancers when their invoices are due and you'll get five different answers, some amounting to "whenever the client gets around to it." That's the real problem behind most late payments: terms only work if they're specific, stated before the work starts, and matched to the job. A client who doesn't know exactly when they're supposed to pay usually doesn't pay on time, not out of malice, but because "due date: unclear" reads as "no rush." Here's how the common structures work and how to pick without guessing.

Due on receipt

"Due on receipt" means the invoice is payable the moment the client gets it, with no 15 or 30-day window. It fits small, quick jobs: a one-off logo tweak, a two-hour consulting call, a single blog post for a first-time client. The job's too small to justify a wait, and there's no relationship yet to extend credit on.

The catch: it isn't self-enforcing. Without a real deadline attached, plenty of clients treat it exactly like Net 30, since nothing about it feels urgent. Pair it with a specific date and a payment link, so paying immediately is the easy option, not the eventual one.

Net 15

Net 15 gives the client 15 days from the invoice date: a middle-ground term, fast enough that you're not floating a balance for a month, but long enough for a client with even a basic approval step (a manager sign-off, a bookkeeper cutting checks weekly) to hit it. It's a good default for repeat clients on small-to-mid-sized projects, where you've built enough trust to extend time but not enough to want 30 days of exposure.

Net 15 also signals "professional but not corporate": more deliberate than due on receipt, without the 30-day cycle most larger companies default to.

Net 30

Net 30 is the term most companies expect, since it matches how their accounts payable departments work: invoices get batched, reviewed, and paid on a fixed monthly cycle. If you're billing agencies, mid-size companies, or any client with a real finance department, Net 30 usually isn't a negotiation: it's their standard process, and asking for less can slow things down instead of speeding it up.

The tradeoff is cash flow: thirty days is a long time to go unpaid, especially if several Net 30 clients land staggered and none of the money arrives the same week. It's the right term for larger, established clients with real payment processes, and the wrong one for a small client with no AP department, where 30 days becomes an invitation to forget.

50% upfront + 50% on delivery

Splitting a project fee into a deposit and balance changes what you're protecting against: instead of managing when a client pays, you're managing whether they pay at all if the project stalls or gets cancelled halfway through. Fifty-fifty is the most common split for freelance project work (a website build, a brand package, a multi-week consulting engagement) because it puts real money down before you start and ties the second half to delivery, not just time passed.

This structure also filters out clients who were never serious: someone unwilling to pay a deposit before you start tells you how the rest of the engagement will go. If you're unsure how much to ask for or how to phrase the request without sounding like you don't trust the client, this breakdown of freelance deposits and upfront payments covers sizing the deposit and the wording that gets it agreed to.

Milestone-based payments

For anything that runs longer than a few weeks (a multi-phase build, a rebrand with several rounds of revisions, a consulting engagement with distinct deliverables), a single deposit-and-balance split leaves too much exposure on one side. Milestone billing breaks the fee into three or more payments, each tied to a specific deliverable (wireframes approved, first draft delivered, final files handed over), with its own invoice and due date.

Milestones keep the money moving in step with the work, instead of piling all the risk onto one deposit and final balance. If a project stalls after milestone two, you've been paid for one and two; if a client is slow approving milestone three, only that invoice is late, not the whole engagement. The tradeoff is more invoices to track: a real cost if done manually, but not a reason to avoid the structure where it fits.

Put the terms in the contract, not just the invoice

An invoice due date is easy to ignore if it's the first time the client has seen it. State the payment terms (due on receipt, Net 15, deposit percentage, milestone schedule) in the contract or proposal before work starts, so the invoice is just executing something the client already agreed to. If your contracts don't currently spell this out, freelance contract essentials covers what to include beyond scope and price.

Retainer and recurring terms

Ongoing work (a monthly coaching package, an on-call retainer, recurring maintenance) doesn't fit the above well: there's no single delivery point to tie payment to. Retainer terms are simpler than project terms: a fixed fee, charged on the same date every billing cycle, regardless of how the hours were used that period. Some retainers bill in advance, for the month ahead; others in arrears, for the month just finished. Advance billing is safer, since you're not extending unpaid work before the first invoice from a new client.

Recurring terms only work if the fee and cadence are actually stable, since forcing scope that's still being negotiated into a fixed schedule just automates a guess. Recurring billing vs. one-off invoices covers how to tell which of your clients have settled into retainer territory versus ones that still need one-off invoices.

Comparing the options at a glance

TermBest forRisk
Due on receiptSmall, one-off jobs and new clientsNo real deadline unless paired with a specific date and payment link
Net 15Repeat clients, mid-sized one-off projectsStill relies on the client's own approval process moving fast enough
Net 30Larger clients and agencies with a formal AP processTies up a month of cash; easy for smaller clients to forget entirely
50% upfront + 50% on deliveryDefined project work with a clear end pointClient may push back on the deposit if it isn't framed clearly
Milestone-basedLonger, multi-phase projectsMore invoices to track and follow up on individually

Set payment terms once, not per invoice

Billebly lets you attach due dates, deposit splits, and payment links to every invoice automatically, so the terms are clear before a client can claim they weren't.

Try the free invoice generator

How to pick the right terms for the job

Three questions get you most of the way there. How big is the job: a few hours, a few weeks, or ongoing? How established is the client: brand new, occasional repeat, or a company with a real finance department? And how much cash flow risk can you actually absorb if payment slips?

Small, short jobs with new clients: due on receipt or Net 15, leaning toward payment before or immediately after delivery rather than extending credit with no track record. Larger projects with a defined end: a deposit plus balance, or milestones past a month or two. Established clients with formal AP processes: Net 30 usually isn't worth fighting, but you can still ask for a deposit on the first engagement before you've built trust. Anything ongoing: a retainer, billed on a fixed schedule, ideally in advance.

The term only does its job if it's unambiguous and stated before the invoice shows up. A client never told when payment is due, what happens if it's late, or how the fee breaks down has no reason to treat any date as firm, which is exactly how invoices drift from "due this week" to "due whenever." If you're deciding whether to attach consequences to a missed date, should you charge a late fee covers when that actually changes client behavior.

Frequently asked questions

Share