Invoicing in stages, without waiting for the job to finish

A renovation job runs for four months. If the only invoice goes out at handover, the company has paid wages, materials and subcontractors for four months before collecting a single euro. The answer fits in one sentence: invoice in three stages, a deposit at signature, one or more progress invoices during the work, and a balance at the end, instead of a single invoice that waits for everything to be finished.

Three invoices, not one#

A properly invoiced job has three documents, not two:

• The deposit, at signature, usually between 20 and 30% of the total.
• The progress invoice or invoices, during the work, as it moves forward.
• The balance, at handover, once any snags are closed or the remaining amount is settled.

Many contractors only issue two: the deposit, then the final invoice. In between, two or three months can go by with hours and purchases piling up, and no invoice going out at all. A progress invoice exists precisely to fill that gap.

What stops contractors from invoicing in stages#

Three reasons come up, in this order:

• No objective way to say the job is 40% done, beyond a gut feeling.
• Nobody has the fixed task of issuing a progress invoice every month: it gets decided case by case, so it rarely gets decided.
• The fear of upsetting the client by invoicing "too early", when a progress invoice explained at signature surprises nobody.

A three-step method#

1. Set the invoicing milestones in the quote, not afterwards. Write down the percentage and the event that triggers each progress invoice: weatherproofing done, windows fitted, handover. The client sees them at signature, not on the invoice.
2. Fix a set date every month to issue the progress invoice, independent of how the work feels: the same day each month, every time, even when the job hasn't moved much.
3. Tie the progress invoice to what was actually done: hours logged, materials taken from stock, finished sections. Never a rough guess you couldn't justify if the client asked for detail.

The table below compares the two ways of invoicing the same job, with hypothetical figures to show the calculation.

In the first case, the company advances up to €42,000 of its own working capital before getting it back. In the second, the outstanding amount never exceeds one progress invoice, here around €18,000. Across several jobs running at once, that gap adds up and weighs directly on available cash.

What changes with an application built for the company#

The quote already carries the invoicing milestones: the percentages and the events that trigger each progress invoice are written once, at signature. The site manager logs progress from their phone, section by section, and the progress invoice is built with the right lines without starting the quote over. The document goes out signed, and the next due date shows up on its own in the list of whoever handles invoicing, instead of depending on their memory.

What not to do#

Don't set a progress invoice on a gut feeling. If progress isn't measurable (a percentage installed, square metres done, hours spent), it's better to wait for the next clear milestone than to invoice a figure you won't be able to defend if the client asks for the detail. A disputed progress invoice costs more in client relations than a month of waiting.

Invoicing in stages: the key takeaways#

A single invoice at the end of the job isn't a neutral habit: it turns the company into its own clients' bank, often without anyone deciding it that way. Splitting invoicing into three stages, decided at the quote, brings cash flow back in step with the job instead of the handover.

The method isn't hard to understand, it fits in three steps. The hard part is keeping it up every month, on every job, without it falling on one person who eventually forgets when they're overloaded. That's exactly what an application built for the company automates: the delay between finishing the work and invoicing it stops being just a question of speed at the end of the job, and becomes something settled upstream, at the quote.

See also how to track a job's margin without waiting for the invoice, and what your application can automate around invoicing.