Navigating the No Surprises Act: Tips for TPAs and Carriers

The No Surprises Act has been on the books long enough that the rules are not really news anymore. What still trips people up is the operational side: turning the statute into edits, payment calculations, EOB language, and dispute timelines that your system actually enforces. We have spent more than 33 years building claims administration software, and we have watched the same handful of mistakes show up across TPAs, carriers, and provider-sponsored plans. None of them are about misunderstanding the law. They are about a system that was not set up to handle it cleanly. This is not legal advice, and you should run anything specific past your own counsel. It is an operator's view of where the work lives.

Start with what the law is asking of you as a payer. In plain terms, it protects members from balance billing in certain out-of-network situations: emergency services, and non-emergency care delivered by out-of-network providers at in-network facilities (think the anesthesiologist or the radiologist a patient never chose). In those cases the member can only be charged their in-network cost share, and the rest is sorted out between you and the provider. That sounds simple until you realize your system has to recognize those claims, apply the right cost-sharing math, and route the remainder down a completely different path than a normal out-of-network claim.

The qualifying payment amount is where the math gets specific

The qualifying payment amount, or QPA, is your median contracted rate for that service in that geographic area, and it drives the member's cost share for protected claims. If your QPA is wrong or stale, every downstream number is wrong: the member pays the wrong coinsurance, your EOB shows the wrong allowed amount, and you have handed the provider an easy argument in any dispute. The QPA is not a field you set once and forget. It needs to reflect your actual contracted rates and update as those rates change. On our Series 3000 platform, that calculation lives in configuration you control, not in code someone has to rewrite every plan year. When a fee schedule moves, the QPA logic moves with it, and the EOB reflects the change without a manual override.

Auto-adjudication is the place this either works quietly or breaks loudly. A protected claim that the system does not flag will adjudicate like any other out-of-network claim, and the first time anyone notices is when a member calls about a balance bill they should never have received. The fix is custom edits that identify protected services up front and apply the right cost share before the claim ever pays. Get that right and these claims stay inside your auto-adjudication rate instead of dropping into the pended queue for a manual touch. Get it wrong and you are paying staff to catch in review what the system should have caught at intake.

Open negotiation and IDR run on a clock

When you and an out-of-network provider disagree on payment for a protected claim, the law gives you an open negotiation window, and if that does not resolve things, an independent dispute resolution (IDR) process with a certified entity. The substance of IDR matters, but the part that quietly sinks plans is the calendar. Each step has a deadline, and missing one can cost you the right to contest the amount at all. These dates do not announce themselves. If the only place a negotiation window lives is someone's inbox or a spreadsheet on a shared drive, you will miss one eventually.

Here is where the operational discipline pays off. A few habits keep these claims from slipping:

• Tag protected claims at intake so QPA logic and the right cost-sharing rules apply automatically, not after a member complains.
• Track the open negotiation clock and the IDR clock as real dates with owners, so a deadline is something the system surfaces rather than something a person has to remember.
• Keep the QPA calculation tied to your live fee schedules, and re-check it whenever contracted rates change, so the median you are using is the one you can actually defend.
• Make EOBs and member disclosures say what the law requires in plain language, including the member's protections and how their cost share was figured, so your call center is not fielding avoidable questions.
• Pull reporting on protected claims, QPA usage, and IDR outcomes regularly, so you can see patterns before they become a provider relations problem.

Notice and disclosure obligations round out the list, and they are easy to underrate because they feel like paperwork. Plans have to make certain information available about balance-billing protections, and your EOBs need to carry accurate allowed amounts and cost-share figures for these claims. When the numbers on the EOB match the QPA logic that produced them, the member sees a coherent story and your representatives are not reverse-engineering an adjustment on the phone. When they do not match, every protected claim becomes a small investigation. We surface this in the member portal and mobile app too, so the same accurate information a member would call about is already in front of them.

The reassuring part is that none of this requires a custom build or a year of development. When we implement a new block of business, this configuration goes in during the same roughly 3 to 4 month window as everything else, and you test it against real scenarios in a live test environment before anything goes to production. You can run a protected emergency claim, a clean out-of-network claim, and a non-emergency claim at an in-network facility, and watch the system route each one correctly with your own eyes.

The No Surprises Act is not the hardest thing your claims operation does. It is just unforgiving about the details, and it punishes plans whose systems were not built to track them. If you want to walk through how the QPA handling, the edits, and the IDR timeline tracking would look against your own book, our team is happy to show you in a working environment rather than a slide deck. Reach out and we will set up a look.