Skip to main content
← Back to Insights
Margin intelligence

The Question Your Finance Office Cannot Answer

For a given payer, service line and site of care: what you billed, what you actually collected, what it cost, and how your rate compares. Every element exists in your systems. Nothing assembles them.

Emphanex Insights · Published June 24, 2026

Ask a healthcare finance team a familiar question — “What did we collect from Payer A last quarter?” — and the answer is usually available. Ask what the practice billed, and the billing system can answer that too. Ask what the practice spent, and the general ledger has an answer at some level.

Now make the question decision-grade:

For this payer, for this service line, at this site of care: what did we bill, what did we actually collect, what did the care cost us to deliver, and is our contracted rate above or below the market?

That answer is much harder. Not because the data does not exist. Because the pieces were created for different jobs, live at different levels of detail and rarely share a common financial model.

The billing system knows the transaction. The remit knows the adjudication. The contract knows the expected economics. Accounting knows the expense. Public rate data can increasingly show the market. None of those views, by itself, tells leadership whether a payer-service-line-site combination is actually creating margin.

Charges are not price

The first trap is the easiest one to recognize and the hardest one to eliminate from executive reporting: billed charges are not the same thing as economic value. A charge is what the practice submitted. It does not tell you what the payer was contractually expected to allow, what the payer actually allowed, or what the practice ultimately retained after adjustments and patient responsibility.

That distinction matters because two payers can receive the same charge for the same service and produce materially different reimbursement. A gross collection percentage built on charges can therefore tell leadership more about the practice's fee schedule than about the economics of its payer contracts.

The 835 tells you what happened — not whether the relationship is profitable

CMS describes the electronic remittance advice as the record of final claim adjudication and payment information, including line-level payment and adjustment detail. That makes the 835 indispensable for understanding what a payer did to a claim. But the remit still answers a transaction question. It does not contain the practice's labor cost, supplies, occupancy, equipment burden, administrative cost to collect or the commercial context needed to judge whether the payment was economically attractive.

A payer can pay every claim exactly according to contract and still be a poor economic relationship for a particular service line. That is why payment accuracy and payer profitability are related questions, but they are not the same question.

The contract tells you expected reimbursement. It still does not tell you margin.

A contract model closes the gap between charge and payment by establishing what should have been allowed under the correct fee schedule, product, provider status, modifier rules, effective date and other applicable terms. MGMA explicitly identifies payer contracts as a major driver of medical-practice profitability and recommends analyzing reimbursement rates, denial patterns, contract language and administrative burden together rather than treating rate negotiation as an isolated exercise.

But even a perfectly modeled contract answers only one part of the question. A $300 allowed amount may be attractive for one service and inadequate for another. The difference is cost.

Cost usually lives at the wrong level of detail

Practice expenses are usually visible in aggregate: payroll, benefits, rent, supplies, software, equipment, malpractice, billing expense and other operating costs. That is enough to produce a practice-level P&L. It is not automatically enough to answer what one service line costs at one site of care.

The useful model does not pretend that every overhead dollar can be assigned with scientific precision. It starts with what can be defended: direct clinical labor, direct supplies, identifiable technology or equipment costs, location-specific expense and other costs that clearly move with the service. Shared overhead can then be allocated separately and transparently rather than blended into a single number that looks precise but cannot be explained.

That matters in 2026 because cost pressure is not theoretical. In a February 2026 MGMA poll, 80% of responding medical groups reported that Medicare reimbursement was below their cost to deliver care. The strategic problem is not merely whether rates increased. It is whether reimbursement, by service and setting, covers the cost structure the practice actually carries.

Site of care can change the economics even when the clinical work looks similar

A payer-service analysis that ignores site of care can hide material differences. Medicare's physician fee schedule, for example, applies different facility and nonfacility payment rates to many services, with the place-of-service code helping determine which rate applies. Commercial contracts can layer their own site-specific terms on top of different operating costs. The same service line delivered in an office, hospital outpatient setting or other location can therefore produce a different revenue-and-cost profile.

That is why “Payer A pays us well” is not a complete statement. The useful version is more specific: Payer A pays this service line at this site at a rate that produces this contribution after the costs required to deliver and collect it.

For the first time, market-rate comparison is increasingly possible — but raw transparency data is not an answer by itself

Under the federal Transparency in Coverage rules, most group health plans and issuers publish machine-readable files containing in-network negotiated rates for covered items and services. That creates something provider finance teams historically lacked: a public source of negotiated-rate information that can support external comparison.

It is powerful data, but it is not simple data. CMS notes that specialized technology may be needed to process the files because of their size and complexity. In its 2025 proposed update to the rules, CMS also identified ambiguity, very large file sizes and improbable provider-rate combinations as barriers to making the information more useful. In other words, public rates make market comparison possible; they do not eliminate the need for normalization, clinical relevance and judgment.

The four questions — and where the answers usually live
What did we bill?
Claim and practice-management data: code, units, modifier, payer, provider, site, charge and date of service.
What did we actually collect?
835/remittance and cash data: allowed amount, payer payment, patient responsibility, adjustments, recoupments and final realization.
What did it cost?
General ledger, payroll and operational data: direct labor, supplies, site-specific expense, technology/equipment and clearly identified allocations.
How does our rate compare?
Executed contracts and amendments, Medicare or other selected benchmarks, and appropriately normalized Transparency in Coverage negotiated-rate data.
The unit of analysis is the part most dashboards get wrong

A practice-wide margin can look acceptable while one payer is underwater for one service line. A payer-wide average can look acceptable while the hospital-based portion of the contract performs poorly. A service-line average can look acceptable while one product or location is carrying the rest.

That is why the useful grain is not “total revenue” and not even simply “payer.” It is the intersection of payer × plan/product × service line or procedure family × provider/site of care × time period, with enough claim-line detail underneath it to explain the result.

At that grain, leadership can finally distinguish four very different problems:

1. A payment problem: the payer is not paying the contract correctly.
2. A contract problem: the payer is paying correctly, but the negotiated rate is too low.
3. A cost problem: reimbursement may be reasonable, but the service is too expensive to deliver in its current operating model.
4. A site-of-care or mix problem: the economics vary enough by location, product, provider or service mix that the average is hiding the actionable issue.
A simple illustration shows why the distinction matters

Assume two commercial payers cover the same service family at the same office site. Both receive the same charge. Payer A's realized reimbursement averages $335 per service; Payer B's averages $290. Direct and attributable delivery cost averages $225.

Measure Payer A Payer B
Submitted charge$600$600
Realized reimbursement$335$290
Direct + attributable cost$225$225
Contribution before shared overhead$110$65

Illustrative example only; not a benchmark or representation of any payer's actual rates.

If the dashboard stops at charges, both payers look identical. If it stops at collections, Payer A looks better. If it adds cost, leadership can quantify the difference in contribution. If it then adds market-rate comparison and administrative cost to serve, the practice can decide whether the right action is payment recovery, renegotiation, workflow redesign, site-of-care change or no action at all.

What a finance-ready model should produce

The goal is not another dashboard with more measures. It is a small number of defensible outputs that can survive questions from finance, operations and physicians.

The decision set
Realized reimbursement per unit or encounter — what the organization actually collected for the defined service.
Expected-versus-actual payment variance — whether the contract was paid correctly.
Contribution before shared overhead — realized reimbursement less direct and defensibly attributable delivery cost.
Rate position — how the contracted/realized rate compares with a defined benchmark or relevant market set.
Cost to serve the payer — where measurable, the administrative friction created by denials, appeals, records requests, aged A/R and other payer-specific work.
Volume and mix — because a strong unit margin on low volume and a weak unit margin on high volume create very different enterprise consequences.

HFMA has long argued that accurate costing improves the ability to analyze contract underpayment, physician and service-line profitability and the financial outcomes of different care alternatives. That is the larger point: the missing answer is not a revenue-cycle metric. It is the intersection of revenue-cycle, contracting, operational and financial data.

The question is answerable. It just was never designed as one question.

Healthcare organizations did not build their billing systems, accounting systems, payer contracts and transparency datasets to function as one margin model. Each system can be accurate for its own purpose while the organization still lacks a defensible answer to the question leadership actually needs answered.

That is why “we collected $8 million from this payer” is not enough. It does not tell you whether the payer paid correctly. It does not tell you which services created the revenue. It does not tell you what those services cost. It does not tell you whether another payer pays materially more for the same work. And it does not tell you whether one site is subsidizing another.

The finance question worth answering is not “How much revenue did we receive?” It is “Where, exactly, did we create margin — and where did we not?”

Emphanex assembles the evidence at that level: claim, remit, contract, cost and external rate context. Not to produce a prettier dashboard, but to make the payer, service-line and site decisions that follow defensible.

See what the Data Diagnostic measures →
Sources
Centers for Medicare & Medicaid Services, “Health Care Payment and Remittance Advice.”
Centers for Medicare & Medicaid Services, “Transparency in Coverage Final Rule Fact Sheet (CMS-9915-F).”
Centers for Medicare & Medicaid Services, “Use of Pricing Information Published under the Transparency in Coverage Final Rule.”
Centers for Medicare & Medicaid Services, “Transparency in Coverage Proposed Rule (CMS-9882-P).”
Centers for Medicare & Medicaid Services, Medicare Claims Processing Manual, Chapter 12, §20.4.2, “Site of Service Payment Differential.”
Medical Group Management Association, “Analyzing Payer Contracts Playbook,” May 8, 2025.
Medical Group Management Association, “Regular auditing of payer payments crucial to ensure accurate reimbursement,” February 12, 2025.
Medical Group Management Association, “2026 Medicare reimbursement changes: Tracking what matters,” February 26, 2026.
Healthcare Financial Management Association, “An HFMA Value Project Report: Business Intelligence,” on costing, profitability and contract-underpayment analysis.

This article is for general informational purposes only and does not constitute financial, legal, coding, reimbursement or compliance advice. Cost attribution, contract interpretation, rate benchmarking and profitability conclusions depend on the organization's accounting methods, payer agreements, service mix, site-of-care structure, provider status and underlying data quality.