How to Invoice Plumbing Deposits Without Double Counting

Keep four records conceptually separate

The approved scope establishes what the customer agreed to buy. A deposit request asks for an amount under agreed terms. A payment record documents money actually received. An allocation connects that payment to the appropriate job or invoice.

Your software may combine some of these steps on one screen, but the underlying questions remain different. Do not mark a job paid simply because a deposit request was created or a link was sent.

Deposit limits, disclosures, refund terms, tax treatment, and revenue recognition can depend on the agreement and jurisdiction. Have an accountant and appropriate local adviser review your setup. This guide explains recordkeeping, not a universal accounting entry or legal policy.

Record the agreed deposit terms

Deposit record
Customer / job / estimate revision: [references]
Agreed deposit amount and basis: [details]
Requested on: [date]
Required milestone, if agreed: [description]
Payment received: [amount, date, verified reference]
Payment status: [requested / reported / verified / other]
Allocated to: [job or invoice reference]
Refund or adjustment reference, if applicable: [details]
Remaining amount under the approved scope: [amount]

Use the customer's actual agreed terms. Do not insert a deposit requirement after approval and imply that it was always part of the proposal.

Work through a simple example

Assume a fictional job has an approved price of $1,000, with a $250 deposit agreed before scheduling. Ignore tax and other adjustments solely to make the arithmetic clear.

Before payment, the deposit request is $250 but verified payments remain $0. After the $250 is received and correctly allocated, $750 remains payable against the $1,000 scope. The price of the work has not become $1,250.

If an approved change adds $100, the revised scope value becomes $1,100. With the same $250 allocated payment, the remaining amount is $850. Keep the change authorization and payment reference separate so both adjustments can be explained.

These are illustrative amounts, not recommended deposit percentages or pricing.

Do not confuse processor settlement with receipt allocation

A customer payment, processor fee, and bank payout can be separate events. The amount arriving in the bank may not equal the amount the customer paid on one invoice.

Use the transaction evidence and your accountant's approved reconciliation method. Do not reduce the customer's payment by a processing fee unless your actual agreement and records support that treatment.

Handle cancellations through an explicit review

When a job changes or is canceled, review the agreement, completed work, payment history, and applicable requirements. Do not automatically assume every deposit is either fully refundable or nonrefundable.

Record the approved decision and any resulting payment reversal or credit adjustment. A note saying “refund approved” is not proof that money was returned. Keep the actual outcome and reference visible.

Check the final bill

Before sending the final invoice, verify the approved scope value, changes, applicable taxes, allocated payments, and remaining balance. Avoid listing the deposit twice under different labels.

The customer should see a coherent story: the agreed work, any approved adjustments, money already received, and the amount still due. That clarity is more important than the specific document label your software uses.