Managing Outstanding Claims and Payer Follow-Up
Insurance follow-up begins when a claim needs attention after submission. Sometimes the payer has not processed it. Other times, the claim was paid incorrectly, denied, suspended for records, or processed but never reflected accurately in the provider's account. Accounts receivable (AR) aging helps teams see how long money has remained unresolved, but age alone can't explain what action is needed.
A strong follow-up process answers two questions together: Where is the claim in the payer's workflow? And what evidence or next action will move the account toward accurate resolution? This guide covers the records, calculations, tools, documentation, and judgment behind those questions.
Which Accounts Actually Need Follow-Up?
Insurance follow-up is the investigation and management of billed claims with outstanding payer-related activity. Follow-up staff check claim receipt and adjudication, respond to requests, correct errors through the appropriate process, dispute questionable decisions, verify payments, and keep unresolved items moving.
Accounts receivable is money owed to a healthcare organization and still recorded as outstanding. In a patient accounting system, a receivable may reflect insurance balances, patient balances, or other components. Insurance AR generally refers to the portion still expected from a payer, subject to the organization's reporting rules.
Aging groups outstanding balances according to elapsed time. It supports prioritization, staffing, management reporting, and identification of stalled claims. It does not establish whether a balance is collectible or even correctly assigned to insurance.
Who works these accounts? Insurance follow-up representatives, AR analysts, billing teams, denial specialists, and designated escalation groups may all participate. Coding, authorization, enrollment, HIM, contracting, and posting teams provide evidence or make corrections within their responsibilities. The precise division of work depends on the organization.
How Aging Is Measured and Why Definitions Matter
Common workqueues show 0–30, 31–60, 61–90, 91–120, and over 120 days. However, an organization's days-since-billing measure, an account's days since service, and a formal industry aging metric can produce different numbers.
HFMA's MAP Keys definition for aged billed AR generally ages hospital accounts from discharge and outpatient, ambulatory, and physician accounts from the date of service. It excludes unbilled accounts and active credit-balance accounts under its stated methodology. That definition should not be confused with a local follow-up queue that starts a clock on the original claim submission date or last action date. See the HFMA reference at the end of this guide.
A worked aging calculation
Consider an outpatient service performed July 10, with a report as of October 12 of the same year. The elapsed time is 94 days, placing the account in a 91–120-day bucket when using the date of service as the starting point. If its payer accepted the claim on September 25, it may have been in the payer's processing inventory only 17 days. Both measures are useful; they answer different questions.
Aging formulas should document the report as-of date, start-date field, inclusive or exclusive day-count convention, and bucket definitions. Otherwise, two analysts can produce different reports from the same accounts and both believe they are correct.
Reading an AR aging report
In this fictional portfolio, $36,000 (18%) is over 90 days old. That is a useful signal to investigate, but it does not tell us whether the balances are awaiting routine payer processing, held for medical records, denied, misposted, or incorrectly left in insurance AR. Aged receivables need classification before action.
The Records and Systems Behind Follow-Up
A single patient-account screen rarely tells the whole story. An analyst may need to match information across an internal billing system, clearinghouse, payer portal, claim-status response, and remittance record.
CMS explains that Medicare claim status can be checked through MAC portals, IVR, and electronic 276 requests / 277 responses. The newer CMS checking-claim-status fact sheet also discusses individual and batch approaches. These resources describe Medicare workflows; private-payer availability varies.
Know the claim's real milestone
A successful file upload isn't proof that a claim was accepted for payer adjudication. A clearinghouse acknowledgment is not the same as payer acceptance, and a payer claim-status response is not an EOB. If the payer cannot locate the claim, inspect the actual transmission and acknowledgment trail before reflexively submitting a duplicate.
A Practical Insurance Follow-Up Workflow
Step 1: Validate the account and its balance
Confirm patient/account identifiers, payer, date of service, original claim number, billed amount, service lines, prior payments, adjustments, and any secondary coverage. Check whether the remaining balance is correctly assigned to insurance. A balance created by a posting error isn't resolved by repeatedly contacting the payer.
Step 2: Trace claim submission and receipt
Check whether the claim was produced, transmitted, and accepted at the relevant stage. Retain the original submission date, clearinghouse claim identifier, payer acknowledgment, and any available payer claim/control number. When a claim is missing, identify which transmission stage failed rather than treating the entire process as one event.
Step 3: Determine the current payer status
Use approved portals, 276/277 responses, IVR, or payer contact. Distinguish not on file, pending, requested information, adjudicated, denied, paid, and adjusted statuses. Record the information source and status date. A vague note such as “claim processing” isn't enough for effective future work.
Step 4: Identify the action and its owner
Determine what will actually move the account forward. A missing clinical record may belong to HIM or the service department. A code question belongs with authorized coding staff. An enrollment issue may need payer enrollment support. A paid claim with an open balance may need posting research. Follow-up staff should not make unsupported clinical, coding, or contractual changes to clear an account.
Step 5: Check all deadlines before choosing a route
Review initial and corrected claim filing rules, appeal or reconsideration limits, request-for-information deadlines, and contract provisions. The applicable start date may differ by action and payer. Don't assume that a new payer call, resubmission, or pending claim automatically extends a deadline.
For example, Original Medicare Fee-for-Service generally has a one-calendar-year claim filing requirement from the date of service, subject to defined exceptions. Its first-level redetermination request generally must be filed within 120 days of receipt of the initial determination, with a stated presumption of receipt. These are different clocks and shouldn't be generalized to every payer.
Step 6: Take a supported action
Possible actions include providing requested documents securely, correcting and resubmitting a truly rejected claim, requesting reprocessing, appealing an adjudicated denial, researching an underpayment, or escalating an unresolved payer discrepancy. Choose the transaction type and channel that apply to the claim's status and payer rules.
Step 7: Record evidence and set a meaningful next step
Document what was verified, who supplied the information, claim/control identifiers, reference numbers, current status, documents sent, action taken, expected payer response, and the next action date. Sensitive account notes should follow privacy and organizational access policies.
Step 8: Confirm resolution rather than merely closing the task
A reference number, appeal submission, or promised reprocess is not payment. Verify the resulting status, corrected adjudication, remittance, account posting, and remaining balance. When payment was issued, check posting and EFT/ERA reconciliation before marking the insurance balance resolved.
Choosing Which Accounts to Work First
Oldest-first worklists are easy to produce but may be poor prioritization tools. A 91-day account facing an appeal deadline tomorrow may require more immediate action than a 180-day account with a documented future payer determination date. Likewise, an unposted payment might need internal investigation rather than another payer call.
Organizations may use financial value, aging, payer behavior, recovery likelihood, action deadlines, staffing, and contract terms in a formal prioritization model. This model must be governed and reviewed, particularly when automation routes accounts or applies dispositions.
Worked Examples: Status, Balance, and Follow-Up
Scenario A: The payer says paid, but $340 is still in insurance AR
An outpatient account shows $500 in charges, $100 contractual adjustment, $60 patient responsibility, and an open $340 insurance balance. A payer portal indicates the claim was paid $340.
Research: Locate the EOB/ERA and confirm the payer payment, service lines, claim number, and bank/EFT information. If the $340 was received but not applied to this account, route the issue to posting for identification and correction. If the remittance shows payment but no corresponding funds were received, investigate the EFT and deposit instead. The account should not be reduced through an arbitrary adjustment simply because the portal says “paid.”
Validation: Charges $500 = contractual adjustment $100 + patient responsibility $60 + insurance payment $340. The arithmetic supports the payer's adjudication, but receipt and posting still require evidence.
Scenario B: A claim aged 127 days but wasn't accepted until recently
A physician service dated June 7 appears on an October 12 report at 127 days old. The original outbound file was rejected due to an invalid subscriber identifier; the corrected initial claim was not accepted by the payer until October 3.
Research: Preserve the rejection trail and payer acceptance evidence; verify the applicable timely-filing date and whether timely-filing proof or an exception may be relevant. The claim's high AR age does not necessarily mean the payer has delayed adjudication for 127 days. It may instead indicate a front-end correction failure and a risk created before payer acceptance.
Action: Confirm the payer has the corrected claim, review the next status date, and escalate filing concerns within the organization's policy. Do not mark the issue as solely “payer pending” without documenting the original rejection.
Scenario C: A denied service line within a partially paid claim
A two-line claim billed $900. The payer's remittance reflects:
The $400 denial balance is not automatically patient responsibility. Review the actual group code, CARC, RARC, benefit information, and relevant contract terms. Determine whether the denial stems from an authorization, coding, medical necessity, coverage, or other requirement. Route the issue to the authorized owner and record any review/appeal deadline.
This is an intentionally simplified financial example. In actual remittances, remaining line amounts must be analyzed through the complete payer adjustment and responsibility data; don't invent an adjustment merely to force a zero balance.
Scenario D: Follow-up notes without progress
An insurer balance is reviewed on three occasions, each documented simply as “called payer, pending.” The balance moves from 45 to 92 days without an identified reason or next step.
A useful follow-up record would instead identify the payer claim number, confirmed processing stage, the reason for the hold, outstanding documentation, contact or portal confirmation, a reference number if supplied, and a specific review date. If the payer repeatedly misses stated response periods, an escalation may be appropriate under contract and organizational policy. Repeated touches are not the same as effective progress.
Common Problems and How to Investigate Them
Don't confuse moving a balance with resolving it
Changing an insurance balance to patient responsibility, issuing an unsupported write-off, or placing the account in an indefinite hold can make a workqueue smaller without establishing the correct financial disposition. The goal is accurate resolution, supported by payer data, authorized accounting treatment, and a reliable audit trail.
Measuring Follow-Up Performance Without Distorting the Picture
Aging distribution describes where balances sit by age. Net days in AR relates net receivables to average daily net patient service revenue under a defined reporting method. Denial rates, resolution time, appeal overturns, and cash recovery answer other questions. These measures shouldn't be used interchangeably.
For example, if $36,000 of $200,000 billed insurance AR is aged over 90 days, the share is 18%. This ratio alone can't show collectability or whether payer delays are increasing. Analysts should review payer mix, balances by status, submission defects, and reporting changes before interpreting movement.
A month-to-month improvement can also be misleading if older accounts were written off, shifted to patient AR, excluded through a report-filter change, or swept into a new workqueue. Financial reporting should reconcile such movements, not assume that falling balances always represent more collected cash.
When a Claim Problem Becomes an Operational Pattern
One missing claim may be an isolated transmission issue. Twenty claims from the same billing provider or batch all showing “not on file” deserve a broader check. An analyst can sample affected claims, compare identifiers and transmissions, document the common feature, and raise the finding with the appropriate billing, enrollment, clearinghouse, or systems team.
Other patterns include payer responses repeatedly requesting the same already-submitted records, claims stuck in a particular status, denials clustered by service or plan, and automated follow-up rules closing accounts before the promised payer action occurs.
Document what the evidence demonstrates and separate it from a possible explanation. A cluster of aged claims suggests a problem; it does not prove a payer violation, system defect, or employee error. Organization-wide root-cause investigations, contract disputes, and automated-control remediation warrant more extensive treatment in the dedicated Denial Trends, Revenue Integrity, and Automation guides.
Insurance Follow-Up Reference Checklist
Use this checklist as an educational reference alongside organizational procedures:
- ☐ Confirm the correct patient account, payer, claim, date of service, and open insurance balance.
- ☐ Review charges, payments, adjustments, responsibility assignments, and prior follow-up history.
- ☐ Locate original/corrected claim submission and acknowledgment evidence when relevant.
- ☐ Identify the payer's current processing status and the date/source of the response.
- ☐ Review the EOB/ERA for any adjudicated amount, denial reason, and prior-payer details.
- ☐ Identify any filing, appeal, record-response, or contract deadline before taking action.
- ☐ Determine the actual unresolved issue and which team is authorized to address it.
- ☐ Record evidence, claim identifiers, communication references, and the action performed.
- ☐ Set a specific next action date or appropriate escalation, rather than an indefinite hold.
- ☐ Verify payment, reprocessing, adjudication, posting, or final disposition before closing the account.
A useful account note should let the next person continue the investigation without starting over. It should make clear what is known, what has been checked, what remains unanswered, who owns the next step, and when that next step is due.
References and Further Learning
These resources support the definitions and examples in this guide. Check the source's scope, effective date, and applicable payer or organization requirements before using it operationally.
References
Additional Learning
Educational Disclaimer
Revenue Cycle Uncovered is an independent educational resource. Content is provided for general informational purposes and does not represent the policies, practices, or positions of any employer or organization. Workflows, payer requirements, regulations, and operational practices may vary. Information should be independently verified when applied to specific situations.