What I Looked for as an IRS Revenue Officer — and What Changed When I Became a Supervisor
A former IRS Revenue Officer and supervisor explains the behaviors, case-development issues, and supervisory considerations that often shaped whether a collection case moved toward resolution or enforcement.
By Brandon Lynch, EA
Founder & Managing Member, Lynx Tax Advisors
Published September 28, 2026
I spent nearly 20 years with the IRS, including Revenue Officer and supervisory assignments.
Those two roles gave me very different views of an IRS collection case.
As a Revenue Officer, I was responsible for developing assigned cases, gathering information, evaluating financial facts, communicating with taxpayers and representatives, and moving cases toward resolution or enforcement.
As a Supervisory Revenue Officer, I looked at cases from another level. I had to determine whether the case had been sufficiently developed, whether taxpayer rights had been protected, and whether the proposed resolution plan was appropriate and supportable.
That distinction matters.
A phrase commonly discussed in Field Collection was that you could give the same case file to ten Revenue Officers and get ten different case plans — and all ten could potentially be appropriate.
Collection work requires judgment.
Here are some of the things that shaped mine.
Trust was developed through behavior
When I was assigned a case, I did not expect every taxpayer to immediately have perfect financial records sitting in front of them.
During portions of my career, Revenue Officers still made unannounced initial contacts. Looking back now as a small-business owner myself, I have an even greater appreciation for how difficult it can be to answer detailed questions about income, expenses, assets, accounts, and financial records on the spot.
Being unprepared did not automatically make someone uncooperative.
Trust developed over time.
If a taxpayer said they would provide something, did they provide it?
If information was missing, did they explain why?
If something in the records was confusing, were they willing to discuss it?
Did the explanation of how the tax problem developed make sense?
Were they willing to acknowledge mistakes?
Those things mattered.
What raised concern was usually not one missing document. It was a pattern.
A story that did not make sense.
Incomplete information without an explanation.
Reluctance to discuss certain assets or sources of income.
Spending that did not seem consistent with reported income.
Transfers to unfamiliar people or accounts with no clear explanation.
When the financial information and the taxpayer’s explanation did not fit together, I generally needed to understand why.
Missed deadlines could change the direction of a case
One of the things taxpayers sometimes misunderstand about an assigned Revenue Officer is that the RO has a supervisor reviewing the case too.
I learned that firsthand.
I had a supervisor who reviewed my inventory. If a taxpayer agreed to provide information by a certain date, failed to do so, and I simply allowed the deadline to pass without taking appropriate action, I could expect to be asked why.
That accountability was directed at me.
Repeated failure to properly follow up on missed commitments could become a performance issue for the Revenue Officer.
That creates an important dynamic taxpayers rarely see.
Consider two taxpayers with essentially the same balance and financial circumstances.
The first taxpayer reaches out before the deadline:
“I have most of what you requested. I can send that now, but I need another week to obtain the remaining statements.”
The second taxpayer misses the deadline entirely and provides no explanation.
Those cases may begin with identical facts.
They may not progress the same way.
Open communication, partial compliance with a request, and a reasonable request for additional time could keep a case moving cooperatively.
Silence after a missed commitment could move the case toward enforcement.
The balance did not necessarily change.
The behavior did.
Saying “I can't pay” was only the beginning of the analysis
Taxpayers frequently told me they did not have money to pay the IRS.
Many genuinely believed that.
Then we reviewed the bank statements.
Financial analysis sometimes showed a very different picture.
That did not necessarily mean the taxpayer was being dishonest. People naturally organize spending around the life they are already living. Housing, vehicles, subscriptions, travel, dining, transfers, business expenses, family support, and other spending can all feel necessary from inside the household.
The IRS analysis may look at those expenses differently.
That is why focusing only on “I can't pay” rarely resolves the problem.
A more productive question is:
Given the actual income, expenses, assets, and circumstances, what is realistically possible?
That is the question the financial analysis is ultimately trying to answer.
Current compliance could matter more than maximizing the payment
When I moved into management, one of the most important things I looked for was whether the proposed resolution was sustainable.
Current compliance was critical.
If the underlying problem had not been fixed, closing the case did not accomplish much. The taxpayer could simply generate another liability and return to Field Collection.
Consider a business that, after allowable operating expenses, had $25,000 per month potentially available.
It might look attractive to apply all $25,000 toward the existing IRS debt.
But if doing that prevented the business from making $10,000 of required current tax deposits, we would be solving one liability by helping create the next one.
A more sustainable resolution might involve $15,000 toward the existing balance while preserving the $10,000 necessary to remain current — assuming the liability could still be paid within the applicable collection period.
That distinction mattered to me as a supervisor.
The highest possible payment was not automatically the best resolution.
A resolution was more valuable if the taxpayer could actually live with it and remain compliant.
I did not want to approve something that looked good on the day of approval but effectively set the taxpayer up to fail six months later.
A supervisor does not have to work the case exactly like the Revenue Officer
This was another important difference between being an RO and supervising ROs.
As an RO, I developed my own case plan.
As a supervisor, I reviewed someone else's judgment.
The question was not necessarily:
“Would I have worked this case exactly the same way?”
It was:
Does the file support the resolution? Were taxpayer rights protected? And is this resolution plan appropriate?
You could give the same case to ten Revenue Officers and potentially receive ten different case plans.
More than one could be reasonable.
My responsibility was to determine whether the Revenue Officer had completed the necessary development, followed required procedures, considered the relevant facts, and reached a conclusion the case file supported.
That included reviewing the applicable Internal Revenue Manual provisions, but supervisory review involved more than checking boxes.
Was the financial information sufficiently verified?
Were important assets considered?
Was current compliance addressed?
Were taxpayer rights protected?
Was the proposed resolution sustainable?
Was the case being closed because that was the appropriate disposition — or simply because everyone wanted the case closed?
Those distinctions mattered.
Sometimes I sent cases back
Revenue Officers manage inventories. They have deadlines, new assignments, field work, taxpayers calling, representatives calling, documentation arriving, and cases competing for attention.
They can become overloaded.
When I returned a case to an RO for additional development, it usually was not because I believed the employee was lazy or incapable.
More often, something important had not been completed or documented adequately.
Information had not been verified.
An asset had not been sufficiently considered.
A required action had not been completed.
The recommendation may have made sense, but the file did not yet support it.
That difference is important.
A good resolution is not just an idea that sounds reasonable.
The case has to be developed well enough to support it.
Good representatives made cases easier to resolve
Representatives varied considerably.
Some developed reputations for delay.
One of the people who trained me once described a local representative by saying, essentially, that he would represent a taxpayer until their last dollar was gone.
That was not a compliment.
The better representatives helped their clients understand reality.
I remember a case involving roughly a quarter-million dollars in liabilities. The taxpayer lived in an affluent area and had substantial equity in the home.
There was no clever procedural trick that made the equity disappear.
With the representative's help, the taxpayer ultimately sold the property, paid the IRS, paid the state, and still had enough remaining for a substantial down payment on another home.
That was a successful resolution.
The IRS was paid.
The state was paid.
And the taxpayer moved forward without the liability hanging over them.
Sometimes good representation means challenging the government.
Sometimes it means helping a client recognize the least damaging realistic path.
Knowing the difference matters.
Payroll-tax cases were often multiple investigations at once
Business payroll-tax cases were different from many individual balance-due cases.
I sometimes think of them as an investigation inside the investigation.
The business collection case had to be worked.
At the same time, the Trust Fund Recovery Penalty investigation could require determining whether one or more individuals were potentially responsible for the unpaid trust-fund taxes.
If there were multiple potentially responsible persons, the work multiplied.
You were effectively evaluating the business liability while separately developing responsibility and willfulness issues involving individuals connected to the business.
That made payroll cases more complex operationally than many straightforward individual income-tax collection cases.
And current compliance became especially important.
A business that continued accumulating new payroll-tax liabilities while attempting to resolve old ones presented a very different problem from a business that had corrected the underlying compliance issue.
Enforcement was often driven by behavior
People understandably focus on the size of their IRS balance.
From my perspective as an RO, behavior could be just as important.
Did the taxpayer meet commitments?
Were requested records provided?
Did they communicate when something could not be completed on time?
Were new liabilities continuing to accrue?
Had the same problem repeated for years?
At some point, a case involving repeated noncompliance stops being only about the dollars currently owed.
It becomes a question of whether anything has changed that would prevent the problem from continuing.
That is why two taxpayers with the same balance could have very different collection experiences.
One might be communicating, fixing compliance, producing records, and working toward something sustainable.
The other might continue missing deadlines, accumulating liabilities, or avoiding the issues that needed to be addressed.
The numbers could be similar.
The cases were not.
What I carry into representation today
Today I sit on the other side of the table.
I am an Enrolled Agent representing taxpayers before the IRS, and I am also a small-business owner.
That changes my perspective in ways I did not fully appreciate while working for the government.
I understand why a business owner may not know their exact monthly expenses during an unexpected conversation.
I understand why gathering several months of financial records can take time.
And I understand how overwhelming it can feel when the IRS asks for information about nearly every part of someone's financial life.
But I also understand why the Revenue Officer is asking.
I understand what can happen when deadlines pass without communication.
I understand why current compliance carries so much weight.
And having reviewed cases as both a Revenue Officer and a supervisor, I understand that a proposed resolution has to do more than sound attractive.
It has to be supported by the facts, appropriate for the case, and sustainable for the taxpayer.
That is one of the most important lessons I brought with me from IRS Collection to Lynx Tax Advisors.
The objective is not simply to get a case closed.
It is to help put the taxpayer in a position where this chapter with the IRS can actually stay closed.
Related reading: What the Revenue Officer Is Evaluating Before You Ever Meet, from Inside IRS Collections™.
Brandon Lynch, EA, is Founder and Managing Member of Lynx Tax Advisors. He has nearly 20 years of IRS experience, including Revenue Officer and supervisory assignments. Lynx Tax Advisors is a private tax representation firm and is not affiliated with or endorsed by the Internal Revenue Service.