Revenue leakage is revenue a firm has earned but never invoices or collects, usually without anyone noticing. In professional services it sits in the gaps between record states, in hours that were worked but never logged, logged but never approved, or approved but never invoiced. You find it by checking each of those states before the invoice run, while the work is still fresh enough to bill.
Key Takeaways
- Revenue leakage in a services firm is mostly an operational problem. Billable time and rebillable expenses stall between the timesheet, the approval and the invoice.
- SPI Research reported average revenue leakage of 4.5% of revenue in 2025, and MGI Research estimates at least three to five percent. At 3%, a consultancy delivering 126,000 billable hours a year at $150 an hour would lose $567,000.
- Unbilled work is not automatically leakage. It becomes leakage when it ages past the point anyone will invoice it, or when it’s written off by default instead of by decision.
- A month-end billing review with a named reviewer for each check finds it while it can still be invoiced. Checking timesheet completeness and pending approvals every week finds it sooner.
- Each billing model leaks in a different place, so time-and-materials, fixed-fee and retainer work each need their own check.
It’s the third working day of the month. Finance is chasing four project managers for timesheet approvals, a delivery lead in another office is asking why a client’s invoice looks lighter than the status report suggested, and someone has just found two weeks of a contractor’s hours that never reached last month’s bill. Nobody did anything wrong, exactly. The work was delivered and the client was happy.
If that sounds familiar, you don’t have a sales problem or a pricing problem. You have records that disagree with each other, and money falling through the space between them. This guide explains where that happens, how to measure it, and how to run a billing review that finds it while you can still invoice it.
What Is Revenue Leakage?
Revenue leakage is revenue a business has earned but never invoices or collects, usually because nobody realises it’s missing. In a professional-services firm, that means billable hours, rebillable expenses and agreed fees that were delivered to the client but never reached an invoice, or reached it at the wrong amount.
What matters in that definition is that the money was earned. A lost deal isn’t leakage, and neither is a discount you chose to give. Leakage is the money you were entitled to and would have billed if the right person had seen the right record at the right time.
You’ll also see the term used widely in subscription billing and sales operations, and the discipline of preventing it has a name borrowed from telecoms, revenue assurance. The idea is the same everywhere, but in a services firm the mechanics are different, because your product is people’s time.
Revenue Leakage vs Unbilled Revenue vs Write-Offs
These three get confused, and the difference decides what you fix.
- Unbilled revenue, often called work in progress or WIP, is the value of time and costs you’ve incurred on a job and haven’t invoiced yet. It’s normal. Every firm that bills monthly carries some.
- A write-off or write-down is a decision to bill less than was recorded, perhaps to protect a relationship or absorb your own rework. It’s visible, and somebody chose it.
- Revenue leakage is what’s left over, the unbilled value that nobody decided to give away.
One more term sits further down the line. An invoice that was sent and never paid is leakage if nobody chased it, and bad debt if the client can’t or won’t pay.
Here’s the thing about WIP. Left long enough, it tends to get written off, either deliberately or by default. The deliberate half is commercial judgement. The default half is the leak. Your goal isn’t to bill every recorded hour. It’s to make sure every unbilled hour is unbilled on purpose.
How Much Revenue Leaks, and How to Measure It
Nobody outside your firm can tell you your leakage rate, but two published figures give a sense of scale. SPI Research’s 2026 Professional Services Maturity Benchmark, which covers 509 professional-services organisations, put average revenue leakage at 4.5% of revenue in 2025. MGI Research estimates that leakage costs at least three to five percent of every company’s revenue, in a research note published in December 2025. Treat both as a reason to measure, not as your answer. The useful number is the one you calculate from your own records.
The calculation itself is simple. Take the value of billable work delivered in a period, subtract what was invoiced for that period, then subtract the write-offs somebody deliberately chose. What remains is leakage, and dividing it by the value of billable work delivered gives you a rate. Invoices that were sent and never collected are a separate count, taken from your overdue receivables.
To see the scale, picture a 120-person digital-transformation consultancy working across three offices on a mix of time-and-materials and fixed-fee projects, with 100 billable consultants. At 1,800 available hours each per year, 70% billable utilisation and a blended rate of $150 an hour, the firm delivers 126,000 billable hours a year worth $18.9 million. If 3% of that leaks, which is the low end of MGI Research’s estimate, the firm loses 3,780 hours or $567,000 a year. At SPI’s 4.5% average it’s $850,500. Seen monthly, 3% is 315 hours, or $47,250 missing from every invoice run.
Realization Rate as the Early Warning
Realization rate is the standard measure of how much recorded billable work gets invoiced, calculated as billed hours divided by billable hours recorded. Legal services show how wide the gap can be. Clio’s 2025 benchmarks show lawyers capturing 3.0 billable hours in an average day, invoicing about 2.6 hours’ worth (an 88% realization rate) and collecting about 2.4 (a 93% collection rate). So about 0.6 of every 3.0 billable hours captured, roughly a fifth, never becomes cash.
Realization tells you that value is disappearing between the timesheet and the invoice. It doesn’t tell you where. Our guide to billable vs non-billable hours covers realization and utilisation in more depth.
Running a Revenue Leakage Audit
A revenue leakage audit, sometimes called a revenue leakage analysis, gives you your own number. Pick a closed quarter and a sample of ten to fifteen projects that spans your billing models and offices. For each one, line up the hours logged, the hours approved and the hours invoiced, then the expenses incurred and the expenses rebilled. Label every gap as a decision or an accident. The accidents, as a share of the billable value delivered, are your leakage rate, and the pattern shows you which stage to fix first.
Where Revenue Leaks Across the Quote-to-Cash Process
Revenue leaks at the handoffs in the quote-to-cash process, wherever a record has to move from one state, one person or one tool to the next. In a services firm the losses that are hardest to see usually sit in the middle, between time capture, approval and invoicing.
Quote-to-cash is the end-to-end commercial process that runs from pricing and quoting a piece of work to collecting payment for it. Sales-led descriptions, such as Salesforce’s outline of the quote-to-cash process, run from configuring the offer and quoting through agreement and order to invoicing, payment and analysis. For a services firm, delivery sits in the middle. The quote becomes a project, people log time and expenses against it, those records are approved, and the approved records become invoices.
Stage | What Leaks | Why It Happens | The Control |
|---|---|---|---|
Quote and scope | Work delivered beyond the agreed scope | Change requests agreed on a call and never priced | Written change requests, linked to the project before the work starts |
Project setup | Hours billed at the wrong rate or flagged non-billable | Rates and billable flags set by hand for each project | One rate source per project, checked at kickoff |
Time capture | Hours worked and never logged | Timesheets filled in days later from memory | A weekly submission deadline with reminders |
Expense capture | Rebillable costs never claimed or not flagged billable | Receipts submitted late, billable flag missed | Capture at the point of spend, with billable as the project default |
Approval | Time and expenses still pending at the billing cut-off | Approver travelling, no deadline, no deputy | A named approver per project and an approval deadline before each invoice run |
Invoicing | Approved time, expenses and fixed fees never added to an invoice | Invoices built from a filtered list or last month’s template | A review of everything approved and uninvoiced, sorted by age |
Collection | Invoices sent late or never chased | No owner for overdue invoices | Automatic reminders and a regular overdue review |
Every row in that table is a gap between two states of the same record. An hour is worked, then recorded, then approved, then invoiced, then collected. It can stall at any of those steps, and a stalled hour doesn’t raise an alarm. It just sits there.
That’s also why disconnected tools make leakage worse. When timesheets live in one system, expenses in a spreadsheet and invoices in the accounting package, every handoff is a manual re-keying step, and every re-keying step is a place for an hour or an expense to be dropped.
Expenses deserve more attention than they usually get. Take a 70-person engineering consultancy that rebills travel and subcontractor costs. If it passes through $40,000 of rebillable costs a month and misses 5% of them, it absorbs $2,000 a month, or $24,000 a year. And unlike a missed hour, a missed expense is cash the firm has already spent.
How Leakage Differs by Billing Model
Every billing model leaks, but each one leaks in a different place. Time-and-materials work loses hours, fixed-fee work loses stages and absorbs extra scope, and retainers lose the work delivered beyond the agreed amount.
Billing Model | How the Client Is Charged | Where It Leaks | What to Check |
|---|---|---|---|
Time and materials | Hours at agreed rates, plus expenses | Unlogged hours, pending approvals, wrong rates | Approved but uninvoiced time, by age |
Fixed fee | An agreed price, often invoiced in stages | A stage never invoiced, extra scope absorbed | Fixed amounts due against fixed amounts invoiced, and hours against budget |
Retainer | A prepaid or recurring amount, from which retainer credit is drawn down | Work beyond the retainer never billed | Work delivered against credit applied in each period |
Milestone | Payment when a deliverable is accepted | Milestone reached and finance never told | Completed deliverables against invoices raised |
Fixed-fee work is where firms often stop looking, on the logic that if hours aren’t billed they don’t need tracking. They do. How the client is charged and how you measure delivery effort are two separate things. On a fixed-fee project the hours are your cost, so untracked overrun leaks margin instead of revenue, and you lose the evidence you’d need for a scope conversation.
How to Find Uninvoiced Billable Time
To find uninvoiced billable time, check four things in order before each invoice run. Start with time that should exist and doesn’t, then time and expenses waiting for approval, then approved items that aren’t on an invoice, and finally fixed fees that are due and haven’t been raised.
- Missing time. Compare the hours each person logged against their expected working week. Anyone who falls short was on leave, was unassigned, or hasn’t completed a timesheet. Only the third is a billing problem, and it’s the one to chase this week. At the 120-person consultancy in the earlier example, 315 leaked hours a month across 100 billable consultants is about three hours each, which is why it hides so easily.
- Time and expenses waiting for approval. List everything submitted and not yet approved, by project and by approver, oldest first. If your system only offers approved records for invoicing, anything still pending is invisible to the invoice run.
- Approved and uninvoiced items. This is the part of your WIP that’s ready to bill. Sort it by age. As a working rule, anything older than one billing cycle needs an explanation, and anything older than two needs an owner.
- Fixed fees and milestones due. Compare the stages and deliverables completed in the period against the invoices raised for them. Nothing in a timesheet will prompt these, so they need their own check.
The Month-End Billing Review: A Step-by-Step Workflow
A month-end billing review is a short, fixed sequence of checks run before invoices go out, each with a named reviewer. It turns finding leakage from a rescue job into a routine, and it works because every check looks at one record state.
Step | Check | What You’re Looking For | Who Reviews |
|---|---|---|---|
1 | Timesheet completeness | People whose logged hours fall short of their working week | Team leads |
2 | Pending approvals | Submitted time and expenses not yet approved | Project managers, chased by finance |
3 | Billable flags and rates | Entries marked non-billable on billable projects, and hours at a zero or outdated rate | Project manager with finance |
4 | Approved and uninvoiced items | Time, expenses and fixed amounts not yet on an invoice, by age | Finance lead |
5 | Scope and write-offs | Hours over budget, and any amount to be written down, with a reason | Delivery director or account owner |
6 | Draft invoice check | Each draft against the engagement terms, including rates, purchase order and retainer credit | Finance lead with project manager |
7 | Send and close | Invoices sent, and the period closed to further edits | Finance |
In practice, you’ll find the first two steps work better weekly than monthly. If timesheets are complete and approved every week, the month-end review becomes a confirmation instead of a hunt.
Back to the 120-person consultancy. With three offices, the review starts by agreeing one billing cut-off in one time zone, so that “end of month” means the same moment everywhere. The review runs steps 1 to 4 across all three offices at once, and the 315 hours a month from the earlier estimate stop being a percentage. They show up as people with missing time, approvals with a named owner, and uninvoiced lines with a project, a person and an age against each one.
Ownership matters as much as the sequence. Finance should own the review, and delivery should own the records.
How to Prevent Revenue Leakage
Preventing revenue leakage means closing each gap at the point where the record is created, so the month-end review has less to find. Most of the controls are habits and settings, not new headcount. Operational maturity shows up in the benchmarks too. In SPI Research’s 2026 benchmark, the most mature firms (Level 5) outperform Level 2 firms by 250% on project margin.
- A weekly submission rhythm. The longer the gap between doing the work and recording it, the more detail is lost. Weekly submission with a fixed deadline keeps it short.
- Notes on every entry. A timesheet line that says what was done can be billed without a follow-up question. One that doesn’t gets queried, delayed and sometimes dropped.
- A named approver for each project, with a deputy. Approval is a control, and it’s also a place where time can stall. Give it a deadline and a backup, otherwise the control becomes the leak.
- Locked periods. Once a period is billed, close it to edits so the figures finance invoiced from stay as they were.
- One source for rates. Set billing rates once per project and check them at kickoff, not at invoice time.
- Written change requests. Scope creep, meaning extra work agreed in conversation and never priced, is the hardest leakage to recover. Write the change down and link it to the project before the work starts.
- Fewer handoffs. Each tool boundary removed is one less place for an hour to disappear.
Operating at 100+ People Across Several Offices
Past about 100 people, revenue leakage stops being about individual forgetfulness and becomes a coordination problem. The same controls apply, but they have to work across offices, time zones and employment types without anyone holding the picture in their head.
Three things change at this size. Cut-offs need a single definition, because a Friday deadline in one office is already Saturday in another. Contractors and subcontractors log time that is both a cost to you and billable to the client, so a missed contractor timesheet hurts twice. And approval chains can no longer run through line managers who don’t know the project, which is why approval by project works better than approval by reporting line.
The controls that hold at this scale are plain ones. Put approval with someone who knows the project, make every time entry say what the work was, and keep a billed period shut once the invoices have gone out. None of that is sophisticated. It’s simply consistent, and consistency is what’s hard to hold across several offices.
ThinkPlace, a management consultancy, is a multi-country example. Its Avaza case study describes a firm of more than 200 people that uses Avaza for time and expense tracking, invoicing and reporting, on projects that are mostly fixed-fee and milestone-based, and that has opened additional offices in the US, the UK, Kenya and Senegal since adopting it. The case study says uninvoiced time, expenses and fixed amounts are visible on the account dashboard and in reports, so that all billable time is included on the invoice.
How Avaza Connects Time, Expenses and Invoicing
Avaza is a connected PSA platform for services firms of 20 to 300+ people running multiple teams and billing models. PSA stands for professional services automation, which in plain terms means quotes, projects, scheduling, timesheets, expenses, invoicing and reporting in one system (our PSA software buyer’s guide covers the category). For leakage, what matters is that the hour you logged, its approval status and the invoice it’s added to sit in one connected system.
Here’s how that maps to the gaps described above.
- Capture. People track time in Avaza timesheets with timers, native mobile apps and Windows/Mac desktop apps, and a weekly reminder can go to anyone whose logged hours fall short of their working week. Notes can be made mandatory on timesheet entries, and billing rates can be set by project, category or person. Expenses can be captured from a photo of the receipt using AI receipt scanning, with billable set as the project default.
- Approval. Timesheet approvals can be switched on by project and by person, expense approvals can be switched on in Expense Settings, and approvers can be assigned at project level. Each timesheet entry shows whether it’s pending, approved or rejected. Approved entries are locked automatically, and timesheets before a chosen date can be locked for everyone except administrators.
- Invoicing. When you create an invoice, you can add some or all of a client’s unbilled time, expenses and fixed amounts. The time and expense lists show billable items that are approved or auto-approved and not yet invoiced, and they can be filtered by project, person and date range. Billable expenses can carry a markup, and retainer credit is held and available to be applied to future invoices. See how this works in Avaza’s online invoicing software.
- Visibility. Avaza’s reports identify unbilled time, expenses and fixed amounts, the Project Dashboard report shows which projects need to be invoiced, and a dashboard widget lists uninvoiced items for each customer for users with the Admin or Finance Manager role. Any report can be scheduled to arrive by email.
It’s worth being clear about the limits. Timesheet and expense approvals are optional. They can be made mandatory, but they aren’t mandatory by default, so you decide where to require them. And a connected system reduces reconciliation and supports more consistent reporting, but it won’t decide what should be written off. One customer describes the practical result as less admin time and fewer errors from copying data between systems.
An Emerging Consideration: AI-Assisted Billing Reviews
As billing data becomes more connected, it becomes useful beyond dashboards and reports. The same live information that helps a finance lead prepare an invoice run can increasingly be accessed through AI assistants, but only when those assistants have sufficient operational context and appropriate controls. AI is therefore worth considering as an emerging extension of the billing review, not as a replacement for sound billing processes or human judgement.
Today, compatible ChatGPT and Claude environments can connect to Avaza through a custom MCP connection to its MCP Server. If MCP (Model Context Protocol) is new to you, our guide explains what an MCP server is. A finance lead can ask which projects have unapproved timesheets before the billing run, request all unbilled expenses for the month, or list overdue invoices, and get answers from live records. An assistant can also prepare a draft invoice for a person to review and send. In a billing review, every AI-assisted step should work that way. The assistant surfaces or prepares, and a person checks and sends.
For firms exploring AI assistants or internal automation, the governance matters as much as the access. A connection operates under the permissions of the Avaza user who authorised it and can be narrowed further through API Permissions. There is no general Avaza review queue where every API or MCP action waits for approval. However, existing timesheet and expense approval workflows still apply to records submitted through an assistant, and organisations can make those approvals mandatory. AI submissions do not bypass those workflows. Firms that want assistants to read billing data without changing it can restrict Create, Update and Delete access for the relevant modules through API Permissions.
As governed agents mature, more of the review’s preparation may be handled this way. That’s a direction, not something to plan this quarter’s close around. AI isn’t the reason most firms fix their billing process, but it’s an increasingly relevant consideration when you choose where your billing data lives.
Frequently Asked Questions
What Is Revenue Leakage in Professional Services?
Revenue leakage in professional services is billable work that was delivered but never invoiced or collected, without anyone deciding to give it away. It usually comes from unlogged hours, time and expenses stuck waiting for approval, approved work left off an invoice, and extra scope that was never priced. It’s an operational gap, not a sales or pricing problem.
What Is the Difference Between Unbilled Revenue and Revenue Leakage?
Unbilled revenue is work you’ve delivered and intend to invoice, also called work in progress. Revenue leakage is the part that never gets invoiced. Unbilled revenue becomes leakage when it ages past the point anyone will bill it, or when it’s written off by default instead of by decision. Sorting unbilled items by age is the quickest way to see which is which.
Do Fixed-Fee Projects Leak Revenue?
Yes, fixed-fee projects leak in two ways. A stage or fixed amount can be completed and never invoiced, and extra scope can be absorbed without a change request. Hours over budget don’t show up as uninvoiced time, but each one comes straight out of margin. Tracking effort on fixed-fee work is what makes the overrun and the unpriced scope visible.
How Often Should You Review Unbilled Time?
Review timesheet completeness and pending approvals every week, and run the full billing review before each invoice run, whether that’s monthly or more often. Weekly checks keep the work fresh enough to correct. If you only look at month-end, you’re reconstructing hours that are up to four weeks old, and some won’t be recoverable.
Who Should Own Revenue Leakage, Finance or Delivery?
Finance should own the billing review and delivery should own the records. Finance is the only team that sees every project, so it’s best placed to spot what hasn’t been invoiced. Project managers are the only people who can confirm whether an entry is right, billable and in scope. Leakage grows when either side is left to do both.
How Do Multi-Office Firms Keep Billable Time From Slipping Through?
Multi-office firms need one billing cut-off defined in a single time zone, an approver assigned to each project instead of each reporting line, and the same timesheet rules in every office. Contractor time needs the same deadline as employee time. Consistency matters more than the specific rule, because one review can’t cover offices that work to different rules.
Can PSA Software Reduce Revenue Leakage?
PSA (professional services automation) software can reduce revenue leakage by keeping time, expenses, approvals and invoices as connected records in one system, so unbilled items can be listed instead of reconstructed. It reduces the re-keying between tools where hours get dropped. It doesn’t replace the review itself. Someone still has to look at what’s unbilled and decide what happens to it.
Find the Leaks Before the Invoice Run
Revenue leakage rarely announces itself. It builds up one unlogged hour and one pending approval at a time, and by the time it shows in the numbers the work is too old to bill. A fixed review, with one check for each record state and a named reviewer for each check, is what stops it.
If you’d like to see how this would work with your own projects and billing models, book a call and we’ll walk through how Avaza would fit your firm’s time, expense and billing workflows. You can also create a free account to explore the platform.
