Revenue Cycle Complexity

What Is Revenue Cycle Complexity? The Root Cause of Poor RCM Outcomes

Revenue Cycle Complexity, or RCC, is the accumulation of errors, omissions, and structural issues across a practice that put your revenue cycle objectives at risk and inflate the time it takes to bill and collect. It is the single biggest hidden challenge in healthcare revenue cycle management, and it is the root cause of poor outcomes: growing accounts receivable, slow payments, lost revenue, and rising cost. Every healthcare organization has some. The only questions are how much, and whether you have measured it. This is a deep dive into what RCC is, how it does its damage, and why reducing it should be the number one focus of every revenue cycle system, process, and function.

Everything here is proven by millions of claims worth of data gathered over seven to eight years. Where I share an opinion, I will say so.

Revenue cycle complexity is a black hole

I call RCC a black hole for a reason. A black hole is invisible to visual inspection. You cannot see it directly; you only know it is there, and how big it is, by measuring its impact on the things around it. Revenue cycle complexity is the same. It has countless contributors, it stays invisible in the moment, and the only way to understand it is to measure what it does to the work around it.

Here is the useful part of the analogy. A black hole grows because there is no shortage of fuel for it to consume. But if you remove the fuel source, it shrinks. That is exactly the work in a revenue cycle: find the drivers of complexity, and remove them. When complexity is high, billing time demand is high, and it becomes very hard for any staffing model to keep up. Reduce the fuel, and the whole thing gets smaller and more manageable.

Complexity, not volume, drives billing time demand

Most people assume the time it takes to do your billing is driven mainly by volume, how many claims you have. It is not. I can prove with data that we have clients one-tenth the size of another client whose billing takes more time than the client ten times larger. Volume is a factor. Complexity is the driver.

Billing time demand is the combination of volume and the complexity inside that volume. And in most practices, volume changes slowly while complexity varies enormously. That is why complexity, not volume, determines how much billing time you actually need. Where it gets dangerous is high complexity inside high volume, where time demand climbs exponentially.

The biller is affected by everything, so the biller can measure everything

Billing is the only revenue cycle function that is affected by every other function. Credentialing, authorization management, patient registration, verification of benefits, documentation, coding, your systems, your payers: all of it lands on the billing process, usually by inflating the time it takes. An authorization that should have been obtained turns what should be a one-minute step into a three or four hour problem.

That is also the opportunity. Because the biller is affected by everything, the biller is positioned to explain everything. The problem is that billers rarely get the chance, and complexity often gets treated as job security rather than a problem to solve. So we built a data platform, Practice Data Solutions, that lets the billing team convert their daily experience into data. A time inflator takes about four to five seconds to log: process issue, authorization not obtained, affected ten claims, save. Over a day those few-second captures build a precise map of where complexity comes from and what it costs in time. If you can measure it, you can reduce it. If you cannot, you never will.

Fixed time supply is why most revenue cycles stay broken

Billing time supply is the time you actually have to do the work. If billing time demand is a variable, and it is, then billing time supply has to be a variable too. Only then can the outcome be a constant, which is what everyone actually wants: all the money, as fast as possible, as cost-effectively as possible.

Almost the entire industry runs the opposite way, on fixed time supply. One biller working eight hours a day is a fixed supply. A hundred FTEs is still a fixed supply. And an outsourced company that charges a fixed percentage of revenue is a fixed supply too; they convert that fee into a labor budget and a set number of people, and they will not spend more time than the budget allows. When complexity rises, a fixed supply cannot flex to meet it, so the outcome breaks. We work in variable time supply models, engineered to match the demand that complexity actually creates.

The one number that tells you it is out of balance: your ADO Score

Days in AR, or average days outstanding, is an important number, but on its own it is close to meaningless, because what counts as good depends entirely on your payer mix. A practice that is 100% Medicare, which pays in about 18 days, should have an ADO around 18. A practice full of slow payers should not.

So we compare your actual ADO to what your ADO should be based on your payer mix, which we call your Target ADO, and the ratio is your ADO Score. If your actual ADO is 18 and your Target is 18, your ADO Score is 100%, which is where you want it. If your actual is 36 against a Target of 18, your ADO Score is 200%, which means your revenue cycle is severely broken. And I can tell you with certainty that a 200% ADO Score means your billing time supply is far below your billing time demand. The ADO Score is the judge and jury of how the whole thing is working, which is why the Target has to be set correctly. Set the Target too high and a slow revenue cycle can look fine when it is not.

How much complexity is too much

We normalize complexity to a standard volume so we can compare any practice to any other, a metric we call objective risk per 100 visits per month. Because it is per 100, it reads like a percentage: 20 objective risks per 100 visits means roughly 20% of your claims needed someone to fix something.

Our target for every practice is under five. Under five supports an efficient billing operation and strong outcomes. You can keep the wheels on up to about 15. Past 15 the time-per-visit curve deflects sharply upward, and past 25 it goes nearly vertical. I have clients running at 60. Not all complexity is equal, either. The most severe are revenue reducers, where the money is simply lost, like exceeding a patient's benefit limits and treating for free. Next are AR inflators, which stall your cash. Least severe are time inflators, which only cost you time, though time is finite and never free.

What high complexity actually costs you in time

We ran the numbers on a low-complexity group averaging three objective risks per 100 visits against a high-complexity group averaging 60 per 100. The difference is not small, and it is mathematically certain across millions of claims.

Total billing time per visit in the high-complexity group was 665% higher. That means it takes 6.65 people to do the work one person does in the low-complexity group. Narrow it to accounts receivable management, the function complexity hits hardest, and the high-complexity group needs 20 times the time, a 2,000% increase. Narrow it further to denial management, the most specialized and expensive work of all, and it is a 4,060% increase, or 40 times the people. No practice can staff against a variable that swings its time by 40 times. The only real answer is to reduce the complexity.

This is also why moving billing offshore to cheaper labor is not a solution. It lowers the cost of the bodies, but it does not remove a single unit of complexity. You have solved a labor-cost problem and left the actual problem in place. I do not want to be in the business of throwing more people at complexity. I want to be in the complexity reduction business, where one person does the work of one person.

Where the complexity comes from: 71 / 10 / 13 / 6

After years of converting billing experience into data across millions of claims and more than 270 quantified sources of complexity, here is where revenue cycle complexity originates:

  • 71% comes from functions internal to the practice but external to billing: credentialing, authorization management, patient registration, verification of benefits, provider documentation, coding, and modifier usage. Patient registration accuracy is the single largest internal source.
  • 10% comes from payers, a share that has grown as some plans process claims less cleanly than others.
  • 13% comes from the systems themselves: the EMR, practice management software, and clearinghouse.
  • 6% is created inside the billing process itself.
Where revenue cycle complexity originates A single bar divided into four parts: 71% inside the practice but external to billing, 10% payers, 13% systems, 6% billing. The first three together are 94%, external to billing. 94% is external to billing 71% 71% Inside the practice, external to billing 10% Payers 13% Systems: EMR, practice management, clearinghouse — most from improper setup 6% Inside the billing process itself
Where revenue cycle complexity originates. Source: Revenue Cycle Solutions.

That means 94% of all complexity is outside the biller's control, almost without exception. Yet when AR climbs and cash gets tight, it is the biller who gets blamed. Think of a billing team as a crew team: eight people rowing in sync, precision in every stroke. Revenue cycle complexity is the wind and the water. Put the greatest crew team in the world in a category four hurricane and ask them to match the time they would post on glass water, and it is impossible. If your AR is a mess and you are running at 60 objective risks per 100 visits, the problem is not your billers. Stand in front of the mirror.

Proof: two practices that reduced their complexity

Numbers make it real. Two quick examples, both driven by reducing complexity.

PT Plus, a physical therapy practice in New Mexico and a client of about three years, started at 16 objective risks per 100 visits in 2022 and finished 2025 at 3.63, a 77% reduction that moved them into our low-complexity target. Their revenue per visit rose from $103 to $136, a $32 increase that, because it costs nothing more to earn, is essentially all profit. Days in AR on the insurance side were cut roughly in half, from 30 to 14.8. That gain came from reducing complexity alongside CPT coding optimization. The fuller story is in the PT Plus case study.

A second practice, a nine-year client, started at 23.3 objective risks per 100 visits and reached 4.83, a 79% reduction, most of it front-loaded into the first three years. Revenue per visit rose from $75 to $105, a $30 increase, or 40%. Days in AR dropped from 63 to 21, a 66% reduction. Because our fee comes down as our efficiency rises, their billing-cost savings alone reached about $140,000 a year as they grew. And grow they did, by 372%, with profitability up 400%. Put a 372% increase in scale together with a 400% increase in margin, and the multiple a buyer would pay went from roughly 4x to 12x. Every dollar you create or save today is worth several times that when you sell. The full nine-year case study has the detail.

Reducing complexity is the whole job

Once you can measure complexity, the data becomes the KPIs for every revenue cycle function: patient registration, authorization management, verification of benefits, and the providers whose documentation supports coding. Everyone's role can then be defined in the same terms, by how much they reduce revenue cycle complexity, and the data connects the dots into true cross-functional teams that finally understand how they affect each other.

This is why you cannot grow your way out of a high-complexity revenue cycle. Scaling a high-complexity practice just adds fuel to the fire. A low-complexity revenue cycle is the scalable, profitable, valuable one: efficient billing, ADO Scores where they need to be, minimal time supply matched to low demand, revenue coming in fast and complete. As Henry Ford put it, if you always do what you always did, you will always get what you always got. The change that matters is quantifying the complexity and removing it at the root. Better data leads to better process, better process leads to better outcomes, and better outcomes lead to a better business.

Find out how big your black hole is

You cannot reduce what you have not measured, and most owners have never seen their revenue cycle complexity quantified. Every RCS relationship begins with a revenue cycle assessment that quantifies the complexity inside your practice and the opportunity to reduce it, shared with you at no cost and no risk.

Request Your Free Revenue Cycle Assessment

Listen to the full episode, "Revenue Cycle Complexity: The Root Cause of Poor RCM Outcomes," on the Rehabbing Your Revenue Cycle podcast: https://rehabbingyourrevenuecycle.com/episodes/revenue-cycle-complexity-the-root-cause-of-poor/.


Frequently asked questions

What is revenue cycle complexity?

Revenue cycle complexity (RCC) is the accumulation of errors, omissions, and structural issues across a practice that put its revenue cycle objectives at risk and inflate the time it takes to bill and collect. It is invisible in the moment, like a black hole, and can only be understood by measuring its impact on the work around it. RCS has quantified more than 270 distinct sources of it.

Why does complexity, not volume, drive billing time?

Because volume changes slowly in most practices while complexity varies enormously. A one-minute billing step can become a three or four hour problem when something upstream, like a missing authorization, was never handled. Comparing a low-complexity group (three objective risks per 100 visits) to a high-complexity group (60 per 100), total billing time per visit was 665% higher, AR time was 2,000% higher, and denial management time was 4,060% higher.

What is an ADO Score?

ADO stands for average days outstanding in accounts receivable. On its own it is nearly meaningless because "good" depends on your payer mix. The ADO Score compares your actual ADO to your Target ADO, the days you should take given your payer mix. A score of 100% is the goal; 200% means your billing time supply is far below your billing time demand and your revenue cycle is severely broken.

Where does revenue cycle complexity come from?

71% originates inside the practice but external to billing (credentialing, authorization, patient registration, verification of benefits, documentation, coding), 10% comes from payers, 13% from systems, and 6% from billing itself. That means 94% of it is outside the biller's control, which is why blaming the billing team almost never fixes the problem.

How do you reduce revenue cycle complexity?

Measure it first, by converting the billing team's daily experience into data, then reduce it at the root through collaboration across every function. Reducing complexity lowers billing time demand, which improves efficiency, cash flow, and cost, and makes the practice scalable. You cannot grow your way out of high complexity; you have to remove the fuel.

← All articles