Contractor Payment Schedule: Deposits, Milestones and Final Payment

A contractor payment schedule should set out three things before work starts: the amount due, the completion trigger for that amount, and the payment term after the invoice is issued. That keeps the schedule, the invoice and the payment record separate.

The schedule is part of the agreement about when amounts can be invoiced. The invoice is the document you send once an agreed trigger has happened. The payment record is separate again, because issued does not mean paid.

That distinction prevents common mistakes. A deposit that has been requested is not cash received. A stage that is finished but not yet invoiced is not the same as an outstanding debtor. And a final invoice should request only the remaining unbilled amount for the original scope, not repeat the full contract value.

Examples below are fictional, shown in USD, and tax is excluded for illustration. Actual tax treatment and contract wording vary by situation.

What to include in the payment schedule

A usable schedule is more than percentages. It should let both sides tell whether an invoice is allowed without arguing about what “mostly done” means.

Include:

The trigger wording matters. “Installation stage one completed and recorded against quote Q-201” is clearer than “50% complete.” If completion needs evidence, name it: dated site notes, photos, delivery confirmation, or a signed handover sheet that you keep in your own records.

If you need a consistent invoice format once a trigger is reached, a contractor invoice template for stage and final invoices can help keep project references, line items and payment instructions consistent.

A worked $10,000 example

Here is a simple schedule for an agreed base project value of $10,000, excluding tax for illustration.

The arithmetic is the point:

• $500 + $3,500 + $4,000 + $2,000 = $10,000 total billed
• the deposit is part of the $10,000 total, not an extra charge on top
• the final invoice requests only the remaining unbilled amount

A practical schedule entry could read:

Booking deposit of $500 payable after acceptance of quote Q-201 and before materials ordering or start-date confirmation. Stage 1 invoice of $3,500 may be issued when preparation and first installation stage are completed. Stage 2 invoice of $4,000 may be issued when main installation is completed. Final invoice of $2,000 may be issued on agreed handover completion.

That wording avoids three problems: it does not treat the schedule as the invoice, it does not assume an invoice proves payment, and it does not bill the full contract value again at the end.

Write milestone triggers that can be checked

A milestone trigger should describe a result someone else could verify later. Usually that means naming the stage, the result and the record.

Stronger trigger wording includes:

• “Site preparation completed and materials delivered to site.”
• “First installation stage completed and photographed against work order WO-18.”
• “Main installation completed and ready for walkthrough.”
• “Handover completed, with punch list closed or separately recorded.”

Weak wording causes disputes:

• “Work underway.”
• “Half complete.”
• “Near the end.”

If the project has several parts, tie each milestone back to the quote, work order or scope reference. Then the invoice can simply name the stage instead of trying to retell the whole job history.

When it is time to bill, use the same project reference on each invoice. A contractor invoice template with line items and payment instructions helps keep those stage invoices consistent.

Keep invoicing separate from payment tracking

For project billing, you need to track three different figures:

1. the agreed project value
2. the amount already invoiced
3. the amount actually received

Suppose in the example above that INV-201 and INV-202 have been paid and INV-203 has just been issued.

This answers two different questions:

• How much is still to collect on invoices already sent? $4,000.
• How much of the original job has not yet been billed at all? $2,000.

Those are not the same number. “Remaining balance” is too vague unless you say whether you mean unpaid or unbilled.

An invoice is also not payment proof. The IRS says businesses should keep records that clearly show income and expenses and retain supporting records; see IRS business recordkeeping guidance. For practical use, that means checking partial payments against your actual payment records before marking any invoice paid.

Deposits: cautious and practical

Deposits are useful when they are tied to a real commencement event, such as reserving a start date, ordering materials or committing project capacity. The safest approach is to say why the deposit exists and what event allows you to invoice it.

In the worked example, the $500 deposit is included within the $10,000 project total. That keeps the arithmetic clean: once the deposit invoice is issued, the unbilled balance drops from $10,000 to $9,500. It is easier to follow than collecting a deposit and later invoicing the full contract amount again.

Simple wording you can adapt:

• “Deposit invoice may be issued after acceptance of quote [reference] and before commencement activities.”
• “Deposit forms part of the total project price, not an additional charge.”
• “Stage invoices will be issued only for agreed completed triggers.”
• “Final invoice will request the remaining unbilled balance for the original scope.”

Because deposit rules can vary by contract type and location, keep your article-level rule broad: agree the trigger in writing and avoid assuming one approach is always required or always allowed.

Two edge cases that often break the schedule

1. The timeline moves, but the milestone has not happened.

If the next invoice is tied to “main installation completed,” do not issue it early just because the job is delayed and the calendar date has passed. Update the timeline separately and keep the invoicing trigger tied to the agreed completion event.

2. A milestone invoice is only partly paid.

Suppose INV-203 for $4,000 is issued, but the customer pays only $2,500. You have still billed $8,000 cumulatively, but you have received only $6,500 across the project to that point. The final invoice should still be based on what remains unbilled, not used to hide the shortfall on an earlier invoice.

So after INV-203:

• unbilled original scope is still $2,000
• unpaid issued invoices include the remaining $1,500 from INV-203
• if INV-204 is later issued for $2,000, total outstanding becomes $3,500 until payments catch up

Approved extra work is a separate issue again. Do not spread it silently across the original stages or bury it inside the final invoice. If extras are approved later, document and invoice them separately. For that scenario, see How to Invoice Approved Change Orders: A Contractor Example. If your project is billed by measured progress rather than named stages, Progress Billing for Contractors: A Worked Invoice Example covers that structure instead.

Turn the schedule into clean invoices

Once a trigger is reached, the invoice itself should be simple. It does not need to restate the whole agreement. It needs to identify the current charge clearly and match the schedule.

A stage invoice usually includes:

For the $10,000 example, line descriptions might be:

• “Booking deposit under quote Q-201” — $500
• “Stage 1: preparation and first installation stage completed” — $3,500
• “Stage 2: main installation completed” — $4,000
• “Final payment: agreed handover completed” — $2,000

If you want a ready structure, use the contractor invoice template for milestone billing. InvoiceSonic can help on the invoice side with business and client details, line items, tax or currency settings, payment instructions, PDF output, saved client details, invoice status tracking and reminders subject to settings and plan limits. If needed, you can review current plan limits. View or open tracking can help confirm an invoice was seen, but it does not prove payment.

Final check before you send

Before sending either the schedule or the next invoice, confirm:

• all base stage amounts add up to the original project value
• the deposit is included once, not added twice
• each milestone has a visible completion trigger
• unpaid issued invoices are not being confused with unbilled work
• approved extras are separated from the original stage arithmetic
• the final invoice requests only the remaining unbilled balance for the original scope

A contractor payment schedule works when both sides can answer three practical questions without much argument: what has been earned, what can be invoiced now, and what remains for final payment.