Epic Revenue Cycle Workqueues: Reducing Backlogs, Denials, and A/R Delays

Epic revenue cycle workqueues can turn thousands of billing exceptions into structured, actionable work. But when routing rules, ownership, prioritization, or upstream workflows are poorly aligned, those same workqueues can become places where unresolved revenue quietly accumulates.

For large health systems, the problem is rarely that a workqueue exists. The larger issue is often why so many accounts are entering the queue, whether the right team receives them, which accounts are worked first, and whether recurring defects are ever corrected at their source.

A University of California audit of Epic workqueue management provides a useful real-world example. It identified opportunities in aging and inactive work queues, supervisor assignment, escalation, timely filing exposure, obsolete work queues, and governance.

The audit also confirmed that encounters can satisfy the criteria for multiple work queues, making coordinated oversight important in complex revenue-cycle environments.

Effective Epic revenue cycle optimization therefore should not stop at clearing today’s backlog. The goal is to reduce avoidable work entering the system, route legitimate exceptions correctly, prioritize them according to financial and time risk, and connect workqueue performance to denials, A/R, and cash outcomes.

What Are Epic Revenue Cycle Workqueues?

Epic workqueues are rules-driven mechanisms used to surface accounts, encounters, or other records requiring review or intervention. The University of California audit describes revenue cycle workqueues supporting activities across areas such as authorization, charge capture, claims processing, billing, accounts receivable, appeals, and denials. It also notes that an encounter meeting multiple workqueue rule criteria can appear in multiple queues.

Within Epic’s financial environment, public documentation identifies Hospital Billing and Professional Billing functionality and refers to Resolute as Epic’s billing module. Epic’s public claims documentation also supports standard electronic transactions associated with claims submission, claim acknowledgments, claim status, supporting information, and remittance processing.

That makes the WQ environment more than a collection of staff task lists

It is part of the operating architecture determining:

• which exception receives attention;
• which team owns the next action;
• when an account becomes actionable;
• how financially important work is prioritized;
• whether unresolved work is escalated; and
• whether recurring problems generate operational improvement.

When those decisions are poorly designed, revenue can remain visible inside the system without progressing efficiently toward resolution.

Why Do Epic Revenue Cycle Backlogs Keep Growing?

A large workqueue balance is often treated primarily as a staffing problem. The organization sees 20,000 unresolved items, increases productivity targets, shifts staff between teams, or creates a temporary backlog initiative. That may reduce inventory temporarily.

It does not necessarily stop the backlog from returning.

Persistent Epic revenue cycle backlog requires revenue cycle leaders to examine both sides of the workload equation: How quickly is work being resolved? And why is the work being created?

The second question is often more valuable.

A claim-edit queue may grow because required claim information is repeatedly missing. A coding-related queue may reflect an upstream documentation or coding workflow problem. 

A denial queue may repeatedly receive the same authorization-related issue. An insurance follow-up queue may contain genuinely actionable accounts mixed with claims still moving normally through payer adjudication.

When every exception is handled as a one-off account problem, the revenue cycle absorbs the same manual work repeatedly.

HFMA’s Claim Integrity guidance reinforces this distinction. It states that denial-producing issues can originate across the revenue cycle and emphasizes standardized data and metrics for identifying where processes and underlying issues are creating avoidable denials and rework.

The operational objective should therefore shift from:

“How do we work the WQ faster?” To: “Why did these accounts require manual intervention, which exceptions are preventable, and what has to change upstream?”

How to Optimize Epic Revenue Cycle Workqueues to Reduce Backlogs, Denials, and A/R Delays 

1. Reduce Workqueue Inflow Before Adding More Capacity

Suppose a team resolves 1,000 WQ items each day while 1,100 new items enter. Even a meaningful productivity improvement may only slow backlog growth.

Sustainable optimization starts by separating work into two categories:

• Legitimate exceptions require efficient intervention because some situations genuinely need staff judgment, payer contact, documentation review, coding review, or escalation.
• Avoidable exceptions should be reduced by correcting the condition that repeatedly produces them.

For example, a recurring claim-related error should not automatically become permanent collector work. 

Teams should determine whether the source lies in registration data, coding, charge capture, documentation, claim creation, payer-specific requirements, interface behavior, or local configuration.

This approach is especially important for denials. HFMA notes that denial prevention and resolution depend on understanding where across the revenue cycle the underlying defect occurs rather than concentrating only on downstream rework.

Increasing WQ output is useful. Reducing unnecessary WQ creation is more scalable.

2. Inventory and Rationalize the Workqueue Environment

Before changing individual Epic Resolute workqueues, health systems should establish an enterprise-level WQ inventory. At minimum, leadership should know:

• WQ purpose;
• business owner;
• supervisor or escalation owner;
• qualifying logic;
• incoming volume;
• current inventory;
• associated dollar balance;
• aging distribution;
• resolution rate;
• upstream dependency;
• downstream dependency;
• escalation process; and
• whether the WQ is still operationally necessary.

Large health systems can accumulate queues over years of Epic changes, payer changes, organizational restructuring, acquisitions, new service lines, departmental requests, and temporary projects.

Over time, some queues may become redundant, inactive, poorly owned, or misaligned with the current operating model.

The University of California audit found 778 work queues with zero activity during the audit scope and identified incomplete monitoring associated with aging or inactive queues and unassigned supervisors.

A separate Impact Advisors Epic optimization case reported 688 back-end WQ redesign changes, including 217 deactivations and enhanced WQ scoring for 294 queues. 

Those figures represent one consulting engagement, not an industry benchmark, but they illustrate how significant WQ rationalization can become in a mature environment.

Deactivation should never be arbitrary. Before retiring a queue, teams should validate its dependencies and confirm that required accounts will continue to reach the appropriate workflow.

3. Establish Ownership and Escalation for Every Financially Important Queue

A revenue cycle work queue should answer three operational questions:

• Who works it?
• Who is accountable for its performance?
• What happens when an account remains unresolved?

Assignment without escalation is not complete ownership.

The UC audit found that person-assigned revenue cycle work queues without a supervisor had accounts that spent an average of 121 days across various revenue cycle work queues, compared with 102 days where a supervisor was assigned. 

These are UCSF-specific observations and should not be interpreted as industry benchmarks, but they demonstrate the relationship between governance and unresolved work.

The same audit identified risks involving claims approaching filing deadlines and recommended formal timeliness, monitoring, escalation, and prioritization processes.

For enterprise organizations, ownership should generally exist on two levels.

Revenue cycle operations should own the business process, performance expectation, exception handling, and escalation model.

Epic application teams should support approved build, routing, testing, configuration, and technical changes.

This prevents a common failure mode in which an operational problem is assumed to be an Epic problem, or a configuration problem is managed indefinitely through additional manual labor.

4. Prioritize Epic A/R Workqueues by Financial and Time Risk

Not every open account has equal financial urgency.

A $100 account awaiting normal payer adjudication should not necessarily receive the same attention as a high-dollar claim approaching a filing or appeal deadline. Depending on the specific workflow and local Epic configuration, useful prioritization considerations may include:

• outstanding balance;
• account age;
• payer;
• claim or denial status;
• timely filing exposure;
• appeal deadline;
• expected next action;
• previous follow-up;
• high-dollar or strategic account classification; and
• other organization-defined risk factors.

Impact Advisors recommends WQ scoring that considers factors such as dollar value, timely filing and appeal deadlines, and payer type, while also emphasizing that prioritization is most useful when underlying WQ inventory is manageable. 

This represents consulting practice rather than a universal Epic requirement.

The distinction is important: Routing determines where work goes. Prioritization determines what gets worked first. An accurately routed account can still become a financial loss if lower-risk work continually takes precedence.

5. Separate Pre-Bill Backlogs From Post-Bill A/R

Revenue cycle leaders should avoid treating every aging WQ as one A/R problem.

An account that has not yet reached claim submission has a fundamentally different issue from a claim that was accepted for adjudication and remains unpaid.

HFMA provides useful standard definitions for separating these stages. Discharged Not Final Billed (DNFB) represents discharged accounts that have not yet reached final-billed status.

Final Billed Not Submitted to Payer (FBNS) measures gross dollars from initial 837 claims held by edits in the claims-processing workflow and not yet successfully submitted to the payer. 

HFMA specifically includes claims rejected during the submission process in FBNS and distinguishes those rejections from denials.

Post-bill A/R should then be analyzed through measures such as A/R aging and Net Days in A/R. HFMA’s MAP Keys use aging categories including 0–30, 31–60, 61–90, 91–120, and greater than 120 days.

A practical diagnostic model looks like this:

X12’s Claim Status Category Codes make the rejection-versus-denial distinction particularly clear. An A3 status indicates that the claim was returned as unprocessable and was not entered into the adjudication system, whereas F2 represents a finalized denial after adjudication.

That distinction matters operationally because the remedy, owner, metrics, and root cause can be completely different.

6. Use Denial Workqueues for Recovery and Prevention

An Epic denial management workflow should do more than distribute denied accounts to collectors.

It should create feedback capable of preventing the next denial. HFMA defines standardized denial measures around actionable denials and recommends metrics including:

• initial denial rate;
• primary denial rate;
• denial write-offs;
• time from initial denial to appeal;
• time from initial denial to claim resolution; and
• percentage of initial denials overturned.

That produces two parallel responsibilities.

Recover the Account

Staff needs to determine what happened, identify the appropriate corrective or appeal action, obtain necessary information, and pursue resolution according to payer and organizational requirements.

Correct the Source

Revenue cycle leaders should aggregate denial information to identify repeat patterns by variables such as payer, reason, department, service line, coding category, authorization process, or other meaningful operational dimensions.

Electronic remittance data can support that analysis.

CMS explains that ERAs use Claim Adjustment Group Codes, Claim Adjustment Reason Codes (CARCs), and Remittance Advice Remark Codes (RARCs) to communicate responsibility and explain payment adjustments. CARCs explain financial adjustments, and RARCs can provide additional detail.

However, not every CARC/RARC combination represents a denial. These codes communicate adjustments more broadly.

Organizations should therefore normalize applicable remittance and denial information and apply consistent denial definitions before using those codes for denial analytics.

The goal is to turn the denial WQ from a rework destination into a revenue-cycle defect detection system.

7. Reduce Manual Claim-Status Work Where Electronic Status Is Available

A/R teams can lose capacity when staff manually check claims that are simply progressing through normal payer processing.

Epic’s public claims documentation supports X12 276/277 claim-status exchange along with 837 claim submission, claim acknowledgments, and 835 remittance processing.

CAQH CORE describes the 276/277 transaction as the standard electronic process through which providers request claim status and health plans respond. Its current operating-rule material also states that electronic claim-status infrastructure is intended to reduce manual follow-up.

Where payer connectivity, organizational workflows, and local configuration support it, health systems can use electronic status information to distinguish:

Claims that are progressing normally from claims that genuinely require human intervention.

This supports a more exception-driven A/R model.

Collectors should spend more of their time on accounts requiring judgment, payer interaction, correction, documentation, escalation, or appeal, not repeatedly checking claims that do not yet require action.

The CAQH Index, published in February 2026, estimates a remaining $21 billion industrywide savings opportunity from fully automating manual and partially manual administrative transactions. 

That estimate spans administrative transactions broadly; it is not an Epic-specific or claim-status-only savings estimate.

8. Apply Automation and AI After the Workflow Is Stable

Automation cannot compensate for unclear ownership or incorrect routing logic.

Automating an unstable workflow may simply move unnecessary work faster.

Organizations should first establish:

• accurate routing;
• appropriate exception criteria;
• data quality;
• clear ownership;
• prioritization;
• escalation;
• reporting; and
• governance.

Then automation and AI can reduce repetitive intervention.

Epic is already extending AI into revenue cycle operations through Penny. In February 2026, Epic reported that more than 200 organizations were using Penny for professional billing coding and that many were seeing more than a 20% reduction in coding-related denials. 

Epic also reported that organizations using Penny for medical-necessity denial appeals were creating letters 23% faster. These are Epic-reported customer outcomes, not guaranteed industry benchmarks.

Epic’s current product information also describes Penny functionality for operational and revenue-cycle workflows, including professional billing denial appeal drafting.

AI-generated or AI-assisted appeal content should remain subject to the organization’s appropriate review, validation, compliance, and governance controls.

The larger principle remains the same:

Do not automate the backlog before understanding what created it.

Before vs. After Epic Revenue Cycle Workqueue Optimization

Epic workqueue optimization is not simply about reducing the number of open accounts. 

The goal is to create a more controlled operating model in which exceptions are routed appropriately, financially important work receives timely attention, recurring problems are addressed at their source, and leadership has better visibility into WQ performance.

The desired outcome is not simply a smaller workqueue. 

It is a revenue cycle in which the right account reaches the right team, higher-risk work receives appropriate priority, and recurring exceptions are reduced before they create another backlog.

Strengthen Epic Revenue Cycle Performance With CapMinds

CapMinds helps healthcare organizations move beyond temporary Epic workqueue cleanup toward sustainable Epic revenue cycle optimization.

Our approach connects Epic technical configuration with the operational and financial processes behind it. That means assessing workqueue architecture, routing, and ownership; identifying recurring claim, denial, and A/R bottlenecks; improving prioritization and reporting; analyzing opportunities for automation and integration; and helping revenue-cycle and Epic application teams establish a governance model that prevents the backlog from rebuilding.

For hospitals, academic medical centers, enterprise physician organizations, multi-hospital systems, and large ambulatory networks, the objective is not simply fewer WQ items.

It is a revenue cycle in which the right exception reaches the right team at the right time and recurring defects are corrected before they create the next backlog.

Ready to reduce Epic revenue cycle backlogs, denial rework, and aging A/R? Talk to CapMinds about an Epic Revenue Cycle Optimization assessment.

Schedule a Strategy Call