Unbilled Revenue: The Work You’ve Delivered but Haven’t Turned Into Cash
A project team completes the work.
Employees have already been paid.
The customer is happy.
But the invoice has not gone out.
Perhaps a timesheet is missing.
A project manager has not approved the billing.
A milestone has not been updated.
Finance is waiting for a purchase order.
Or somebody simply needs to confirm what can be invoiced.
The work is commercially real, but the cash cycle has not even started.
For service businesses, consultancies, agencies, engineering firms, MSPs, and other project-led organisations, this gap between doing the work and billing the work can become a surprisingly large hidden inefficiency. 💷
It matters particularly when service-sector activity is growing. Office for National Statistics data published on 11 September 2026 showed UK services output rising 0.6% in the t
hree months to July, with professional, scientific and technical activities up 2.1%.
More work is good.
More completed work sitting unbilled is not.
Automation and AI can help identify billing delays earlier, but the solution does not start with automating invoices. It starts with understanding why completed work is not moving smoothly from delivery to billing.
The hidden inefficiency is the gap between delivery and invoicing
Most businesses monitor overdue invoices.
Far fewer monitor work that has not yet become an invoice. That distinction is important.
Once an invoice exists, finance can:
See the amount owed
Track the due date
Chase payment
Include it in debtor reporting
Forecast expected receipts
Before the invoice exists, visibility is often much weaker.
The value may be sitting across:
Timesheets
Project-management systems
Service tickets
Contract schedules
CRM records
Expense systems
Finance spreadsheets
Individual inboxes
Nobody has one complete picture. The organisation knows it is busy.
It may not know how much completed work is currently waiting to be billed.
Unbilled revenue is often a workflow problem
A common assumption is that unbilled work exists because finance has not produced the invoice quickly enough.
Often, finance is simply the final step in a much longer process.
The real workflow might look like this
An employee completes billable work.
Time needs to be recorded.
A manager checks the time.
Project progress is confirmed.
Expenses are added.
A billing milestone is reviewed.
Customer purchase-order information is checked.
The project manager approves the amount.
Finance prepares the invoice.
Someone reviews it before release.
If one stage stops, billing stops.
Finance may then spend time chasing the missing information manually.
The problem is not the invoice.
It is the handoff between operational delivery and finance.
Why the delay costs more than it appears
A five-day delay does not sound significant.
Across dozens or hundreds of projects, however, small delays accumulate.
Cash arrives later
Employees, contractors, software, travel, and other delivery costs may already have been paid.
Until the invoice is issued and subsequently paid, the business is funding the gap.
The longer billing takes, the longer cash remains outside the organisation.
Cash-flow forecasts become less reliable
A forecast may assume £200,000 will be invoiced this month.
But if £60,000 depends on:
Missing timesheets
Unapproved milestones
Customer purchase orders
Project-manager sign-off
then the forecast is partly dependent on operational tasks that finance may not be able to see.
Revenue forecasting becomes much stronger when operational billing readiness is included alongside financial data.
Hydrogen BI’s Forecasting Module is built around this principle: bringing finance, CRM, and operational information together so forecasts reflect real business activity rather than static spreadsheet assumptions.
Project profitability becomes harder to understand
A project can appear financially healthy while operational activity tells a different story.
Perhaps:
More hours have been delivered than planned.
Additional work has not been approved commercially.
Expenses have not been recharged.
A fixed-fee project is consuming resource faster than expected.
If the business only looks at invoices, these issues may remain hidden until late in the project.
Billing disputes become more likely
The longer the gap between delivery and invoicing, the harder it can become to reconstruct exactly what happened.
People forget details.
Project teams move on.
Customer contacts change.
Scope discussions become harder to evidence.
Faster billing is therefore not simply a finance objective.
It supports cleaner commercial conversations.
WIP, unbilled revenue and accounts receivable are not the same thing
Businesses often use these terms interchangeably.
Operationally, it is useful to separate them.
Work in progress
WIP generally represents work that has been undertaken but has not yet completed the full journey to invoicing.
Depending on the organisation and its accounting policies, the precise financial treatment can vary.
Unbilled revenue
Unbilled revenue usually refers to value that has been earned or recognised but has not yet been invoiced.
Again, the exact accounting treatment depends on the contract and accounting policy.
Accounts receivable
Accounts receivable begins once an invoice has been issued and money is owed by the customer.
The operational journey therefore looks broadly like:
Work delivered → WIP/unbilled value → invoice raised → payment received
Each transition can create delay.
Good business intelligence helps make those transitions visible.
Where unbilled work usually gets stuck
Several patterns appear repeatedly.
1. Timesheets are late
If invoicing depends on employee time, missing timesheets delay everything downstream.
Finance cannot bill what it cannot evidence.
Managers then spend time chasing employees manually.
2. Project managers become billing bottlenecks
A project manager may need to review dozens of billing lines.
That task competes with:
Customer meetings
Delivery work
Resource planning
New projects
Operational problems
Billing approval becomes something to complete “when there is time”.
3. Contract milestones are not connected to delivery data
A contract may allow invoicing when:
A phase is completed
A deliverable is approved
A certain percentage of work is finished
If that milestone is tracked in a separate system, finance may not know that an invoice can now be raised.
4. Purchase-order information is missing
The work is complete.
The invoice is ready.
But the customer requires a valid PO.
Someone has to locate it.
That delay could often have been identified much earlier in the project.
5. Scope changes are unresolved
Additional work has been delivered, but nobody has confirmed whether it is:
Included in the original fee
Chargeable separately
Subject to a change request
Being absorbed commercially
Automation cannot decide this.
A human needs to make the commercial decision.
6. Expenses arrive late
Travel, materials, subcontractor charges, or other reimbursable costs may reach finance after the main billing review.
The organisation then chooses between:
Delaying the invoice
Billing twice
Absorbing the cost
Better data flow reduces that decision.
Automation can shorten the billing gap 🤖
The objective should not be to automatically invoice everything the moment work is recorded.
That would create obvious commercial and control risks.
A better use of automation is to remove the repetitive checking around the billing process.
Automatically check time completeness
Instead of managers manually searching for missing timesheets, a workflow can identify:
Missing submissions
Incomplete weeks
Unapproved time
Unusual time entries
Only exceptions need attention.
Surface completed milestones
If project status changes to an agreed billable milestone, the system can notify finance or create a billing-review task.
The invoice still receives appropriate approval.
The trigger no longer depends on somebody remembering to send an email.
Create a billing-readiness check
A project can be assessed automatically against agreed conditions.
For example:
Required time submitted?
Expenses recorded?
Milestone completed?
Purchase order present?
Customer billing details valid?
Commercial approval obtained?
Finance can then focus on projects that are ready rather than investigating every project manually.
Flag ageing unbilled work
A useful workflow might surface work that has remained unbilled for:
15 days
30 days
60 days
90 days
The thresholds should reflect the organisation’s normal billing model.
The important point is that the issue becomes visible before somebody discovers it during month-end.
Automate the billing pack
Where appropriate, automation can assemble:
Time records
Expenses
Milestone information
Customer details
Purchase-order references
Supporting documentation
The reviewer receives one prepared view instead of collecting information from several systems.
Where AI can help
AI becomes useful when the billing process includes large amounts of unstructured information.
For example, important billing context may exist inside:
Emails
Meeting notes
Statements of work
Project updates
Contracts
Customer correspondence
AI could assist by:
Summarising why a project cannot yet be billed
Extracting billing milestones from documents
Identifying references to customer approval
Categorising billing blockers
Summarising recent project activity
Highlighting unusual movements in WIP
Drafting internal billing-review notes
Hydrogen BI’s approach to AI follows a similar principle: use AI to monitor activity, identify patterns, automate analysis, and surface meaningful change while business leaders retain control of decisions.
That is particularly important around billing.
AI can tell you:
“This project appears ready for review.”
It should not independently decide:
“Charge this customer £42,000.”
Fix the process before adding AI
If the organisation cannot reliably answer basic billing questions, more sophisticated technology will not solve the underlying problem.
Start with these foundations.
Use consistent project identifiers
Finance, CRM, time recording, and project-management systems need to identify the same project reliably.
If one system calls it:
PROJ-1098
another calls it:
ABC Transformation
and a spreadsheet calls it:
ABC Phase 2
automated reconciliation becomes unnecessarily difficult.
Record billing rules somewhere structured
The business should be able to see whether a project is billed:
Monthly
On milestones
Time and materials
In advance
On completion
On a fixed schedule
If the answer only exists inside a contract PDF or somebody’s memory, billing automation becomes harder.
Keep customer billing requirements current
Record requirements such as:
PO numbers
Billing contacts
Invoice portals
Supporting documents
Submission deadlines
A perfectly prepared invoice can still sit unpaid if it enters the customer’s process incorrectly.
Define ownership
Every billing blocker needs an owner.
For example:
Missing time → employee or line manager
Project approval → project manager
Commercial scope issue → account owner
Missing PO → customer/project owner
Invoice preparation → finance
Without ownership, dashboards simply display stuck work more attractively.
Why a monthly WIP review may be too slow
Many businesses review WIP at month-end. That is better than not reviewing it.
But consider work completed on the second day of the month.
If nobody examines it until the final working day, almost a month may already have passed before the billing issue is discovered.
Then somebody has to resolve the problem.
Then finance raises the invoice.
Then the customer’s payment terms begin.
The delay compounds.
A better operating model continuously monitors billing readiness and exceptions rather than waiting for a monthly spreadsheet.
This aligns closely with Hydrogen BI’s broader approach to business intelligence: move beyond dashboards that people must repeatedly inspect and surface meaningful changes when action is required.
What an effective WIP dashboard should show 📊
A useful dashboard should answer more than:
“How much WIP do we have?”
Headline position
Show:
Total unbilled value
WIP by age
WIP versus previous period
Estimated value ready to bill
Value currently blocked
Expected invoice value by period
Project view
For each project, show:
Project manager
Customer
Contract value
Delivered value
Invoiced value
Remaining budget
Current WIP
Expected next invoice date
Billing blocker
Ageing view
Group unbilled work into useful categories.
For example:
0–15 days
16–30 days
31–60 days
61–90 days
90+ days
The exact buckets matter less than making old items obvious.
Billing blocker view
Categorise why work is not being invoiced.
Possible categories include:
Missing timesheet
Awaiting project approval
Missing PO
Milestone incomplete
Scope query
Customer dispute
Missing expense
Commercial hold
This is where the dashboard becomes operationally useful.
Management can see not only how much value is stuck, but why it is stuck.
Profitability view
Connect WIP with:
Labour cost
Project budget
Forecast completion cost
Invoice value
Expected project margin
This helps identify projects where a billing problem may actually be a wider profitability problem.
A practical example: £90,000 of work that looked like a finance problem
Imagine a consultancy with £90,000 of unbilled work at month-end.
The initial assumption is:
Finance needs to invoice faster.
The business connects project, timesheet, customer, and finance data.
The picture changes.
Of the £90,000:
£28,000 is waiting for project-manager approval.
£19,000 is missing customer PO references.
£17,000 relates to incomplete timesheets.
£14,000 is additional scope awaiting a commercial decision.
£12,000 is genuinely ready for finance to invoice.
Finance controls only £12,000 of the £90,000.
The rest is an operational workflow problem.
The solution is therefore not:
“Ask finance to work faster.”
It might be:
Automated timesheet reminders
Earlier PO validation
Billing-readiness alerts
Clearer scope-change workflows
Manager approval deadlines
A live WIP exception dashboard
That is a very different intervention.
Seven signals worth monitoring
Avoid creating hundreds of alerts.
Start with changes that clearly justify action.
1. Completed work not billed within the expected period
The threshold should reflect normal billing terms.
2. Missing timesheets on billable projects
Especially where upcoming invoices depend on them.
3. Milestones reached without billing activity
A strong candidate for automated notification.
4. WIP ageing beyond normal expectations
Old unbilled work deserves investigation.
5. Project cost rising faster than invoicing
This can expose both billing delay and margin risk.
6. Repeated billing blockers by customer
If one customer consistently has PO or approval problems, the process may need changing.
7. Forecast invoices at risk
Identify expected billing that is unlikely to occur because prerequisites are incomplete.
These signals move the organisation away from reviewing every project manually.
Better WIP visibility improves forecasting
Revenue forecasts frequently treat expected invoicing as if it will happen automatically.
Operational reality is messier.
Suppose a forecast contains £400,000 of invoices expected next month.
Connected project data reveals:
£220,000 is fully ready.
£80,000 depends on milestones due shortly.
£55,000 has unresolved scope changes.
£45,000 is missing required customer information.
The forecast can now reflect different levels of confidence.
That is more useful than a single £400,000 number.
Hydrogen BI’s platform is designed to connect finance, CRM, operational software, and spreadsheets so reporting, forecasting, and analysis use the same underlying information rather than separate departmental versions.
Why this matters in the current business environment
The latest economic data suggests activity is improving in parts of UK services.
The ONS reported that professional, scientific and technical activities grew 2.1% in the three months to July 2026, helping drive services growth.
The Bank of England’s 11 September 2026 Agents’ summary similarly reported modest improvement in business-services volumes, with robust areas including IT, tax, employment law, restructuring, and engineering consultancy. But it also described growth as uneven, employment intentions as broadly flat, and firms continuing to look for efficiency savings while labour and other costs remain important pressures.
That combination matters.
A service business can win more work without wanting to add proportionate administrative headcount.
The answer is not necessarily more finance staff.
It may be a more efficient flow from:
Delivery → approval → billing → cash
A practical unbilled revenue checklist ✅
Choose your ten largest active projects and review them.
Project data
Is the current project stage accurate?
Is there one consistent project ID?
Is the contract value recorded?
Is the billing method clear?
Time and costs
Are timesheets complete?
Are expenses current?
Are subcontractor costs recorded?
Is actual delivery cost visible?
Billing
What can be billed today?
What is preventing the remaining work from being billed?
Is the customer PO available?
Has the billing milestone been reached?
Who needs to approve the invoice?
WIP
How old is the unbilled work?
Is it still expected to be recoverable?
Has additional scope been approved?
Is any value likely to be written off?
Forecasting
When is the invoice realistically expected?
When is payment realistically expected?
Does the cash forecast use those dates?
Has a billing delay affected project margin or resource planning?
Automation
Which checks are repeated manually?
Could missing information trigger a workflow?
Could billing-ready projects be surfaced automatically?
Could management receive exceptions instead of reviewing every project?
If answering these questions requires opening several systems and emailing multiple people, the business has found the hidden inefficiency.
The goal is not faster invoices. It is a shorter path from work to cash
Unbilled revenue is easy to treat as an accounting number.
In reality, it often reveals how well different parts of the organisation work together.
Sales agrees the contract.
Operations delivers it.
Employees record the activity.
Project managers approve it.
Finance bills it.
Customers pay it.
When those stages are disconnected, cash moves more slowly and management sees problems later.
Connected data provides the visibility.
Automation removes repetitive coordination.
AI can help identify patterns and billing blockers where appropriate.
But the most important improvement is simpler:
Make it obvious when completed work is not progressing towards an invoice - and why.
People Also Ask
What is unbilled revenue?
Unbilled revenue generally refers to value earned or recognised from work that has been delivered but has not yet been invoiced. The exact accounting treatment depends on the contract and the organisation’s accounting policies.
What causes unbilled revenue to increase?
Common causes include missing timesheets, delayed project approvals, incomplete milestones, unresolved scope changes, missing purchase orders, late expenses, and billing processes that only run periodically.
What is the difference between WIP and accounts receivable?
WIP relates to work that has not yet completed the billing process, while accounts receivable relates to invoices that have already been issued and remain unpaid. Exact accounting definitions can vary depending on the business and reporting framework.
How can businesses reduce unbilled work?
Start by identifying where billing becomes blocked. Standardise project and customer data, clarify billing rules and ownership, then automate repetitive checks such as timesheet completeness, milestone monitoring, approval reminders, and WIP ageing.
Can AI help manage WIP?
Yes. AI can help summarise project activity, classify billing blockers, extract information from documents, detect unusual patterns, and support forecasting. It should assist the billing process rather than independently make contractual or commercial decisions.
What should a WIP dashboard include?
Useful measures include total WIP, unbilled value by age, billing-ready value, project profitability, expected invoice dates, billing blockers, missing approvals, and forecast invoicing by period.
Further Reading
Office for National Statistics — GDP monthly estimate, UK: July 2026: Published 11 September 2026, with the latest official data on UK services growth and professional, scientific and technical activity. Read the July 2026 GDP release
Bank of England — Agents’ Summary of Business Conditions, September 2026: Current insight into business-services activity, labour costs, capacity, margins, automation, and AI adoption. Read the September 2026 Agents’ summary
Hydrogen BI — Finance Module: How connected financial data and automated reporting can reduce manual work and improve financial visibility. Explore the Hydrogen BI Finance Module
Hydrogen BI — Forecasting Module: How finance, CRM, and operational data can be combined to provide earlier visibility of revenue and performance changes. Explore Hydrogen BI Forecasting
