Freelance payment terms (guide)

Payment terms are not a formality. They are the rules that govern when you get paid, how much arrives first, and what you do in the gap between delivering work and seeing money. Get them right and your cash flow is predictable. Get them wrong and you spend half your time chasing invoices.

This guide covers the full spectrum of freelance payment term structures, when each one fits, how deposits protect you, why the specific wording of a due date changes client behavior, and how to propose your terms without apologizing for them. If you do not have a registered company and need to invoice clients professionally, Ruul invoices your client under its own name as the legal counterparty, so you can work with clients in 190 countries without a business entity.

What payment terms actually do

Payment terms do two things at once. They communicate the logistics of payment: when, how much, in what sequence. And they set an expectation in the client’s mind about the priority and urgency of paying you.

A freelancer who invoices with clear, specific terms gets paid differently from one who sends an invoice with no terms at all. The difference is not just mechanical. It is behavioral.

What payment terms include, at minimum: the due date or payment window, whether a deposit is required, how payment is structured across the project, and any conditions attached to each payment. They belong in your proposal, your agreement, and on every invoice you send.

The payment terms spectrum

Here is every structure you are likely to encounter as part of learning how to get paid as a freelancer, ordered from most protective of your cash flow to most accommodating of the client.

Payment in full upfront (100%)

Rare in practice, but appropriate in specific situations. Full upfront payment makes sense for small, well-defined digital deliverables: a single blog post, a logo, a short proofreading job. It also makes sense when a client shows early signs that they will be difficult to chase, or when you are doing rush work that cannot be paused.

Full upfront is harder to sell on larger projects. Most clients expect to tie some portion of payment to delivery. For higher-ticket work, a deposit plus milestone structure tends to be more effective than asking for everything upfront.

50% deposit, 50% on completion

The simplest way to share the risk. You collect half before starting and the remainder when the project is delivered or approved. This structure works because it splits the financial risk between you and the client. You take on the work; they take on the delivery milestone. Neither party has all the leverage.

It works best for project-based engagements of clear scope and predictable duration: a website redesign, a brand identity, a copywriting package, a short consulting engagement. It starts to break down on longer projects, where waiting until completion to collect the second half means you carry weeks or months of unpaid work. In those cases, milestone invoicing is a better fit.

Milestone payments

On longer or more complex projects, invoicing at defined deliverable points protects you from carrying large amounts of work without payment. On a three-phase project, you might invoice 30% upfront, 30% at a defined midpoint and 40% on delivery, or a third at each point. Each phase gets its own invoice. A long project with several distinct phases can start with a 25% to 30% deposit and add a payment at each major deliverable.

If a client stops paying or disappears halfway, you have been paid for every phase you finished, so only the current one is at risk. Each milestone is also a natural point to raise scope changes before they pile up. Milestones follow deliverables, while a retainer follows the calendar. For extra security, the client can pay the full amount into escrow at the start, and each milestone’s share is released as you deliver it.

Net 7

Payment due within 7 calendar days of the invoice date. This is the most protective net term available for standard freelance work. It is appropriate when the deliverable is already in the client’s hands, the project is complete, and there is no dispute about scope.

Net 7 is a reasonable ask in freelancing, especially once the work is delivered. It communicates that you run a professional operation and expect payment to happen promptly, not eventually.

Net 14

A two-week window is the sweet spot for most independent professionals. It gives clients enough time to process payment internally without creating a long enough gap to let the invoice slip down the priority list. Net 14 works across most client types and project sizes.

Net 15

Functionally the same as Net 14. Some freelancers and some client invoicing systems default to 15-day terms. Either works.

Net 30

The standard for established companies and corporate clients. Net 30 is a common baseline in procurement departments: invoices go into a payment cycle that runs roughly monthly. Thirty days is also the legal default for business clients in the EU and the UK when no payment date is agreed. That doesn’t mean the money arrives on day 30. In 2024, EU suppliers reported that business clients took 60.3 days on average to pay, against agreed terms of 43 days, according to the EU Payment Observatory.

For large enterprise clients, Net 30 is often non-negotiable on their end. For smaller clients and direct-hire freelancers, there is no reason to offer 30-day terms unless the client specifically requires them. It’s tempting to default to Net 30 because it sounds professional, when Net 14 or Net 7 would serve you better. Longer terms tend to go with later payment: in a QuickBooks survey of 1,305 US business owners in December 2025, 55% of businesses on net-30 terms had overdue invoices, against 26% of those that asked for immediate payment.

Net 60

Two months from invoice to payment. Net 60 shows up with large enterprises and some public-sector buyers, although public bodies often have shorter legal limits. EU public authorities generally have to pay within 30 days (60 in exceptional cases), UK public bodies usually within 30 days, and US federal agencies 30 days after receiving a proper invoice unless the contract says otherwise. In practice they can still be slow: EU suppliers reported that public authorities took 69.8 days on average to pay in 2024. Rules differ by country, so check the ones that apply to your client. Net 60 creates a genuine cash flow challenge: you deliver in week one and see money in week nine or ten, counting from the start of the work.

If a client requires Net 60, your options are to price the engagement higher to account for the cash flow gap, to invoice in shorter milestone intervals so that individual invoices clear faster, or to push back and negotiate to Net 30. If the engagement is large enough and the client is stable enough, Net 60 can be acceptable. It is genuinely problematic if you rely on this income to cover near-term expenses.

Due on receipt

Payment is expected immediately on receiving the invoice, typically by end of business that day or the next. This is appropriate for small, one-off deliverables where the work is already done, the client has received it, and the amount is modest. It also fits established client relationships where trust is high and payment has always been prompt.

One important caveat: corporate clients with accounts payable departments cannot process payments on demand. For them, “Due on Receipt” often becomes “whenever AP gets to it,” which can mean weeks. Use Due on Receipt with individual clients, small business owners, and established relationships where you control the payment dynamic. For enterprise clients, Net 14 or Net 30 is more realistic.

Retainer (recurring monthly)

A retainer is a recurring monthly arrangement where the client pays a fixed amount in advance of each work period in exchange for a defined scope of ongoing work. How to structure retainers and invoice for them is covered in the subscription payment guide. If you have ongoing client work that could convert to a retainer, subscription invoicing lets your client approve once: Ruul charges their card every week or month, issues the invoice each period and pays you within one business day.

Quick reference: Payment terms at a glance

Term	Best For	Cash Flow Protection	Typical Client Friction	When to Use
100% Upfront	Small digital deliverables, rush work, new clients with limited track record	Highest	High for large amounts	Small jobs under $500, rush delivery, red-flag clients
50/50 Deposit-Completion	Project-based work with clear deliverables	High	Low to medium	Most standard freelance projects
Milestone (phased)	Long or complex projects	High	Low if structured clearly	Projects over 4-6 weeks, large budgets
Net 7	Completed deliverables, established clients	High	Low	Small jobs, final invoices, repeat clients
Net 14	Most freelance work	Medium-high	Low	Default for most independent professionals
Net 30	Enterprise clients, large companies with AP departments	Medium	Very low	Corporate clients with formal procurement
Net 60	Large enterprise, some public-sector buyers	Low	Very low	When required; price accordingly or negotiate shorter terms
Due on Receipt	Small amounts, trusted clients, individual buyers	High	Medium	Single-session work, established relationships only
Retainer	Ongoing recurring work	High (predictable)	Low once established	Long-term clients with consistent monthly scope

Deposits: The most effective cash flow tool you have

A deposit is not a sign of distrust. It is common practice across many service industries: construction, photography, event planning, legal services. Clients who have worked with professionals before expect to be asked for a deposit.

A sensible range is 25% to 50% of the total project value. What pushes the number higher: a new client with no track record with you, a large project where front-loaded time investment is significant, or work that requires purchasing materials or tools. What allows a lower deposit: a long-standing client relationship, a project with a clearly defined and immediate final milestone.

How to propose a deposit without making it awkward

The approach matters. State your terms as fact, not as a question seeking permission.

This works: “My standard terms are a 50% deposit to begin and the balance due within 14 days of delivery.”

This is weaker: “Would you be okay if I asked for a deposit?”

The first framing treats your terms as a policy, which is what they are. The second invites the client to negotiate or decline.

Include deposit terms in your initial proposal, before the conversation reaches contract stage. Once a client has agreed to your proposal, the payment structure is already agreed to. Trying to introduce a deposit requirement after a client expects to start is harder.

Do not begin work before the deposit clears

This is the professional norm, and it is the right one. Your time is the asset. Once you invest it, you cannot recover it. A client who has not paid a deposit has made no financial commitment to the project. A client who has paid one has skin in the game.

If a client asks you to start immediately and pay the deposit later, the answer is that work begins when the deposit arrives. This is not inflexible. It is the same standard that any professional service operates on.

Deposits arrive sooner when the invoice goes out the moment the client agrees. With Ruul, you can send the deposit invoice right away or schedule it for the start date, and your client gets an email with a link to pay by card or bank transfer.

When clients push back on deposits

Some clients will tell you deposits are not standard in their industry. Some will say their procurement process does not allow upfront payments. Some will just resist on principle.

When to hold firm: new clients, large projects, any situation where the first half of work is the riskiest.

When there is room to negotiate: long-term relationships, clients who have paid you reliably before, situations where the project kicks off in the future and you can structure the deposit invoice to be due before the start date.

If a corporate client genuinely cannot process an upfront payment, make the first milestone small and early: a paid discovery or planning phase, invoiced as soon as it’s delivered and before the bulk of the work begins. You still get paid before significant time is invested.

A client who refuses any staged payment on a large project is telling you something. It can point to cash flow trouble or a reluctance to commit.

How to set up milestone payments

Milestones only protect you if nobody can argue about whether one has been reached. Three things make them hold.

Tie each payment to something you deliver

Every milestone needs a deliverable the client can see, test or sign off on. The payment falls due because you delivered it, not because the client is pleased with it. “First draft approved by client” lets the client decide when you get paid.

Work	Vague milestone	Clear milestone
Design	First draft approved by client	Homepage and inner page designs delivered in Figma, with desktop and mobile layouts
Writing	First draft complete	First drafts of all five articles delivered as Google Docs, one round of revisions included
Development	Backend done	Core features deployed to a staging URL the client can review
Consulting	Research finished	Findings document delivered, covering the competitor analysis and three recommendations

Set a review window

Without one, a client who never replies can hold up payment indefinitely. Give the client five to seven business days to review each delivery, and state in your contract that a milestone counts as approved if they haven’t responded by then.

Invoice the day you deliver

Send the milestone invoice when you deliver, not after the client approves: the review window runs alongside the payment term, not before it. Net 7 or Net 14 suits milestone invoices. Net 30 leaves a gap in a project where the next phase waits on the current payment. On the invoice, name the milestone, refer to the agreement and the milestone number, and give the amount and the exact due date.

Keep each milestone’s delivery confirmation, the client’s approval (or the date the review window closed) and the invoice together. If a payment is ever disputed, you can show what was delivered and when.

How payment terms affect client behavior

This is where the practical advice gets counterintuitive. Your payment terms do not just tell clients when to pay. They tell clients how much urgency to attach to paying.

Vague terms create permission to delay

“Payment upon completion” sounds clear. It is not. Completion means different things. The client’s approval process might mean completion is two revision rounds away from when you consider it done. “Upon completion” gives clients implicit permission to decide when completion actually occurs.

“Net 30” is clearer, but still abstract. Thirty days from when? From invoice date? From approval? From when the client gets around to processing it? Without a specific date on the invoice, Net 30 terms leave a window of ambiguity that some clients, consciously or not, will use.

Specific date terms work better

When your invoice says “Payment due by July 3, 2026,” the client has a date. A specific, calendar date anchors their behavior to that point in time. There is nothing to interpret. The date either passes or it does not.

An explicit date leaves nothing to interpret, and your client’s accounts payable team can schedule it without working anything out. Add the calculated due date to every invoice, even if you also write the net term.

The problem with “payment upon completion”

Beyond ambiguity, this phrase ties your payment entirely to an approval event you do not control. Use milestone terms or net terms instead. Define what “complete” means before the invoice goes out, and attach a specific date to it.

State your late fee up front

Make clear in your terms, and again on each invoice, that a late fee applies after the due date. You do not have to charge it every time, but a fee the client never agreed to is hard to enforce, so put it in writing before the work starts. For example: “Invoices unpaid after the due date accrue a late fee of 1.5% per month on the outstanding balance, or the highest rate the law allows if that is lower.” Our late payment guide covers how to set the rate and when to charge it.

Where the law sets terms for you

Some places add their own rules on top of yours. In the EU, if a business or public client pays late, you’re entitled to interest of at least 8 percentage points above the central bank’s reference rate, which came to 10% a year or more in every EU country in the second half of 2026, plus at least €40 for each late invoice, automatically and without a reminder. Your Europe lists each country’s current rate. In the UK, statutory interest is 8% above the Bank of England base rate, plus a fixed £40 to £100 depending on the amount owed, unless your contract sets its own interest rate. These rules cover business clients, not private individuals.

In the US, some states and cities protect freelancers by law. In New York State, a client who hires you for $800 or more must give you a written contract and, if it sets no payment date, pay within 30 days of the work being completed. Illinois, California and Los Angeles have similar rules with lower thresholds ($500 over 120 days in Illinois, $250 for professional services in California and $600 in Los Angeles). These rules change and differ by country and state, so check what applies where you and your client are based.

Choosing the right payment terms for your situation

No single structure fits every engagement. Here is how to think through the decision.

Project size and duration

Short projects with a clear, singular deliverable can use simple structures: full upfront, or 50/50 with completion at delivery. Long projects with multiple phases need milestone invoicing. The rule is simple: you should never carry more than one phase of work without payment.

A branding project delivered over two weeks might be 50/50. A website build spanning three months should be invoiced in phases, with each major deliverable generating its own invoice.

Client type

Small business clients often pay quickly, partly because their own cash flow depends on it too. EU data points the same way: in 2024, micro companies were the most punctual payers in 13 of 20 member states, while large companies paid latest in 16 of 20.

Mid-size companies often have Net 15 or Net 30 built into their processes. Ask early what their standard payment cycle is.

Enterprise clients often have Net 30 to Net 60 terms set by their AP departments. These terms are often non-negotiable at the working level. If you work with enterprise clients regularly, price accordingly or negotiate more frequent milestone invoicing to offset the longer wait.

New vs. established clients

New clients warrant more protective terms: higher deposit percentage, shorter net period. You do not know their payment behavior yet. Established clients with a strong payment track record allow for more flexibility.

This is not cynicism. It is risk management. Most clients who pay late are not acting in bad faith. They are just not prioritizing your invoice. Stronger terms at the outset mean your invoice is harder to deprioritize.

Invoice amount

Counterintuitively, larger amounts should come with shorter or more structured terms, not longer ones. In Bonsai’s 2018 analysis of three years of invoices sent through its platform, 58% of invoices of $20,000 or more were paid late, against 19% of invoices under $100. A large invoice sitting unpaid for 60 days is a significant cash flow event. Break it into milestones.

Your cash flow needs

If you need income to cover near-term expenses, short terms are not optional. Net 7 or a deposit structure is appropriate regardless of what the client prefers. Your financial stability is a legitimate variable in setting terms. You are not obligated to extend 30-day credit to every client just because they would prefer it.

One often-overlooked option: if you want to receive payment in cryptocurrency without asking clients to pay differently, Ruul’s Crypto Payout lets you invoice clients normally and withdraw your earnings in USDC. Your clients pay by card or bank transfer as usual, which avoids the friction that comes with invoicing in crypto directly.

Getting clients to agree to your terms

Present terms as standard practice

The framing determines the outcome. When you present your terms as a question, the client hears that they are negotiable. When you present them as standard practice, the client hears that this is how you work.

Say: “I work with a 50% deposit to begin and the balance due within 14 days of delivery. Does that work for your timeline?”

Do not say: “Is it okay if I ask for a deposit?”

The first version acknowledges that logistics need to align. The second version treats your terms as a favor you are asking.

Include terms in the proposal, not after

The point at which to introduce payment terms is before the client has mentally committed to the project scope. Once a client has seen the proposal and said yes to the work, they have already said yes to the terms embedded in it. Introducing payment terms after a verbal agreement creates friction because it feels like new conditions being added.

Which terms are worth holding firm on

Deposit requirement: worth holding on. Starting work without financial commitment is the highest-risk situation in freelancing.

Net period: some flexibility is reasonable for long-term enterprise relationships. But shorten the default, not lengthen it. Your starting position should be Net 14. Clients who need Net 30 can ask.

Payment method: flexible, but make clear which methods are accepted and any fees that apply.

Late fee policy: worth including in writing, even if you negotiate case by case.

Know your industry’s norms

Acceptable payment terms vary by industry and client type. Design and development work often runs on Net 14 or Net 30 depending on client size. Writing and editorial work tends toward shorter terms with smaller invoices. Consulting often uses retainer or milestone structures for long-term engagements.

Knowing what is standard in your market gives you confidence in the negotiation. You are not making unusual demands. You are operating within professional norms.

Communicating payment terms before starting work

Payment terms belong in the conversation before a contract is signed, not after work has started.

A practical note on payment records: every payment you collect is a tax-relevant transaction. Keep documentation of agreed terms, invoices sent, and amounts received in one place. Ruul’s organized payment history centralizes your transaction records and exports summaries for tax time, so you are not reconstructing payment history from email threads at the end of the year.

The right moment is during the proposal or initial agreement stage. You are agreeing on scope, timeline, and deliverables. Payment structure is part of that same conversation. Treating it as an afterthought signals that it is negotiable, which invites clients to treat it that way.

Once both parties have agreed on terms in writing, the terms are set. Any change requires explicit renegotiation. Do not adjust your terms mid-project without something in return.

If a client asks to extend terms after work is underway, pause and assess. An established client with a cash flow issue is a different situation from a new client testing your boundaries. Respond professionally, put any change in writing, and factor it into how you structure the next engagement with them.

What your contract should say about payment

Your terms are easiest to hold a client to when they sit in a contract you both sign before work starts. Ruul’s free service agreement template covers the basics. Beyond the amount and the due date, these clauses do the most work:

• The trigger. Tie the due date to the invoice: “Payment is due 14 days from the date of the invoice.” Not to delivery, approval or the client’s satisfaction.
• The deposit. Say that work starts once it clears, and that it isn’t refundable if the client cancels after work has begun. Without that line, a client who cancels may ask for it back.
• Each milestone. Its deliverable, amount and due date, plus the review window and what happens when the client doesn’t respond.
• Your right to pause. If an invoice is overdue, you can stop work until it’s paid without that counting as a breach on your side. Without the clause, stopping work on a signed project is a gray area. When you use it, tell the client in writing, with the amount owed and when you’ll resume.
• Ownership on payment. The rights to the work pass to the client only once you’re paid in full. On a milestone project, each phase’s work can pass as that milestone is paid. Until then, the client may review the work but not use it commercially, and if they use it anyway, you may have a copyright claim on top of the unpaid invoice.
• Cancellation. Which payments already made are non-refundable, and how you invoice work done since the last paid milestone.
• Governing law. Which country’s law applies, and where disputes are heard. The statutory late payment rights above can depend on it. Client contracts usually name the client’s country, so ask for your own where you can.

Read the client’s contract before you sign

When the client sends their own contract, its terms are written for them. Look for:

• payment “upon approval” or “upon satisfaction”, which lets the client decide when you get paid
• very long terms, such as Net 90 or Net 120
• rights to the work passing to the client on delivery rather than on payment
• no late fee clause
• “each party bears its own costs” in the payment section, which can stop you recovering collection costs
• a broad set-off clause that lets the client deduct amounts it says you owe under other agreements; ask to limit it to this contract

Ask for changes before you sign. Once the work has started, you have far less leverage.

When terms are not met

When a client does not pay by the agreed date, your next steps involve follow-up, reminders, and escalation. Those mechanics belong to the late payment guide. What payment terms do is reduce how often you get there: clear terms, a specific due date, a deposit already collected, and a stated late fee policy combine to make your invoice much harder to ignore.

Payment terms quick reference: Proposed language

Here are brief framings for the situations where proposing terms most often feels uncomfortable.

Deposit at project start: “My standard terms are a [X]% deposit to begin, with the balance due within [Y] days of delivery. Happy to send the deposit invoice today so we can lock in the start date.”

Net 14 for ongoing work: “Invoices are due within 14 days of the invoice date. I’ll include the specific due date on each invoice so there’s nothing to calculate.”

Responding to a Net 30 counter-offer: “I typically work on Net 14. I can work with Net 30 for this engagement, though I’d want to add a milestone invoice at the midpoint to keep payments regular.”

Starting date tied to deposit: “Work begins when the deposit clears. Once I have confirmation, I can confirm the start date.”

Proposing milestones: “For projects of this scope, I work with milestone payments: [X]% to begin, [Y]% when [deliverable] is delivered, and the balance on completion. That gives us both clear checkpoints, and you only ever pay for work that has been delivered.”

Pausing between milestones: “As agreed, I’ll hold the next phase until the current milestone payment clears, and pick it up as soon as it does.”

Setting the right terms is just the beginning

Terms only work when invoices go out on time and reminders happen without you chasing. With Ruul, you send the invoice now or on a set date, Ruul can email your client up to three reminders until they pay, and pays you within one business day after your client’s payment reaches Ruul. There’s no setup cost or monthly fee, just 5% per paid invoice.