Who Reconciles Our Facility and Anesthesia Claims So Mismatches Stop Causing Dual Denials?

What a Real Facility-Anesthesia Reconciliation Step Looks Like

The goal is simple: two claims for the same case that agree on code, date, and detail before either one reaches the payer, and a fast fix on the mismatches that slip. Here is what does that, move by move.

1. Reconcile the Two Claims Before Either Is Submitted

The mismatch is cheapest to catch before it ships. The first move is a pre-submission reconciliation: the facility claim and the anesthesia claim for the same case are checked against each other on the things payers compare, primary CPT, service date, and case detail, so a disagreement is flagged and fixed before either goes out. Because the two claims usually come from separate organizations, nobody does this today, which is exactly why the payer is the first to notice the mismatch. A single owner checking the pair first turns a future dual denial into a five-minute fix.

2. Sync Post-Submission Coding Changes Across Both Entities

Most mismatches start with a legitimate change: the facility coder revises the primary CPT after an op-note query, and that revision never reaches the anesthesia biller in the other organization. The move is a propagation rule: any coding change on one claim triggers a matching update on the other before the payer reconciles them. When the facility code moves, the anesthesia code moves with it, or the mismatch is flagged and worked immediately, so a correct correction on one side stops becoming a denial on the other.

3. Run a Shared Exception Report Every Week

Some mismatches slip through anyway, and they hide because no single report shows both claims side by side. The move is a shared exception report that lists every case where the facility and anesthesia claims disagree, aging fastest first, so mismatched pairs surface while there is still time to correct and resubmit rather than after a ninety-day denial. The report is what gives one owner visibility across two billing organizations that otherwise never see each other’s work.

4. Own the Appeal on Any Dual Denial

When a mismatch does reach the payer and both claims deny, the worst outcome is two teams trading emails about whose code is right while the claim ages. The move is single ownership of the appeal: one specialist reconciles the correct code across both entities, corrects and resubmits both claims aligned, and works the denial to resolution instead of routing it back and forth. A dual denial with an owner clears; a dual denial that belongs to no one ages ninety days and then gets written off.

5. Hand Reconciliation to a Dedicated Owner

Centers that stop losing cases to facility-anesthesia mismatches do it by giving the reconciliation step a dedicated owner: a remote specialist who checks the pair before submission, syncs coding changes across both entities, runs the weekly exception report, and owns the dual-denial appeals, live in 1 to 2 weeks. Neither billing team has to babysit the other, a trained backup covers every gap, and the mismatch stops being the denial nobody is responsible for. Below is what it sounds like when nobody owns it yet, in providers’ own words.

Why This Keeps Happening

If both coders did their jobs, why does the claim still deny? Because the work is split across two organizations with no bridge between them. In most ASCs, the facility bills on a UB-04 and the anesthesia group bills separately on its own claim form, often from an entirely different company, and industry ASC billing guidance is consistent that the two claims must agree on code and date to avoid dual denials. There is no shared step where anyone compares the pair before it ships, so when one side changes a code, the other never learns of it, and the payer becomes the first party to notice the mismatch. The denial is not a coding error; it is a coordination gap. Closing that gap is exactly what a dedicated revenue cycle management desk is built to do.

The second half of the problem is that the mismatch is usually born from a correct decision. An op-note query prompts the facility coder to revise the primary CPT, which is exactly what should happen, but the revision lives only in the facility’s system. The anesthesia biller, in another organization, submits against the original code because that is the last thing they knew. AAPC and ASC billing coordination guidance both stress that a coding change on one claim has to propagate to the other, yet with no reconciliation owner, it cannot. So doing the right thing on one side quietly breaks the other, and the correction becomes a denial. An AI automation layer that flags the mismatched pair the moment the codes diverge is what makes that propagation possible for two teams that never see each other’s work.

And the cost is the aging, not just the denial. A mismatched anesthesia claim does not fail loudly at submission; it fails weeks later at the payer, and then it sits, because it belongs to no one. The facility team believes the anesthesia code is wrong, the anesthesia team believes the facility’s is, and the claim ages ninety days while emails go back and forth. HFMA denials guidance ties exactly this kind of ownerless, cross-entity denial to the slowest recoveries and the highest write-off risk, because a claim nobody owns is a claim nobody works. The lost revenue is real, and it grows the longer the two teams point at each other instead of reconciling.

Most groups have already tried the obvious fixes before they talk to anyone. Each one fails the same way: the work lands back on the practice. The pattern, in one table:

The Solution

So what does “someone whose whole job it is” look like on a split facility-anesthesia case? The specialist sits in the gap neither team owns. Before either claim ships, they reconcile the pair against each other on the fields payers compare, primary CPT, service date, and case detail, so a mismatch is caught and fixed before it becomes a denial. That single pre-submission check is the core of what dedicated claim reconciliation and coordination is built to deliver, and it converts the most common dual denial into a routine catch.

Then comes the propagation that keeps corrections from breaking the other side. When the facility coder revises a primary CPT after an op-note query, the specialist carries that change to the anesthesia claim before the payer reconciles them, so a correct fix on one side updates the other instead of denying it. A weekly shared exception report backs this up, surfacing any pair that still disagrees while there is time to correct and resubmit, so the mismatches that slip the first check do not age into denials.

Behind all of it, AI drafts the first pass and a credentialed human verifies. The workflow compares the two claims, flags divergent codes, and drafts the corrections; a person confirms the right code across both entities and owns any dual-denial appeal end to end, instead of letting it bounce between teams. Every security control that protects the claim and chart data moving between the two billing organizations is documented and auditable, and the whole approach is described on our HIPAA and security page, because moving case data across two entities through a reconciliation workflow is only safe when the controls are real.

Who Actually Does This Work

Fair question: why would an outsourced owner reconcile your two claims better than your own two teams? Because reconciling cross-entity claims is their entire job, not a step that falls between two organizations that never talk. The person owning your reconciliation is a credentialed medical professional, drawn from a bench of overseas-trained physicians, US-licensed nurses and pharmacists, and PharmDs, all trained in US ASC and anesthesia billing workflows. They know what payers compare across a facility and anesthesia claim, how an op-note query changes a primary CPT, and how to propagate that change so both claims agree. That is not a task that belongs to whichever team happens to notice; it is a dedicated reconciliation role.

We are not a call center. We are a clinical operations partner, a healthcare BPO built on dedicated virtual staff: 500+ credentialed professionals, 24/7 coverage, and the AI-first-pass plus human-verify workflow you just read about behind every one of them. A typical center is live in 1 to 2 weeks, at up to 70% below the cost of hiring locally, and no one on our side goes out without a trained backup already inside your workflow, so a mismatched pair never sits because the one person who reconciles both claims is on vacation.

And the security piece your compliance officer will ask about: we are audited to SOC 2 Type II with zero exceptions and certified for ISO/IEC 27001:2022, HIPAA, and GDPR, with zero breaches in eight years. Every workstation runs inside a secure enclave on US-based servers, with screen captures and downloads blocked by policy, so PHI never sits on someone’s home laptop. Every client account carries a $5M E&O and cyber liability policy and a BAA signed before any work starts; the full detail lives in our HIPAA and security posture.

Put the routine and the people together, and a specific list of things simply stops happening.

How We Permanently Fix the Process

A person alone is not the fix, and neither is a bot alone. The fix is a documented reconciliation workflow: which fields the facility and anesthesia claims must agree on, how a coding change on one side propagates to the other, the weekly exception report that surfaces mismatched pairs, and the ownership rule for any dual denial. Before we take a single case for a new center, we chart where your facility and anesthesia claims actually diverge, by procedure and payer, so we can see where the mismatches are born, and we build the workflow against that, not against a generic template.

From there the workflow becomes a living playbook rather than an assumption that the other team will catch it. It records how each payer compares the two claims, the propagation rule for op-note coding changes, the exception-report cadence, and the escalation path when a dual denial lands. It is written down, kept current as coding and payer rules change, and owned by one person who sits between both billing organizations. When your specialist is out, a trained backup works the same playbook the same way, so a mismatched pair never waits because one person is away.

That is the difference between reworking this month’s dual denials and fixing the process for good, and it is what a dedicated revenue cycle management partner actually buys you. A gap between two billing organizations used to mean coding changes broke claims and dual denials aged unowned. Under this model the reconciliation runs, the playbook stays, the backup steps in, and a facility-anesthesia mismatch stops being the denial nobody is responsible for.

The Whole Thing in Four Sentences

Facility and anesthesia mismatches cause dual denials because the two claims come from separate organizations with no shared reconciliation step, so when the facility coder revises a primary CPT after an op-note query, the anesthesia group never hears of it and the payer denies the mismatch. Letting each team work its own claim, fixing coding changes only where they happen, or resolving dual denials by email all fail the same way. The fix is a single owner who reconciles the two claims before submission, propagates any coding change across both entities, runs a weekly exception report on mismatched pairs, and owns the appeal on every dual denial. A multi-specialty ambulatory surgery center runs exactly this model with us today, names withheld, no patient data shown.

If you want to check us out before talking to anyone: our security posture is independently auditable, we are an MGMA 2026 Corporate Member, and 800+ providers run back office work with us.

Ready to stop facility-anesthesia dual denials? Try us risk free: two weeks, your real split-claim cases, a dedicated specialist reconciling both claims and owning the mismatches, and if it does not earn the handoff, you walk away. From here down is the sales part, and it is short: here is exactly what it costs.

Written By

Dan Nandan

Founder and CEO, Staffingly, Inc. · Piscataway, NJ

Dan Nandan has spent 25+ years in IT consulting and healthcare BPO, was among the first in the US to build an RPO/BPO delivery network in India, and has been featured in Computerworld. He runs the operations and the dedicated virtual teams behind the workflows on this page; the team-voice answers above come from the remote specialists who work them every day.

Connect on LinkedIn

Where the Claims on This Page Come From