Partial billing can reduce risk for both parties, but only when every document preserves the full commercial picture. A deposit, milestone payment, retainer draw, or installment should not make it difficult to determine the agreed total, the work covered, or the amount that remains.
The control is a simple payment schedule tied to observable events. Each invoice should reference that schedule, each receipt should reference an invoice, and the running balance should reconcile to confirmed funds.
Choose a structure that matches the work
A booking deposit can reserve capacity or fund initial costs. Milestones can follow accepted deliverables. Installments can spread a fixed obligation across dates. A retainer may fund future work and require a separate usage ledger.
State whether each payment is refundable, earned on receipt, applied to the final price, or connected to a cancellation term. Those decisions belong in the agreement, not in an improvised invoice note.
Create one schedule of record
Show the total agreed amount, each payment trigger or date, and the amount or formula due. Identify taxes, reimbursable costs, approved changes, and any holdback separately.
When the price changes, issue a documented revision that explains how remaining installments change. Do not silently recalculate only the final invoice.
Invoice and allocate consistently
Reference the project, agreement, milestone, and payment sequence such as “2 of 4.” Show prior confirmed payments and the remaining contract balance without subtracting money that has only been promised.
Apply each incoming payment to a specific invoice or invoices. If the customer underpays or combines multiple invoices, record the allocation explicitly and confirm it with the customer.
Close the project balance
Before the final invoice, reconcile the schedule, approved changes, invoices, credits, payments, and refunds. Resolve differences while project evidence and contacts are still available.
Issue a final paid record only after funds clear. Retain the schedule and allocation ledger with the other project records.
Pre-send control checklist
- Payment type and purpose are defined in the agreement.
- Total price and payment schedule use the same baseline.
- Each trigger is a date or observable event.
- Refund and cancellation treatment are documented.
- Each invoice identifies its sequence and milestone.
- Prior payments shown are confirmed, not merely promised.
- Changes update the remaining schedule transparently.
- Every receipt is allocated to an invoice.
- Credits and refunds remain visible.
- Final balance is reconciled before project closure.
Decision table
| Stage | Control question | Required action or evidence |
|---|---|---|
| Deposit | Booking, initial cost, or risk sharing | Treatment on cancellation is unclear |
| Milestone | Payment follows an observable delivery event | Acceptance trigger is subjective |
| Installment | Fixed obligation is divided by date | Schedule no longer matches changed scope |
| Retainer | Funds are held or earned under agreed rules | Usage and remaining balance are not tracked |
Primary sources
BillingFixPro reviewed the following government guidance for the recordkeeping and financial-control principles used on this page: