The No Surprises Act: How Compliance Rules Are Reshaping Patient Billing
August 25, 2026|Read 12 min|Blog
The No Surprises Act: How Compliance Rules Are Reshaping Patient Billing
Here's the deal. Patient billing used to be primarily a financial function with some compliance edges around coding and documentation. The No Surprises Act changed that structural relationship. What practices bill patients, when they communicate cost expectations, how they handle out-of-network situations, and how they document all of it are now governed by federal law with real legal exposure for getting it wrong not just a billing correction to make and move on from. The law introduced requirements that reach backward into the pre-service financial conversation, forward into how balance billing can be applied in specific scenarios, and sideways into an independent dispute resolution process that requires organized documentation and strategic engagement to navigate effectively.
The law's intent is patient protection specifically, protecting patients from unexpected bills in situations where they had limited ability to choose their provider or their payer's network status. Emergency services, certain facility-based care, and specific out-of-network scenarios are the primary contexts the law covers. But the operational requirements it imposes don't stay neatly within those contexts. Good faith estimate obligations, balance billing restrictions, and dispute resolution requirements touch billing workflows across patient types and service lines in ways that require cross-training, process redesign, and documentation discipline that most billing teams weren't originally built to provide.
The Good Faith Estimate Requirement Changes the Pre-Service Conversation
The most operationally significant piece of the No Surprises Act for most practices is the good faith estimate requirement for uninsured and self-pay patients. Before a scheduled service, the practice must provide a written estimate of expected charges that is accurate enough to meet the law's standards and if the actual billed amount exceeds the estimate by more than $400, the patient has the right to dispute the bill through a patient-provider dispute resolution process. That $400 threshold is the operational reality that makes this requirement demanding: it's not a general transparency gesture, it's a commitment that creates legal exposure if the estimate is materially wrong.
Getting this right requires practices to have a reliable, current understanding of their own pricing across service lines in a format that can be translated into patient-facing estimates before care is delivered. Historically, many practices never needed to formalize that information for patients in advance charges existed in the billing system, but nobody was producing pre-service estimates from them in a systematic way. Building the infrastructure to generate good faith estimates consistently, accurately, and in the timeframes the law requires (within one business day for services scheduled less than three days out, within three business days for services scheduled further out) is an operational requirement that most practices have had to build from scratch. The practices that treat it as a one-time policy adoption tend to produce inconsistent compliance. The practices that build it into the scheduling and registration workflow as a default step produce the consistency that compliance requires.
Balance Billing Restrictions Eliminate a Default That No Longer Exists
The balance billing restrictions are where practices face the most significant change to long-established billing behavior. In the situations the No Surprises Act covers emergency services, non-emergency services at in-network facilities where the patient had no meaningful choice of provider, and air ambulance services providers can no longer bill patients the difference between what an out-of-network payer reimbursed and the provider's billed charge. The patient's cost-sharing obligation is limited to in-network levels, the provider must accept whatever the payer determines as the payment rate (subject to the dispute resolution process), and applying balance billing in these situations creates legal exposure rather than just a billing error to correct.
The operational challenge isn't understanding the restriction in principle it's identifying correctly which situations fall under the law's coverage and which don't. An out-of-network service at an in-network facility where the patient was given a genuine opportunity to choose an in-network provider may not trigger the same restrictions as an out-of-network service at an in-network facility where no network option was available. Emergency situations at any facility are covered. But applying the restrictions consistently across the variety of out-of-network scenarios a practice encounters requires billing staff to make coverage determinations in real time and inconsistent application is exactly what creates compliance risk, because the same situation handled differently in two billing cycles becomes evidence of a process that doesn't reliably function.
The Documentation Problem That Creates Compliance Risk
The most common compliance failures under the No Surprises Act aren't dramatic violations of the law's core restrictions. They're process inconsistencies a good faith estimate workflow that exists as a written policy but isn't executed reliably for every eligible patient, balance billing restrictions that staff understand conceptually but apply inconsistently across similar cases, and documentation that would need to be reconstructed after the fact rather than existing cleanly as part of the normal billing workflow. These gaps are manageable in normal operations because nobody is actively auditing them daily. They become serious problems the moment a patient files a complaint or a regulatory review is triggered.
The system failed them; they didn't fail the system. Billing teams that developed inconsistent No Surprises Act compliance didn't choose to be noncompliant they were given a regulatory framework that requires workflow redesign, cross-training, and documentation discipline that goes well beyond traditional claims processing competency, without always receiving the operational infrastructure investment that compliance at scale requires. Staff who understand balance billing restrictions in theory but apply them inconsistently are working from general knowledge rather than clear decision rules embedded in a workflow that makes the correct path the default path. Documentation that doesn't exist contemporaneously is the product of a process that added compliance requirements to existing workflows without adding the documentation steps that compliance evidence requires.
The Independent Dispute Resolution Process Requires Preparation
When a payer and provider can't agree on payment for services covered under the No Surprises Act, the law provides an independent dispute resolution process where a certified IDR entity makes a binding payment determination. This process is available to practices when payer payment falls below the practice's expected reimbursement, and it's a legitimate recovery mechanism for situations where the law's payment framework produces below-market results. But it requires something that improvised engagement can't deliver: organized documentation, a clear presentation of the practice's case based on the factors the IDR process weighs, and strategic understanding of how to make the best argument for a favorable determination.
Practices that engage with IDR without preparation submitting inadequate documentation, failing to address the relevant factors the IDR entity evaluates, or presenting their case in formats that don't align with the process requirements routinely get outcomes that don't reflect the actual value of the service. The IDR process is a formal quasi-judicial procedure, not a billing appeal, and it rewards preparation the way any formal proceeding does. For practices with meaningful volume of out-of-network services in covered situations, building IDR engagement capability into the revenue cycle operation knowing which disputes are worth pursuing, how to organize the supporting documentation, and how to present the case effectively is a revenue protection function rather than an optional legal exercise.
Signals That No Surprises Act Compliance Has Gaps in Your Practice
These patterns in your billing operations and patient interaction data tell you that compliance infrastructure needs attention before a complaint or review surfaces the problem for you.
Good faith estimate completion rates below 100% for uninsured and self-pay patients with scheduled services. If the practice can't confirm that every eligible patient received a compliant estimate before every scheduled service, the process exists on paper but not reliably in practice which is exactly the gap that creates compliance exposure when a specific case is examined.
Balance billing applied inconsistently across similar out-of-network situations without a documented decision framework that explains why different situations were treated differently. Inconsistency is the compliance risk similar cases handled differently without a principled explanation suggests the process isn't working by rule, it's working by individual staff judgment, which doesn't survive regulatory scrutiny.
Patient complaints about unexpected bills in situations that should have been covered by the law's protections. Patient complaints are the most direct signal that the law's patient protection intent isn't being operationalized and they're also the most likely trigger for regulatory attention, making them the compliance risk that self-correcting quickly produces the most protection against.
Turning Compliance Into a Patient Trust Advantage
The compliance framing of the No Surprises Act makes it easy to miss what it actually produces for practices that implement it well. A billing process that proactively communicates expected costs before care is delivered, that applies balance billing restrictions accurately rather than defaulting to the patient bill, and that handles disputes through a structured process rather than protracted back-and-forth with confused patients doesn't just avoid compliance risk. It produces the patient financial experience that reduces billing disputes, accelerates payment, and builds the kind of trust that affects long-term patient retention and referral behavior.
Practices that have always communicated costs proactively and managed out-of-network billing carefully were doing voluntarily what the No Surprises Act now requires. For practices that hadn't built those habits, compliance implementation is an opportunity to build them because the operational requirements of the law and the operational requirements of a high-quality patient financial experience are essentially the same. Transparent cost communication, accurate billing, and organized dispute resolution are what patients want from their financial relationship with a healthcare provider, and they're also what the law requires. Compliance and patient trust are the same investment.
If your practice needs revenue cycle support, denial management, or billing optimization, Medisure can help your clinical teams verify, submit, and collect with confidence. No Surprises Act compliance is part of the complete patient billing infrastructure that Revenue Building requires because billing accuracy, financial transparency, and legal compliance are the foundations of patient financial relationships that sustain both collection performance and practice reputation over time.
Conclusion
The No Surprises Act isn't a law that practices can comply with through a one-time training and a policy update. It's a regulatory framework that requires workflow integration good faith estimates built into the scheduling process, balance billing determinations made by decision rules rather than individual judgment, IDR engagement approached with documentation discipline rather than improvisation, and compliance evidence created contemporaneously rather than reconstructed when scrutiny arrives. The practices that build these workflows correctly are protecting themselves from compliance exposure while simultaneously building the patient financial experience that reduces billing disputes and builds trust. Those two outcomes aren't in tension they're the same investment producing two different forms of return.
Pick one compliance gap from this framework to address this month. If good faith estimates aren't being completed for every eligible patient, build the scheduling workflow that makes completion the default rather than the reminder. If balance billing is being applied inconsistently, build the decision framework that standardizes the determination. If IDR cases have been handled without preparation, document the framework for which disputes to pursue and how to organize the supporting case. Each one of those improvements protects the practice legally and improves the patient billing experience simultaneously which is exactly the combination that well-designed billing compliance should produce.
On we go.
FAQ
What does the No Surprises Act actually require practices to do?
The No Surprises Act requires practices to provide good faith estimates of expected charges to uninsured and self-pay patients before scheduled services, restricts balance billing in specific out-of-network scenarios including emergency services and certain facility-based care where patients had no meaningful choice of provider, establishes a patient-provider dispute resolution process when billed charges exceed good faith estimates by more than $400, and creates an independent dispute resolution process for payer-provider payment disagreements on covered services. Together, these requirements change what has to happen before, during, and after billing in ways that require workflow redesign and documentation discipline beyond traditional claims processing.
What is a good faith estimate and when must it be provided?
A good faith estimate is a written document provided to uninsured and self-pay patients before scheduled services that communicates expected charges with enough accuracy to stay within $400 of the actual bill. The law requires the estimate within one business day for services scheduled within three days, within three business days for services scheduled further out, and upon patient request within three business days regardless of scheduling timeline. Producing compliant good faith estimates requires practices to have reliable, current pricing information across service lines and a workflow that generates and delivers estimates consistently for every eligible patient within required timeframes.
What balance billing restrictions does the law impose and where do they apply?
The No Surprises Act restricts balance billing billing patients the difference between provider charges and payer reimbursement in situations where patients had limited ability to choose in-network providers. This includes emergency services at any facility, non-emergency services at in-network facilities where the patient had no meaningful opportunity to choose an in-network provider (such as when care was provided by an out-of-network provider at an in-network facility without advance notice), and air ambulance services from non-participating providers. In these situations, patient cost-sharing is limited to in-network amounts, and balance billing the remainder creates legal exposure rather than just a billing correction.
What is the independent dispute resolution process and when should practices use it?
The IDR process is a formal mechanism for resolving payment disputes between providers and payers on services covered by the No Surprises Act when the payer's payment falls below the provider's expected reimbursement and the parties can't reach agreement through open negotiation. A certified IDR entity reviews submissions from both parties and makes a binding payment determination based on specific factors the law establishes. Practices with meaningful volume of out-of-network services in covered situations should evaluate IDR engagement as a revenue recovery mechanism, but preparation matters significantly organized documentation and a case presented around the factors IDR entities weigh produce better outcomes than improvised submissions.
How does Medisure help practices build No Surprises Act compliance into their billing operations?
Medisure helps practices build No Surprises Act compliance into normal billing workflows good faith estimate processes integrated into scheduling and registration, balance billing decision frameworks that produce consistent determinations rather than individual staff judgment calls, documentation standards that create compliance evidence contemporaneously rather than requiring reconstruction, and IDR engagement support for disputes worth pursuing. The goal is to ensure that Medical Billing operations meet the law's requirements by default rather than by reminder, protecting the practice from compliance exposure while simultaneously building the transparent patient financial experience that supports faster payment, fewer disputes, and the Revenue Building performance that patient financial trust enables.