Revenue Leakage in a Service Business: Where It Hides and How to Find It

Revenue leakage examples at each hand-off

The six hand-offs below run from the first inquiry to the money that stays after the job is paid. Each example is a mechanism, not a statistic: something that can happen at that hand-off and that the company’s own records can confirm or rule out.

• Inquiry to quote. An after-hours call that rings through to voicemail and gets no callback the next morning. A web form routed to an inbox nobody checks on Fridays. A caller who asked for a price and got a request to fill out another form instead.
• Quote to contract. An estimate sent and never followed up. A proposal that stalled waiting on one answer from the owner. A customer who said “let me talk to my spouse” and never heard from the company again.
• Contract to delivery. A signed job that waits weeks for a start date until the customer cancels. A deposit never requested, so the customer has nothing at stake. A scope that grows on site without a written change order.
• Delivery to invoice. Extras done on the spot and left off the bill. A finished job whose paperwork rides in a truck for a week. Monthly billing that misses services added in the middle of the month.
• Invoice to payment. A short-pay posted as paid in full. An insurance or third-party denial that nobody reworks before the appeal window closes. An invoice past terms that gets no call because the customer is “good for it.”
• Payment to margin. A discount given once to close a deal and repeated on every renewal since. A price list that has not moved while labor and parts costs have. A seat count, a headcount or a unit count billed from last year’s number.

Each hand-off has its own long read on this site — speed to lead, the second touch on a quote, the invoice that waits after the job is done, net-30 terms that stretch, detention a broker never paid. This page is the map; those pages are the detail.

Where does revenue leak in a medical practice?

In a medical practice, revenue leaks at the hand-offs between the visit and the deposit: the note that waits for a signature, the claim a payer turned back before processing, the denial nobody appealed, and the payment that came in under the contract. The work is done when the patient is seen; every later step belongs to someone else — the provider, the front desk, the coder or billing company, the payer — and each one can stall without a line on the P&L.

Payer deadlines turn delay into loss. For Medicare, 42 CFR 424.44 says that, with narrow exceptions, a claim must be filed no later than the close of the period ending one calendar year after the date of service, and the Medicare Claims Processing Manual says a submission that is not complete and consistent with its instructions will not be considered filed for timely-filing purposes. A denial has its own clock: under 42 CFR 405.942, a Medicare redetermination request must be filed within 120 calendar days of receiving the notice of the initial determination. Commercial payers set their own limits in their contracts, so read each one. This explains the rules; it is not legal advice.

Where an outside billing company files the claims, the leaks do not leave the practice; they move into the company’s reports. Is Your Medical Billing Company Doing a Good Job? lists the eight monthly reports that show each of the gaps below.

• Visit to signed note. A practice that holds the claim until the note is signed carries every unsigned note as revenue it cannot bill, while the Medicare filing year runs from the date of service, not the signature. Measure the lag by provider and by dollar; see Charge Lag: The Claims Waiting on Unsigned Notes.
• Claim to acceptance. A rejected claim was turned back before processing. The same CMS manual says a claim returned as unprocessable for incomplete or invalid information is not denied and has no appeal rights, so a rejection parked with the denials can age past the filing limit. Work rejections as their own daily queue; see Claim Rejection vs. Denial: Two Queues, One Clock.
• Front desk to denial. A skipped eligibility check or a missing or expired prior authorization can come back later as a denial, and a denial written off without reading its reason code can repeat on the next claim. See Prior Authorization Tracker: What to Log and Why.
• Payment to contract. A payment below the contracted allowed amount, posted as paid in full, closes the claim and hides the short-pay. Match each remittance line to the payer’s fee schedule, and list the patient balances that never got a statement.

Where does a staffing firm lose revenue without noticing?

A staffing firm loses revenue without noticing in the gaps between its payroll and its invoices: approved hours that never reach a client invoice, conversion fees nobody billed, invoices a client’s system turned back, bill rates that stopped covering the burden, and contractors who finished an assignment and never got a call about the next one. Each gap sits between two records the firm already keeps, so neither record shows it alone.

The pay side is what makes these gaps expensive. Payroll goes out on payroll day whether the matching invoice has been sent, accepted or paid, so every day an invoice waits is a day the firm carries the client’s labor on its own cash. The days the client sets in its terms are only part of that wait; Staffing Agency Payment Terms: The Payroll Float splits out the days the firm adds itself.

Each leak below can be counted from the payroll register, the ATS, the timesheet or VMS records and the invoices, and each has its own long read on this site.

• Approved hours never invoiced. Match the payroll register, the timesheet approvals and the client invoices assignment by assignment for the last four weeks; hours paid and not billed are the gap. See Staffing Agency Timesheet Approval to Invoice.
• Conversion fees earned and never billed. When a temporary worker is hired onto the client’s payroll, the client agreement decides whether a fee is owed and how much, and the fee is money only once someone invoices it. Match every assignment that ended as hired or converted to an invoice or a written waiver, and ask about the ones that ended early with no reason. See Temp-to-Hire Conversion Fees Earned, Never Billed.
• Invoices a VMS or AP team rejected. Where the client’s terms run from receipt of a correct invoice, each rejection pushes the due date back by the days it takes to notice, fix and resubmit, and nobody books that as a loss. Keep a rejection log by client and program. See Staffing Agency Invoice Rejected: VMS and PO Fixes.
• Margin lost to burden. A markup that cleared the target when the rate was set can miss it once burden moves by state, class of work or time of year. Recheck gross margin per client with burden included. See Staffing Markup vs. Gross Margin, With Burden.
• Contractors nobody redeployed. When an assignment ends and the call about the next one belongs to no one, the contractor can take the next job through another agency, and the firm pays again to source the next worker for the same skills. See Staffing Redeployment Rate: Margin You Earned.

Why revenue leakage never shows on the P&L

A profit and loss statement records transactions that happened. Leakage is made of transactions that did not happen, so the statement has nowhere to put it. An inquiry that went unanswered produces no entry at all. The marketing that produced the inquiry does produce one — it sits in expenses, looking like the ordinary price of doing business.

The billing kind hides differently. When extras are performed and never invoiced, the labor and materials are booked and the revenue is not, so the job simply shows a thinner margin. The easy explanation is that the job ran over, and it is half true: the costs ran over the revenue because part of the revenue was never asked for.

Collections hide in plain sight. A short-pay posted as paid in full closes the invoice, so the open balance disappears from the aging report. A denial written off as uncollectible becomes one adjustment line at month-end. And every standard receivables report starts its clock on the invoice date, so a job finished on the 2nd and invoiced on the 30th looks current on its first day.

The result is a business whose books are accurate and still silent about its largest controllable loss. The accountant has done the job correctly; the job just does not include counting things that never became transactions. Finding them takes a different kind of look.

How to find revenue leakage in the company’s own records

Finding leakage is a matching exercise: two records that should agree, laid side by side, and the gaps counted. No new software is needed for a first pass. A spreadsheet, one recent month and an honest afternoon are enough to see whether a hand-off is tight or loose.

• Inquiries against responses. Export a month of calls from the phone system and form fills from the website, then find each one in the CRM or the job system. Count the ones with no recorded response, and the ones answered the next day or later.
• Quotes against follow-ups. List every quote sent in a recent month. For each, count the touches after sending, and note whether it closed, was lost with a stated reason, or simply went quiet.
• Work orders against invoices. Take the completed jobs or tickets for a month and match each to its invoice. Look for jobs with no invoice, invoices that left off extras noted on the job, and the days between completion and the invoice date.
• Invoices against deposits. Match each payment received to the invoice it paid, line by line. Any difference posted as paid in full is a short-pay nobody disputed.
• Write-offs against their reasons. Pull every adjustment, write-off and credit memo for a quarter and sort them by reason. A reason that repeats is a process, not bad luck.

Work one hand-off at a time, start with a sample small enough to finish, and write down how each gap was found so the same count can be run again next quarter. The free Revenue Self‑Audit scores all six hand-offs in a few minutes and points at the one to sample first.

How to put a dollar figure on each leak

A leak without a dollar figure loses every argument for attention. The arithmetic is simple, and it should be run on the company’s own numbers rather than an industry benchmark: the count of items that leaked, times the average value of one, times the share that would realistically have been collected.

That last factor is where honest estimates and sales pitches part ways. Not every unanswered inquiry was a sale, so use the company’s own close rate on the inquiries it did answer. Not every unbilled extra would have been paid without an argument, so discount it. Some guides define revenue leakage as expected revenue minus collected revenue; but expected revenue on a budget is a hope, not money earned. Price the specific items found in the records, not the gap to a target.

Illustrative example: a contractor reviews 20 completed jobs from one month. Six had a change discussed on site, and three of those changes never reached the invoice, at about $400 each. That is $1,200 in a month from one hand-off, or roughly $14,400 a year if the month was ordinary — before anything at the other five hand-offs is counted. A number like that decides whether the fix is a one-line rule for the crew or not worth a meeting.

Then rank the leaks by two things: the dollars, and how hard the fix is. A large leak with a cheap fix — a same-day invoicing rule, a second follow-up on every quote, one person who disputes every short-pay — goes first. A large leak that needs new staff or new software goes on the list with its price written next to the price of the fix. The free Leak Calculator runs the first pass of this arithmetic for the inquiry side from four numbers the owner already knows.

How do you stop revenue leakage once you have found it?

Stop revenue leakage by giving each leak three things: one named owner, a record that shows the leak at the moment it happens, and a weekly check where the owner reads the number out loud. A leak found once and fixed with a memo comes back, because the hand-off that produced it is still there. Preventing, stopping and controlling leakage are one job done at different moments: the record prevents it, the owner stops it, and the weekly check keeps it under control.

• One owner per leak. A person, not a department: the office manager owns finished-but-unbilled jobs, the estimator owns quotes past their follow-up date, the bookkeeper owns short-pays. The owner can chase the paperwork, price the extra or call the customer without asking first.
• A record at the hand-off. Make the leak visible where it starts, not three weeks later. A job cannot be closed without an invoice number or a written no-charge reason. A quote cannot be marked sent without a follow-up date. A payment that does not match its invoice is posted with a short-pay code, not as paid in full. An extra agreed on site gets a change-order number before the crew builds it.
• A weekly check. One short list per owner, read in the same meeting every week: how many items are open, how old the oldest one is, and what happened to last week’s. A list someone has to read aloud by name gets worked; a dashboard nobody has to speak to gets scrolled past.
• A quarterly re-count. Run the same matches from the section above every quarter, on a fresh sample. If the count has not dropped, the fix did not hold, and the record or the ownership needs to change.

Fix one leak at a time, in the order the dollar ranking gives, and move to the next when the weekly number for the first has held for a month. Software can carry part of the load, such as a required field, an alert when a quote passes its follow-up date, or a reminder before an invoice is due, but only after the owner and the rule exist. The leak gets a name before it gets a tool.

When revenue leakage is not worth chasing

Not every leak deserves a fix. Chasing one costs someone’s time, and some gaps cost more to close than they return.

• The leak is smaller than the fix. A handful of small extras a quarter does not justify a new approval step that slows every job.
• The gap is a pricing decision, not a leak. A discount the owner gives on purpose to keep a good customer is a choice; write it down as one and move on.
• The demand was never a fit. Inquiries for work the company does not do, or in an area it does not serve, are not lost revenue; a quick, polite answer is enough.
• The company is short of cash this month. Collect the invoices already owed first, and leave mapping every hand-off for the month after.
• The records do not exist. If calls, quotes and jobs are not recorded anywhere, the first fix is recording them; any dollar figure before that is a guess.

If the leaks found in an afternoon are small, that is a good answer, and it cost nothing. If they are not, The Revenue Review is the paid next step: two weeks of read-only access to the company’s own records, and a written report that prices each leak and ranks the fixes. It is not worth it for a company that already runs these matches every month and acts on them — that company has done the work. A free 20-minute call is enough to tell which one applies.