Medical billing isn’t difficult because teams “don’t know what they’re doing.” It’s difficult because the rules and the environment keep moving: code sets refresh annually, payers adjust coverage and documentation expectations, prior authorization expands, and more costs shift to patients—often without the transparency patients expect.
A good example of the pace of change is the annual CPT update. The CPT 2025 code set includes 420 total updates: 270 new codes, 112 deletions, and 38 revisions, according to the American Medical Association. When practices don’t operationalize this kind of change (training, templates, charge masters, payer rules, scrubbers), outdated or mismatched codes can translate into denials, rework, or downcoding.
At the payer level, denials are not a “rare exception.” Several reputable analyses show denial rates that are high enough to materially change a practice’s cash flow and staffing needs. The American Hospital Association summarized research indicating that nearly 15% of claims submitted to private payers are initially denied (including 15.7% Medicare Advantage and 13.9% commercial), and noted that many denied claims are later overturned—but only after costly appeals work. A 2025 analysis in Health Affairs reported 17% denial rates for initial Medicare Advantage claim submissions and found that 57% of denied claims were ultimately paid (again implying substantial avoidable friction). State-level reporting can show even higher rates: the Massachusetts Health Policy Commission reported an average 20.4% overall denial rate for claims submitted to fully insured commercial insurers in Massachusetts in 2024.
Prior authorization adds a separate layer of administrative “drag.” In the 2024 prior authorization physician survey, the AMA reported that 93% of physicians said PA delays care, and 82% said PA can lead to treatment abandonment at least sometimes. CMS has acknowledged the administrative burden of prior authorization and is pushing policy and technical approaches intended to streamline data exchange (including API requirements with major implementation dates in 2026–2027).
Finally, the patient side has changed as well. Affordability issues are now common enough to directly shape collections strategy, making medical billing services more important than ever. KFF reports that 44% of U.S. adults say it is difficult to afford health care costs, while 28% report problems paying for care in the past 12 months. Even among people with employer-sponsored coverage, cost-sharing remains significant. For example, 33% of covered workers are enrolled in a high-deductible health plan with a savings option (HDHP/SO) in 2025. These trends show why providers need stronger collections workflows and greater financial transparency.
What follows is a research-backed, practice-oriented view of the ten billing problems that most commonly create denials, delays, and write-offs—and the operational changes that consistently reduce them.
Regulatory and coding changes outpacing your internal updates
The core problem is not just “new codes exist.” The problem is that multiple downstream systems must change quickly and consistently: scheduling and registration prompts, EHR templates, charge entry, code editing rules, payer billing guidance, and staff habits. CPT updates alone can be large (e.g., 270 new CPT codes in the CPT 2025 release).
What works: formalize a quarterly “billing change cycle” (not an ad hoc email). Assign ownership for (1) monitoring official updates, (2) change testing in a sandbox, and (3) go-live training. Build a short “what changed and what we do now” note for front desk, clinical staff, and billing staff—because each group touches different failure points. For code-assist tooling, computer-assisted coding can help if it is implemented with governance: AHIMA defines CAC as extracting and translating documentation into ICD/CPT/HCPCS codes for coding/billing use, with the expectation of professional review rather than full automation.
High claim denials and rework becoming routine
Denials are often treated as a back-office nuisance; the data says they are a systematic operating reality. Initial denial rates around the mid-teens are reported in large analyses, with meaningful variation by payer and setting. The fact that many denials are later overturned suggests that a large portion of denials are administrative friction rather than true non-coverage—but that still costs time and delays cash.
What works: treat denials like quality defects. Use remittance and denial codes to group denials into a small number of “root cause buckets” (eligibility/coverage, authorization, coding mismatch, documentation/medical necessity, timely filing, duplicates). Then fix the upstream step where the defect is created, rather than only appealing and resubmitting. A payer-facing denial prevention goal should be “clean submission” and “first-pass yield,” not “we appeal fast.”
Prior authorization and benefits verification gaps
If you miss an authorization requirement or verify benefits too late, you can deliver a service that is clinically appropriate and still create a denial that is difficult to overturn. The AMA survey results underscore how pervasive PA has become and how often it delays care. On the policy side, CMS’ Interoperability and Prior Authorization final rule sets expectations and timelines for payers to implement APIs that support electronic exchange for prior authorization and related workflows (with major API requirements taking effect primarily by January 1, 2027).
What works: separate PA work from “everything else.” A dedicated authorization work queue—with daily review, clear escalation rules, and standardized documentation expectations—prevents last-minute scrambles. Where possible, lean on eligibility and benefits transactions and operating rules: CMS describes how the X12 270 transaction is used to send eligibility benefit inquiries and the 271 transaction returns the response. Operationally, that means fewer phone calls, fewer “surprise non-covered” visits, and fewer downstream patient billing disputes.
Inconsistent documentation and medical necessity shortfalls
Documentation problems don’t only lead to denials; they can also create overpayment risk and retrospective take-backs. CMS’ documentation guidance is blunt: Medicare can deny payment for incomplete/illegible records; if there is insufficient documentation, there is no justification for the services or level of care billed, and paid claims can become recoverable overpayments. Documentation is also a known driver of payment integrity findings; for example, CMS reported that 77.17% of FY 2025 Medicaid improper payments were due to insufficient documentation (which CMS notes is generally not indicative of fraud).
What works: make documentation support easy at the point of care. Use specialty-specific templates that guide clinicians toward the facts payers care about (medical necessity rationale, relevant history/exam/MDM elements where applicable, clear orders, signatures, and linkage between assessment and plan). Then validate with targeted chart audits that map directly to denial reasons you see in remits.
Telehealth billing complexity and frequent policy shifts
Telehealth billing is often “mostly fine” until rules change—then denials spike because a modifier or place-of-service code is wrong. CMS’ telehealth FAQ states that practitioners should use POS 02 for telehealth provided other than in the patient’s home, or POS 10 for telehealth provided in the patient’s home, and notes that Medicare telehealth services provided to patients in their homes are to be paid at the non-facility rate starting January 1, 2024.
What works: build payer-specific telehealth rules into the workflow rather than relying on memory. A “cheat sheet” can help, but the stronger approach is to configure visit types and billing rules in the EHR/practice management system so the correct POS/modifier defaults based on how the visit was delivered. Re-audit quickly after payer policy updates.
Staffing shortages and fragile single points of failure
Even high-performing billing teams struggle when knowledge is concentrated in one or two people. Staffing pressure is widespread across healthcare operations; an MGMA Stat poll found 53% of medical group leaders cited “finding candidates” as their top staffing challenge (with compensation and retention following).
What works: design billing so it can survive a resignation or PTO season. That means documented SOPs, cross-training for the highest-risk tasks (charge entry rules, PA submission, denial appeals, refund logic), and role-based access so temporary coverage is possible without creating compliance risk. If outsourcing is considered, treat it as a structured vendor program (SLAs, audit rights, reporting cadence), not an emergency handoff.
Slow payments and uncontrolled accounts receivable
Not every delay is a denial—some are normal timing and payer processing—but you can’t manage what you don’t measure. CMS explains “payment floors” for Medicare clean claims: to check the payment status of a clean claim, providers should wait at least 14 days for electronic claims and 29 days for paper claims (processing time can vary).
What works: build a disciplined A/R operating rhythm. Use aging buckets, assign follow-up ownership, and run a short weekly “stale claims” huddle focused on the highest dollars and oldest claims. Also use claim status tools: CMS describes electronic claim status request/response transactions (276/277) as a way to check status without manual calls.
System interoperability problems creating data errors and duplicate work
When systems don’t “talk,” staff re-key information, and manual re-entry creates predictable mistakes (wrong subscriber ID, missing modifiers, mismatched diagnosis/procedure, etc.). Industry-wide benchmarking emphasizes the gains from automating eligibility and claim status workflows: CAQH’s key takeaways highlight that implementing electronic standards and operating rules for eligibility/benefit verifications and claim status inquiries could save over $15 billion annually across the healthcare industry. CMS also documents the standard purpose of the eligibility inquiry/response transactions (270/271), supporting the idea that automation is not just a convenience—it is the expected standard output of modern administrative infrastructure.
What works: reduce the number of “handoffs” where humans must re-enter data. Prioritize integration for (1) registration/demographics, (2) eligibility verification, (3) charge capture, and (4) remittance posting. If full integration isn’t possible, standardize inputs (consistent payer mapping, standardized plan names, required fields) and add pre-billing validation.
Data security and compliance risk in billing operations
Billing workflows routinely touch protected health information and financial data, so the downside of weak security is outsized: operational disruption, breach notification obligations, payer/vendor disruptions, and loss of patient trust. The HIPAA Security Rule requires “reasonable and appropriate” administrative, physical, and technical safeguards to protect electronic protected health information (ePHI). HHS also points to substantial increases in large breaches involving hacking and ransomware as a reason covered entities and business associates must ensure compliance with the Security Rule.
What works: treat billing systems like critical infrastructure. Use strong access controls (least privilege), MFA where available, logging, patching, secure backups, and staff training that specifically addresses billing-related phishing and vendor payment fraud. If data is handled by third parties, include security expectations in contracts and require auditable proof of controls.
Many practices try to fix revenue cycle problems by pushing harder on the back end (more appeals, more A/R calls). That helps, but it’s expensive because it treats the symptom.
A more resilient approach is to shift effort forward—into the first days of the patient and claim lifecycle—because that’s where many denials are created:
This is the operational difference between a team that is constantly reacting and one that steadily improves its first-pass yield.
Automation isn’t automatically beneficial; it pays off when it reduces preventable human re-entry and makes payer rules harder to “forget.”
Two areas are repeatedly highlighted as high-value:
Eligibility and claim status automation is often a “short path to ROI.” CAQH identifies eligibility/benefit verification and claim status inquiries as high-savings opportunities and estimates that fully electronic workflows can unlock substantial savings and reduce time spent on manual calls and follow-up. CMS materials reinforce that these workflows are built on standardized transactions and operating rules.
Computer-assisted coding can support consistency when it is implemented as assistance rather than replacement. AHIMA’s toolkit defines CAC as extracting and translating clinical documentation into code suggestions (ICD/CPT/HCPCS), positioning it as a structured support tool within a governed coding process. In practical terms, CAC can help teams keep pace with volume and reduce some omissions, but it still requires human validation—especially for complex cases, payer-specific rules, and medical necessity nuance (which is where denials often live).
Collections strategy works better when it matches how patients actually experience health care bills: “I didn’t understand it” and “I didn’t expect it to be that high” are common drivers of delayed payment and disputes.
Given that nearly half of adults report difficulty affording health care costs, patient communication needs to be clear, early, and flexible. Practices can reduce friction by simplifying statements (fewer codes, more plain language), offering multiple payment options, and proactively discussing patient responsibility when scheduling and at check-in—especially for HDHP patients who may owe large amounts before coverage applies.
Reminders can be effective when they are respectful and opt-in where required; peer-reviewed work on debt collection highlights that reminders (including text reminders) can improve timely payments. The operational key is to pair reminders with a frictionless way to pay (mobile-friendly, simple authentication, payment plans for larger balances) and a clear path to dispute resolution.
Billing operations should be designed with the assumption that credential theft, ransomware attempts, and vendor compromise are not hypothetical. The HIPAA Security Rule’s safeguard requirements (administrative, physical, technical) are the baseline. HHS points to increased large breaches involving hacking/ransomware as an ongoing signal that covered entities and business associates must stay aligned with Security Rule compliance—not as a one-time project, but as continuous risk management.
If you outsource any portion of billing, extend your control environment outward. That includes a current Business Associate Agreement (BAA), clear subcontractor rules, audit rights, and proof of controls (security attestations, incident response expectations, encryption practices, access logs). CMS also explicitly flags that risk varies based on geographic handling of electronic health information; covered entities should incorporate outsourcing-related factors into required risk analysis and risk management.
This post has been authored and published by one of our premium contributors, who are experts in their fields. They bring high-quality, well-researched content that adds significant value to our platform.
