Somewhere between the day a patient needs a CPAP and the day that money lands in your account, a lot has to go right.
The revenue cycle is the name for everything in between.
It's the whole path a charge travels: the first phone call, the eligibility check, the authorization, the documentation, the coded claim, the payer's decision, the appeal if it comes to that, and the cash that finally posts.
When it runs well, it's invisible.
When it doesn’t it shows up as denials, as aging accounts receivable, and as a harried team that spends its days chasing paper instead of serving patients.
For a DME operating on razor-thin margins, that path is the business. This is a map of it, stage by stage, so you can see where money and time leak and why.
What Does "Revenue Cycle" Actually Cover in a DME?
Revenue cycle management is often treated like a billing-department problem.
It isn't.
It starts the moment a referral comes in and doesn't end until the balance is zero.
Different DMEs may use different names for different things, but generally the cycle runs through six stages:
- Intake and eligibility
- Prior authorization
- Documentation and coding
- Claim submission
- Denials and appeals
- A/R and collections
Each stage hands off to the next. Any gap early in the cycle travels downstream and shows up as a denial or a delay weeks later, far from where it originally started.
That's the single most important thing to understand about revenue cycle work: the place where cash gets stuck is usually not the place where the problem was created.
Let's walk the stages.
Stage 1: Intake & Eligibility
This is where the cycle either starts clean or starts broken.
At intake you're gathering the patient's information, confirming their insurance is active, and checking what that plan actually covers for the item they need. It sounds routine. It's also where a huge share of downstream denials are born.
An eligibility check that gets skipped or done sloppily means you might deliver equipment to a patient whose coverage lapsed, or bill a plan that never covered the item in the first place. You won't find out at intake. You'll find out sixty days later when the claim comes back denied and the equipment is already in the patient's home.
The fix is front-loading the work. Confirm active coverage, benefits, and any plan-specific requirements while the patient is still in front of you and the order is fresh. Capturing complete, accurate information at this stage is the cheapest insurance you can buy against denials later.
For more on getting the front end right, see our piece on digital intake for DME.
Stage 2: Prior Authorization
Once you know the patient is covered, many items still need the payer's permission before you deliver.
Prior authorization is the payer saying yes in advance. No auth, or a flawed one, and the claim is dead on arrival no matter how clean the rest of the paperwork is.
This stage stalls for predictable reasons. Payers each have their own rules and their own forms. Documentation to support medical necessity is incomplete. Timing windows get missed. Someone assumes an item is exempt when it isn't, or chases an authorization for one that is.
And every day an auth sits unresolved is a day a patient waits for equipment they need.
Because prior auth is repetitive, rules-based work, it's one of the stages where the right support makes the biggest difference. We cover what stalls it and how teams keep it moving in prior authorization in DME.
Stage 3: Documentation & Coding
This is the connective tissue of the whole cycle, and the place small errors do the most damage.
Every claim rests on a paper trail: the physician's order, the medical necessity documentation, the certificate of medical necessity where one applies, proof of delivery, signatures, and dates that all have to line up across every document and every system. On top of that sits the coding — the right HCPCS codes and modifiers that tell the payer exactly what you provided and why it was covered.
A clean claim and a denied one can look nearly identical at the moment of submission. The difference is whether the record behind the claim holds up.
Coding errors are their own category of leak. A wrong modifier, a mismatched code, a missing unit — any of these turns a valid service into a rejected claim. And because the same coding patterns repeat across thousands of claims, a single misunderstanding can quietly cost you for months before anyone traces it back.
The goal at this stage is a record so complete and so consistent that a payer review changes nothing about how fast you get paid.
Stage 4: Claim Submission & the First Pass
Now the claim goes out. What happens next is measured by one number that matters more than most DMEs track: the first-pass rate.
Your first-pass rate is the share of claims that get paid the first time they're submitted, with no rework. Every claim that clears on the first pass is cash that arrives fast and cheap. Every claim that doesn't has to be researched, corrected, and resubmitted — and that rework costs staff time you can't get back.
A low first-pass rate is expensive in a way that's easy to miss, because the cost is spread across dozens of small corrections rather than concentrated in one obvious failure. It doesn't feel like a crisis. It feels like a busy billing team. But a busy billing team fixing avoidable errors is a leak, not a workload.
The claims that fail the first pass become denials. That's the next stage.
Stage 5: Denials & Appeals
A denial is the payer refusing to pay, at least for now.
Some denials are appealable and worth appealing. Some are the result of a process problem you'll keep paying for until you fix the upstream cause. Telling those apart is where a lot of DMEs lose ground.
If you're reworking the same denial reason over and over — the same missing document, the same coding mismatch, the same eligibility miss — the denial isn't really the problem. It's a symptom of something that broke back at intake, authorization, or documentation. Appealing it recovers the one claim. Fixing the source recovers all the future ones.
This is the rework loop, and it's one of the most expensive habits in the revenue cycle. Every trip through it delays cash, ties up staff, and normalizes a workaround that should have been designed out. We break down why claims get denied and how to catch it before submission in clean claims the first time. (Placeholder link to current article. Can add a link to the new article later.)
Stage 6: A/R & Collections
Finally, the money you're owed but haven't collected yet. This is your accounts receivable, and how long it sits there is the clearest read on whether the whole cycle is healthy.
Aging A/R is money that's rightfully yours, stuck in a queue. The longer a balance sits unworked, the less likely you are to ever collect it in full. A/R that keeps climbing is a signal that something upstream is leaking — denials aren't being worked fast enough, follow-up is inconsistent, or the oldest balances are being ignored in favor of easier, newer ones.
The DMEs that stay healthy here manage by the number. They read their aging report, work the oldest buckets first, and track denial root causes so the same balances stop landing in A/R in the first place. We cover how to read the number and bring it down in A/R days in a DME.
What Metrics Are Worth Watching?
You can't manage a cycle this long by feel. Three numbers tell you most of what you need to know:
- Clean claim rate (first-pass rate): the share of claims paid on first submission. Higher means less rework and faster cash. This is your best single read on how well the front of the cycle is working.
- Days in A/R (DSO): how long, on average, it takes to collect what you're owed. Rising days-in-A/R is an early warning that cash is getting stuck somewhere upstream.
- Denial rate: the share of claims denied. Watched by reason code, it points you straight at which stage is leaking.
They are not hard to calculate but it's hard to act on them consistently.
Together they turn a cycle you mostly feel into one you can actually manage.
The Bottom Line
The revenue cycle shouldn't be six separate tasks handled by six separate people. It's one system, and it should be treated like one.
A shortcut at intake becomes a denial in billing. A coding habit becomes a month of lost cash. A slow authorization becomes a patient waiting and a claim aging.
The stages are connected, which means the leaks are connected too, along with the fixes. That's also where the opportunity is lurking.
Because the cycle is a system, small improvements grow on each other. A cleaner front end means fewer denials, which means less rework, which means faster cash and more room for your team to do the work that actually needs a person.
This is where automation earns its place as a way to make the cheap, repetitive checks happen automatically inside the workflow you already run, so complete claims become the default path instead of the goal.
When the record is right before the claim goes out, the whole cycle gets shorter, and a shorter revenue cycle affects far more than just cash.
Every claim that clears without a delay is a patient who gets their equipment on time.
That's what the revenue cycle is really for.
