Cost per Claim at an RCM Outsourcer: How to Calculate It and What Drives It
Cost per claim is your fully loaded operating cost divided by claims worked to resolution. Here is how to build the number and break it down by workflow, channel, client and payer.
Updated November 5, 2026, based on CAQH and X12 as of that date.
Cost per claim at a billing company is your fully loaded operating cost for a period divided by the number of claims your team worked to resolution in that period. Most of that cost is people time, so the number moves with how many times someone touches each claim and which channel they use for each touch.
A claim that is submitted cleanly, accepted and paid on the first pass costs very little. A claim that needs an eligibility re-check, two portal lookups, a phone call and a corrected resubmission costs several times as much, even though both count as one claim. If you want to lower cost per claim, the useful view is touches per claim and cost per touch, broken out by workflow, client and payer.
The formula: what goes in the numerator and the denominator
The numerator is everything it costs to run the operation for the period:
- Wages, benefits and payroll taxes for everyone who works claims, including onshore and offshore staff and contractors.
- Supervisors, QA, trainers and the share of management time spent on production.
- Software: practice management and billing systems, clearinghouse fees, telephony, and any automation tools.
- Overhead you can reasonably allocate: facilities, IT support, and compliance work.
The denominator is the trickier choice. Count claims resolved in the period, meaning paid, denied with no further action, or closed by a decision, rather than claims submitted. A firm that counts submissions credits itself for work it hasn't finished. The follow-up, appeals and resubmissions that come later still land in the numerator, so a submissions-based number looks better than it is and gets worse each month a backlog builds.
Pick one definition of "resolved" and use it for every client, or client-to-client comparisons won't hold.
Break it down by workflow, because each touch type has its own cost
A single firm-wide number tells you whether things got better or worse. It doesn't tell you why. For that, split the work into the touch types your team actually performs, for example:
- Eligibility and benefits verification
- Claim submission and edits
- Claim status follow-up
- Denial review and appeals
- Payment posting and remittance reconciliation
- Patient balance work
These map closely to the administrative transactions the CAQH Index tracks, from eligibility and benefit verification through claim status inquiry and remittance advice.
For each workflow, estimate two things: how many touches it generates per claim, and what one touch costs. Time studies, ticket or work-queue logs, and call records are the usual sources. Cost per touch is minutes per touch multiplied by the loaded cost per minute of the person doing it. Multiply touches by cost per touch, sum across workflows, and you should land close to your total cost per claim. If you don't, some work isn't being captured, and finding it is part of the exercise.
Manual and electronic transactions cost different amounts
The channel matters as much as the count. The same claim status check can be an electronic 276/277 inquiry through a clearinghouse, a portal lookup, or a phone call that waits on hold, and each takes a different amount of staff time.
One public reference for that gap is the 2025 CAQH Index Executive Report. The Index collects data from health plans and providers on how administrative transactions are completed and what they cost. For medical providers, the 2025 Index reports an average cost of $8.03 per manual transaction and $2.65 per electronic transaction. The 2024 Index had $7.93 and $3.39, and the 2023 Index had $7.19 and $3.45.
Read those figures with care. They are industry averages across all the transaction types the Index covers, measured on the provider side, not at billing companies. They aren't a cost per claim, and your own costs per transaction will differ by workflow, payer and labor market. What they do show is direction: in the 2025 Index the average manual transaction cost about three times the electronic one, and the gap widened from the 2023 Index to the 2025 Index.
For your own model, the practical step is to tag every touch by channel (electronic, portal, phone, fax or mail) and price each channel separately. That tells you which workflows are expensive because of volume and which are expensive because of the channel they run through.
Rework drives the number: denials, re-checks and repeat calls
Rework is where touches multiply. Every denial adds at least one review touch, often a correction or appeal, and then a new round of status follow-up. The X12 Claim Adjustment Reason Codes on the 835 describe why a claim or service line was paid differently than it was billed, and grouping your denials by those codes shows which causes are generating the most repeat work.
Other common sources of rework:
- Eligibility checked at scheduling but not re-checked before the claim went out, so coverage changes turn into denials.
- Status checks repeated on the same claim because the last result wasn't recorded where the next person would see it.
- Calls to the payer that end without an answer and have to be made again.
- Claims touched by two people because work queues overlap.
Track rework touches separately from first-pass touches. A rising rework share is an early warning that cost per claim is about to climb, often before the monthly total shows it. The guides on denial management automation and claims follow-up automation go deeper on those two workflows.
Compare clients and payers, not just the firm-wide total
Once you have cost per claim by workflow, cut it by client and by payer. Two clients with the same claim volume can cost very different amounts to serve. One may send clean demographics and have mostly electronic payers. Another may have high denial rates, payers that only answer by phone, or a specialty with frequent prior authorizations.
A per-client view tells you which contracts are priced correctly, which SLAs are at risk, and where a conversation about front-end data quality would pay off. A per-payer view tells you where a channel change would save the most, for example payers where your team still calls for status even though the payer supports electronic inquiry or a portal. Aged AR is worth its own cut, since old claims tend to need the most touches; the guide on AR recovery automation covers that work.
Frequently asked questions
Should offshore staff be costed separately?
Yes. Use each team's own loaded cost per hour, including management, QA and any vendor fees, rather than a blended rate. A blended rate hides where the cost sits, and offshore teams may handle different workflows with different touch counts.
Does software cost count?
Yes. Billing systems, clearinghouse fees, telephony and automation tools belong in the numerator. Leaving them out makes manual work look cheaper than it is compared with tools that replace it.
What's a good cost per claim?
We didn't find a sourced public benchmark for cost per claim at billing companies, and figures vary with specialty, payer mix and how "claim" and "resolved" are defined. The useful baseline is your own: measure three to six months with fixed definitions, then track the trend by workflow, client and payer. Judge changes against that baseline rather than against a number from outside your operation.
Working out which touches drive your cost per claim?
Champ automates portal and phone work, such as eligibility checks on payer portals. We set it up and run it, so your team sees only the finished results. If you're deciding which touches to take off your team's plate, learn more here.
This post is general information, not legal, compliance or billing advice. Rules vary by payer and change often, so confirm with your payers and your own compliance and finance advisers before acting. Champ is not affiliated with or endorsed by CAQH or X12.
Continue reading
See all
Prior Authorization Turnaround Times: What CMS Requires Payers to Meet
Under CMS-0057-F, most Medicare Advantage and Medicaid plans must decide prior authorizations within 7 days, or 72 hours when urgent. This guide covers who the rule applies to, when payers can extend, and how to keep requests moving.

Can You Share a Payer Portal Login? MFA, User Accounts and Credential Rotation
Payer portals like Availity and UnitedHealthcare require a separate login for every user. Here's how to handle administrators, billing vendors, MFA and password changes.

Payers Without an API: How RCM Software Gets Eligibility, Claim Status, and Prior Auth Answers
HIPAA standardizes the format of eligibility, claim status and prior auth transactions, not how much detail comes back. Here is what X12, CMS-0057-F APIs, portals and phone each return, and how to set a fallback order per payer.