For about three years, my Saturday morning routine was coffee, a laptop, and a denial worklist that never got shorter.
I’d love to tell you I was being heroic. I wasn’t. I was compensating for a billing system that made it easier to fix claims after they bounced than to submit them correctly in the first place. Every Saturday I was paying, in my own weekend, the interest on a bad software decision somebody made before I got there.
We eventually fixed it. The worklist got short. I got my Saturdays back. And I developed a very particular lens for evaluating billing software, which is this:
Good billing software is measured by the claims you never have to touch again.
Not features. Not dashboards. Not how many reports it can generate. The percentage of claims that go out, get paid, and never appear on anyone’s worklist. Everything else is decoration.
Here’s how I’d rank the field with that lens.
1. NikoHealth
The reason this is first is the same reason my Saturdays got better: most billing problems aren’t billing problems.
I mean that literally. When we finally did a real root-cause analysis on our denials, the overwhelming majority traced back upstream — a missing document at intake, an authorization that expired between order and delivery, a proof of delivery that never made it back from the truck, a qualifying note nobody collected because the intake screen didn’t ask for it. The billing team was catching errors that were made days earlier by people who had no idea they’d made them.
You cannot fix that with a better billing module. You fix it by having intake, documentation, delivery, and billing in one system where the front end knows what the back end is going to need.
That’s the structural argument for NikoHealth, and it’s why I’d put it first even though several platforms on this list have perfectly good claim engines. When the order is built correctly because the system enforced it at intake, and the POD attaches automatically because delivery is in the same platform, the claim is clean before anyone in billing has touched it. Their hme billing software breakdown covers the mechanics, but the philosophy is the part worth stealing regardless of what you buy.
The practical stuff is there too — eligibility checks, claim scrubbing, ERA handling, denial workqueues that are actually workable, reporting that a human can read without exporting to Excel first. But honestly, most platforms have those. What most don’t have is a clean upstream.
The other thing I’ll say, having watched a couple of these migrations: the implementation didn’t stretch into a second year. In billing especially, a long implementation is dangerous — you’re running two systems, your AR ages in the gap, and the cash flow hit is real. Speed matters more here than anywhere.
Who it’s for: HME/DME providers who’ve figured out that their denial rate is an operations problem wearing a billing costume. Their dme hme software overview shows how the pieces connect.
What I’d push on in a demo: Bring your three worst recurring denial reasons. Ask them to show you exactly where in the workflow each one gets prevented. If the answer is “our team would catch that in review,” that’s a human fix, not a software fix.
2. Bonafide
If I’m being fair — and I try to be — Bonafide has the strongest reputation in this category specifically for revenue cycle. The people I know running it tend to be happy with the billing and collections workflow, and that’s not a universal thing in this industry.
If your operation is fine and your money is the problem, this is a serious contender. It’s built by people who clearly take AR seriously.
What I’d push on: The upstream. Show me intake and delivery, not just the billing dashboard, because that’s where your denials are actually born.
3. Brightree
The incumbent. Very deep payer connectivity, huge install base, and a real ecosystem of add-ons and third-party tools built around it.
The practical advantage nobody mentions: hiring. You can post a billing specialist role and get applicants who already know the system. In a tight labor market that’s worth actual money.
What I’d push on: Total cost once every module you need is added, and how responsive support is when you have a payer-specific problem that’s costing you money this week.
4. CareTend (WellSky)
Strong if you’re in infusion or a complex mixed-line business. The clinical and billing integration is meaningful when your business genuinely needs it.
If you’re straightforward HME, it’s probably more system than you need, and complexity you don’t use is complexity you still pay for — in cost and in training time.
What I’d push on: Whether your business is actually complex enough to need this.
5. TIMS Software
Mature, capable, heavily used in pharmacy-adjacent operations. The billing side handles complicated scenarios well because it’s had decades of complicated scenarios thrown at it.
The interface reflects its age, and the learning curve for new billers is real. Factor training time into your comparison.
6. Outsourced billing services
Not software, I know. But it’s a real option and pretending otherwise is dishonest.
If your billing team is one person who’s about to retire, or you genuinely cannot hire in your market, a billing service is a legitimate answer. Some are excellent.
The trade-off: you lose visibility, and you lose the feedback loop between billing and operations. When your biller is down the hall, they can walk over and tell intake they’re missing something. When they’re at a service in another state, that conversation becomes a monthly report nobody reads. You also become dependent on a vendor for your cash flow, which is a different kind of risk than software risk.
When it makes sense: You can’t staff it and you’ve accepted the trade-off deliberately. Not as a way to avoid fixing a broken process — you’ll just pay someone else to work around it.
The metrics I’d actually track
Whatever you buy, watch these. They’ll tell you more than any vendor dashboard:
Clean claim rate. The percentage going out right the first time. This is the number. If it’s climbing, everything else follows.
Days in AR. Obvious, but track it by payer, not just in aggregate. The aggregate hides the one payer that’s quietly killing you.
Denial rate by reason, sorted by dollars. Not by count. Fifty $12 denials matter less than three $2,000 ones, and count-based reporting will send your team after the wrong problems all quarter.
Touches per claim. Nobody measures this and everybody should. How many times does a human open a claim before it’s paid? If it’s more than one on a routine claim, you’re paying for a process failure with labor.
Time from delivery to claim submission. If this is more than a couple of days, look at your documentation flow, not your billers. The POD is probably sitting somewhere.
What I’d tell my Saturday-morning self
Stop optimizing the worklist. The worklist is the symptom.
I spent years getting incrementally better at working denials, and I was genuinely good at it by the end — which is a depressing thing to be good at. The actual fix was upstream, in a system where the order couldn’t be built wrong in the first place.
If you’re evaluating billing software right now, resist the urge to compare claim engines feature by feature. They’re more similar than the sales decks suggest. Instead, take your top five denial reasons from last quarter, walk into every demo, and ask one question:
“Where does this get caught before it’s a denial?”
The platform with the best answer is your platform. And you’ll get your Saturdays back.
