A Completed Job and a Billable Milestone Are Not the Same Thing
Most project businesses track whether jobs are open, in progress, or complete. What that doesn't capture is whether the specific milestone has been confirmed that makes the next invoice due - and those are two different pieces of information with different consequences for cash flow.
Most project businesses track whether a job is open, in progress, or complete. That tells you where work stands and whether the team is occupied. What it does not tell you is whether the specific event has occurred that makes an invoice due. In businesses where payment is linked to stage completion, sign-off, or delivery acceptance, the milestone that triggers payment is a separate piece of information - and one that most job trackers are not built to capture. When that information has no formal home, invoices go out late for reasons that have nothing to do with how quickly customers pay.
What a Payment Milestone Actually Is
A stage payment milestone is a defined event, agreed in the contract or quote, that entitles the business to raise the next invoice. It is not "most of the work is done" or "the job is nearly complete." It is a specific, confirmable outcome.
For an electrical subcontractor, that might be first fix certified by the site manager. For an AV integrator, it might be system commissioning accepted in writing by the client. For a furniture dealer, it might be delivery and installation confirmed with no outstanding snags. The milestone is a boundary, not a percentage of progress - and both sides agreed to it when the job was awarded.
What is rarely agreed is how the business will know when that boundary has been crossed. Who confirms it? Where does that confirmation go? Who sees it? In most businesses, the answer to each of those questions is "whoever was on site at the time." The milestone lives in their memory, their inbox, or a note they made and will get back to.
The Week Between the Milestone and the Invoice
When milestone confirmation has no formal home in the job record, the gap between the milestone being reached and the invoice being sent is measured in days rather than hours.
The pattern is common. The engineer finishes the installation and tells the project manager it is done. The project manager is managing two other jobs and makes a mental note to raise the invoice. Three days later, the accounts person asks what is outstanding. The project manager checks and remembers. The invoice goes out on day five.
Those five days are not the customer's fault. The customer's payment clock starts when the invoice arrives. If the payment terms are 30 days, the wait just became 35. Multiply that across the number of project phases and the number of live jobs, and the timing slip accumulates across the business.
UK construction sector invoices average 61 days from invoice date to payment, according to Build UK and Constructionline data compiled by Market Invoice - the highest average of any major UK sector. For businesses that issue invoices days or weeks after milestones are reached, the real gap between delivering work and receiving payment is longer still.
The milestone clock and the payment clock run separately
When a milestone is reached but not formally confirmed and recorded, the payment clock has not started. Customers pay from the date the invoice arrives, not from the date the work was completed. Every day between those two events is delay that the business created itself.
Why Progress Tracking and Milestone Tracking Are Different Problems
A job tracking system tells you where work stands in aggregate: 40% complete, installation in progress, awaiting final inspection. A milestone confirmation record tells you whether a specific, defined event has occurred and been documented.
The two rely on different inputs. Job progress is typically updated by the person doing the work. Milestone confirmation requires a signal - often from the client, the main contractor, or a designated approver - that a defined output has been accepted. The information comes from a different person and triggers a different action.
A job can show as 80% complete while no payment milestones have been formally confirmed. It can also show as complete while one milestone - practical sign-off, return of a client approval form, formal delivery acceptance - remains unrecorded. Either way, whoever handles invoicing is working without the information they need.
According to Xero Small Business Insights data compiled by Market Invoice, 52% of UK SME invoices were paid late in 2024. A portion of those delays begin before the invoice is raised - in the period between the milestone being reached and the invoice being sent. Ambiguity about whether a milestone has been satisfied is also, according to construction payment specialists, a leading cause of invoice disputes. When there is no documented confirmation, the dispute is harder to resolve quickly.
What Changes When Milestone Confirmation Is Part of the Job Record
When milestone confirmation is attached to the job record rather than left in an inbox or a verbal exchange, three things change.
The milestone becomes visible to everyone who needs to act on it. The person completing the work, the project manager, and whoever handles invoicing can all see whether sign-off has been received without calling anyone to ask. This is the same principle that makes a job tracker useful for job status: it replaces inference with a shared, current record.
There is a documented audit trail. When a customer questions invoice timing - "I did not think this phase was complete yet" - the response is a dated confirmation attached to the job, not a recollection of a conversation from two weeks ago. That documented record is what protects the business in a dispute and speeds its resolution.
The invoice is raised when it is due, not when someone remembers to check. When milestone confirmation is recorded and visible, the invoice follows the milestone event rather than the next time someone happens to review outstanding jobs. For businesses running multiple live projects simultaneously, that shift from reactive to systematic is where the most consistent timing improvement comes from.
Three milestones cover most jobs
For most project businesses, three formally tracked milestones per job cover the majority of payment triggers - project start confirmed, stage completion signed off, and final acceptance recorded. Adding these to the job record does not require a complex system; it requires that each one has a target date and a named person responsible for confirming it.
Zigaflow's project tracking feature logs milestones against each job, with confirmation status visible alongside the rest of the job record - purchase orders, delivery notes, and job timeline. Milestone confirmation is not a separate process; it is part of how the job is managed from the point of award.
Closing
Job progress and payment milestones track different things, and treating them as equivalent is where most preventable invoicing delay in project businesses begins. The fix is not a new payment-chasing process - it is building milestone confirmation into the job record from the start. For businesses where the gap between milestone reached and invoice raised runs to several days across multiple active projects, that is where the timing improvement actually lives. For more on the wider pattern of invoicing that runs behind the jobs it bills for, see why invoices take longer than the jobs that produce them.
Sources
- UK Late Payment Statistics 2026Market Invoice · accessed 2026-08-19
- How UK SMEs Use Invoice Finance in 2026 to Beat Late PaymentsFunding Fred · accessed 2026-08-19
Related pages
Ready to run your business
on one platform?
Book a free demo and see how Zigaflow fits your team.