The Revenue Officer's Case History: What Goes Into ICS and Why It Matters

There is a running narrative of your IRS collection case, written by the people working it. You have probably never seen it. The officer types in it after every call. The manager reads it during reviews. The next officer reads it before contacting you.

It lives in the Integrated Collection System, called ICS, and the IRM has specific rules about what goes in it.

What ICS is

IRM 5.1.20.4.3 (rev. 2024-10-07) describes ICS as the system that provides workload management, case assignment and tracking, inventory control, electronic processing and case analysis tools to support SB/SE collection fieldwork. It is a Windows-based application with a mainframe tier at the Tennessee Computing Center and software on each employee's workstation.

IRM 5.1.20.4 says ICS supports electronic case management, including assignments and opening and closing actions, electronic case documentation through contact and history recording, and electronic lien requests that flow to the Automated Lien System.

ACS has its own history system. Field Collection uses ICS. If your case moved from one to the other, there are two histories.

On the ACS side, IRM 5.19.5.4.3 (rev. 2025-03-03) says history codes record actions taken by the call site or ACS Support, generate documents, upload transactions to IDRS and record journal entries for taxpayer and third party contacts, and that consistent nationwide use of the codes assists with case review. A new Revenue Officer reads both records before calling you.

The standard for a history entry

IRM 5.1.10.8 (rev. 2025-04-24) says Collection uses ICS history to record actions and decisions taken on cases, and that it is extremely important for entries to be clear, accurate, concise, complete and timely. Entries are made in chronological order and recorded the day the action occurs or as soon as practical afterward.

Some actions create entries automatically. Beyond that, the IRM lists items that should be included: the resolution plan, action expected of the taxpayer, target dates, taxpayer compliance, plans for next actions, enforcement actions and financial analysis.

The IRM makes certain pick lists mandatory. Officers must use them to document taxpayer contact, taxpayer or asset location activity, federal tax deposit verification and the closing narrative for business accounts. Even when a form is in the paper file, the IRM says a history entry should reference the action.

What the officer records about you

Read across IRM 5.1.10 and you can see what ends up in your history. That you received Pub 1 and had your questions answered. Your compliance with current filing and payment. The cause of your delinquency and the officer's advice on how to avoid it, recorded under a pick list called Cause and Cure.

Every deadline you were given, recorded with a summary of the Form 9297. The specific enforcement action you were told would follow if you did not comply, recorded under Deadline Communicated. Whether you responded to appointment letters, and what follow-up the officer planned when you did not.

Extension requests and the officer's decision on them, with the basis. IRM 5.1.10.9 requires that documentation. Reasons the officer delayed a follow-up beyond 15 days, which the IRM says should be clearly documented.

The tone of the history matters to how the next reader sees you. A file that reads promised, delivered, promised, delivered tells a manager one story. A file that reads promised, missed, excuse, missed tells another.

What the officer is not allowed to write

IRM 5.1.10.8 says Section 3707 of the IRS Restructuring and Reform Act of 1998 prohibits using any tax protester designation to describe a taxpayer. The IRM permits terms such as frivolous argument, tax avoidance argument or frivolous filer to describe behavior.

The IRM also tells officers not to paste emails or communications with IRS Counsel into case histories, because doing so may make it harder to assert legal privilege when responding to discovery or a Freedom of Information Act request. Instead, the legal advice goes in the case file with a note in the history.

And taxpayer records, including copies of checks, cannot be kept by Collection personnel after the account is disposed of. They must be handled under approved records control schedules.

Managers write in it too

Group managers document reviews in the history. IRM 1.4.50.5.2.1 (rev. 2025-04-01) says managers use the ICS History pick list to note Case Reviewed and the date of the review. Managers may suggest or request specific actions in the history but should avoid making numerous case decisions for the officer, and documentation of an evaluative nature should not be entered in the case history.

When a manager changes a case grade, IRM 1.4.50.10.1 says the factors are documented in the ICS history using the pick list. When a case stays in the manager's hold file for more than 45 days, IRM 1.4.50.10 says the reason should be documented.

So the history is not only about you. It also shows whether the IRS did what its own manual requires, and when.

Histories can be corrected, but not casually

IRM 5.1.10.8 says all requests to delete ICS history must be in writing, stating exactly which entry is to be deleted and why, for example history documented in the wrong case. The field compliance manager's concurrence must be noted before deletion, and the analyst performing it keeps the request with prints of the history before and after.

Entries in the wrong case are treated as a potential disclosure problem. The IRM points to the procedures for reporting suspected unauthorized disclosures.

Other employees who look at a case that is not assigned to them are encouraged to write a brief narrative explaining the access.

Keep your own history

The IRS's record is not the only one that counts. Keep a log of every contact: date, time, who you spoke with, what was asked, what you promised and what deadline was set. Save every letter, envelope and Form 9297.

IRM 5.1.10.5 says all IRS correspondence to taxpayers must include the employee's title, last name, employee identification number and telephone number. Write those down. If you ever need to raise a problem with a manager, Appeals or the Taxpayer Advocate Service, you will need to identify exactly who did what and when.

The same subsection says letters required by statute that relate to a joint return, such as the notice of intent to levy, must be sent separately to each spouse who filed the return. If only one spouse received a notice, that is worth noting in your log and asking about.

When your log and the ICS history disagree, the discrepancy itself is useful. A history entry that says a deadline was communicated when no Form 9297 was ever handed over, or that says you failed to respond when you have a fax confirmation, is the kind of thing a group manager is supposed to care about.

Why this matters to you

The history follows your account. IRM 5.1.10.2 tells a newly assigned officer to review the prior case history, including current and archived ICS history and the ACS history, and to note actions already taken by previous officers or ACS. Your reputation with the IRS on this account is whatever that history says.

You can often get a copy. The history is an agency record, and taxpayers and their representatives commonly request it through the Freedom of Information Act. It is one of the most useful documents in a collection case, because it tells you what the IRS thinks happened.

Build a good record from the first contact. Confirm appointments. Meet deadlines or ask for extensions before they pass. Put commitments in writing. The officer is writing your story. Give them good material. For the deadlines that drive most of the entries, see Form 9297 and the Revenue Officer's Deadlines.