Inside Collection
The IRS Collection Pipeline: Notice Status, ACS, the Queue and the Field
Your balance does not sit in one pile. The IRM routes it through notice status, the Automated Collection System, the queue or a Revenue Officer, and each stop has its own rules.
Most people picture the IRS as one big office with one big file on them. It is not. An unpaid balance moves through a set of separate collection functions, and which one holds your account decides who calls you, what they are allowed to do and how fast things happen.
The Internal Revenue Manual describes this routing in plain terms. Once you understand the pipeline, the letters stop looking random. They are coming from a specific place, for a specific reason, on a schedule someone wrote down.
Stage one: the notice stream
Every balance due starts in what the IRS calls the notice stream. The campus computers mail a series of balance due notices. During this period the account carries what the IDRS manual calls a first notice status, status 19 or 21, which IRM 2.4.28 (rev. 2025-02-05) uses as a prerequisite for moving an account into later collection statuses.
Nobody is personally working your file at this stage. The system is. If you pay, set up a plan or otherwise resolve the balance while it sits in notice status, it never goes any further.
Here is the part most people miss: the notice stream is the cheapest, quietest place to fix a balance. The closer you are to the start of the pipeline, the fewer people have touched the file and the fewer enforcement options have been teed up.
Stage two: the Inventory Delivery System decides where you go
If the notices do not resolve the account, it becomes a Taxpayer Delinquent Account, or TDA. A missing return becomes a Taxpayer Delinquency Investigation, or TDI. At that point, according to IRM 5.1.20.1.1 (rev. 2024-10-07), collection inventory that has not been resolved during the notice stream is systemically routed to the collection functions by the Inventory Delivery System, known inside the IRS as IDS.
IDS uses a business rules engine plus data analytics. IRM 5.1.20.2.1 says it uses predictive modeling techniques, case grade and routing indicators to prioritize cases. Model scores indicate the likelihood that a predicted case outcome will occur.
Based on those rules, IDS sends a case to one of a handful of destinations: Field Collection by direct assignment, the Queue, the Automated Collection System, or the Automated 6020(b) program for certain business returns that were never filed.
There is a fifth outcome that surprises people. IRM 5.1.20.2.2 says IDS also uses business rules to shelve cases due to resource limitations when the case is predicted to be inactive or unproductive, and it identifies the transaction as TC 530 with closing code 39. In other words, the IRS can decide your account is not worth working right now and put it on the shelf. The debt does not disappear. It just stops moving.
Stage three, option A: the Automated Collection System
Most individual balances land in the Automated Collection System. IRM 5.19.5 (rev. 2025-03-03) describes ACS as a computerized inventory system created in 1984 so that taxpayers or their representatives could resolve delinquent accounts with a single telephone contact.
On the IRS's own computers, an account sitting in ACS shows a status 22. IRM 5.19.5 refers to case dispositions for modules in Status 22 using the ACS database. When a transcript or a practitioner's account research shows status 22, that is who has you.
ACS works by phone and by mail. It issues letters and levies from campus call sites and support sites rather than from field offices. I cover how that inventory is divided and worked in Inside the Automated Collection System.
Stage three, option B: the Queue
The Queue is the least understood stop in the pipeline. IRM 1.4.50.8.3 (rev. 2025-04-01) defines it in one line: the queue is an electronic file holding unassigned collection cases. Cases in the queue are prioritized for selection, and the IDRS assignment number for queue cases is AOTO7000.
Cases arrive in the Queue two ways. Some skip ACS entirely. IRM 5.1.20.3.2 lists examples that go from notice status straight to the Queue, including certain special noncompliance cases, certain delinquent return case codes, and any installment agreement needing financial review. Other cases get there after ACS works them and transfers them out.
In IRS shorthand, a queue account shows status 24. IRM 5.1.20.3.2 describes cases whose last Master File status equals status 24 as cases with an embedded queue assignment.
Sitting in the Queue means a case is waiting for a Field Collection group manager to pull it and hand it to a Revenue Officer. Some cases wait a long time. Some are never pulled at all.
Stage three, option C: Field Collection
Field Collection is where Revenue Officers work. These are the IRS employees who make field calls, visit businesses, interview taxpayers in person and handle the larger and more complicated accounts. An account assigned to the field shows status 26. IRM 5.1.20.3.1 refers to cases whose last Master File status was status 26 as carrying an embedded field assignment number.
Some cases go to the field directly from notice status. IRM 5.1.20.3.1 lists the categories that bypass both ACS and the Queue and land in the group manager's hold file in the Integrated Collection System. They include any Non Master File account, IRS employee accounts, Letter 903 cases with a balance over $50,000, quick or prompt assessments, defaulted in-business trust fund installment agreements, cases with a large dollar sub code, and cases returning from Appeals where the most recent prior assignment was Field Collection.
That list tells you something. Business trust fund problems and large balances are designed to reach a human being with field authority quickly. If you are in one of those categories, plan on meeting a Revenue Officer.
Cases that cannot move freely
The routing rules also lock certain cases in place. IRM 5.1.20.3.3 says some cases cannot be moved to the Queue at all. The list includes Non Master File accounts, IRS employee accounts, the Federal Employee/Retiree Delinquency Initiative, refund hold cases, accounts under Appeals jurisdiction for a Collection Due Process or equivalent hearing, and cases with a module whose collection statute expiration date expires within six months.
IRM 5.1.20.3.4 adds restricted assignment cases, which cannot be sent to the Queue or transferred while the restriction is present. Examples include accounts carrying disaster codes 2 or 3.
The six month rule matters. A case close to its collection statute does not get parked. It either gets worked or it expires. If the statute is your issue, read CSED Tolling Traps before you file anything that pauses the clock.
Why the status code changes your strategy
Knowing where your account sits tells you who you are dealing with and what they can do. ACS assistors work from scripts and authority limits set out in IRM 5.19. A Revenue Officer works from IRM Part 5, Chapter 1, has a group manager reviewing the case, and can do things ACS cannot, such as field visits and in-person interviews.
It also tells you whether a call to the IRS toll-free number will reach anyone who can help. IRM 5.19.5.1 says ACS employees receive incoming calls for accounts where at least one module is in TDA status 22, 24 or 26. So even a queue or field account can generate a phone conversation, but that conversation has limits when a Revenue Officer controls the case.
And it tells you about timing. A case in the Queue may sit. A case assigned to a Revenue Officer will move on the officer's follow-up dates. A shelved case may come back to life when the IRS's resources or your circumstances change.
The pipeline is not personal, and that is useful
IRM 5.1.20.1 says collection inventory is routed using systemic scoring and routing so that no one individual can control the enforcement selection decision-making process, consistent with Policy Statement P-1-236. Nobody at the IRS picked you out of a hat. A rules engine did.
That cuts both ways. You cannot talk your way out of the pipeline by calling the right person. But you can predict it. The rules are written down, and the person who reads them can usually tell you what happens next and what will stop it.
Knowledge is protection. Find out which stage you are in before you decide what to do.
Questions readers ask
How do I find out whether my account is in ACS, the Queue or the field?
The IRS's internal status codes are not printed on most notices. A representative with a power of attorney can research the account, and the type of contact you are getting is a strong clue. ACS works by phone and mail from campus call sites. A Revenue Officer contacts you individually, usually with an appointment letter or a phone call, and every letter carries the officer's name, employee number and phone number.
What does it mean if my case is shelved?
IRM 5.1.20.2.2 says the Inventory Delivery System can shelve cases due to resource limitations when they are predicted to be inactive or unproductive, using TC 530 closing code 39. The balance remains owed, interest continues, and the account can be reactivated. Shelving is an IRS workload decision, not relief.
Can a case in the Queue be sent back to ACS?
The routing systems move cases among functions according to business rules. IRM 5.19.5 describes cases returned from the field queue being assigned to an ACS research unit. The exact path depends on the case characteristics the IRS's systems evaluate.
Why did my case go straight to a Revenue Officer without ever going to ACS?
IRM 5.1.20.3.1 lists case types that bypass ACS and the Queue, such as Non Master File accounts, IRS employee accounts, Letter 903 cases over $50,000, quick assessments, defaulted in-business trust fund installment agreements and large dollar sub code cases. If your account fits one of those categories, direct field assignment is the designed outcome.