Handling partial payments, deposits, and refunds cleanly

Almost no real project gets paid in one clean lump at the end. You take a deposit to start, bill again at a milestone, collect the remainder on delivery — and once in a while you refund something. Each of those moments is a chance for your books to drift out of sync, and for an awkward conversation about what's actually owed. The fix isn't more spreadsheets; it's a consistent way of recording money against the invoice it belongs to. This guide walks through deposits, staged billing, partial payments, and refunds so the number you see is always the number that's true.

Why deposits protect you (and your client)

A deposit does two jobs. It gives you working capital so you're not financing the client's project out of your own pocket, and it's a commitment filter — a client who won't put down 30% was unlikely to pay the final 100%. For most independent work, a deposit of 30–50% upfront is normal and defensible. For long or expensive engagements, take the deposit and then bill the rest in stages rather than waiting for one big payment at the end.

Make the deposit a line on the proposal so it's agreed before any work starts. If you send proposals with a live pricing table, the deposit and remaining balance are visible to the client at acceptance — no surprise invoice later.

Bill in stages tied to deliverables

Vague dates invite disputes. Tie each payment to something the client can see is done:

1. Deposit on signature — secures the slot, starts the work.

2. Milestone payment when a defined deliverable ships (design approved, first build delivered, draft submitted).

3. Final payment on completion and handover.

Stating the trigger in plain language ("40% on approval of the homepage design") means you never have to argue about whether a payment is due — the deliverable either shipped or it didn't.

Record partial payments against one invoice

The cleanest model is one invoice that the client pays down over time, not three separate invoices you have to mentally add up. When a partial payment lands, record it against that invoice and let the balance update. In Kliently each payment auto-reconciles the invoice, so a $2,000 invoice that's received $800 shows $1,200 outstanding immediately — across the dashboard, the reminders, and the client portal. Nobody has to do the subtraction by hand.

This matters most when reminders are involved. If partials aren't recorded properly, an automated nudge can chase a client for money they've already sent — which damages trust fast. Recording each payment as it arrives keeps reminders honest.

Handle refunds as a recorded event

Refunds happen: a project gets cancelled, scope shrinks, or you simply agree a goodwill return. The mistake is doing it quietly — sending money back through your bank without recording it against the invoice. Do that and your revenue figures, tax records, and the client's portal view all disagree.

• Record the refund against the original invoice so the paid total reflects reality.

• Note the reason briefly — cancellation, partial scope, goodwill — for your own audit trail.

• Refund through the same rail the client paid on where possible, so the money path matches.

Kliently supports full refunds that keep the books correct: the invoice and your totals move together, so a refunded payment never lingers as phantom revenue.

Set deposit and refund expectations in writing

The smoothest refunds are the ones you've already explained. State your terms once — in the proposal or contract — and you avoid renegotiating under pressure later. Common, fair positions:

• Deposits are non-refundable once work has begun (or partially refundable before a start date).

• Cancellation mid-project is billed for work completed up to that point.

• Refunds are processed within a set window — say, 14 days — to the original payment method.

Putting this in the contract means both sides signed off on the rules before money or work changed hands. (Treat these as practical norms, not legal advice — local consumer rules vary, so adapt to your situation.)

A simple end-to-end workflow

1. Quote the deposit and stages on the proposal; get it accepted.

2. Invoice the deposit; record the payment when it lands.

3. At each milestone, invoice the next stage and record the partial as paid.

4. On completion, collect the final balance — the invoice closes itself.

5. If a refund is needed, record it against the invoice so totals stay true.

Done this way, the awkward "how much do I still owe?" question answers itself, and your year-end numbers reconcile without a rescue mission. See how it fits together in invoicing.