Payment Terms in Freelance Contracts: Net-30, Milestone-Based, and Retainer Structures That Actually Get You Paid

You finished the project on a Friday. You sent the invoice. Then Monday came, and Tuesday, and somehow three weeks passed with nothing but a cheerful "we'll get that processed soon." If you have been in freelancing for more than six months, you know exactly how this story ends — a frantic email chain, a client who "didn't see" the invoice, and a payment that arrives forty-two days after it was due, if it arrives at all. The culprit is almost never bad faith on the client's part. It's a vague payment clause that gave everyone too much wiggle room.

Payment terms are the most frequently skipped section of a freelance contract. Everyone rushes to define the scope of work and the deliverables, then throws in "Net-30" at the bottom as if those words are self-explanatory. They are not. This article breaks down the three main payment structures — Net-30 and similar intervals, milestone-based payments, and retainers — and shows you exactly what language to use in each. Whether you use a freelance contract template or draft from scratch, the wording you choose will determine whether you get paid on time, or at all. The full document template catalog also has related agreements worth bookmarking.

Why "Due Upon Receipt" Is the Fastest Way to Never Get Paid

Walk into any accounts payable department and ask what "due upon receipt" means. You will get blank stares. Larger companies operate on payment cycles — net-30 is often the shortest internal cycle they will honor, and many run on net-45 or net-60. When you write "due upon receipt" in your freelance contract, you have, in practice, written nothing at all. It is the contractual equivalent of "sometime soon, if that works for you."

Beyond corporate bureaucracy, "due upon receipt" has been challenged in court as ambiguous. The principle that contract terms must be clear enough to define the parties' obligations is well established in U.S. contract law, and lower courts have declined to enforce payment clauses that failed to specify a definite due date anchored to an objective event. The logic is simple: if there is no ascertainable deadline, there is no breach when the deadline passes — because no one can agree on when it was.

The fix is equally simple: replace "due upon receipt" with a specific number of days tied to a specific trigger. "Payment due within seven (7) calendar days of invoice date" is enforceable. "Payment due upon receipt" is a polite suggestion that sophisticated clients will cheerfully ignore. Even a standard online contract generator will offer you a field for a specific payment window — use it, and fill in a real number.

Net-30, Net-15, and Net-7: Choosing the Right Payment Window

Net-30 is the standard payment term in U.S. commercial practice — it means payment is due thirty calendar days after the invoice date. It is widely recognized in accounting software, understood by corporate clients, and accepted by most courts as a definite, enforceable deadline. For that reason, it appears in almost every sample freelance contract template you will find online, and it is the de facto starting point for any commercial negotiation about payment timing.

But "standard" does not mean optimal. For solo freelancers billing small projects under $5,000, net-30 creates a thirty-day cash flow gap that can be genuinely painful. Net-15 or net-7 are defensible and increasingly common in creative and technology services. Courts in commercial disputes generally apply whatever interval the parties agreed to, provided it is stated clearly in writing and accepted by both sides. The key is that the contract must specify: (a) the trigger event, (b) the counting method — calendar days versus business days — and (c) what happens if that day falls on a weekend or a federal holiday.

Sample Net-30 Payment Clause:
"Client shall pay each invoice submitted by Contractor within thirty (30) calendar days of the invoice date ('Payment Due Date'). If the Payment Due Date falls on a Saturday, Sunday, or a federal holiday, payment shall be due on the next business day. Payment shall be made by [ACH transfer / wire transfer / check], to the account or address designated by Contractor in writing. Invoices not disputed in writing within ten (10) days of the invoice date are deemed accepted by Client."

One detail that trips up a lot of freelancers: the trigger should be the invoice date, not the date the client "receives" or "approves" the invoice. Approval-triggered clauses let clients delay the clock indefinitely by simply not approving the invoice. Anchor the thirty-day window to the date printed on the invoice, full stop. If the client claims they never received it, require delivery confirmation and name a specific email address in the contract.

When working with an independent contractor agreement, the payment window should also account for whether the client is a business or a private person. Corporations generally expect net-30 because their AP departments are built around it. Individual clients often have no accounts payable system at all, and a shorter window — net-7 or net-14 — is entirely reasonable and easier to enforce.

Milestone-Based Payment: How to Define "Done"

Milestone payments are the preferred structure for longer projects: web builds, software development, marketing campaigns, book-length content projects, brand identity work. The basic concept is easy — split the project into phases and the client pays at the end of each phase. What makes this structure succeed or collapse entirely depends on how each milestone is defined. Vague milestones are the single most common cause of freelance payment disputes.

The core legal problem with poorly defined milestones is that they create a subjective completion standard. If the contract says "payment due upon completion of Phase 1: Website Design," and the client insists the design is not complete because they want to change the color palette, the payment obligation is paralyzed. Courts in contractor-client disputes have consistently held that when a milestone is defined by the client's subjective satisfaction, the contractor bears the burden of proving that standard was met — often an impossible task when the standard exists only in the client's head.

The solution is to draft milestones around objective, verifiable events: deliverables submitted, mockups provided, code committed to a repository, files uploaded to a designated location, documents emailed to a specified address. "Phase 1 is complete when Contractor delivers three (3) homepage mockups in PDF format to Client's designated email address" is objective and enforceable. "Phase 1 is complete when Client is satisfied with the design direction" hands a veto to the person who owes you money — never a good contractual strategy.

A framework for milestone definitions that holds up in disputes:

• State the deliverable in concrete, measurable terms — number of pages, word count, file format, feature set
• Specify the delivery method — email with PDF attachment, shared cloud folder, version control repository
• Set a client review period — five to seven business days to provide written approval or written objections
• Include a deemed-approval clause: if no written objection is received within the review period, the milestone is approved and payment is due
• Specify that objections must be written and must state specific, reasonable grounds — not simply "we want changes"

The deemed-approval clause is particularly important. Without it, a client can simply go silent — technically neither approving nor rejecting the deliverable — and the payment clock never starts. The deemed-approval concept is well established in U.S. contract law; courts in New York, California, and Texas have all enforced it in contractor disputes when the clause was clearly written and the review period was reasonable. A five-business-day window is almost universally considered reasonable for creative and professional services work.

The Deposit Clause: How Much to Ask and Why Courts Uphold It

A deposit — also called an advance payment or project retainer — is the most effective single payment protection tool available to a freelancer. It creates a financial stake for the client from day one, dramatically reduces the risk of a client walking away mid-project without paying, and ensures you have something in hand even if the professional relationship deteriorates. Despite these obvious benefits, deposits are absent from a surprising number of freelance contracts — often because the drafter used a generic online template that omitted them, or was reluctant to ask for money upfront.

The market standard for freelance and creative services is 25 to 50 percent of the total project fee, paid before substantive work begins. Some contractors require full payment upfront for small projects, particularly when working with new clients who have no established track record. Courts routinely uphold deposits in these ranges as reasonable consideration and not a penalty clause, provided the contract clearly labels the payment as a non-refundable deposit and explains what happens to it if the project is cancelled by either party.

The non-refundable language deserves careful attention. Under the Restatement (Second) of Contracts § 356, a forfeiture clause must bear a reasonable relationship to the anticipated harm from breach. A blanket statement that "the deposit is non-refundable under any circumstances" may be challenged if the contractor has performed no work at all. The stronger approach is to tie refundability to the work actually performed:

Sample Deposit and Cancellation Clause:
"Upon execution of this Agreement, Client shall pay a non-refundable deposit of [●]% of the Total Project Fee ('Deposit'). The Deposit compensates Contractor for reserving capacity, conducting preliminary research, and completing project setup. In the event Client terminates this Agreement prior to delivery of any milestone, Contractor shall retain the Deposit as liquidated damages for lost opportunity and preparatory work. In the event of cancellation after delivery of one or more milestones, all fees for completed milestones are due and payable in full, and the Deposit shall be applied against the final outstanding balance."

When you use a generator or online document tool to create a freelance agreement, verify whether it includes a deposit clause at all. Many standard templates either omit it entirely or bury it in an appendix that references a "schedule" that was never actually attached. Draft the deposit clause explicitly, with the dollar amount or percentage stated clearly in the body of the contract itself — not in an exhibit that might get lost in a long email thread.

Retainer Structures: What the Monthly Fee Actually Covers

A retainer is a recurring payment — typically monthly — in exchange for a defined scope of ongoing services. It is popular with consultants, marketing professionals, legal advisors, copywriters, and developers who maintain long-term client relationships. The appeal is mutual: predictable income for the contractor, predictable budgeting for the client. The legal pitfalls, however, are less obvious and arrive reliably about three months into any poorly drafted retainer arrangement.

The first and most common problem is scope creep. A retainer that says "Client pays $3,500 per month for marketing services" invites the client to keep adding requests until the contractor is effectively doing the work of three people for the price of one. Every retainer agreement must define explicitly what is and is not included within the monthly fee. The scope definition should be specific enough to draw a clear line — and that line must include an explicit provision for how additional out-of-scope work will be billed, typically at an agreed hourly or per-project rate.

The second structural problem is the rollover question: if the client does not use all of their allocated hours or does not request a specific deliverable during a given month, do those hours or deliverables carry forward to the next billing period? Courts have resolved this differently depending on how the contract is framed. If the retainer is an "availability fee" — paying for access to the contractor's time and capacity — unused hours generally do not roll over. If it is framed as prepayment for specific deliverables, unused deliverables may create a future performance obligation. The cleanest approach is to address this explicitly:

Sample Retainer No-Rollover Clause:
"The Monthly Retainer Fee compensates Contractor for reserving availability and performing the Services described in Schedule A during each calendar month. Unused hours or undelivered items within a given billing month do not accumulate, carry forward, or create any credit toward future months. The Monthly Retainer Fee is non-refundable once the applicable billing month has commenced."

The third structural issue is termination. Unlike project-based contracts, retainers are open-ended by design — they continue until one of the parties ends the relationship. Without a clear termination clause, courts may apply a "reasonable notice" standard, and "reasonable" has been interpreted anywhere from two weeks to three months depending on the scope of the engagement and the industry. The standard professional practice is a 30-day written notice requirement for either party, with the contractor entitled to the full month's fee for any month in which notice is given or services are rendered. The consulting agreement template includes a well-structured termination and retainer billing framework you can adapt for most service types.

One nuance that is easy to overlook: when the retainer involves recurring payments between legal entities — your LLC billing the client's corporation — include an auto-payment authorization or ACH authorization provision. Chasing a monthly invoice from a corporate client is a full-time job you did not sign up for. Auto-pay provisions are standard in B2B service contracts and rarely generate client pushback when presented as a convenience feature.

Invoice Timing and the "30-Day Clock" Problem

Timing is everything in payment clause drafting, and the question "when does the clock start?" resolves roughly half of all freelance payment disputes before they ever reach a lawyer's desk. There are three common trigger approaches used in freelance and service contracts, each with a different risk profile for the contractor.

• Invoice date trigger: The payment window starts when the contractor sends the invoice. Simple, objective, and preferred by contractors because the clock cannot be paused by a client who sits on an invoice without responding.
• Delivery trigger: The window starts when the deliverable is received by the client. Better for clients; riskier for contractors because "receipt" can be disputed, especially when delivery happens by email.
• Approval trigger: The window starts when the client formally approves the deliverable. The worst option for contractors — it effectively gives the client a unilateral right to pause payment indefinitely by withholding approval.

Whatever trigger you choose, specify it explicitly in the contract. Do not leave it to implication. Equally important is the mechanics of sending the invoice. If the contract says payment is due thirty days from invoice date, but you email the invoice informally and it ends up in a spam folder, you may face a genuine dispute about when the clock started. Best practice: name a specific email address for invoice delivery in the contract, send the invoice as a PDF attachment with a delivery receipt, and follow up by a second communication if no acknowledgment is received within two business days.

One underrated drafting detail: specify the invoice format. If the contract requires electronic invoices in PDF format and the client later claims they could not "process" an image file or a non-standard format, you have handed them a procedural objection. Keeping the format requirement simple — "invoice delivered via email as a PDF attachment to the address designated in writing by Client" — eliminates most format-based objections while still creating a clear evidentiary record of when the invoice was sent and to whom.

Late Payment Fees: Language That Survives State Scrutiny

A late payment fee — also called a finance charge or interest penalty — is your financial enforcement mechanism when a client misses the payment deadline. It is also the clause most likely to be drafted incorrectly, often citing interest rates that create an unenforceable penalty clause instead of a legitimate commercial charge. Getting this language right requires understanding two distinct legal concepts: usury law and the penalty-versus-liquidated-damages distinction.

Under U.S. law, usury limits technically apply to loan transactions, not to contract payment delays — but several states extend usury-adjacent scrutiny to commercial late fees that appear punitive rather than compensatory. The broadly accepted safe harbor is a monthly rate of 1.5 percent on the unpaid balance, which equates to 18 percent annualized and sits below the commercial usury threshold in virtually every state. Some practitioners use 2 percent per month, which is defensible in most jurisdictions but may attract closer scrutiny in high-dollar commercial disputes in New York or California.

The drafting magic words are "per month on the unpaid balance" — not a flat fee, not "per week," not a lump-sum amount. Courts consistently distinguish between interest-like charges, which track the actual unpaid amount over time, and arbitrary penalties, which bear no rational relationship to the contractor's actual harm. Flat late fees are harder to defend, particularly in jurisdictions that apply a proportionality test to contractual penalties. When referencing a loan agreement template for guidance on interest language, note that the same clarity standards apply: state the rate, the calculation base, and the compounding method.

Beyond the rate, specify a grace period. Charging interest on the thirty-first day creates unnecessary goodwill friction with clients who are a single day late due to a payment processing delay. A five-to-seven-calendar-day grace period after the Payment Due Date is common in professional services and rarely weakens your enforcement position if the client's tardiness becomes a pattern. Draft the grace period as a floor, not a waiver: the grace period delays when interest begins to accrue, but it does not waive your right to interest after the grace period expires, and it does not reset the clock if the client pays partially and still has an outstanding balance.

One additional consideration when drafting late fees in agreements between individuals — where one or both parties are natural persons rather than companies — is whether consumer protection statutes apply. California, New York, and several other states impose additional disclosure and limitation requirements on penalty clauses in consumer contracts. If your client is a private individual rather than a registered business entity, verify whether any consumer contract laws in your state or the client's state impose restrictions before inserting an aggressive late fee structure.

Kill Fee Clauses: When the Project Dies Before Completion

A kill fee is the payment mechanism for cancellation after work has begun. You get compensated for what you have already done, plus a contractual premium for the disruption to your schedule and pipeline. Kill fee clauses are standard in publishing, advertising, film, and creative industries, but they are underused in technology, consulting, and professional services — where they are equally, if not more, necessary. Projects that die in month two of a six-month engagement leave the contractor with significant uncompensated work and a blown capacity schedule.

A well-structured kill fee clause answers three questions clearly: first, at what stage of the project does the kill fee apply; second, how is the fee calculated; and third, what are both parties' obligations upon cancellation? Each of these requires explicit language — none can be left to inference.

• Kill fee applies once the Contractor has commenced substantive work on any milestone, including discovery, research, or preparatory work
• Fee equals a defined percentage (typically 25–50%) of the remaining contract value at the time of cancellation notice
• Contractor delivers all completed work product in its current state; client receives a limited license to use it
• All invoices for fully completed milestones are due immediately upon cancellation, regardless of the kill fee
• Kill fee payment is due within 14 calendar days of the written cancellation notice

One drafting detail that freelancers consistently overlook: the kill fee clause must address both directions. Most contracts only cover client-initiated cancellation. But a contractor may also need to exit a project — due to non-payment, undisclosed scope changes, or changed circumstances. Draft symmetrical cancellation rights and specify what each party owes the other in each scenario. A contractor-initiated cancellation should not automatically forfeit the deposit or trigger a kill fee in the opposite direction; the contract should specify a separate regime for contractor-initiated termination, typically requiring notice and return of any unearned deposit.

Payment Terms in Contracts Between Individuals vs. Business Entities

The payment clause that works perfectly in a business-to-business service agreement may create unexpected problems in a contract between individuals, or in a hybrid situation where your business is contracting with a private person rather than a company. The difference is not merely a matter of formality — it can affect enforceability, applicable legal standards, and the regulatory framework governing the transaction.

When both parties are businesses — contracts between legal entities — the Uniform Commercial Code and state commercial law generally govern payment disputes. Courts apply a commercial sophistication standard: the parties are presumed to have negotiated at arm's length and to understand the documents they signed. Aggressive late fees, substantial deposits, short payment windows, and kill fee clauses are all generally enforceable under this standard, provided the language is clear and unambiguous.

Contracts between individuals — where either party is a natural person acting outside a business capacity — may trigger consumer protection statutes, state wage laws if the engagement looks more like employment than contracting, or other regulatory frameworks depending on the subject matter of the services. The analysis is fact-specific and state-specific, but the practical drafting advice is: if your client is a private individual rather than a registered business entity, include an express statement in the contract clarifying the commercial nature of the engagement. A short clause such as "The parties acknowledge that this Agreement is a commercial transaction entered into for professional services purposes and that neither party is acting in a consumer capacity" goes a long way toward avoiding unwanted regulatory overlap.

The B2B versus B2C distinction also affects the language level of your payment terms. Contracts between legal entities can use accounting terminology — "net payment," "calendar quarter," "invoice date" — without explanation. Contracts where the client is an individual may benefit from plain-language descriptions. "Payment is due 30 days after we send you an invoice" is legally equivalent to "Net-30 from invoice date" but far less likely to produce a "what does that mean?" email from a private client. For tailoring payment language to different contexts, the service agreement template provides a solid starting point for both B2B and individual-client arrangements.

Auto-Renewal Retainers and Annual Rate Adjustments

If a retainer agreement is silent on renewal, most U.S. states will treat it as a month-to-month arrangement terminable by either party on "reasonable" notice. That is legally acceptable but practically uncertain — courts have found anything from two weeks to three months to be reasonable depending on the scope of the relationship, the industry, and how dependent the client was on the contractor's services. Uncertainty about how long you are committed to a retainer, or how much notice you need to give, is unnecessary when a few sentences can eliminate it entirely.

The cleaner approach is to specify automatic renewal explicitly and pair it with a defined notice window for non-renewal. A standard formulation: the agreement renews automatically for successive one-month terms unless either party provides written notice of termination at least fifteen days before the end of the current term. This creates certainty for both sides, prevents the awkward "are we still doing this?" conversation that delays final payments, and ensures that the contractor's capacity is not held in limbo while the client decides whether to continue.

For annual retainers — common in accounting, PR, legal advisory, and enterprise marketing — include a rate-adjustment clause that gives you the right to modify the monthly fee at renewal. Without it, you are locked into the original rate even if your costs have risen, your expertise has increased, or the market has moved. A workable provision: "Contractor may adjust the Monthly Retainer Fee upon thirty (30) days' written notice to Client, effective at the start of the next renewal term. If Client does not accept the adjusted rate in writing within fifteen (15) days of such notice, this Agreement shall terminate at the end of the then-current term." This protects both parties — the client has advance notice and a clear exit if they disagree with the new rate, and the contractor is not trapped in an undervalued engagement.

Common Mistakes in Payment Term Drafting

After reviewing dozens of freelance contract disputes, the same drafting errors recur with depressing regularity. Each one seems minor in isolation; each one is capable of costing thousands of dollars in unpaid fees or protracted disputes. Here are the five most common ones and why they matter:

• Missing the trigger event: Writing "Net-30" with no anchor — invoice date? project completion? client approval? — creates genuine ambiguity about when the clock starts. Courts will not fill this gap in your favor.
• Subjective milestone definitions: Tying payment to client satisfaction, approval, or "acceptance" without objective criteria creates an indefinite delay mechanism that the client controls entirely.
• Omitting the interest rate: A contract that says "late payments are subject to interest" without specifying a rate gives the contractor a theoretical right and no practical remedy. Courts will not insert a rate on your behalf.
• No invoice dispute window: Without a clause requiring disputes to be raised within a defined period (ten days of invoice date is standard), a client can contest an invoice months later, after you have already relied on the payment in your cash flow projections.
• Forgetting reimbursable expenses: If the project involves pass-through costs — software licenses, subcontractor fees, travel, materials — the contract must specify how expenses are invoiced, what documentation is required, and whether they are subject to the same payment window as the service fee or a different one.

Many of these errors occured because the drafter used a generic online template that was not tailored to the specific engagement type or service relationship. A contract generator is a genuinely useful starting point — it gives you the structure, the boilerplate representations, and the standard clauses — but the payment section requires thoughtful customization every time. The difference between "net-30 from invoice date" and "net-30 from client approval" looks like a six-word difference. In a $50,000 project dispute, those six words can determine the outcome.

One mistake that is particulary common among first-time freelancers: drafting the payment terms in an email rather than in the signed contract. Email evidence is admissible and can help establish intent, but it will not override a signed contract that says something different. The contract controls. If the payment window, the late fee rate, and the deposit amount are not in the signed document, they may not be enforceable at all.

Drafting Language Side-by-Side: A Quick Reference

Different project types call for different payment structures, but all three share a common drafting standard: the clause must state who owes what, when they owe it, how it is to be paid, and what happens if they fail to pay on time. Here is how that plays out across the three structures.

For net-interval contracts, the payment clause should be self-contained: amount, trigger event, payment method, grace period, and late fee rate in one consolidated paragraph. Clients read this section once, during or after signing, and the clause should answer every payment question without requiring them to cross-reference another document. When you create this language using a standard template, make sure the late fee rate and grace period are filled in — many template forms leave these as blanks, and a blank clause is an unenforceable clause.

For milestone contracts, the payment clause in the body of the contract should reference a schedule: "Payment terms and amounts for each milestone are set forth in Schedule 1, which is incorporated herein by reference and signed by both parties." The schedule then lists each milestone with its objective completion criteria, client review period, deemed-approval language, and payment amount. Both the contract body and the schedule must be signed — unsigned schedules are frequently challenged as not incorporated into the contract.

For retainer agreements, the payment clause references two other documents: the scope of services schedule (what is included) and, if applicable, an out-of-scope rate card. A well-structured retainer contract built on an independent contractor agreement base gives you the intellectual property assignment, the confidentiality obligations, and the termination rights in a single document, with the payment terms cleanly separated into their own numbered section for easy reference during disputes.

Pre-Signature Checklist: Payment Terms

Before you send a freelance contract for signature, run the payment section through this checklist. It takes less than five minutes and addresses the gaps that generate the vast majority of payment disputes. Think of it as the last line of defense before the contract goes live.

• Is the payment amount — or rate, for hourly work — stated explicitly in the contract body, not just in an email or verbal agreement?
• Is the trigger event tied to an objective, verifiable occurrence: invoice date, delivery confirmation, or completion of a defined milestone?
• For milestone contracts: does each milestone have objective completion criteria, a client review period, and a deemed-approval clause?
• Is the late payment rate specified (e.g., 1.5% per month on the outstanding balance), along with a grace period and the start-date for accrual?
• Is a deposit clause present, with the percentage or dollar amount stated, and the non-refundability condition tied to work performed rather than a blanket forfeiture?
• For retainers: is the scope defined, are rollover rights addressed, and is the termination notice period explicitly stated?
• Is there an invoice dispute window — requiring the client to raise objections in writing within a set number of days?
• For contracts with individual (non-business) clients: is there a clause clarifying the commercial nature of the transaction?

Payment terms are not a formality tacked on at the end of a scope document. They are the mechanical core of the financial relationship between you and your client. A contract that clearly defines when money is owed, how much, and what happens when it does not arrive on time is the single best investment of drafting effort you can make. Use a reliable standard template, adapt it to your specific service type, and check every payment clause against the list above before it goes out. Your future self — the one watching the net-30 clock tick on a $15,000 invoice — will thank you.

Article reviewed by: Michael M. (Attorney)