Why Freelancers Ask for a Deposit (And How to Request One)

Start Here and Set the Rule Before Any Work Begins#

For a new direct-client project, a useful default is to begin production after the consulting agreement is signed and the agreed advance payment is confirmed in your own bank or provider records. A manually marked-paid invoice or a client screenshot is not enough. Define the payment state that permits kickoff, then use it consistently in the proposal, agreement and invoice.

The rule only works if the client sees it the same way in every document. If the proposal implies one thing, the agreement says another, and the invoice is vague, signing alone starts to look like permission to begin. Keep the upfront payment tied to both documents so the release condition stays unmistakable. The client should never have to guess whether a signature alone starts the clock.

This default limits how much work you finance for a client. It is a commercial choice, not a universal legal requirement. An established client may need purchase-order approval and payment after delivery. If you accept that arrangement, agree the credit limit, billing dates and stop conditions before signing; record who approved the exposure rather than making an informal exception during production.

1. Set one written start condition. Specify the signed agreement and method-specific payment confirmation required before production. Use the same condition in the proposal, agreement and invoice. If you agree credit terms instead, document the limit and approval before work starts.
2. Choose the prepayment format before promising delivery dates. A fixed-fee project can use a percentage advance or staged payments. Recurring work can use a first-month service payment with defined coverage. Base any minimum on early work and committed costs; do not present an invented rush threshold or percentage as an industry standard.
3. Run a release check before scheduling. Keep the signed agreement and matched payment evidence on file. Verify the invoice amount, currency, reference and payer, including an authorized accounts-payable agent if applicable. If the agreed condition is unmet, tell the client what is missing and discuss the revised date.

Starting “just one part” creates exposure too. If prepayment is the agreed condition, explain that it applies to that work. A separately agreed, paid discovery phase can resolve scope before you commit to production; starting unpriced discovery is still work financed by you.

For deeper clause-level protections, read International Freelance Contract Clauses You Cannot Ignore. If you want to move immediately, Try the free invoice generator.

Once that rule is fixed, the next step is to package it so you are not improvising payment terms on the call.

Prepare Your Deposit Packet Before the Sales Call#

Prepare your proposed terms before the sales call so you can explain the amount, coverage and start condition. The client should have a chance to discuss them before signing. Update the packet after any agreed change, rather than treating your first draft as already accepted.

A useful packet is small and consistent: one terms block, matching agreement language, and invoice templates ready to send. You are not adding paperwork for its own sake. You are making sure the client hears one process, then sees the same process again in writing.

Once terms are accepted, send the matching documents promptly. Same-day delivery can be a useful internal target, but accuracy matters: do not issue a deposit invoice using the old amount or due date after the client approved a change.

This is also where you decide who can release time on the calendar and what proof they need to see first. If you handle sales and delivery yourself, writing it down still matters. Verbal exceptions tend to appear when the process lives only in your head.

1. Put one kickoff trigger in writing. State the required payment confirmation, due date and accepted methods. Define who bears permitted fees, any agreed late-charge terms, notice before suspension and dispute handling. A clause still needs to comply with the law applicable to the engagement.
2. Keep two invoice drafts ready. Maintain recurring-service and fixed-fee templates with placeholders for scope, amount, currency, due date and start condition. Send the accepted version promptly and preserve its agreement reference.
3. Write the scheduling checklist. Name the person who checks the signed agreement and matches payment evidence to the invoice. State how an authorized third-party payer or approved credit arrangement is documented.
4. Explain what the advance covers. List early work and approved travel, materials, site visits or collaborator commitments. Include cancellation, unused-balance and refund handling as well as the notice and review process for a failed or reversed payment.

Keep the agreed start condition consistent after signing. If either party wants a different structure, amend the terms and rerun the checks before changing the schedule.

With the packet ready, you can choose the amount and format from the job itself instead of negotiating them from scratch.

Choose the Right Deposit Structure for the Job#

There is no single split worth defending as the standard. Match the upfront ask to the risk you are taking, the clarity of the scope, and the way the work will actually be delivered.

Use these options to explain your proposal. If effort cannot yet be bounded, quote a limited discovery phase before the main project instead of relying on a larger deposit to absorb unlimited revisions.

For recurring support, distinguish payment for specified monthly services from payment for reserved availability. Set included hours or deliverables, response boundaries and the treatment of unused time. For fixed work, show how the advance reduces the remaining price; the client should not pay the quoted total plus an unexplained extra deposit.

Consider a hypothetical USD 3,000 project. Before the first milestone, you expect 18 hours of work at an internal cost of USD 50 per hour, plus USD 300 of approved outside costs: USD 900 + USD 300 = USD 1,200. A 40% advance would cover that planned exposure. This is a planning example, not a market benchmark or a guarantee that the budget cannot change.

Under that example, credit the USD 1,200 advance against the USD 3,000 price and invoice USD 900 at the agreed intermediate acceptance point and USD 900 at final acceptance. The three payments total USD 3,000. Define the work, review window and acceptance criteria for each event; separately approve scope changes before adding cost.

1. Match the structure to the exposure. Estimate early labor and approved commitments. If scope is uncertain, use bounded paid discovery or smaller funded phases with explicit revision limits.
2. Consider client history and procurement. For an unknown payer, favor a confirmed advance or funded platform milestone under the platform rules. For an established client, decide whether documented, capped credit terms are acceptable.
3. Explain the calculation. Show what the amount covers and how it is credited. Treat percentages as choices for the actual project, not as proof of a universal standard.

Whatever model you choose, the client should be able to find the amount, due date, and release trigger quickly in the paperwork. That is what turns the structure from a policy choice into a workable start condition.

Write Clear Payment and Cancellation Terms#

The paperwork only protects you if the agreement and invoice tell the same operational story. If they trigger different actions or timelines, you have already created room for delayed starts and unnecessary disputes.

Before you send anything for signature, read the agreement and invoice side by side. If compensation, currency, due dates, or the start trigger drift even slightly, fix that first. Small wording differences are exactly what turn a payment issue into an argument about what the client thought they approved.

Write terms that explain the next action when payment arrives, is late, is reversed or the project ends early. Operational clarity helps you administer the contract; it does not establish that every suspension, late fee or non-refundable clause is legally enforceable.

Use the same labels for phases, milestones, and invoice events everywhere. Renaming the same step across documents sounds minor, but it makes payment mapping harder when something slips and you need to trace what was due, when, and why.

1. Define scope and payment events together. Link deliverables, milestones, deadlines, review windows and acceptance criteria to invoices. Show how the advance is credited and who approves extra work.
2. Mirror payment terms. Use the same price, currency, method, due date and start dependency in the agreement and invoice. Separate deposit timing from the net terms on later milestone invoices.
3. Define late-payment and cancellation actions. State required notices, any cure period, permitted suspension and how earned work, approved commitments and unused advances are reconciled. Identify who issues the closing statement and refund.
4. Distinguish collection from your own payout. Agree the confirmation needed for kickoff and how a genuine collection failure or reversal is handled. A successful client payment followed by a delayed payout to your bank is a different event; it should not automatically reopen the invoice or trigger another collection.

For a hypothetical cancellation, suppose the USD 1,200 advance has funded USD 600 of authorized, completed work and USD 300 of approved, nonrecoverable external costs, with no overlap between them. If the agreed terms and applicable law permit those deductions, the closing calculation is USD 1,200 − USD 600 − USD 300 = USD 300 to refund. Record the work and cost evidence and the refund reference. If nothing was earned or committed and no lawful charge applies, the unused advance is USD 1,200. Do not treat the advance as automatically earned on receipt.

For more warning signs in contract text, see 10 Freelance Contract Red Flags That Scream 'Run Away'.

Check the customer type and applicable jurisdiction before adopting cancellation wording. For example, the UK CMA’s consumer-contract guidance warns against keeping prepayments regardless of the reason for cancellation and recovering the same loss twice. That guidance concerns trader–consumer contracts; it is not a worldwide business-contract rule. Your worksheet supports the accounting, while the actual terms and legal rights determine what can be retained.

Pick the Payment Method With Clear Tradeoffs#

Treat payment method as an operations choice, not just a preference. The best option is the one you can verify and reconcile without guesswork, within a timeline you can actually schedule around.

Choose a method by the evidence you can verify, the client’s access and your actual cash needs. The FTC explains that banks can make check funds available before discovering a fake. For cards, Stripe distinguishes authorization from capture: reserving funds on a card is not the same as completing the charge. Neither point makes another method universally safe.

Match the payer, amount, currency and reference in your own records. A company may pay through a named accounts-payable service or treasury entity; document that authorized relationship instead of rejecting a legitimate payment solely because the displayed sender name differs. Investigate unexplained differences before clearing kickoff.

Define the confirmed payment state for each accepted method. For a card payment, check successful capture rather than authorization alone. A successful payment can still face later dispute or reversal. Stripe’s payout documentation separately describes moving available balance to your bank; payment confirmation does not mean your bank cash is already available. If your agreed start condition depends on cash being available to fund external costs, define that condition in advance and explain any scheduling effect without billing the client twice.

A weak method creates work twice, once when the money arrives and again when you need to match it back to the invoice or explain a delay. A strong method gives you a clear confirmation state, a usable reference trail, and a practical fallback if the first attempt fails.

1. Define confirmation before choosing dates. Specify the method-specific state required for kickoff and how your own cash availability affects commitments. Do not promise an exact bank arrival date based solely on a payment submission.
2. Match payment evidence. Verify amount, currency, invoice reference and payer or authorized paying agent using your bank or provider records. Keep the transaction ID and confirmation time.
3. Agree a fallback. State the permitted method and any additional fees. Reconcile the first attempt before requesting another payment; use the fallback for a confirmed failure or reversal, not simply because your payout is pending.

Resolve an unexplained mismatch before scheduling under a prepayment condition. If the payer is authorized and the money is correctly applied, document that explanation so the next person reviewing the invoice does not mistake it for missing payment.

With the method chosen, onboarding becomes the final pass or fail step before anyone begins delivery.

Run a Client Onboarding Gate Before Kickoff#

Use onboarding as a release check, not a formality. This is the point where a verbal yes becomes an operational yes. Until the record set is complete and consistent, the project is not ready to start.

That sounds simple, but it matters because payment problems rarely come from one missing item alone. They come from small mismatches between the signed terms, the billing record, and the payment evidence. The gate exists to catch those mismatches before they become production problems.

One owner matters here. When everyone assumes someone else cleared the exception, the exception usually survives long enough to reach kickoff. Put one person in charge of marking pass or fail, even if that person is also the one doing the work.

1. Confirm the record set. Keep the signed agreement, issued invoice, matched payment evidence and payer details together. Under an approved credit arrangement, retain its written approval and exposure limit instead of falsely recording an advance as received.
2. Separate deposit timing from later net terms. An advance due before kickoff should not accidentally inherit net 30 terms from the final invoice. For later net 10, 15 or 30 invoices, specify what starts the clock and keep the agreement and invoice consistent.
3. Assign one decision owner. Log pass or fail, date, evidence, unresolved issue and next action. For any permitted exception, record its approver and limit.
4. Update agreed changes before acting. If amount, scope or timing changes, capture written acceptance, amend the affected agreement and invoice, then rerun the gate. Do not let an unrecorded conversation replace the agreed condition.

If an agreed requirement is unmet, tell the client exactly which record or action is missing. Keep the production start provisional until the condition is satisfied or both parties formally accept a different arrangement.

With the start condition agreed, send the payment request. The payment check can pass only after the required confirmation arrives; requesting the advance comes before that approval.

Ask for the Deposit Without Sounding Defensive#

Ask like a scheduler, not like you are asking for a favor. A clear, procedural message lands better than a long explanation because it gives the client one obvious next action and makes the release condition feel normal.

This works best when the note sounds like process, not suspicion. The client should be able to read it, pay the invoice, and know what happens next without a second email. Long defenses usually create more friction than a short, specific request.

A working message for the hypothetical project is: “The total project price is USD 3,000. Invoice DEP-001 requests the USD 1,200 advance, credited against that total, by 12 October 2026. Please use the invoice’s accepted payment option and reference DEP-001. We propose kickoff on 14 October, subject to the signed agreement and confirmed payment. Once confirmed, I’ll send the agreed first-milestone schedule.” Adapt the dates and confirmation condition to the accepted terms; do not promise an unavailable slot.

1. Send a complete payment request. Include the invoice number, amount, currency, due date and agreed start condition. Link the actual invoice and state the next action.
2. Give usable payment options. Offer the supported options you actually accept, with beneficiary details or the provider link and invoice reference. Explain permitted fees and currency handling.
3. Discuss structure before changing protection. Smaller funded phases or paid discovery may suit the client. If considering payment after delivery, assess and document the capped exposure before amending the agreement.
4. Confirm receipt and schedule. Match the payment to the invoice, acknowledge it and confirm the start date and first milestone. Track your own pending payout separately; resolve actual mismatches before production.

That framing keeps the conversation about scheduling and records, not about whether you trust the client. It also makes it easier to hold the line later, because you have already presented the deposit as a normal part of kickoff.

Handle Failures Without Losing Control of the Project#

When a payment problem appears, identify what failed before choosing the remedy. A missing advance, disputed client payment and delayed withdrawal from your provider have different implications. Apply the agreed notice and suspension process and preserve the evidence; do not assume every provider hold gives you an immediate right to stop contracted delivery.

After an agreed suspension, record which tasks and dates are affected, the notice given and what permits resumption. Continuing selected tasks changes your exposure; authorize and document that decision instead of quietly letting paused work continue.

Keep the client-facing status, responsible person and next update date in the project thread. Submit verification documents and dispute evidence through the provider’s designated channel, and link the ticket or case reference in your internal record.

1. Late deposit: identify the missing condition. Restate the due date and invoice reference, propose the next update and agree any revised schedule once payment or amended terms are confirmed.
2. Hold: reconcile before retrying. Check whether the client payment succeeded, failed, was reversed or remains incomplete. Escalate a pending payout with the provider. Request another collection only after confirming it is actually needed and preventing duplicate payment.
3. Reversal: preserve evidence and follow the remedy. Record the deadline, dispute or return reference and delivery history. Notify the client and apply any suspension only under the agreed terms and applicable rights.
4. Refusal: decide the exposure. Offer a bounded alternative if suitable. Approve any credit limit in writing before starting; decline if you cannot fund that risk.

You are not trying to punish the client. You are keeping project status unambiguous until the money issue is resolved. If the records stay clean, your next decision usually stays clear too.

Put Your Deposit System on One Page and Reuse It Every Time#

If you want this to hold up when things get busy, put it on one page you can actually use. You do not need a long policy. You need a short working document that tells you what must be true before work begins, who checks it, and what happens if payment fails.

That one-page limit matters for a reason. The simpler the process is to review, the more likely you are to follow it when a client is pushing for a fast start or a verbal exception. You should be able to read that page and know within a minute whether the job is cleared to start or still blocked.

1. Run the five checks in order. Confirm the agreement, issue the invoice, verify the agreed payment or funded-milestone condition, log the approval, then confirm kickoff. Keep any approved credit arrangement explicitly identified.
2. Show the primary and fallback methods. Record accepted bank, card, wallet or check options, the required confirmation state and fee handling. Reconcile the first attempt before retrying.
3. Standardize the packet. Use matching agreement and invoice wording for price, advance credit, milestones, notices and cancellation or refund treatment. Keep the payment reference and evidence linked.
4. Review failures monthly. Track late advances, incomplete payments, provider payout delays and reversals separately. Update the relevant check or term with the client’s agreement where required.

Keep the page usable for the person who schedules work and the person who reconciles receipts. Traceable invoicing and payment status can support the process, but the record must still show the agreed condition, who verified it and the evidence used.

If you are dealing with nonpayment after the fact, see Client Won't Pay? Your Step-by-Step Guide to Collecting Overdue Payments. If you need country or program specifics, Talk to Gruv.