04 / Customer Economics & Cash

The Cash Delay Before Receivables Begins

An operation can finish work long before it can bill. Measure the wait before receivables so each lost day can be traced to its cause.

The example below is illustrative.

Find the invoice that could not be raised

An $80 million services company had stronger revenue and stable collections on issued invoices. The controller still needed more borrowing capacity. Several closed jobs were sitting in a billing queue. One needed proof of completion, one needed an approved change order and a third could not be billed until a future contractual milestone. The list looked like one cash problem. Those three jobs called for three different responses.

Start with a portion of completed work the company can value consistently. For each billing tranche, record work completion, contract eligibility, paperwork readiness, invoice issuance and receipt. Preserve the dates even when they occur out of order. An acceptance record can arrive ahead of the scheduled billing date. A correct invoice cannot ordinarily go out until both gates are open. Count each pre-invoice day once by identifying the gate actually holding the invoice on that date.

Build a weighted delay bridge

Illustrative completed trancheValueCompletion to contract eligibilityAvoidable documentation or rework after eligibilityEligible and ready to issuedTotal
A$600,0002 days7 days3 days12 days
B$300,00020 days0 days0 days20 days
C$100,0000 days0 days2 days2 days

The value-weighted completion-to-invoice time is 13.4 days. Work in a contractual wait accounts for 7.2 weighted days. Documentation and rework contribute 4.2. Issuance after readiness contributes 2.0. This attribution assumes the listed gates bind sequentially. Where the last missing document, contractual milestone and batch date overlap, test the effect of removing each in the actual sequence. Removing an early delay can yield no improvement if it finishes before an independently binding milestone.

Track open tranches as well as invoices already sent. An analysis of issued invoices can omit the worst exceptions because they are still open. List aged unbilled work by value and reason, and keep disputes and amount uncertainty visible. For recurring work, reconcile the calculated wait with the actual month-end balances. Cohort arrivals and year-end seasonality can invalidate a simple average.

One more cut matters when backlog is growing. Compare the same service line across completion cohorts of the same age. A month with many jobs completed in its last week can have a rising unbilled balance while billing performance on each job improves. A low unbilled balance can also conceal declining delivery. Reconcile arrivals, tranches billed, new disputes and the ending queue. If you change the workflow, track cases entering after the change separately from the old backlog. Clearing a one-time backlog can release cash without changing the time the next job will spend waiting.

Put bounds around the cash impact

Consider the scale of an 11-day wait in an $80 million operation. If completed, eventually billable work flows steadily at that rate, $80 million divided by 365 is roughly $219,000 per calendar day, and eleven days corresponds to about $2.41 million of work awaiting invoicing. If that amount is persistently financed at the margin and earlier invoicing advances receipts by the same amount of time, the modeled annual carry at 10% is about $241,000.

For the specific tranches above, the 6.2 weighted days outside contractual waiting mark the potential process opportunity before considering the next batch date or customer payment rules. If operating changes reliably cut three days across the relevant $80 million stream, the steady-state implication is about $658,000 of earlier cash and up to $65,800 annual carry at 10% under those same assumptions. If just $50 million flows through the affected path, use that base instead. Compare realized receipt dates before reporting a cash release. Work awaiting a bill is a value measure. Its recorded asset balance, the cash already paid to deliver it and its eventual collection can all differ.

Recognize when the wait is doing work

Suppose a customer accepts a complex installation only after a functional endurance test. Removing the test could move an invoice forward and increase failures or disputes. The right question might be whether the contract can allow a staged invoice on verified completion, not whether the customer should accept unproven work. Another case is a consolidated invoice customers pay on a fixed weekly run. Sending it a day earlier may help administration without changing receipt. Compare customer payment rules and issuance time to decide which intervention solves the cash problem.

The library’s revenue and cash conversion research addresses the larger gap. This article resolves a specific measurement problem: which delay began before receivables, who owned it, and would removing it change the outcome?

Run a completed-work aging review

Pull all material tranches finished in the last 30 days, including those still unbilled. Record value, date of completion, first contractual eligibility, first documentation readiness, invoice date and receipt or expected receipt. Reconstruct the binding gate for the top ten delays. Choose one fix by value weighted days and credible cash impact. In the next cycle, measure both the gate and what happened to cash. If the gate moves and receipts do not, identify the next condition that governs payment.

Take this to your team. What is the largest amount of completed work the company could bill earlier through a decision it actually controls?

← Back to Customer Economics & Cash