Job management · Guide · 3 min read
Builder’s quote-to-invoice workflow: scope, changes and payment
Keep scope, acceptance, variations, stage payments and the final balance connected as a trade job moves from quote to invoice.
The final invoice is easier to explain when it follows the same story as the quote. The customer can see what they agreed, what changed and what they have already paid. The office can see what remains to be billed without reconstructing the job from messages.
Give the quote a clear starting point
Use a reference, date and scope that distinguish it from earlier versions. State the work, quantities, access assumptions, exclusions and agreed payment stages. If you have offered alternatives, identify which option the customer accepts.
Keep the acceptance record with that version. A general “looks good” message may need clarification if several prices or options were discussed. Our quote and estimate guide explains why scope and uncertainty should be explicit.
Set up the live job from the accepted scope
Copy or link the agreed details through your system’s supported process. Check the address, contact, dates and materials requirements. Do not assume that a quote conversion copied every attachment or note correctly.
Give the job one place for current instructions. If a customer changes access arrangements by text, add the relevant information where the person attending will find it. Avoid relying on a message visible only on the owner’s phone.
Record variations before they disappear into the work
For a requested change, set out the added or removed scope, price and timing effect, then obtain the required agreement before proceeding. Preserve the original quote. Overwriting it with the new total makes it harder to explain how the price changed.
Original quote: [reference/version]
Requested change: [scope]
Price change and tax treatment: [amount/details]
Effect on timing: [details]
Agreement recorded: [person/date/evidence]
Keep billed and paid amounts separate
A stage invoice can be issued without being paid. Show the difference in your job record. If the system marks a milestone complete, check whether that means the work is complete, the invoice is issued or the money is received.
Consider an illustrative £4,000 job with no VAT or deductions in the example. A £1,000 deposit and a £1,500 stage payment have both been received. The original balance is £1,500. If an agreed £200 variation is added, the final amount to account for is £1,700. Check actual tax and invoicing requirements separately.
Review the final invoice against the whole job
| Check | Evidence |
|---|---|
| Original amount | Accepted quote version |
| Changes | Agreed variations and credits |
| Previously billed | Deposit and stage invoices |
| Previously paid | Matched receipts |
| Final amount due | Reconciled balance and correct tax treatment |
Where CIS or the VAT reverse charge applies, use the correct treatment rather than applying this simplified example unchanged. Your accountant should be able to follow the invoice sequence without counting the same sale twice.
Close the job with a readable record
Keep the final document, payment evidence and any handover information together. Resolve disputed or incomplete work explicitly. An invoice sent is not a payment received, and a payment received does not prove every handover item was delivered.
Try this sequence with one sample customer in PAforTrades. Open each generated document and check the records after every change. The aim is a job history another person can understand without needing the original conversation.
Reviewed 15 September 2026. The workflow and examples are editorial guidance, not measured customer results.
Put the paperwork in one place.
Try PAforTrades with a customer, a job and a quote. Check the result before you send it.
Start your free trial →30 days, no card needed. AI allowances apply; Business Phone is an optional paid add-on.