Billing follow-up: the revenue cycle task that falls through the cracks

Denied and unresolved claims can materially reduce collected revenue, but the impact varies by payer mix, specialty, and the practice's follow-up process. The useful baseline is your own initial-denial rate, overturn rate, write-offs, filing deadlines, and days in accounts receivable. The AMA's revenue cycle guidance recommends tracking denial reasons and building a process around them rather than relying on one market-wide percentage.

This guide fits healthcare practices and medical billing department workflows where staff still chase payers in portals and phone queues.

Treat denials as a queue system, not a single inbox. Common groupings (adjust to your remittance data):

• Administrative / registration: eligibility, COB, missing subscriber ID, timely filing (often CARC/RARC-driven on the 835 remittance).
• Coding and billing edits: missing or invalid modifier, duplicate claim, bundling, medical necessity edits pending documentation.
• Authorization: no prior auth or referral on file when the payer requires it.
• Medical records: payer requests additional documentation before reconsideration.

Route each category to a named owner (front desk for eligibility, billers for coding corrections, authorization specialist for auth gaps, coders or providers when clinical records are required). Automation should label and sort using reason codes from the 835 (and payer remark codes where present), not replace that routing policy.

When clearinghouses and payers support them, HIPAA X12 276/277 claim status inquiries and 277CA claim acknowledgment responses can reduce blind portal checking. An 835 remittance explains paid, denied, or adjusted lines with reason codes that feed triage rules.

Design status automation to poll or receive events on approved channels, diff against your practice management system, and surface only changed or aged claims (for example, no 277 acknowledgment within N business days, or denied with a code that has a documented playbook). Do not scrape payer portals or bypass MFA.

Many denials start payer-specific clocks (corrected claim windows, appeal levels, fax or portal deadlines). Workflows should attach deadline metadata to each queue item from your policy table and escalate items within a configurable buffer (for example, 5 business days before expiration). Human review gates stay on any submission that changes clinical coding, adds modifiers, or alters charged amounts.

Denial triage by reason code and age, with SLA timers per category.

Routine appeal assembly (forms, cover letter templates, attachment checklist) when staff have already confirmed coding and documentation.

Worklists for status changes from approved 277/277CA or 835 feeds.

Many denials trace back to authorization problems. If that is your biggest category, read what prior authorization automation can and cannot do before building the appeal side.

Provider involvement for peer-to-peer or clinical necessity appeals.

Any write-back to the practice management system that changes CPT, ICD, units, or modifiers.

Outbound appeals or corrected claims above a dollar threshold or for high-risk payers.

Payer portals and telephony still dominate some follow-up; automation should queue and document manual steps rather than imitate unavailable APIs.

Billers spend less time sorting routine status and denial data and more time on complex denials, payer escalation, and appeals that need clinical judgment. Measure recovery against your own baseline denial and overturn rates, not generic industry stats.

For the rest of the practice, see our medical practice automation guide.