Payment Upfront Wording: Scripts That Get Deposits Paid

Key Takeaways

• Four specifics do the work, not the politeness. The amount, what it covers, the calendar date it is due, and what happens once it clears. A request missing one gets read and parked.
• The proposal is where a deposit stops being a surprise. By the time you send the email, the client should be confirming a term they already agreed to.
• A payable link beats a payment instruction. Bank details add a task to the client's list. A checkout step removes one.
• Wording is not a legal term. Whether an advance is refundable comes from your contract and your jurisdiction, not the sentence you send.
• Most late deposits are process, not refusal. An effective follow-up repeats the amount and the link rather than asking whether the invoice arrived.

Most advice on this topic optimises the wrong variable. It tells you to sound confident, on the theory that the client is hesitating because your sentence was too soft. The requests that get paid are the specific ones: they name the amount, what it buys, the date it is due, and what happens the moment it clears. A warm, apologetic request missing the due date sits in an inbox for three weeks. A blunt one with all four gets paid on Friday.

Below is wording for the three places the request appears, the proposal, the email and the invoice, plus scripts for a client who pushes back and for a deposit that never lands. Settle one thing first: there is no single norm. A 10-comment r/freelancing thread on how much upfront freelancers actually ask for spreads across 30 to 50 percent, with full prepayment on smaller jobs.

Politeness is not the variable that decides this

The wording problem almost always shows up downstream of a missing commercial term. In a 30-comment r/graphic_design thread, a designer asks how to message a client about payment after already starting work for someone who used to pay reliably and has stopped. No sentence is a good sentence at that point, because the request arrives as a change of terms rather than as a term.

There is a quieter blocker too: people are not sure the ask is legitimate. A 20-comment r/selbststaendig thread asks outright whether a 30 to 50 percent advance on a service engagement is unusual, and the answers treat it as standard for project work. If you are writing tentatively, that uncertainty is usually why, and it resolves once the term lives in a document instead of in a favour.

The cost of leaving it unfixed is concrete. A 10-comment r/smallbusinessowner thread describes losing €2,000 to a client who refused 50 percent upfront and going ahead anyway.

The four specifics every upfront request names

The fourth row is the one people leave out, and it sets the pace. A due date tells the client when they are late. A consequence tells them what being late costs, with no pressure in the sentence.

Wording for each place the request appears

Step 1: Put the term in the proposal, not in the invoice

The deposit belongs in the document the client signs, above the signature line, not in an appendix and not in the email carrying the first invoice.

Payment terms. 40% of the project fee (€1,800) is payable before work begins. The remaining 60% (€2,700) is invoiced on delivery and due 14 days from the invoice date. The project start date is confirmed once the first payment clears.

Three deliberate choices in four lines. Percentage and euro figure both appear, so the client never does the arithmetic. The balance has its own due window, which stops the conversation happening twice. And the start date is tied to the payment rather than the signature, which prevents a client booking your January and paying in February. If the proposal is signed digitally, the term sits inside the e-signature step rather than a separate PDF nobody reopens.

Step 2: The email that carries the deposit invoice

Subject: Deposit invoice for the [project name] kickoff

Hi [Name],

Attached is the deposit invoice for [project name]: €1,800, the 40% we set out in the proposal. It covers discovery and the first design round.

It is due Friday 10 October. You can pay it here: [payment link]

Once it clears I will confirm Monday 13 October for the kickoff and send the calendar invite. If that week needs to move, let me know now and I will hold a different one.

Best,
[Your name]

Nothing in that email apologises, and nothing explains the policy either, because the policy was agreed in step 1. The subject line names a document rather than a request. The amount is repeated even though it is in the attachment, because attachments go unopened. And the last paragraph puts a calendar week at stake, which is a reason to pay today rather than on the due date.

The link matters more than it looks. A 10-comment r/freelancing thread on chasing clients for payment describes the drain as the reminders and the waiting, not the original ask. Bank details mean opening banking, retyping an IBAN and finding a reference. A link means finishing while your email is still on screen.

Step 3: The wording on the invoice itself

The invoice says the same thing in accounting language, and it has to be obvious that it is an advance rather than a final bill.

Line item: Deposit, 40% of project fee, [project name]. Covers discovery and first design round.

Payment terms: Due 10 October 2026. Project start date confirmed on receipt of payment.

Balance: Remaining 60% (€2,700) invoiced on delivery, due 14 days from invoice date.

Two things to check before sending it. An advance-payment invoice is a distinct document type in most EU accounting systems, and the VAT point can fall when you receive the money rather than when you deliver. A plain PDF also no longer counts as a structured invoice everywhere it used to. Our walkthrough of the fields an invoice needs to be deductible covers that side; settle the format with your accountant, not from a template.

Step 4: Wording when the client pushes back

Two objections account for nearly all of it. The first is procedural, from a client whose accounts payable process has no slot for prepayment.

I understand deposits sit outside your standard process. Two ways forward: we can split the engagement into two smaller pieces and invoice each on completion, or you can approve the deposit as a one-off and I will note it in the contract. The second keeps the timeline we discussed. The first moves the start to [date].

The second is a negotiation about the number rather than the principle.

I can start on 20% instead of 40% if the balance falls due at the first milestone rather than on delivery. That lowers your exposure and keeps mine workable.

Both trade rather than concede, and neither defends the policy. A 10-comment r/smallbusiness thread on requiring deposits from new clients lands on the same distinction: a deposit stated as a standing term invites a counter-offer, one stated as a preference invites a debate about whether it should exist.

Step 5: The follow-up when the deposit has not landed

Hi [Name],

The deposit invoice for [project name] (€1,800) was due Friday. I have kept Monday 13 October open for the kickoff and can hold it until Thursday.

Here is the link again: [payment link]

If it is sitting in an approval queue, tell me who to send it to and I will invoice them directly.

Best,
[Your name]

No checking in, no hoping this finds you well, no apology. Amount, link and the date at stake are all repeated, because the recipient has not reread the original email and will not. The last line is the highest-yield sentence in the sequence: the usual reason a deposit is late is that it reached a project contact who cannot approve spend, and naming that gives them an easy answer.

If the second follow-up also goes unanswered, stop writing emails and release the slot. Holding a start date for an unpaid deposit is the loss the r/smallbusinessowner thread describes.

Wording by scenario

Full prepayment reads as aggressive for a project and normal for a session, which is why coaches and trainers charge at booking without a conversation while an agency asking for 100% upfront starts one.

What wording cannot do

Clear wording sets an expectation and creates a record. It does not create an enforceable term on its own, and this is where generic advice gets risky.

Whether an advance is refundable, what you may keep if the client cancels mid-project, and what late-payment interest you can charge are jurisdiction-specific. Many legal systems treat a refundable deposit, a non-refundable deposit and a prepayment for work as three different things, and consumer clients often have stronger cancellation rights than business clients, so a term that holds in B2B may not in B2C.

The practical rule: never write non-refundable in an email if your contract does not say it. Get the clause checked locally once, then reuse it. A written cancellation policy is the companion document, because most deposit disputes are really cancellation disputes.

Collecting the payment, not only asking for it

meetergo is a Cologne-built scheduling and client-pipeline tool with coverage across consulting, coaching, sales and other verticals. What matters for this workflow is where the payment sits: clients complete payment at checkout before the booking is confirmed, so the deposit and the calendar slot become one action instead of two emails.

• Payment at booking through Stripe and PayPal, with deposit or full-payment options per meeting type
• Automated receipts to the client and a tax-ready transaction export
• Cancellation rules that trigger refunds automatically rather than by hand
• Invoicing that turns a quote into an invoice, handles recurring retainers, runs automated dunning on overdue bills, and emits EN 16931 e-invoices in XRechnung and ZUGFeRD with a DATEV export
• Workflows for the reminder sequence, so the step 5 follow-up sends itself the day after the due date

The payments feature page puts paid bookings at 60 percent fewer no-shows, the same mechanism as a project deposit: money already moved changes how the client treats the date. Accepting payments is on the free plan, and paid tiers run €9.90 a month for Light and €29.90 for Suite with a 7-day trial, all listed on the pricing page.

Where this stops: meetergo collects the payment and issues the invoice, and it does not draft your deposit clause. The term still has to live in a document the client agreed to before the invoice arrives, which is step 1 and stays your job. If booking is settled elsewhere and you only need a payment link, a standalone processor covers it, and our comparison of booking tools with payment built in is the better starting point.

Start free with meetergo. Live in 30 seconds, no credit card required.

Common mistakes

• Introducing the deposit in the invoice email. The client reads it as a new condition, so the first reply is a question about the policy rather than a payment. Put it in the proposal and the email becomes administrative.
• Writing due on receipt instead of a date. There is no deadline in it, so the client never becomes late and you never get a moment where following up is obviously reasonable.
• Attaching bank details instead of a link. Every step between reading and paying is a place the request goes dormant. An IBAN plus a reference number is three steps.
• Calling a deposit non-refundable when the contract does not. It creates an expectation you cannot enforce and undermines the terms you can.
• Softening the follow-up until the ask disappears. Just checking in, no rush, whenever you get a chance: each one drops the amount, the date or the link. A follow-up without all three is a message about your discomfort, not the invoice.

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

Sarah NowakManaging Director · Intro call · 30 min09:0010:3014:00

100% GDPR compliant

Booking + video conferencing in one tool.

No downloads.No extra costs.Set up in 30 seconds.

Use for free

FAQs

Is it normal to ask for payment upfront for services?

For project work with a defined scope, yes. The r/selbststaendig discussion linked above treats a 30 to 50 percent advance as standard, and full prepayment is routine for sessions, packages and first-time clients. What reads as unusual is introducing it late, not the request itself.

How much should I ask for upfront?

Commonly 30 to 50 percent for project work, at the higher end for a first engagement or work with real costs before delivery. Below 20 percent a deposit filters nothing. Above 50 percent, expect procurement friction at larger companies.

What do I say if a client refuses to pay a deposit?

Offer a structural alternative rather than defending the term. Splitting the engagement into two pieces invoiced on completion gives similar protection with no prepayment on their books, and a lower deposit with the balance at the first milestone usually clears procurement objections.

Should a deposit be refundable?

That depends on your jurisdiction, your contract and whether the client is a business or a consumer. Refundable deposit, non-refundable deposit and prepayment for work are not interchangeable labels in most legal systems, so have the clause reviewed locally once and then reuse it.

What is the difference between a deposit and a retainer?

A deposit is part of the fee for a specific piece of work, paid before it starts and credited against the total. A retainer buys availability or a block of hours over a period, usually billed for the month ahead. The wording differs accordingly: a deposit references the project total, a retainer references the period.