Unbilled Revenue: What’s Trapping Your Working Capital (2026 Guide)

The Complete Guide to Unbilled Revenue: Why It’s Trapped, How to Find It, and What to Do About It

There’s roughly $600 billion trapped in accounts receivable across the largest 1,000 U.S. companies right now.

That number, from the Hackett Group’s 2025 Working Capital Survey, has grown 54% since 2018. It represents the single largest pool of recoverable working capital sitting on corporate balance sheets — and most companies are barely touching it.

But here’s what makes that number even more uncomfortable: the standard playbook for fixing it is aimed at the wrong target.

Most working capital improvement programs focus on collections — getting paid faster after the invoice is sent. They invest in AR automation, dunning workflows, payment portals, and early-pay discounts. That’s all fine. But it only addresses what happens after the invoice exists.

For companies with complex billing processes — oilfield services, manufacturing, construction, mining — the bigger problem usually happens upstream: the time between completing the work and creating the invoice. That gap is where the real money gets stuck.

This guide is about that gap. We’ll break down what unbilled revenue actually is (not the accounting textbook version), why it accumulates in enterprise SAP systems, the eight root cause categories that create it, and how to calculate what it’s really costing you. No product pitch — just the operational reality that most finance teams aren’t measuring.

What Is Unbilled Revenue? (The Version That Actually Matters)

If you search “unbilled revenue,” you’ll find dozens of articles explaining the accounting definition: revenue recognized under ASC 606 or IFRS 15 that hasn’t been invoiced yet. Debit unbilled receivables, credit revenue. Balance sheet asset. Period.

That definition is technically correct and operationally useless.

Here’s the version that matters for the people running billing operations and managing working capital:

The distinction matters because the accounting definition makes unbilled revenue sound like a timing issue. Something that resolves itself once the billing cycle catches up. But in practice, for companies with complex order-to-cash processes, unbilled revenue isn’t a timing issue. It’s an operational failure with real financial consequences.

Consider what “unbilled” really means in a $5 billion revenue company with 15% of AR sitting in unbilled status:

That’s not a rounding error. That’s a CFO-level working capital problem hiding inside an operational process.

Why SAP Doesn’t Surface the Problem

If unbilled revenue is this costly, why don’t companies see it?

The short answer: SAP wasn’t built to measure it this way.

SAP’s standard order-to-cash process tracks orders, deliveries, billing documents, and payments. Each step has its own transaction codes, its own reports, its own organizational owners. What SAP doesn’t provide — natively, out of the box — is a view of the time gap between when work was completed and when the billing document was created.

Think about what that means. SAP can tell you that Sales Order 100234 was billed on March 15. It can tell you the delivery was posted on March 2. But there’s no standard dashboard that says: “This order sat unbilled for 13 days, and here’s why.”

The result is a measurement black hole. Finance sees DSO (Days Sales Outstanding), which is a composite number that blends billing delays with payment delays into one metric. If DSO is 65 days, how much of that is billing? How much is collections? Standard SAP reporting doesn’t tell you.

So finance teams attack collections — because that’s the part they can see. Meanwhile, the billing-side delay continues unchecked, invisible, and expensive.

The 8 Root Cause Categories of Unbilled Revenue

After working inside SAP billing environments across oilfield services, manufacturing, and construction for over two decades, I’ve identified 46 distinct causes of billing delays. They cluster into eight categories. Understanding these categories is the first step to measuring and reducing your unbilled exposure.

Here’s an overview of each. (For the full breakdown of all 46 causes, download the complete guide at the end of this article.)

1. Operational & Field Execution Delays

The invoice can’t be created until the work is confirmed in SAP. But in field-intensive industries, there’s often a significant gap between when a crew finishes a job and when that completion is reflected in the system.

A crew completes a job on a rig at 2 AM on a Friday. The field ticket sits in someone’s truck for three days. Then it’s keyed into a spreadsheet. Then emailed to billing. Then re-entered into SAP. By the time the system knows the work is done, two weeks have passed — and every one of those days represents trapped working capital.

Common triggers: incomplete field tickets, missing service entry sheets, delivery completion flags not set, work completion not communicated from field to billing, and rework or change orders that delay final confirmation.

2. Documentation & Approval Bottlenecks

Even when SAP knows the work is done, billing often can’t proceed until a stack of documents is assembled and approved. Customer-required certificates, proof of delivery, QA forms, inspection reports — the billing package has to be complete before the invoice goes out.

Add multi-tier approval workflows (operations signs off, then project management, then finance), email-based routing where status is invisible, and third-party verification requirements (common in oilfield services and construction), and you have a category that alone can add 5–15 days to billing cycle time.

3. Contractual & Commercial Factors

Not every billing delay is a process failure. Some are structurally embedded in how contracts are written.

Milestone billing misalignment is among the most common: work is complete, but the contractual milestone hasn’t been technically reached in SAP’s project system. Progress billing holds, retention clauses (5–10% held until project completion), change order approvals, and split billing complexity in multi-party arrangements — especially Joint Interest Billing (JIB) in upstream energy — all create legitimate but often prolonged delays.

These causes are harder to eliminate but critical to measure. Many companies mistakenly classify contractually delayed revenue as “normal” when it’s actually a symptom of misaligned billing milestone configuration in SAP.

4. Data & System Integration Gaps

SAP is rarely the only system involved in billing. Field service apps, time capture tools, maintenance systems, customer portals — all feed data into the order-to-cash process. When those integrations are slow, unreliable, or manual, billing delays follow.

The most common trigger in this category: missing or mismatched purchase order numbers. A customer PO is missing, expired, or doesn’t match what’s in SAP, and the billing document is blocked until someone resolves it manually. Other triggers include incorrect tax codes, failed IDoc transmissions, and configuration errors in copy control or account determination that silently prevent billing documents from being created.

5. Pricing, Costing & Dispute-Related Causes

When the price in SAP doesn’t match the contract, billing stops. When delivered quantities don’t match ordered quantities, billing stops. When a prior invoice is under dispute, new billing for that customer may be held as a control measure.

These causes share a common thread: they’re downstream consequences of upstream data problems. The rate sheet wasn’t updated in SAP master data. The cost allocation for a project isn’t complete so the system can’t compute the final amount. A credit hold was triggered because the customer exceeded their limit. Each of these Blocks the invoice from being released to accounting — and each one extends the billing cycle.

6. Customer & External Dependencies

Some billing delays originate with the customer, not with your internal process. Pending customer signoff on field tickets or progress reports is endemic in oilfield services, where approval delays of weeks or months are common. Customer portal requirements (Ariba, OpenInvoice) add processing time. Requests for consolidated or monthly invoicing delay transactional billing. And customer shutdown periods — financial close cycles where they simply don’t process incoming invoices — create predictable but often unmanaged gaps.

7. Compliance & Governance Barriers

Regulatory invoicing requirements are an increasing source of delay, particularly for global companies. E-invoicing mandates in India, Brazil, and Mexico require specific system configurations. Audit holds freeze billing during review periods. Country-specific fiscal and language documentation requirements add processing steps. And internal governance — month-end freezes, system downtime during batch processing — creates predictable billing blackout periods that accumulate unbilled revenue.

8. Behavioral & Organizational Causes

This is the category that finance teams rarely examine — and it’s often the most damaging.

Billing deprioritized versus delivery: field teams are measured on execution speed, not invoicing speed, so billing is an afterthought. No defined billing ownership: responsibility for the unbilled backlog falls into the gap between operations, finance, and shared services. KPI misalignment: performance metrics reward delivery volume, not billing timeliness. Inadequate training: billing clerks don’t understand SAP’s process flow or milestone triggers. Reactive management: unbilled revenue gets addressed only during quarter-end reviews, when it’s already too late.

And perhaps most fundamental: lack of visibility tools. No dashboard. No alerts. No way to see unbilled status at the customer, region, or job level. If you can’t see it, you can’t manage it.

How to Calculate Your Unbilled Revenue Exposure

Most finance teams know their DSO. Far fewer know their unbilled AR percentage. Here’s how to find it and translate it into a working capital cost your CFO will care about.

Step 1: Find Your Unbilled Percentage

Unbilled % = Unbilled AR ÷ Total AR

In SAP, this requires comparing open sales orders or service orders that have been delivered/confirmed but not yet billed against your total accounts receivable balance. There’s no single standard report that produces this number — it typically requires a custom query or extracting data from VBAK/VBAP (sales), VBRK/VBRP (billing), and BSID/BSAD (accounting) tables.

If your finance team can’t produce this number today, that’s not unusual. It’s also the problem. Industry data suggests that for asset-intensive companies, unbilled percentages typically range from 5% to 25% of total AR. Companies that have never measured it are almost always at the higher end.

Step 2: Calculate the Daily Cost of Delay

Daily trapped capital cost = (Daily Revenue) × (Unbilled %) × (WACC ÷ 365)

This formula converts your unbilled balance into a daily cost-of-capital figure. For a $5 billion company with 15% unbilled AR and 10% WACC, the calculation looks like this:

Read that last line again: every single day of billing delay costs this company roughly $2 million per year in trapped working capital. A 10-day reduction in billing cycle time releases over $20 million in working capital annually.

That’s not a billing process improvement. That’s a balance sheet transformation.

Step 3: Identify Your Top Delay Categories

Once you know your unbilled percentage, the next question is: where is the time going? Map your billing delays against the eight categories above. In my experience, most companies find that 60–70% of their unbilled balance concentrates in just two or three categories — which means focused improvement can yield outsized results.

The most common concentrations by industry:

Why Collections Alone Won’t Fix This

Here’s the core insight that most working capital improvement programs miss:

Think about what that means. If your DSO is 65 days, and 25 of those days are billing delay and 40 are collections delay, then a world-class collections automation project that cuts payment time by 20% saves you 8 days. That’s meaningful.

But addressing the billing side — reducing that 25-day billing cycle by even 40% — saves you 10 days. And it’s an entirely different kind of improvement: it releases working capital from a pool that no collections tool can reach, because the invoice doesn’t exist yet.

We call this the pre-invoice delay Billing Cycle Time, or BCT. It’s the time from work completion to invoice creation, measured in days. And for companies with complex billing, it’s often the larger component of DSO.

If you’re interested in how BCT differs from DSO and why it matters as a standalone KPI, we’ll be publishing a deep dive on that topic shortly. https://www.getbilled.io/blog/bct-vs-dso/“>BCT vs. DSO: Why Fixing Collections Isn’t Enough

What You Can Do Today

You don’t need a new tool or a transformation program to start addressing unbilled revenue. Here are three things any SAP-based company can do in the next 30 days:

1. Measure your unbilled percentage

Pull your total AR and your unbilled balance. If your finance team can’t separate them, that’s useful information in itself — it means you have a visibility problem. The number doesn’t need to be precise to be actionable. Even a rough estimate (total open orders with delivery posted but no billing document) will tell you whether you have a 5% problem or a 25% problem.

2. Identify your top three delay categories

Sample 20–30 of your most recent late-billed orders. For each one, identify why the billing document was created late. Was it a field ticket delay? A missing PO? An approval bottleneck? A pricing dispute? You’ll almost certainly see patterns — and those patterns will cluster into the categories described above. Knowing your top three categories tells you where to focus.

3. Quantify the working capital cost

Use the formula from the calculation section above. Translate your unbilled percentage into a daily cost-of-capital number. Then present it to your CFO in those terms. Not “we have a billing backlog” (an operations problem). Instead: “We have $X million in working capital trapped because invoices aren’t being created on time” (a finance problem). The framing matters. It’s the difference between a process improvement request and a capital allocation conversation.