Handling Deposits, Partial Payments and Refunds

Explain what the deposit is for

• The agreed payment planThe amounts or percentages due, the dates or stages involved and the remaining payment expected.
• The payments receivedThe confirmed amounts and references, linked to the relevant customer and job.

Decide whether a deposit is required before booking, ordering materials or starting work. Staff need to see whether that requirement has been met without marking the entire job paid.

Keep the payment connected even if the final invoice is created later. Agree how it will be applied so the customer is not asked to pay the same amount again.

Show each payment and what remains

For a simple example, a $2,000 agreed total with confirmed payments of $500 and $700 leaves $800 before any other changes or adjustments. Show the two payments separately as well as the remaining amount.

If a job changes, update the agreed amount through a clear process. Preserve the earlier agreement and explain what caused the difference.

A single payment may cover more than one invoice. Keep the allocation visible so the customer’s overall account and each invoice can be understood together.

Distinguish a failed attempt from an unknown result

A confirmed decline means the attempt did not complete successfully. A missing response may mean the result is still being checked. Staff should see a different next action for those situations.

Keep the existing payment reference and check with the provider before starting another charge when the outcome is uncertain. Repeatedly pressing pay should not be the recovery process.

Connecting payments to sales and jobs explains how to keep attempts and provider confirmations tied to the same business record.

Connect a refund to its original payment

Record why money is being returned, who approved it and which payment it relates to. For a partial refund, keep the refunded amount separate from the rest of the original payment.

Stripe’s refund documentation describes refunds that can remain pending or fail. Check your provider’s process and show the actual result rather than assuming a refund request means the customer has already received the money.

Use the provider’s supported refund process and keep its reference. Give staff a way to find an unresolved refund without sending another request by mistake.

Keep changes to the invoice and money distinct

A cancelled item may require a correction to what is owed. Returning money already paid is a separate event, even when both changes happen together.

Follow the accounting system’s process for credits, corrections and deposits. Keep the related documents connected rather than editing an old total until it happens to match.

Decide what the customer sees in their account or confirmation message. They should be able to understand the changed amount, the refund status and any remaining payment due.

Try a complete payment history

Walk through a deposit, a later payment, an agreed job change and a partial refund. Ask someone unfamiliar with the job to explain the final balance from the records.

Include a failed attempt and a delayed result using the payment provider’s test process. Check what staff can do and which actions require additional permission.

An existing billing product may cover these steps, or you may need a connection to your job software. Compare how each option handles the history and corrections, not only the first successful payment.

Your next step

Write out one example with a deposit, another payment and a later change. Agree how the customer, job, invoice and provider records should explain each amount before configuring the process.