Setting Up Split Payment Schedules: 50/50, 30/40/30, and Milestone Billing Explained

The single biggest mistake freelancers and small contractors make is invoicing at the wrong time. Bill too early and the client suspects you're cash-strapped. Bill too late and you've already absorbed the entire project's risk yourself. Bill in one chunk on completion and you've effectively loaned the client the full project value, interest-free, for however many weeks the work took.

The answer to all three problems is the same: split your invoices across the project's lifespan using a payment schedule that matches your cash flow needs and your client's psychology. This guide walks through the five most useful split-payment models, when each one fits, and how to set them up — with contract clauses and the specific InvoiceFlow features that make them work.

Why split-payment schedules matter more than your hourly rate

Most freelancers think about pricing in terms of "how much do I charge." A better question is "when do I get paid?" The first determines your gross income on paper. The second determines whether you actually receive it, when, and whether you stay solvent in the meantime.

Three risks scale with project length:

• Scope-creep risk: the longer a project runs, the more it tends to drift from the original spec. Payments tied to milestones force re-alignment at each one.
• Client-abandonment risk: some clients lose interest, change priorities, or change companies mid-project. If you've billed nothing, you have nothing.
• Solvency risk: long projects with materials costs or subcontractor payments eat your working capital fast. You need cash arriving while costs are accruing.

Split payments address all three.

Model 1: 50/50 (the safe default)

Structure

50% deposit at project start. 50% on delivery.

When to use it

Most freelance projects under 6 weeks long. Photography shoots. Logo design. Short copywriting projects. Small web development. Any work where the deliverable can be clearly identified as "done" and "not done."

Why it works

The deposit covers your initial work and signals client commitment. The final payment is psychologically tied to receiving the deliverable, which most clients pay promptly to gain access.

Setup

Create a payment schedule on the invoice with two installments. First is dated at project start with "Due on receipt." Second is dated at expected delivery with payment terms (typically net-7 or net-14). The invoice PDF shows the full project value, the deposit amount, the balance amount, and the due dates for each.

Contract clause

Payment terms: 50% deposit due upon contract signing. Work commences upon receipt of deposit. Remaining 50% due within [7] days of delivery. Late payment after delivery incurs [4%] late fee per month outstanding.

Model 2: 30/40/30 (the balanced project model)

Structure

30% deposit at start. 40% at a defined mid-project milestone. 30% on completion.

When to use it

Projects of 6-16 weeks with a clear midpoint. Brand identity projects (concepts approved → design phase complete). Web development (wireframes approved → development → launch). Small construction projects (materials ordered → rough-in complete → final).

Why it works

The middle 40% rewards completion of the highest-risk phase (typically the work that's hardest to redo). If a client wants to abandon at that point, you've recovered 70% of the project's value already.

Setup

Three installments. The middle one is tied to a milestone that should be defined in the contract — not just a date. Examples: "concept approval," "wireframes signed off," "rough-in complete and inspected."

Contract clause

Payment schedule: 30% upon contract signing. 40% upon completion and written acceptance of [milestone]. 30% upon final delivery. Each installment due within [7] days of issuance. The project will not proceed past any milestone until that milestone's invoice is paid in full.

The last sentence is critical. Without it, you carry the risk of the next phase without the cash for the current one.

Model 3: 25/25/25/25 (the long-project model)

Structure

Four equal installments at project start, two intermediate milestones, and completion.

When to use it

Projects of 4-12 months. Larger software development. Long-form documentary production. Multi-room renovations. Annual retainer-like consulting engagements where the work has phases.

Why it works

Smoother cash flow for both sides. The client doesn't face a large upfront expense; you don't face long periods between invoices. Smaller individual payments are also psychologically easier for clients to approve.

Setup

Four installments tied to either dates or milestones. For very long projects, milestone-based is better — date-based schedules drift when the project drifts.

Contract clause

Payment schedule: project fee divided into four equal installments of [X], invoiced at: (1) contract signing, (2) completion of Phase 1 deliverables, (3) completion of Phase 2 deliverables, (4) final delivery and acceptance. Each invoice due within [7] days of issuance.

Model 4: Milestone-only (the deliverable-based model)

Structure

No fixed percentages. Each milestone has a dollar amount tied to it.

When to use it

Projects where milestones vary substantially in scope. Software development with feature-based releases. Custom manufacturing. Multi-deliverable creative projects.

Why it works

The pricing matches the work distribution. A milestone that includes 70% of the technical risk can be priced at 60% of the project value, while a smaller polish-and-launch milestone is priced at 10%.

Setup

Each milestone is its own invoice, issued when the milestone is reached. The contract specifies the milestones and prices; the actual issuance is on completion.

Contract clause

Project deliverables and pricing: [list each milestone with description, deliverables, and price]. Invoices issued upon completion of each milestone, payable within [7] days. Total project fee: [sum].

Model 5: Recurring + final balloon (the retainer + delivery model)

Structure

Small monthly retainer for the duration of the project, plus a larger final payment on completion.

When to use it

Long, slow projects where you need consistent income but the deliverable is a single end-product. Long-form writing (book ghostwriting). Long documentary editing. Year-long brand-strategy engagements.

Why it works

The retainer covers your ongoing work and prevents the client from losing visibility. The balloon payment provides the upside on completion. Splitting it this way makes long engagements financially viable for solo practitioners.

Setup

A recurring monthly schedule (the retainer) that ends one month before the expected delivery date, plus a one-shot final invoice for the balloon amount, scheduled for the delivery month.

Contract clause

Payment terms: monthly retainer of [X] for the project duration (approximately [N] months), invoiced on the [1st] of each month, due net-[7]. Final completion fee of [Y] due upon delivery and acceptance of the final manuscript/work product. Total expected project value: [N × X + Y].

The three errors freelancers make with split payments

Error 1: No deposit

The most common mistake. "I'll bill them when it's done." This is fine for 30-day-net corporate clients with long histories. It is not fine for new clients, residential customers, or any project longer than a few weeks. Always take a deposit.

Error 2: Vague milestones

"50% at the halfway point" creates argument about what "halfway" means. Milestones should be specific deliverables that the client has to acknowledge in writing. "Upon written approval of the final concept" is clear. "When we're about halfway" is not.

Error 3: Continuing work before payment is received

The most damaging error. You finish milestone 2, issue the invoice, and start working on milestone 3 before milestone 2 is paid. Now you've committed work for which you have no leverage. The contract should explicitly state that work pauses until each milestone invoice is paid. Most clients will not push back on this clause if it's in the contract from the start.

Setting these up in InvoiceFlow

The payment-schedule feature on each invoice lets you split the total into multiple installments, each with its own date and amount. You can choose between percentage-based splits (which adjust automatically if the project value changes) or fixed-amount installments.

For milestone-based schedules, each installment becomes its own draft invoice that you finalize when the milestone is hit. Reminders fire automatically as due dates approach. The dashboard shows you, at any moment, how much of each active project's value has been billed, paid, or is outstanding.

For recurring-plus-balloon schedules, you combine the recurring-schedule feature (for the monthly retainer) with a scheduled single invoice (for the balloon). Both live on the same client record so the project's full picture is in one place.

The wider point

How you split payments matters more than what you charge per hour. Most freelancers think of "payment terms" as boilerplate at the bottom of an invoice. They're not — they're a strategic choice that determines your risk, your cash flow, and your relationship with the client. Pick the right model for the project type and your business survives projects that would otherwise sink it.

Pick the wrong model and you can be highly paid on paper while perpetually unable to pay rent.