BRSi and the art of getting paid

In March 2026, Pennsylvania’s Department of Human Services had a message for medical providers: some claims Medicaid had already paid belonged with Medicare. The patients had overlapping coverage. The department had not known about it when the care was delivered. BRSi was helping untangle the payments.

There is an entire business inside that administrative loose end. Care happens once. The question of who pays can keep moving long afterward. Houston-based BRSi, also known as Benefit Recovery, works in that gap, combining billing specialists with software built to follow a claim through its complications.

A payment can be wrong twice

The Pennsylvania project makes the distinction unusually clear. Its notice concerned people with both Medicare and Medical Assistance coverage. The department described eligibility data exchanges that can identify coverage after a claim has been paid. BRSi’s assignment involved recovering public money from claims for which another payer should have come first.

That is a different job from simply collecting an unpaid hospital bill. For a provider, the task may be getting reimbursement. For a public program, it may be recovering a payment made against the wrong coverage. BRSi sells services across both settings. The shared skill is understanding responsibility before pursuing the money.

Its provider offering includes insurance discovery, eligibility checks, claims submission, patient billing, denial resolution, and underpayment analysis. Its government work adds third-party investigations, payer coordination, auditing support, and financial reporting. The company occupies the operational territory where healthcare, insurance, and accounting meet.

Four people. A very particular problem.

Founder Tony Stegman started Benefit Recovery in 1992. The company’s current history puts the original team at four people. Its early proposition has proved durable: help healthcare organizations receive appropriate reimbursement. The instruments have expanded to include proprietary software, analytics, automation, and consulting.

BRSi says it is trusted by more than 200 hospitals and health systems. Its website displays names including Memorial Hermann, Children’s National Hospital, Beloit Health System, Mary Rutan Health, TennCare, and the Defense Health Agency. Its market also includes provider groups, managed care organizations, Medicaid agencies, and tribal healthcare organizations. These customers have different missions, but all need financial operations that can handle exceptions.

The interesting part of this history is continuity. Billing rules change; someone still has to investigate the account. BRSi’s stated values spell CARE: Collaboration, Agility, Resilience, Ethics. In this business, agility has a practical meaning: can a workflow change when a payer’s requirements do?

“You have to know the questions to ask.”Natalie Van Baale, in BRSi’s Outcomes Rocket interview recap, July 2025

The company describes a consultative approach to reporting, too. During onboarding, it says it works with the client to choose performance indicators and develop reports around existing processes. That is a useful idea to copy: decide what improvement means before the work starts. A team trying to clear an old backlog may need different measures from a public program checking whether another insurer should have paid.

The software has a long name for a reason

ARMS PRO stands for Accounts Receivable Management System Provider Reimbursement Optimization. It sounds like a filing cabinet trying to introduce itself. Its functions are more revealing than its name: configurable business rules, claim edits, rate tables, reimbursement methods, invoicing, ledger transactions, and denial workflows.

The platform is modular and web-based. BRSi offers licensing or SaaS contracts, with modules spanning commercial claims, other health insurance discovery, Medicaid eligibility, cost avoidance, estate recovery, and a provider portal. Customers can select capabilities around the program they operate rather than treating every account as the same problem.

BRSi also says its revenue cycle staff perform work inside a client’s electronic health record system, preserving the system of record and audit trail. That detail explains its positioning better than a dashboard does. The offer combines software with people who work the accounts. Alternatives include internal billing departments, outsourced recovery firms, and standalone revenue cycle tools.

Read the collections column

One company-published hospital example reports $16 million collected from denied claims averaging 296 days old, with a 36% recovery rate. Those are BRSi’s reported project results, rather than a forecast for another hospital. Still, they describe the kind of backlog the company is prepared to work.

Another example deserves careful reading. BRSi reports receivables falling from $110 million to $62 million, alongside $44.7 million identified for write-off and $3.2 million in cash collections. A falling balance and cash arriving are different events. A buyer should track them separately, then compare collections with fees and implementation effort.

That distinction is a useful purchasing discipline. Define which accounts the partner will handle, what counts as recovery, and how results reach the ledger. The commercial structure includes services and modular software contracts. The sensible buying unit is a defined assignment with measurable results.

Catch the mismatch earlier

In July 2025, BRSi announced Aamir Syed as president, with responsibilities across products, growth, and customer success. His background spans patient access, documentation, billing, and denial management. That breadth matters when the cause of a payment problem sits several steps before the unpaid claim.

In March 2026, BRSi and Milagro announced a collaboration combining revenue cycle expertise with surgical coding automation and authorization-mismatch detection. The aim is to catch discrepancies between an authorized procedure and the procedure performed before they become denials. It extends BRSi’s work from pursuing payment toward preventing avoidable rework.

The transferable lesson is straightforward: study the exception before automating the queue. Was coverage missed? Did authorization match? Was the claim underpaid? Automation built on the wrong answer can repeat the mistake faster. Recovery also depends on documentation, access to accurate records, and filing deadlines. Software cannot make every old claim collectible.

BRSi’s business rests on asking those questions repeatedly. Behind a reimbursement delay may be a missing policy, a mismatched code, or a perfectly valid payment request sent to the wrong place. Finding the difference is the work.