Why delivered work waits for cash
The milestone shipped and the client is happy. Two months later the cash still has not arrived. The work was done on time. The paperwork after it was not.
MonrixField note · IT services · November 2026 · 7 min readServices firms track utilization, margin and delivery quality with care. The line from a delivered milestone to cash in the bank gets far less attention, and it is often the slowest part of the business. Weeks pass between handing over the work and sending an invoice the client can actually pay.
This note follows one milestone from delivery to payment: where it waits, who could move it, and what follow-through looks like.
About field notes. Field notes describe how a process typically runs and where it typically breaks. The figures are sample data, not any company's results.
Out of 1,000 delivered milestones
- DeliveredDelivery team
- Accepted by clientEngagement manager−180 (18%)
- InvoicedBilling−86 (10%)
- Approved for paymentClient accounts payable−63 (9%)
- PaidCollections−53 (8%)
The path, and who owns each step
The delivery team finishes the milestone. The engagement manager needs the client to accept it. Billing raises the invoice, which the client's accounts payable team has to approve against a purchase order. Collections makes sure it is paid. Two companies, five teams, and a handful of systems that do not talk to each other.
Delivery leaders are measured on delivery. Finance is measured on collections. The days in between, when the work is done but not yet billable, belong to neither, and they are where most of the time goes.
Four places delivered work waits
Timesheets and evidence
Before any of this, delivery has to be provable. Incomplete timesheets or missing test evidence push every later step back.
Client acceptance
The biggest leak in most samples. The milestone is done, but nobody has sent the client a clear acceptance request with the evidence attached. The client sponsor is busy, and sign-off waits for the next status meeting.
Purchase order
The invoice is ready but the client's PO number is missing, expired or out of funds. Billing finds out only when it tries to raise the invoice.
Client approval
The invoice reaches the client's accounts payable team and waits in their approval queue, or is rejected for a missing detail and nobody hears about it.
One milestone, 64 days
- Day 0Delivered
- Days 1–4Waiting: acceptance pack not sent
- Day 5Pack sent
- Days 6–17Waiting: for client sign-off
- Day 18Accepted
- Days 19–24Waiting: for a new PO number
- Day 25Invoiced
- Days 26–33Waiting: in the client's approval queue
- Day 34Approved
- Days 35–64Agreed payment terms
- Day 64Paid
Half the time is waiting, not terms
Payment terms are agreed in the contract, and they are not the problem. In the sample above, thirty of the sixty-four days were agreed terms. Another thirty were waiting: for a pack to be sent, for a sign-off, for a purchase order, for an approval. People worked on the milestone for four days.
Those thirty waiting days are cash the firm has already earned. Shortening them does not need new terms or a harder conversation with the client. It needs the right message sent on the right day by the person who owns the step.
The work was done on time. The paperwork after it was not.
What follow-through looks like
Follow-through is not more reminders. It is four rules, applied to every milestone, every day.
Acceptance, invoicing and approval each have an agreed time, set by the person who owns days to cash. A milestone past its clock is stalled, whatever the reason.
Every stalled milestone has a named person and a specific action with a due date, not a line in a weekly report.
Routine follow-up goes ahead within agreed rules. Anything that touches the client relationship or the terms goes to the owner, and every approval is logged.
A milestone moves forward when the PSA, the ERP or the bank shows it, not when someone says it is done.
The number to watch
Track days from delivery to cash each week, from source systems, and the value of work delivered but not yet invoiced. Alongside them, track how many milestones are past their clock at each step. The first two tell you whether things are getting better. The third tells you where to look this week.
- Counts
- Days from milestone delivered to payment received
- For
- Milestones paid in the last 90 days
- Alongside
- Value delivered but not yet invoiced
- Owner
- CFO or Head of Finance Operations
Five questions to ask this week
- What is the value of work delivered but not yet invoiced, today?
- How many delivered milestones are waiting for client sign-off, and for how long?
- How many invoices are blocked by a missing or expired purchase order?
- How many sent invoices have not been approved by the client, and has anyone checked why?
- Could you report last quarter's days from delivery to cash from source systems today?
If the answers take more than a day to find, that is the first finding. An Outcome Baseline measures this path with your team and finds your leak before anything is built. Read the Baseline guide.