Before the No Surprises Act, surprise out-of-network billing occurred in about
1 in 5 emergency-room visits, and federal estimates projected the statute would apply to roughly
10 million out-of-network surprise bills a year, according to
KFF's review of No Surprises Act implementation. Patient protection was the public result. It didn't set the provider's rate.
Federal Independent Dispute Resolution volume in the program's first year ran far above what the Departments had projected for a full calendar year. That volume is the revenue problem the law opened. A protected patient can still sit on a claim the payer denied or paid far below what the record supports.
Emergency medical billing services now have two jobs. They have to release a clean claim, and they have to keep the file usable if that claim ends up in negotiation or arbitration. The second job is decided upstream. Coding specificity, medical-necessity documentation, and the payment history captured at posting are what an arbitrator reviews months later, and none of it can be rebuilt convincingly after the fact. I would treat every out-of-network emergency encounter as a possible dispute from registration, not as a collections issue that starts after the remittance.
Why Emergency Billing Needs More Than Claim Submission
Sending claims faster isn't the same as getting paid correctly. In 2017, emergency departments recorded approximately
144.8 million visits, generating aggregate visit costs of
$76.3 billion and an average cost of
$530 per visit, according to the
Agency for Healthcare Research and Quality statistical brief. That benchmark is still the clearest national picture of how much money moves through emergency claims.
One encounter isn't one bill. It can produce a
facility claim, a
professional claim, and ancillary charges, each with its own payer, codes, and clock. The work on a single visit can include eligibility verification, emergency-service coding, medical-necessity documentation, payer-specific edits, coordination of benefits, and a patient-responsibility calculation.
Think of the claim as a multi-leg trip. Each leg has a different carrier, ticket rules, and baggage limits. Miss one connection and the rest of the journey stalls. At this volume, a modest denial or underpayment rate isn't a rounding error. It's large revenue leakage across public programs, commercial plans, and self-pay accounts.
The Emergency Billing Workflow From Registration to Posting
Value is created or lost at a specific handoff, not in a vague "billing process." The
2024 CAQH Index estimates that shifting remaining manual medical claims to electronic submission represented a
$2.5 billion industry-wide savings opportunity. Electronic status transactions also leave a machine-readable trail. That trail is what you need later if a payment is wrong.
Stage
What Happens
Output
Typical Owner
Eligibility and benefits check
Verify payer, plan, network status and authorization need at or before arrival
Verified coverage record
Registration
Charge capture and coding
Translate the encounter into CPT, HCPCS and ICD-10 codes, with level of service and modifiers
Coded professional and facility charges
Certified coders
Claim creation and scrubbing
Apply payer-specific edits and catch modifier, place-of-service and demographic errors
Clean claim
Billing team
Submission and acknowledgement
Transmit the claim and capture 999 and 277CA responses
Accepted claim with tracking reference
Billing team and clearinghouse
Adjudication and remittance
Payer adjudicates and returns an 835 remittance advice
Paid, denied or adjusted claim
Payer, with posting team review
Payment posting and reconciliation
Post payments and adjustments and reconcile to bank deposits
Accurate accounts receivable
Posting team
Patient balance and exception routing
Calculate patient responsibility and route denials and underpayments to queues
Work queues by root cause
Collections and appeals team
Where each stage usually fails
Eligibility and benefits check. A name or subscriber ID that doesn't match the plan creates a denial you could have avoided. Confirm payer, plan, network status, and any authorization need at or before arrival, then store that record with the encounter.
Charge capture and coding. ED visit levels rest on medical decision making, not on a long history. Critical care is time-based, and Medicare and CPT don't use the same threshold for add-on time. The failure is a coder who still levels on history, exam, or a single time rule for every payer.
Claim creation and scrubbing. Run payer-specific edits before transmission. A modifier conflict or a bad place-of-service value that leaves the office becomes a preventable defect, not a payer dispute.
Submission and acknowledgement. A 999 rejection means the claim never entered adjudication. If nobody works the acknowledgement queue daily, the timely-filing clock runs on a claim the payer doesn't have.
Adjudication and remittance. Read the 835 line by line. A "paid" status can hide an allowed amount that doesn't match the contracted or out-of-network position.
Payment posting and reconciliation. Post adjustments to the deposit, not to a control total someone typed from a portal. Unmatched deposits hide underpayments inside a balanced batch.
Patient balance and exception routing. Don't send a statement until you've classified the balance. Protected out-of-network emergency balances aren't ordinary patient responsibility.
Practical rule: Eligibility, edits, attachments, remittance posting, and denial categories have to sit in one closed loop. Separate tools create separate stories, and arbitrators don't reconstruct your story for you.
Build these exception queues now: missing authorization data where a plan requires it, modifier conflicts, invalid place-of-service values, coordination-of-benefits errors, and underpayments. That split is what separates a defect you can fix and rebilled from payer behavior that needs negotiation.
Which Payer Rules Apply to Each Emergency Service
Say a patient is stabilized at an in-network hospital, then moved by a ground ambulance that isn't in the patient's network. Staff often assume "emergency" means the whole episode is protected. Federal protections cover emergency services and air ambulance, and they generally don't cover ground ambulance. Some states write their own ground-ambulance rules. If you file the transport as if it were an emergency-department claim, you'll pick the wrong recovery path and the wrong patient bill.
IDR Data's coverage guide reports more than
4 million determined emergency-medicine and emergency-department line items, with an
85.3% provider win rate, while radiology exceeded
1.5 million line items and a
93.3% win rate. Those aren't one-off patient-billing mistakes. They're recurring payer-provider fights, and the service type decides which fight you're in. Our notes on
No Surprises Act emergency services walk through how that classification should be made before a claim goes out.
Service Type
Federal Coverage Position
Billing Implication
Emergency department services
Protected from balance billing for out-of-network care
Patient is protected; provider recovers through negotiation or IDR
Post-stabilization care
Protected in some settings, depending on notice and consent
Document consent and whether the patient could choose an in-network provider
Air ambulance
Covered by federal protections and IDR
Dispute-driven; file on time and assemble evidence
Ground ambulance
Generally not covered federally
Confirm transport type and check state law
Facility-based ancillary services
Protected when an out-of-network provider serves a patient at an in-network facility
Classify each professional and facility line separately
Uninsured or self-pay care
Outside the federal IDR pathway
Follow good faith estimate and self-pay rules
The four questions before you pick a strategy
Was this an emergency service? Screening and stabilization at the emergency department usually fall inside federal protection even when the patient couldn't choose the clinician. Facility-based ancillary lines, including anesthesia and radiology, need their own classification. An out-of-network specialist at an in-network hospital isn't "the hospital's claim."
Could the patient choose an in-network provider? After stabilization, protection can continue or stop based on setting, notice, and whether the patient had a real chance to pick an in-network clinician. If consent is missing, don't guess. Hold the patient bill and document why the service stayed emergent.
Which jurisdiction's rule applies? State law, an All-Payer Model Agreement, a negotiated rate, or federal dispute resolution can each set the path. "NSA-covered" isn't a billing diagnosis. Setting, transport type, state law, and the chart decide the recovery strategy.
What supports the air or ground classification? For air ambulance, charges and clinical need have to be documented before you argue the amount. A plain-language
air ambulance pricing breakdown is useful background when finance leaders are comparing a billed transport with what payers typically allow. Ground ambulance still needs a state-law check before anyone promises the patient a federal protection that doesn't apply.
Denials and Underpayments That Recur in Emergency Claims
Institutional outpatient claims, which include emergency-department care, had a median denial rate of
23% in 2024, the highest among the claim categories analyzed by the
Massachusetts Health Policy Commission. That's the baseline. The useful work is sorting which of those denials you caused.
Level-of-service downcoding. A critical care service comes back as a standard emergency visit. Fix it by keeping time, the qualifying condition, and the interventions on the same note the coder used. If two of three medical-decision-making elements don't support the level, the code shouldn't have gone out.
Modifier conflicts. An emergency visit and a procedure land on one claim without a distinct-service indicator, or modifier 25 is used when critical care began on arrival. Put a pre-submission edit on that pair so the conflict never leaves the office.
Invalid place of service. An emergency visit is billed as a clinic or observation stay because the status changed after arrival and nobody updated the claim. Confirm status against the facility record before scrubbing.
Authorization after stabilization. Some plans still want authorization once the emergency condition is stabilized and care continues. Capture the auth number on the post-stabilization lines only. Don't delay the emergency claim waiting for a number the emergency service didn't need.
Coordination of benefits. A patient with two plans gets the primary and secondary reversed, often because registration copied an old card. Verify the order before the first submission. A secondary denial for "other insurance" is usually a data error, not a coverage dispute.
Timely filing. The acknowledgement sat in a queue, or the hospital feed arrived late. Measure charge lag from date of service to accepted claim, by site. A group that staffs several hospitals will find one feed is always the late one.
Underpayments that look paid. The remittance says paid, the allowed amount is short, and the account drops off the denial report. These need an underpayment queue, not a "resolved" status. A pattern on the same code across one payer is payer behavior. A scatter of one-off coding errors is a defect you fix upstream and rebilled.
A preventable defect gets corrected and sent again. A repeated short payment on the same code needs an offer, a contract comparison, or a dispute file. Mixing those two queues is how recoverable balances age out.
Running an IDR Dispute From Negotiation to Decision
In 2024, federal No Surprises Act IDR entities closed more than
1.37 million disputes, including over
1.33 million involving out-of-network emergency or non-emergency services and
41,338 involving out-of-network air-ambulance services. Nearly
1.048 million closed disputes produced payment determinations, more than three-quarters of the total, according to the
Congressional Research Service. IDR is a reimbursement workflow, not a rare escalation.
Health plans generally must make an initial payment or issue a denial within
30 calendar days after receiving the bill. Federal rules released in May 2026 were written to streamline IDR communications and clarify timelines, as described in
IDR Data's No Surprises Act guide. The sequence after that payment or denial is open negotiation, then a short window to file if the parties don't agree, then selection of a certified entity, offer exchange, and a payment determination. Our walkthrough of
No Surprises Act IDR is the operational checklist finance leads can hand to the team that owns the clock.
What has to already be in the file
Don't start assembling evidence after negotiation fails. By then you're choosing among documents you already kept.
Service codes and clinical complexity: The level, critical care time, and procedures have to match the chart, with procedure time kept out of the critical care total.
Access and specialty: Geographic limits and why this specialty was the one available belong in the offer narrative, not in a later email.
Prior payment history: What this payer allowed for the same service is more persuasive than a single anecdotal underpayment.
Support for the requested amount: The Congressional Research Service reports that median prevailing offers for emergency-service disputes were approximately
2.5 to 3 times the qualifying-payment amount in each quarter of 2023 and 2024. Compare the payer's offer with the QPA and with market evidence. Don't treat the QPA as a ceiling.
A billing function that can't spot eligible underpayments, meet the filing window, and standardize that packet will let recoverable balances age into non-collection. Our IDR engine is built for cases where underpayment is systemic and a compliant claim still doesn't get a fair result. We structure the evidence, benchmark the offer, and write the narrative so it can stand up to arbitrator review.
I would escalate when the same codes keep paying short and internal appeals don't move the allowed amount. If your team can't finish the file before negotiation closes, the filing window will close on an incomplete case.
Compliance Risks in Emergency Claim Documentation
A claim can look clean and still fail an audit. Payers and government reviewers test whether the billed level matches the chart, not whether you transmitted on time.
Level-of-service audit. Compare visit levels and critical care against recorded acuity and interventions. Sample the highest-level claims for each clinician.
Critical care time. Record total time, the condition that required it, and the physician's involvement. Pull out time spent on separately billed procedures.
Diagnosis linkage. ICD-10 codes have to support every service, and ancillary charges have to match orders in the record.
Good faith estimates. Give uninsured and self-pay patients the required estimate, and route cases that exceed it to a defined resolution step.
Patient balance limits. Statements have to respect federal protections and state surprise-billing laws before they go out.
Edit change control. Log every payer-edit change with a date and an owner.
One audit trail. Keep the claim, the remittance, and any dispute file together.
Clinicians who finish notes after the shift are more likely to drop the time and decision-making an auditor will ask for. Tools aimed at
reducing after-hours charting for physicians matter here because the note is the evidence, not a formality after the code is chosen. Route audit findings into the same root-cause queues you use for denials, so an upcoding pattern gets fixed before the next claim, not only defended on appeal.
Criteria for Vetting a Specialized Billing Partner
The first question isn't the fee. It's what the contract covers. Sales decks describe a full revenue cycle. Contracts sometimes cover claim submission and leave appeals, underpayments, and disputes as extras. We put the services in the client contract so that argument doesn't start after go-live.
Criterion
Question to Ask
Red Flag
Specialty coding depth
Are coders specialized in emergency and related services, and how is accuracy audited?
Generalist coders with no emergency audit process
Contract scope
Which services are listed in the contract, including appeals and underpayment recovery?
Scope described only in sales materials
Clearinghouse and edits
Who owns payer-specific edits and how are they updated?
Edits managed without documented change control
Denial root-cause reporting
Are denials categorized by cause and linked to fixes?
Only total denial counts reported
Level-of-service outlier review
Are comparative billing reports run per provider to flag audit risk?
No provider-level comparison available
Payer rule updates
How often are payer coding requirements communicated?
No defined update cadence
Dispute capability
Is IDR handled in-house or referred, and who builds the evidence file?
Dispute work promised without defined process
Before you sign, ask for a denial analysis on your own claims. A partner that can only show a net collection rate hasn't shown you where the money leaks. Our coders are specialty-focused, and we run Comparative Billing Reports on each provider so level-of-service outliers are visible before a government or commercial payer flags them. You can compare how firms structure that work on our overview of
medical billing companies.
Price belongs in the same review. Ask whether the fee is a percentage of collections, a flat rate, or a per-claim charge, and whether recovered underpayments and IDR awards sit inside the fee base. A low percentage that excludes dispute recovery isn't the cheaper contract. Promises of guaranteed payment timing, an undefined IDR process, and reports that show only totals are reasons to walk away.
Deciding Whether to Outsource Emergency Billing
Outsource the dispute and root-cause layers if your team can't meet filing windows or build an evidence file. Keep the front end in-house only if that team already tracks denials by cause and hits those windows. Specialty mix and out-of-network exposure matter more than headcount.
Situation
Recommended Model
Reason
Single hospital emergency department with an established coding team
Keep in-house and add denial and audit analysis
Strong front-end control; gap is usually dispute handling
Multi-specialty group with air ambulance or out-of-network emergency exposure
Specialist partner for RCM and IDR
Dispute deadlines and evidence needs exceed a generalist team
Emergency physician group with frequent underpayments on the same codes
Hybrid: in-house front end, partner for IDR and analytics
Systemic underpayment needs data and dispute capacity
Multi-state platform with mixed payer contracts
Specialist partner with transparent KPI reporting
Consistent reporting across states and specialties is the main need
We offer emergency IDR work to emergency physician groups, emergency service organizations, hospital-affiliated emergency departments, and PE-backed emergency medicine platforms. The point of combining revenue cycle work with dispute work is simple. The claim data captured at coding is the same data the offer has to stand on later.
If you aren't sure which row you're in, request a billing assessment and look at where claims leak. Then schedule a 20-minute out-of-network revenue review and test whether the short payments are recoverable. I would not outsource a functioning front end just to change vendors. I would outsource the layer your current team is already missing deadlines on.
RevGuard builds emergency medical billing services so the claim is clean on the way out and ready if a payer underpays, from eligibility and specialty coding through denial work and No Surprises Act disputes. If out-of-network emergency revenue is aging on your books, visit
RevGuard to request a billing assessment or a 20-minute out-of-network revenue review and see which balances are still recoverable.