Every CFO and revenue cycle leader knows it: your P&L looks healthy on paper, but cash in the bank tells a different story. Claims are “technically billed” yet sit unpaid for months. Payer reps give conflicting answers. Call notes are sketchy. Patient balances drift into bad debt. This is not a technology problem alone. It is an operational discipline problem inside accounts receivable (A/R) management.
In a typical mid‑size medical group or hospital outpatient department, 20–30 percent of A/R often lives in the 90+ day bucket. That drag affects days in A/R, cash forecasting, capital planning, and even clinician satisfaction. The good news is that most of these issues are fixable when you treat A/R as a managed process, not a “back office” afterthought.
This article lays out a practical framework for leaders who want more than generic advice. You will see how to structure your A/R follow‑up program, how to arm callers with real process knowledge, how to fix documentation and call quality, and how to use data to keep everyone honest. The focus is simple: fewer surprised write‑offs, faster cash, and less operational chaos.
Build an A/R Operating Model Instead of “Working the List”
The most common A/R failure pattern is simple. Teams “work the oldest claims” from a static report, make some calls, key a few notes, then repeat next week. There is no explicit operating model: no clear ownership, no standardized cadence, no feedback loop to front‑end or coding teams. This creates busy work without measurable impact.
A modern A/R operating model should answer five questions very clearly.
- What is the primary objective for this month and this quarter: days in A/R, 90+ day percent, net collection percentage, or cash vs budget?
- Who owns which buckets by payer, facility, specialty, and balance size?
- What is the follow‑up cadence by risk segment, for example 7 days, 14 days, or 21 days between touches?
- How do accounts move between statuses (dispute, appeal, rebill, patient responsibility, bad debt) and who authorizes that movement?
- Which metrics drive behavior and appear on weekly scorecards?
Practical framework: design your A/R model as a set of “service level agreements” (SLAs) and playbooks.
- Define target days to first follow‑up by payer and claim type, for example 20 days for commercial inpatient, 10 days for Medicaid outpatient, 5 days for high‑dollar trauma.
- Set maximum “idle days” where an account can sit in any status without activity, for example no more than 15 days between touches for any account over 2 500 USD.
- Assign primary and secondary owners for each payer segment so there is no ambiguity when someone is out or leaves the organization.
Key KPIs for this section:
- Days in A/R, overall and by payer
- Percent of A/R over 90 days (goal often less than 15–18 percent for healthy practices)
- Worked accounts per collector per day, segmented by payer
- Average days from first bill date to first payer contact
When leadership codifies this operating model and publishes it, A/R is no longer “whoever has time will make some calls.” It becomes a transparent process where you can diagnose bottlenecks and hold people accountable.
Upgrade A/R Callers from “Phone Operators” to Payer Problem‑Solvers
Many organizations put their least experienced staff onto A/R calling because it is perceived as low‑skill: dial, ask for status, document, hang up. In reality, this is where you either rescue or permanently lose revenue. Callers who do not understand payer policies or denial patterns will accept incorrect answers, miss opportunities to correct errors on the fly, and escalate far too little.
To turn callers into problem solvers, you need three pillars: payer‑specific training, issue‑based call guides, and decision authority.
Payer‑specific training and routing
Having everyone call everyone produces shallow knowledge. Instead, route work by payer and sometimes by program (for example Medicare Advantage vs traditional Medicare vs Medicaid plans).
- Create short payer playbooks that include: appeal time frames, common denial reasons, portal URLs and what is available there, escalation paths, and typical documentation requirements.
- Keep these playbooks in a shared knowledge base and update them monthly from denial and appeal trends.
- Aim for callers to become experts on 3–5 payers, not generalists on 20.
Issue‑based call guides
Scripts alone are not enough. Callers need branching decision trees that reflect how payers actually behave. For example:
- If status is “no claim on file” and submission date is less than X days ago, then verify clearinghouse trace and recheck in 72 hours instead of blindly resubmitting.
- If denial is “coordination of benefits” ask the three specific questions that usually reveal whether the payer actually attempted to contact the patient.
Build these as templates in your collections system so that when a caller selects a denial reason or payer code, the application surfaces recommended questions and data points to capture. Over time this standardizes what gets documented and makes your appeals more effective.
Decision authority at the edge
Callers who must escalate every minor issue to supervisors waste time and let accounts age. Give experienced staff limited authority to:
- Initiate corrected claims when the change is minor and well defined, for example modifier or place of service corrections.
- Trigger standard appeal packets for pre‑defined denial types.
- Move accounts to patient responsibility when payer documentation clearly supports that status.
Document what they can and cannot do in a “decision grid” to avoid both overreach and hesitation.
Fix Documentation: Bad Call Notes Are a Hidden Source of Lost Revenue
Poor call documentation is one of the most expensive but least visible A/R problems. Notes such as “spoke with payer, resubmit” or “pending” tell you almost nothing. When the same claim resurfaces 45 days later, the next caller must restart the investigation from scratch. Repeated calls on the same account annoy payers and burn labor without improving yield.
To fix this, you need structured documentation, real‑time entry expectations, and systematic auditing.
Structured note templates
Replace free‑form comments with required fields tied to the type of interaction:
- Payer contacted (name, department, reference number, call ID)
- Precise status (for example “denied for medical necessity after first level review” rather than “denied”)
- Action taken during the call (fax sent, appeal initiated, claim re‑opened, records requested)
- Next action and due date (who does what by when)
Configure your system so accounts cannot be moved out of the worklist without these fields completed. This feels burdensome for a week and then becomes routine. The payoff comes when different agents can pick up where others left off.
Real‑time entry standard
Require that notes be entered during the call or immediately after ending it. Delayed documentation leads to missing details and incorrect re‑construction of events. Callers will occasionally resist this if they are measured only on volume. Balance their metrics:
- Track “notes completeness” and random accuracy checks alongside “dials per hour” or “claims touched per day”.
- Reward both speed and quality, not speed alone.
Audit and coaching program
Establish a simple but relentless audit cadence.
- Each week, sample 5–10 accounts per caller: review notes, listen to recorded calls where available, compare outcome with what should have happened.
- Score on criteria such as clarity, completeness, and whether the next step is obvious and scheduled.
- Use findings in short coaching sessions instead of treating audits as punitive.
Over time, your documentation standard becomes a powerful asset. It supports compliance, reduces rework, and gives you strong evidence in payer disputes and internal root cause work.
Embed Call Quality and Ethics to Protect Revenue and Relationships
Call quality is not only about politeness. It affects how much information callers extract from payers and patients, how often they can negotiate informal solutions, and whether they raise compliance risks. Aggressive or sloppy calls can lead to complaints, damaged payer relationships, and even audits if agents misrepresent services or coverage.
A structured call‑quality program should cover three dimensions: tone and etiquette, technical accuracy, and compliance.
Tone and etiquette that support resolution
Teach callers to:
- Open with clear identification: who they are, which provider they represent, and which claim or patient they are discussing.
- Use neutral language when encountering resistance, for example “Help me understand what is still missing” instead of “You already have that.”
- Close each call by restating what the payer or patient has committed to and when.
This reduces confusion and creates surface area for escalation later. A calm, structured caller is more likely to be taken seriously when they seek a supervisor or clinical reviewer.
Technical accuracy and avoiding misstatements
Train callers on what they must never guess about:
- Coverage determinations or benefit interpretations that cross into clinical advice.
- Guaranteed payment statements, for example claiming that “insurance will definitely cover this” when not confirmed.
- HIPAA‑sensitive details shared with unauthorized parties.
Use call‑listening sessions to highlight strong examples and gently correct missteps. It is cheaper to retrain now than to handle an OCR complaint or payer audit later.
Compliance and documentation alignment
Ensure that your call‑quality standards align with documentation expectations. If a caller promises to send specific records, the note must reflect exactly what was promised and where it was sent. If a patient agrees to a payment plan, the terms should be written in the system and, where appropriate, confirmed in writing to the patient.
Call quality is often viewed as a “soft” topic. In reality, it determines how often your team can negotiate extensions, get exceptions approved, or reverse denials informally. Soft skills have hard revenue impact.
Use Analytics to Prioritize, Not Just Report After the Fact
Many organizations have A/R dashboards but use them mainly as rear‑view mirrors. Leaders look at days in A/R and 90+ day percentages once a month, then urge teams to “work harder.” Analytics should drive which accounts you touch today, not only describe what happened last month.
Start by segmenting A/R into actionable risk buckets rather than simple aging buckets.
- By collectability:</strong net expected reimbursement, considering contract rates and past experience with that payer/product.
- By denial risk:</strong claim types historically prone to denials, such as high‑cost imaging or certain surgeries.
- By time sensitivity:</strong appeals approaching deadlines, timely filing limits, medical record request due dates.
Then build worklists that integrate these risk factors. For example, a tier 1 worklist might show high‑dollar accounts with appeal deadlines within 15 days. A tier 2 worklist might show mid‑dollar accounts with missing documentation requests. A tier 3 worklist covers low‑dollar clean claims simply awaiting status checks.
Key analytics questions to answer weekly:
- What percentage of high‑value claims have had at least one payer contact within the last 30 days?
- Which denial categories are contributing most to new 90+ day A/R, and are those denials preventable upstream?
- Which payers show abnormal payment lag trends compared to contract terms or historical norms?
Use these insights to adjust staffing and workflows. For instance, if a specific payer’s lag has doubled in the last quarter, you might dedicate a focused team to that payer for 60 days, refine the payer playbook, and escalate contractually if needed.
Analytics should also flow upstream. Denials that are consistently unresolved in A/R often have their root in eligibility, authorization, or documentation. Feed denial reason codes back to front‑end and coding leaders each month with concrete examples and projected revenue impact if fixed.
Decide What to Centralize, What to Automate, and What to Outsource
Not every component of A/R follow‑up belongs in‑house. At the same time, indiscriminate outsourcing can create distance between A/R and the rest of the revenue cycle. Leadership needs a deliberate sourcing strategy that considers complexity, variability, and scale.
Centralize complex work; standardize simple work
High‑complexity activities such as clinical appeals, payer grievance processes, and negotiation on large underpayments are usually best handled by a centralized, experienced team within your organization. These accounts often require access to physicians, legal counsel, and contract management data.
Simpler, repetitive tasks such as status checks on low‑dollar clean claims, follow‑up on standard documentation requests, or calling on routine coordination of benefits issues can be standardized and either automated or delegated.
Automation opportunities
Before you think about outsourcing, examine what can be automated.
- Automated status checks through payer APIs or clearinghouse feeds, reducing manual calls for claims that are simply in process.
- System rules that automatically route accounts to the right worklist based on status, denial code, and aging.
- Trigger‑based tasks: when an electronic remittance advice posts a specific denial code, the system opens a follow‑up task with a pre‑populated appeal template.
Automation is not a replacement for skilled staff. Instead, it removes the “noise” so human effort focuses on accounts where nuanced judgment is needed.
When outsourcing makes sense
Outsourcing portions of A/R can be effective if you:
- Retain visibility through shared dashboards and agreed‑upon KPIs, for example cash collected, resolution rate, and impact on aging.
- Define clear boundaries of work: which payers, account sizes, and denial types the partner will handle vs those kept in‑house.
- Integrate their workflows with your denial prevention efforts so learnings are not trapped in a vendor’s system.
Whether work is internal or external, the same standards should apply: structured documentation, call quality, analytics‑driven prioritization, and alignment with your overall revenue strategy.
Turn A/R Into a Continuous Improvement Engine, Not a Fire Drill
Most organizations treat A/R improvements as projects. They launch a 90‑day “clean‑up” on old buckets, bring in temporary staff, see cash spike, then slowly drift back to prior performance. To sustain gains, you must embed A/R into your continuous improvement cycle.
Consider a simple monthly rhythm.
- Week 1:</strong Review prior month A/R metrics and denial trends with RCM leadership, including front‑end, coding, and patient access leaders.
- Week 2:</strong Identify 2–3 high‑impact issues (for example a payer’s new prior authorization rule) and assign owners to design fixes.
- Week 3:</strong Pilot revised workflows or documentation standards on a subset of accounts, with tight feedback loops.
- Week 4:</strong Decide what to standardize across the enterprise and update training, payer playbooks, and system rules accordingly.
In parallel, keep a short list of “vital few” A/R KPIs on every executive dashboard: days in A/R, 90+ day percent, cash vs budget, denial rate by category, and net collection percentage. Review these alongside clinical and operational metrics so A/R is not seen as isolated.
When your teams see that insights from their daily work lead to real system changes, engagement rises. A/R stops being a never‑ending backlog and becomes an engine that constantly feeds lessons back into eligibility, scheduling, authorization, documentation, and coding.
Driving Impact: Cash, Predictability, and Strategic Options
Stronger A/R management is not just about “cleaner books.” It makes your organization more resilient and more strategic. Lower aging and higher net collections improve cash on hand, which supports capital investments, staffing stability, and the ability to weather payer or volume shocks. Clear documentation and analytics reduce compliance risk and defensive audits. Better call quality and workflows reduce burnout in your revenue cycle teams.
If you lead an independent practice, a multi‑specialty group, a hospital revenue cycle, or a billing company, now is the time to treat A/R as a core capability, not a clean‑up task. Start with one or two areas where you can get quick traction: redesign call note templates, create payer playbooks for your top five payers, or build risk‑based worklists for high‑value accounts. As you see improvements, extend the same discipline to the rest of your portfolio.
If you want an outside perspective on how to redesign your A/R workflows, train your follow‑up teams, or evaluate where automation and outsourcing make sense, you can contact our team. A short, focused assessment can often reveal hidden opportunities that internal reports have normalized over time.
References
