The IRS Collection Queue: Where Unassigned Cases Wait

Clients tell me the IRS went quiet. The letters stopped. Nobody called. They wonder whether the IRS forgot about them.

Usually it did not forget. The case moved into the Collection queue, and the queue is a quiet place. Understanding what it is, and what it is not, keeps you from making two expensive mistakes: assuming the problem went away, or panicking about enforcement that is not actually coming yet.

What the queue is

IRM 1.4.50.8.3 (rev. 2025-04-01) defines it in a sentence: the queue is an electronic file holding unassigned collection cases. Cases in the queue are prioritized for selection. They carry the IDRS assignment number AOTO7000.

Cases come into the queue from both ACS and Field Collection. Some come directly from notice status. IRM 5.1.20.3.2 (rev. 2024-10-07) lists case types that bypass ACS and go to the queue, including certain special noncompliance cases, certain delinquent return case codes, innocent spouse cases with a particular freeze code and any installment agreement needing financial review.

A queue account shows status 24 on the IRS's systems. IRM 5.1.20.3.2 refers to cases whose last Master File status equals status 24 as cases with an embedded queue assignment.

How a case gets pulled out

Field Collection group managers pull cases from the queue using GM Case Assignment in the ENTITY system. IRM 5.1.20.4.1 calls that the primary method managers use to assign inventory from the queue to Revenue Officers.

What a group can see depends on zip code. IRM 1.4.50.10 says the cases available to a group are based on the group's zip code assignments. ENTITY presents them in priority order, reprioritized weekly, with a priority level and one of five predictive values. Managers are told to assign the highest priority available for each type of case.

In other words, getting pulled from the queue is a competition you did not enter. Your case is ranked against every other unassigned case in your area. If yours ranks below what the local group can handle, it waits. I explain the ranking rules in How Collection Cases Are Assigned to Revenue Officers.

What TIGTA found about the queue

The Treasury Inspector General for Tax Administration audited this in Report No. 2017-30-069, issued September 25, 2017. The numbers are old, but the findings explain the design.

TIGTA reported that during fiscal year 2015 the Inventory Delivery System routed approximately 74 percent of new modules to ACS, 18 percent to the queue, 6 percent directly to the field and 2 percent to Compliance Services Collection Operations.

It found that as of September 2015 the queue contained nearly 3.3 million unassigned balance due modules valued at $57.5 billion, plus 1.4 million unassigned modules valued at $8.4 billion in shelved status.

And it found that although IRS procedures describe the queue as unassigned field inventory, IRS management told TIGTA the queue is actually potential inventory for all collection operations. Since fiscal year 2010, TIGTA reported, less than 20 percent of queue inventory on average was assigned to the field, while 29 to 34 percent was transferred to ACS.

TIGTA also reported that collection cases can remain unassigned within an active or inactive inventory for up to 10 years, and that cases can pass through the Inventory Delivery System more than once because of the annual queue review or when a new module becomes available.

Quiet is not the same as safe

The same TIGTA report found that cases waiting in the queue or shelved are not subject to the same number of routine systemic enforcement actions and checks as cases routed to ACS or the field. That is why things go quiet.

But the debt keeps growing. Interest and the failure to pay penalty continue to accrue. Refunds can still be offset. A federal tax lien that was already filed stays filed. And every year you file a new return or create a new balance, a new module can send the whole account back through the routing system, which may land it in ACS or with a Revenue Officer.

So the right reaction to a quiet queue is not relief. It is planning. A case in the queue is a case you can often resolve on your own terms, through a payment plan or another collection alternative, before someone else decides the timing for you.

Cases that cannot go into the queue

Not every case is allowed to wait. IRM 5.1.20.3.3 lists cases that cannot be moved to the queue, including Non Master File accounts, IRS employee accounts, accounts in the Federal Employee/Retiree Delinquency Initiative, refund hold cases, accounts under Appeals jurisdiction for a Collection Due Process or equivalent hearing and any case with a module whose collection statute expires within six months.

IRM 1.4.50.10.2 adds a longer list that applies when a group is over its inventory targets and a manager wants to send cases back. Even then, managers may not return cases that are accelerated issuances, cases with no lien determination unless the history explains why, cases with fewer than 6.5 months (195 days) before the collection statute expires, cases awaiting pending enforcement such as an outstanding levy or summons, in-business trust fund cases, certain trust fund cases with less than a year on the assessment statute and no trust fund determination, and cases with taxpayer contact in the last 6 months.

That list is revealing. An open business that is not paying payroll taxes does not get parked. A taxpayer an officer has recently talked to does not get parked. An account with pending enforcement does not get parked.

When a case goes back to the queue

Cases also return to the queue from the field. When a Revenue Officer leaves or a group is overloaded, IRM 1.4.50.10.3 tells the manager to review the departing officer's inventory and identify cases that can be resolved before the officer leaves, returned to the queue, or reassigned to others, with the transfers normally completed within 45 days.

Office-based tax examiners in Field Collection can also send certain corporate cases back with managerial approval. IRM 1.4.50.10.5.1 lists examples such as business cases that cannot be fully resolved and show no signs of continuing operations or employees.

From ACS, the path runs through the investigation units. IRM 5.19.5.4.11.5 describes the I4 unit as the last stop before a case is closed as currently not collectible, transferred to the field or transferred to the queue, and I7 as the unit for cases requiring transfer to the queue.

The queue and your collection statute

The collection statute expiration date shapes the queue more than most people realize. Cases with a module expiring within six months cannot be moved into the queue under IRM 5.1.20.3.3, and group managers cannot return cases with fewer than 195 days left on the statute.

Coming out of the queue, the same clock matters. IRM 1.4.50.10 says modules with less than six months remaining on the collection statute normally will not be assigned to a Revenue Officer, with exceptions for high priority cases, high income non-filers and potentially egregious repeat trust fund taxpayers.

Put those rules together and you see the design. The IRS does not want to park a case right before it expires, and it does not want to start a field investigation that cannot finish in time. Old balances near the end of their statute are handled differently from fresh ones.

What to do if you think you are in the queue

First, confirm it. A representative can research the account status. Do not assume silence means the queue. It can also mean a shelved case, a hold, or a Revenue Officer who has not reached you yet.

Second, stay compliant. File every return on time and pay current year taxes. New balances are the fastest way to restart activity on an old account.

Third, decide whether to act now. Waiting in the queue has a cost in penalties and interest, and the collection statute is the only clock that runs in your favor. Read CSED Tolling Traps before choosing a path that pauses it.

The queue is a waiting room. Use the wait.