A milestone payment should arrive at the point work is completed, not become another task for the office to chase a week later. Knowing how to collect milestone invoices properly helps protect cash flow, keeps a job moving and gives customers a clear, professional way to pay the amount they agreed.
For businesses completing kitchens, extensions, solar installations, repairs, clinic treatments or substantial professional projects, milestone billing is often the sensible commercial model. The challenge is turning an agreed payment schedule into money in the bank without relying on vague promises, copied bank details and repeated follow-up calls.
Set the payment schedule before the job starts
The easiest invoice to collect is one the customer already expects. Agree the number, value and trigger for each milestone before work begins, then include it in the quote, contract or job confirmation. Avoid labels that leave room for interpretation, such as "mid-project payment". Be specific: "£3,500 due when materials are delivered" or "£2,000 due once first-fix work is complete".
A typical schedule might include a deposit to secure the booking, a payment when materials are ordered or delivered, a stage payment after an agreed phase of work, and a final balance at handover. The right structure depends on the job. A short garage repair may need a deposit and completion payment, while a loft conversion needs more frequent stages to avoid carrying too much labour and material cost.
Each milestone should answer three questions: what has been completed, how much is due, and when must it be paid? If the customer can see the connection between the work and the payment, there is less room for surprise or delay.
Keep the amount proportionate to the work completed
A milestone schedule needs to be fair as well as commercially useful. Asking for a large payment before the customer can see progress may create resistance, particularly on home-improvement work. Equally, letting several expensive stages pass before collecting payment can leave your business funding the project.
Match each request to a tangible point in the job. This gives your team a straightforward reason to issue it and gives the customer confidence that they are paying against visible progress.
Send the milestone invoice at the right moment
Do not wait until the end of the day, or until someone returns to the office, if the milestone is reached on site at 11am. Send the payment request while the work, delivery or approval is fresh in the customer's mind. A short message confirming what has been completed and what happens next is usually more effective than a formal invoice sent without context.
For example: "Hi Sam, the windows have now been installed as agreed. Your stage payment of £2,400 is now due. Please use the secure payment request below so we can book the finishing visit." This is clear, polite and linked to the agreed next step.
Give a due date even where you expect payment immediately. "Due on receipt" can work for smaller jobs, but a specific date makes the expectation clearer. For larger stages, you may agree payment within 24 or 48 hours. Where the contract allows it, make clear that the next phase, delivery or handover is scheduled once the payment has been received.
How to collect milestone invoices with less friction
Manual bank transfers create avoidable work. You send account details, the customer has to type them into their banking app, and then someone on your team checks the account and tries to match a reference. A customer may say they have paid when the transfer is pending, sent from a different account or made with an unclear reference.
A Pay-by-Bank payment request gives the customer a more structured route. Instead of asking them to set up a transfer themselves, you create a request for the exact amount and reference, then send it by WhatsApp, SMS, email or QR code. The customer follows the request, authorises the payment securely in their own banking app, and receives confirmation.
The process is simple:
- Create a request with the milestone amount, job reference and customer details.
- Send it through the channel the customer is most likely to see promptly.
- The customer chooses their bank and approves the payment in their banking app.
- Receive payment status updates and send a receipt or confirmation once it is complete.
This does not remove the need for a clear agreement or a properly issued invoice. It removes much of the payment administration around it. Kube Pay, for example, allows businesses collecting higher-value payments to create and track these requests while keeping the payment conversation in the channels customers already use.
For customers, the key reassurance is that they authorise the payment with their own bank. They do not provide their bank login details to your business, and the request presents the amount and reference clearly before they approve it.
Make every request easy to recognise
A customer is more likely to pay promptly if your message looks legitimate and gives them enough context. Use your business name consistently, include the job or invoice reference, and state the reason for the payment in plain English. If your payment system allows branded requests and hosted checkout pages, use them. A professionally presented request is less likely to be mistaken for a scam or ignored in a busy inbox.
Keep the message short. The customer does not need a long explanation after a conversation with the installer or project manager. They need the amount, the reason, the deadline and a secure way to act.
It also helps to nominate one contact for payment questions. On a larger project, confusion can arise when the homeowner speaks to the installer, office manager and salesperson separately. A single contact prevents conflicting information and makes it easier to resolve a query before it becomes a delayed payment.
Follow up promptly, without making it personal
Payment chasing is most effective when it is consistent rather than confrontational. Send a friendly reminder before the due date where appropriate, then follow up shortly after if the payment remains outstanding. Reference the original request and make it easy for the customer to complete it rather than asking them to search through old messages.
A first reminder might say: "Just a reminder that the £1,800 stage payment for materials is due today. We have resent the secure payment request here. Please let us know if you have any questions." If the next site visit or order depends on payment, explain that plainly. Do not threaten work stoppage unless that is set out in your agreement and you are prepared to follow through.
If a customer raises a concern about the work, separate the issue from the process. Record the concern, decide whether it affects the amount due, and respond quickly. Some delayed payments are genuine disputes; treating every delay as simple reluctance can damage a valuable relationship. But where the milestone is complete and there is no dispute, keep the request focused and repeat the agreed due date.
Give the office a reliable record
Milestone collections become harder when job notes, invoices, bank statements and customer messages sit in different places. Keep a record of when the request was created, sent, viewed where available, paid and receipted. Match each payment to the specific job and milestone rather than relying on a generic reference.
Real-time payment status and downloadable records can reduce the daily checking that comes with manual transfers. They also make handovers easier when the person who issued a request is not the person reconciling payments. For businesses managing several live jobs, that visibility is often as valuable as the payment method itself.
Consider the cost of collection too. Card payments can be convenient, but percentage-based charges become more noticeable on larger stage payments. A fixed per-payment cost may be easier to predict when collecting substantial invoices, although the best option depends on the customer's preference, the payment value and how quickly you need confirmation.
A good milestone process should feel routine to the customer: work reaches an agreed stage, a clear request arrives, they approve it securely, and both sides know where they stand. That consistency protects your margin, keeps projects moving and leaves your team with more time to do the work customers hired you for.