How denial management works, and what it costs to skip

Denials are the part of the revenue cycle where effort and outcome come apart most easily. It is entirely possible to have somebody working denials full time, closing accounts every day, and to see no improvement at all in what the practice collects — because the same reasons keep arriving and the queue never gets ahead of them.

The distinction that matters is between working a denial and understanding it. Working it recovers this claim. Understanding it is what makes next month’s pile smaller. A queue that only does the first is a treadmill, and the practice pays for the treadmill every month.

Read the reason before deciding anything

In our experience the most common way denial labour is wasted is resubmission without reading. A claim comes back unpaid, somebody rebills it, and the payer refuses it again for the same reason it refused it the first time. That cycle can run three or four times, and on the fourth pass the account is close enough to the filing limit that a correctable denial becomes a write-off.

So the first action on any denial is to establish what the payer actually said: the remittance advice, the adjustment and remark codes together, and the claim as submitted. The codes are a summary, not an explanation — and two claims carrying the same code can need entirely different work.

Classify by cause, not by code

Grouping a denial report by code is the obvious first move and it is not enough. A useful classification puts every denial into the place where the problem was created:

• Registration and demographics — wrong identifier, wrong payer, wrong subscriber, wrong date of birth.
• Eligibility and coverage — not active on the date of service, benefit not covered, wrong plan, coordination of benefits unresolved.
• Authorization and referral — permission not obtained, obtained but not recorded, expired, or obtained for different codes.
• Coding and documentation — code combinations the payer bundles, modifier requirements, level of service, medical necessity.
• Claim build and submission — missing data elements, wrong place of service, wrong rendering or billing provider, format failures.
• Payer process — duplicate handling, adjudication errors, requests for information, and delays that are simply the payer’s.
• Filing and timing — submitted after the limit, or appealed after the window.

That classification is what turns a list into a diagnosis. Twelve denials with different codes that all trace back to registration are one problem, not twelve — and the fix is at the front desk, not in the billing queue.

A working sequence for a single denial

1. Confirm what the payer said, from the remittance rather than from a summary screen.
2. Compare it against the claim as submitted and the record behind it.
3. Decide the action: correct and resubmit, appeal with documentation, rebill to a different payer, refer upstream, or write off.
4. Check the clock. Note the filing limit and the appeal window before doing the work, not after.
5. Carry the action out, and record what was sent and when.
6. Set the next review date. An account with no next date is an account that will age.
7. Record the category, so the pattern is countable.

Step four is the one that changes outcomes most and takes the least time. An account with three days left on an appeal window is a different priority from an identical account with ninety, and nothing on the denial itself makes that obvious.

Appeals are a document, not a phone call

Where an appeal is the right route, it needs to be written as an argument: what was billed, why it was appropriate, what the payer’s stated reason was, and what evidence answers it. Attaching the operative note without a covering argument leaves the reviewer to construct the case themselves.

It also needs a record: the date sent, the route, the reference, and the date to check back. An appeal with no follow-up date is an appeal that will be forgotten, and the second-level window will close while the account sits looking like it has been dealt with.

The part that cannot be outsourced

A denial queue can surface that thirty per cent of last month’s denials came from eligibility. It cannot change what the front desk does on Monday morning. That decision belongs to the practice, and the seat’s job is to make it unavoidable — a monthly count by category, ranked, with the top three named.

The same applies to clinical documentation. Where a payer disputes medical necessity, the record either supports the service or it does not, and no amount of follow-up substitutes for a clinician’s note. What the seat can do is get the question in front of the right person quickly, with the payer’s stated position attached.

What to define before handing over the queue

Priority order

By appeal window first, then by value, then by age, is a defensible default. Whatever the order is, write it down, because otherwise the queue is worked from the top of whatever report was opened.

Authority

What the seat may do alone — correct a demographic error, rebill, submit a standard appeal — and what must be escalated. Write-offs almost always stay with the practice, and should.

The category list

Agree the categories in advance and keep them stable. A classification that changes every month cannot be counted across months, which defeats the purpose of classifying at all.

Documentation standard

Where notes go, what a note must contain, and how an appeal is filed and evidenced. Another person should be able to open the account and know what happened without repeating the investigation.

The upstream route

Who receives the monthly category report, and who is expected to act on it. Without a named owner it becomes a report that is produced and filed.

How to assess it

• Which accounts were worked, and what changed on them?
• How many denials were resolved on the first action rather than the third?
• Were any appeal windows or filing limits missed, and why?
• What are the top five categories this month, and how do they compare with last month?
• Which categories are being routed upstream, and is anything changing there?
• Does every unresolved account have a next action and a next date?

The fourth and fifth questions are the ones that separate a denial function from a rework function.

When a dedicated seat makes sense

When denials are being reworked but not counted. When nobody can say what the top three causes were last month. When appeals are going out late, or not at all. When the practice is growing and the pile is growing faster. And when the people currently doing this work are the same people doing charge entry and answering patients, which means denials get whatever is left of the day.

Questions to ask a provider:

• Will the seat work US hours, so payers can be reached and appeals filed the same day?
• Will they work in your system, so the audit trail is in the account rather than in a spreadsheet?
• Is the categorisation part of the service, or only the rework?
• What arrives on your desk monthly, and who is expected to act on it?
• Is it a dedicated full-time seat, or shared capacity across several clients?
• How are appeal windows tracked?

How Soft Home Global staffs this

Soft Home Global provides trained full-time back-office seats from Rawalpindi, Pakistan. AR calling and denial management is published at $1,700 per seat per month, billed per seat with a one month minimum — a seat rate rather than a percentage of collections, so the cost of the work does not rise with the value of what it recovers.

The seat works your queue on US hours, inside your system: reading the payer’s stated reason, deciding the action within the authority you set, filing appeals with the documentation you make available, recording every contact with its reference, and categorising every denial so the monthly pattern is countable rather than anecdotal.

Where a denial traces to eligibility, authorization, credentialing or coding, it is routed to that queue rather than called on repeatedly. Soft Home Global staffs those seats too, which is what makes routing possible instead of theoretical.

Where to start

Take last month’s denials, group them by cause rather than by code, and rank the categories. Most practices find that three causes account for the majority of the volume, and at least one of them originates before the claim was ever built.

That ranking tells you two things at once: what a denials seat should work first, and what needs to change somewhere the seat cannot reach.