How to Invoice a Deposit or Down Payment: A Freelancer's Guide
When to ask for a deposit, two practical invoice patterns (separate deposit bill vs amount paid), a $1,000 worked example, and how to keep balance invoices clear without messy half-paid status.

You quoted a project at $2,000. The client said yes. Now what—wait until delivery to bill everything, or protect yourself with a deposit first?
Most freelancers who get burned on large projects skip the second option. They send one invoice at the end, wait weeks for payment, and discover the client "didn't budget for that" only after the work is done.
A deposit (or down payment) is how you share risk: part of the money lands before you commit full time, and the balance is clear when the work ships. This guide covers when deposits make sense, the two practical ways to put them on invoices, a worked $1,000 example, and how to avoid the paperwork traps that make clients push back.
Why freelancers use deposits
A deposit is a portion of the total fee collected before or early in the work, with the remainder billed later (or held on the same invoice as "already paid").
Common reasons:
- New clients you have not billed before
- Projects above a threshold you set (e.g. anything over $1,000)
- Custom work that is hard to resell if they walk away mid-project
- Scope that takes weeks before the first usable deliverable
Deposits are not a substitute for a clear contract. They are a cash-flow and commitment tool. Pair them with written scope, payment schedule, and what happens if either side cancels.
Language varies by industry: deposit, down payment, retainer (sometimes), or "50% upfront." On the invoice, pick one plain phrase and use it consistently in line items, payment terms, and notes.
When a deposit is worth it (and when it is not)
| Situation | Deposit fits? | Why |
|---|---|---|
| New client, multi-week project | Yes | You have no payment history with them |
| Fixed-price build ($1k+) | Yes | Common 30–50% upfront / balance on delivery |
| Milestone project (design → build → launch) | Yes | Invoice per phase, or deposit + progress + final |
| Trusted retainer, same monthly amount | Usually no | Recurring billing is cleaner than a deposit each month |
| Small one-off under your threshold | Optional | Admin cost may exceed the risk |
| Hourly consulting, billed weekly | Rarely | Short cycles already limit exposure |
If you already use recurring invoices for retainers, do not force a deposit model on top. Deposits shine for project-shaped work with a clear total and an end date.
Two ways to put a deposit on invoices
There is no single "correct" format. Freelancers and studios usually pick one of these patterns and stick to it so accounting stays simple.
Pattern A — Two invoices (deposit + balance)
Invoice 1 (deposit): bills only the upfront amount.
Invoice 2 (balance): bills the remainder when work is ready, and references the deposit invoice.
Example for a $1,000 project, 50% deposit:
| Document | What the client sees | Amount due |
|---|---|---|
| INV-1001 | Line: "Website redesign — 50% deposit" | $500 |
| INV-1002 | Line: "Website redesign — final balance" + note "Deposit INV-1001 paid" | $500 |
Pros
- Clear for accounts payable: each document is a full bill for a known amount
- Easy to mark paid on the deposit without confusing open AR
- Works well if different people approve different stages
Cons
- Two numbers, two due dates, two follow-ups
- You must keep the math consistent ($500 + $500 = $1,000)
Pattern B — One invoice with amount already paid
One invoice shows the full project total. A line (or the Amount paid field) records the deposit. Balance due is what they still owe.
Example for the same $1,000 project after the deposit lands:
- Line items still describe the full work (or a single project line at $1,000)
- Amount paid: $500 (label can read "Deposit paid" if your tool allows custom labels)
- Balance due: $500
Pros
- One document for the whole engagement
- Balance due is obvious for the client and for you
Cons
- Some AP teams prefer a separate deposit invoice they can close independently
- If you send the invoice before the deposit is paid, "amount paid" should stay zero until money arrives—do not mark a deposit as paid just because you asked for it
Rule of thumb: use Pattern A when the client needs a clean bill for each payment. Use Pattern B when you want one running document and a clear "still owed" total—especially if your software already supports amount paid and balance due.
What not to do
- Do not invent a third "ghost" invoice that never gets sent but holds numbers only in a spreadsheet
- Do not rename status to "half paid" if your tool only has draft / sent / paid / overdue—use amount paid or a second invoice instead
- Do not leave payment terms as only "Net 30" when you actually need 50% before kickoff—spell the deposit schedule in plain language on the document
What to put on the deposit invoice itself
Whether you use Pattern A or B, the document should answer the same questions as any professional invoice—plus deposit-specific clarity.
Line items that read clearly
Prefer specific wording over vague "Payment":
- Good:
Brand identity package — 50% deposit (of $4,000 total) - Good:
Homepage redesign — deposit per proposal dated 12 Jul 2026 - Weak:
Depositwith no project name - Weak:
50%with no base amount
If the full scope is long, keep the description short and commercial. Put supporting context under that line with item details (the optional sub-line under the description)—not a wall of text in the amount column.
Line item details vs invoice notes
Many tools (including NeatInvoice) let each line carry a second text field: details. It sits under the description on the invoice paper and PDF, slightly quieter than the main line. Use it when the extra text belongs to that row, not the whole document.
| Field | Best for | Deposit example |
|---|---|---|
| Description | What they are buying / which payment this is | Landing page design — 50% deposit (of $1,000) |
| Item details | Scope, proposal ref, or phase tied to that line | Per proposal 12 Jul 2026 · Kickoff after deposit clears |
| Invoice notes | Document-wide terms and cross-invoice references | Project total $1,000. Balance invoice after final files. Deposit INV-1042 paid. |
| Payment terms | Short due schedule for humans | 50% deposit due on acceptance · balance on delivery |
Rule of thumb: if a stranger in AP only reads one line, the description should still make sense. Details answer “what does this line cover?” Notes answer “how does this invoice fit the whole project?”
On a balance invoice, put the project name on the line description, and use either details or notes for Deposit INV-1042 ($500) received—details if that sentence is only about that balance line; notes if you also spell refund policy, PO numbers, or multi-phase context for the whole bill.
Payment terms and due date
Spell the schedule on the invoice, not only in Slack:
50% deposit due on acceptance · balance due on deliveryDeposit due on receipt · remaining Net 15 after final delivery
Set a real due date on the deposit invoice (often the same week as kickoff). Tools that send automatic reminders usually key off due date and sent/overdue status—not free-text terms alone.
Notes that prevent arguments
Useful one-liners when the point applies to the whole invoice:
- Total project fee and what the deposit covers
- When the balance invoice will be issued
- Whether the deposit is non-refundable after a certain date (only if that matches your contract)
- Reference to proposal or SOW ID (if not already on the line details)
- On the balance invoice: deposit invoice number and amount already paid
Do not duplicate the same paragraph in both details and notes. Pick one home for each fact.
Numbering
Keep sequential numbers across deposit and balance invoices (INV-1042, INV-1043). On the balance invoice, mention the deposit number in notes (or that line’s details) so both sides can reconcile.
Worked example: $1,000 project, 50% deposit
Agreed total: $1,000 for a landing page design.
Deposit: 50% before work starts.
Balance: 50% on delivery of final files.
Option A — two invoices
-
Kickoff week — Create INV-1042
- Description:
Landing page design — 50% deposit (project total $1,000) - Item details (optional):
Per proposal · Work starts after deposit clears - Amount due: $500
- Payment terms:
Deposit due on receipt - Due date: today or in 3–7 days
- Share a live link so you know they opened it
- When money arrives, mark paid
- Description:
-
Delivery week — Create INV-1043
- Description:
Landing page design — final balance - Item details:
Deposit INV-1042 ($500) received - Notes (optional, whole bill):
Project total $1,000. Final files delivered. - Amount due: $500
- Due date: Net 15 or due on receipt
- Mark paid when the balance clears
- Description:
Option B — one invoice
- After kickoff (or when you are ready to formalize the full bill): create INV-1042 with the full $1,000 project line.
- Description can stay the project name; use item details for
50% deposit due before kickoff · balance on deliveryif you want that next to the line (or put the same idea in payment terms). - When the deposit lands, enable amount paid =
$500. Optionally rename the label toDeposit paidif your workspace allows editable totals labels. - Balance due shows $500. Client pays the remainder; then mark the invoice paid (or leave amount paid at full total).
Both options are valid. The important part is that the client can see what they already paid and what is left—without opening a separate spreadsheet.
Common deposit mistakes
Mistake 1: Deposit only in the email body
If the money amount lives in a paragraph under "Thanks for signing," AP may never enter it. Put the deposit on an invoice (or amount paid on the project invoice).
Mistake 2: Calling it paid before the bank clears
Status paid should mean money received (or committed in a way you trust). A "please pay deposit" invoice is sent, not paid.
Mistake 3: Vague balance invoice
"Remaining balance" with no project name or deposit reference creates disputes. Always tie balance lines to the project and the prior invoice number.
Mistake 4: 50% of a moving total
If scope changes mid-project, write a change order (new line or new invoice) instead of silently rewriting the original deposit math. Keep a paper trail.
Mistake 5: Building a product feature you will not maintain
Some tools try one-click "create balance invoice from this deposit." That sounds helpful until linking, partial refunds, and currency edits create edge cases. Two honest invoices—or one invoice with amount paid—almost always ages better for freelancers.
How this works in NeatInvoice
NeatInvoice is built for freelancers who already think in documents, not accounting ledgers. Deposit workflows use tools you already have on an invoice—no separate "deposit product" required.
Pattern A in the workspace
- Create the deposit invoice with a clear line item and amount.
- Set payment terms and a due date.
- Share a live client link (and email from the app if you want delivery in one place).
- When paid, mark paid.
- Duplicate or create a new invoice for the balance; adjust the line and amount; mention the deposit invoice in item details and/or notes.
Your library keeps both documents under the same client, so Overview still shows what is open versus paid.
Pattern B with amount paid
- Build the project invoice with the full total. Use + Add details on the line if you want proposal or phase text under the description (Preview and PDF show it as a quieter sub-line).
- Turn on Amount paid in totals and enter the deposit once it is received.
- Edit the Amount paid label if you want the PDF and preview to say "Deposit paid" instead of the default wording (same idea as custom discount/shipping labels).
- Balance due updates automatically so you and the client see the remainder.
Payment terms can still say 50% deposit · balance on delivery even when only one invoice exists—terms are plain text for humans; reminders and aging use the due date and status.
What we deliberately do not force
There is no magic "Create balance invoice" button that invents a second document with hidden links. That path is easy to misread (wrong totals, wrong client, half-paid status confusion). Two invoices you control—or one invoice with amount paid—stays legible in Preview, PDF, and live link.
Live links, view tracking, finance overview, email delivery, and payment reminders on Solo and Studio (trial or paid) help after you send the deposit invoice—not only on the final bill. See pricing for plan limits.
Quick comparison
| Approach | Documents | Best when | Watch out for |
|---|---|---|---|
| Two invoices (A) | Deposit + balance | Client AP wants separate bills | Keep numbers and references consistent |
| One invoice + amount paid (B) | Single running bill | You want one balance due number | Only enter amount paid after money arrives |
| Milestones (3+ invoices) | One per phase | Long projects with defined stages | Do not over-split tiny amounts |
| Recurring only | Schedule-generated | Retainers, not project deposits | Wrong tool for one-off 50% upfront |
Bottom line
Deposits are not complicated finance theory. They are a clear split between money you need before you start and money you collect when value is delivered.
Pick Pattern A (two invoices) or Pattern B (one invoice + amount paid), write line items a stranger in AP can understand, put row-level context in item details, document-wide context in notes, schedule in payment terms, and mark paid only when the money is real. Do that consistently and you spend less time chasing full project fees after the work is already out the door.
Start a 7-day free trial on Solo or Studio (no card required) to draft deposit and balance invoices in one workspace. New to the basics? Read how to create a freelancer invoice. After you send, know when your client viewed the invoice so follow-ups stay calm and timely.