Deposits and Milestone Invoicing

Last reviewed on April 24, 2026.

For any project that takes more than a couple of weeks to deliver, billing in one lump at the end quietly absorbs risk that belongs with the client. Splitting a project into a deposit and milestone invoices fixes that. This guide explains when to use deposits, how to structure milestone splits, how to present them on an invoice, and what to do when milestones slip.

Why split an invoice at all

A single end-of-project invoice works for small, short jobs — a few days of work, a fixed scope. It stops working as projects get longer, more expensive, or more open-ended. Deposits and milestones solve three specific problems:

• Cash-flow matching. You buy materials, subcontract parts of the work, and cover your own time while the project is in progress. A deposit covers that spend in real time instead of financing it until the end.
• Commitment. A paid deposit tells you the project is real. A client willing to sign an agreement but unwilling to pay 30% upfront is often a client who isn't as ready as they say.
• Risk sharing. If something goes wrong at the end of a project, milestone billing means you are at risk of the final slice only, not the whole total.

When to ask for a deposit

Not every project needs a deposit. The useful decision criteria are:

• Duration. Ask for a deposit once a project runs longer than about two weeks of your time.
• Out-of-pocket spend. If the project requires you to buy materials, book subcontractors, or pay for software before delivery, the deposit should at least cover those costs.
• New client. For a first project with a new client, a deposit reduces the downside if they turn out to be slow payers.
• Custom scope. When the work is bespoke and cannot easily be sold to someone else, a deposit compensates for that lack of reusability.

Trusted repeat clients you invoice monthly, or short projects under a couple of thousand dollars, often don't need a deposit. Save the conversation for where it's worth the friction.

Common split structures

There are four structures that show up again and again in small-business work. Pick the one that matches the shape of the project rather than applying the same split to everything.

50% / 50% — deposit and completion

Half upfront, half on delivery. The simplest option and a good default for two-to-six-week projects with a single deliverable, such as a logo design, a small website, or a photography session. Use it when the project has a single clear "done" moment.

30% / 30% / 40% — deposit, mid-project, completion

Best for projects of a month or two where there is a meaningful mid-point the client can see (a first draft, a working prototype, a rough cut of a video). The mid-project slice keeps both sides engaged and catches scope drift before it snowballs.

25% / 25% / 25% / 25% — even monthly slices

Useful for longer projects — three or four months — where the natural rhythm is monthly. Each slice is paid at the end of a calendar month or at a named checkpoint. The downside is that if any one slice is disputed, there's still a meaningful amount at risk.

Milestone-per-deliverable

Instead of percentages, each deliverable is a fixed dollar amount. Common in construction, product development, and agency work, where the list of deliverables has natural granularity. Each milestone is its own small project: agreed scope, agreed price, issued as a separate invoice when accepted.

How to present milestones on the agreement and on the invoices

Milestones live in two places: the original agreement or contract, and each individual invoice. If you want the structure to hold up when a question comes up later, each place has to match.

On the agreement, list every milestone with: a short description, the deliverable that triggers it, the amount, and the expected date. Use the exact same wording when you later issue the milestone invoice, so the client can line the two documents up instantly.

On the invoice itself, make the milestone the invoice's subject. Instead of a generic line-item table, the first line should say something like: "Milestone 2 of 3 — first-draft delivery on website project X, per agreement of 3 March 2026." Include a short summary of what's already been invoiced ("Milestone 1 paid 12 March — $2,400") so the client sees the project's payment progress on one page.

Worked example — a web project billed 30 / 30 / 40

A designer agrees to build a small e-commerce site for $6,000, split 30/30/40 across three milestones. The project runs for eight weeks. Here is how the invoices would look across the project:

1. Invoice 2026-0140 — 30% deposit. $1,800, issued on the day the contract is signed. Due on receipt. Triggers the start of the work.
2. Invoice 2026-0151 — 30% mid-project. $1,800, issued when a working staging site is delivered to the client for review. Due Net 14.
3. Invoice 2026-0164 — 40% completion. $2,400, issued when the live site is handed over. Due Net 14.

Each invoice sits in its own PDF, uses a sequential invoice number following the designer's numbering system, and references the same project name so that the client's accounts team can file them together. If a milestone is missed or slips, only the affected invoice needs to move — the other two stay anchored to their own triggers.

Retainers — a special case of recurring deposit

A retainer is effectively a recurring deposit: the client pays a fixed amount at the start of each billing cycle in exchange for a guaranteed block of your time or availability. Retainers work well for ongoing advisory, legal, accounting, and agency relationships where the exact work varies month-to-month but the underlying commitment is steady.

Structure a retainer invoice like any other invoice, with two extra lines: the period the retainer covers ("April 2026 retainer — 1 April to 30 April"), and the scope it buys ("up to 20 hours of consulting, one strategy call per week"). If the client goes over the retainer, invoice the overage separately at the end of the period so the retainer itself stays clean.

What happens when a milestone slips

Milestones slip. The useful question is who's responsible for the slip.

• If the slip is on the client's side — they've gone quiet on feedback, delayed approvals, or not provided content — you are usually entitled to invoice the milestone anyway, because the only thing blocking it is client action. Put that wording into the agreement upfront so the conversation is already settled when it arises.
• If the slip is on your side — delivery is late — don't invoice yet. Communicate the new expected date and wait for the trigger you actually promised.
• If the project is paused with work in progress — common in larger or more political projects — you can issue a partial milestone invoice for the work already completed. Describe exactly what's been delivered to date and how that maps to the original milestone.

Common mistakes

• Skipping the deposit on a "good" client. The relationship often feels trustable until the first time there is a real-world problem. Every serious project deserves the same structure.
• Making milestones vague. "50% halfway through" is not a trigger. "50% on delivery of the first-draft wireframes" is.
• Changing the split after work has started. Clients lose confidence fast when the financial structure moves mid-project. Lock the split into the agreement.
• Forgetting to reference the deposit on the final invoice. The last invoice should show the full project total, then subtract payments already made, so the remaining amount due is obvious.
• Billing the full retainer and then doing none of the work. If you've had a quiet month and haven't used the hours, offer a brief note acknowledging that. Clients remember both directions.

Quick checklist before you issue a milestone invoice

• The milestone trigger has actually happened.
• The invoice references the original agreement or quote number.
• The milestone's position in the sequence is named on the invoice (e.g. "Milestone 2 of 3").
• Previous payments are listed as a subtotal so the client can see project-to-date progress.
• Payment terms match the original agreement, not some newer default.

Related guides

• Invoice Payment Terms: Net 15, Net 30, and Beyond
• How to Write an Invoice: Complete Guide
• Invoice vs. Receipt vs. Estimate vs. Quote vs. PO
• Handling Late Payments and Overdue Invoices