Most taxpayers assume that once a return posts to the IRS Master File, the hard part is over. In many cases, that is true. However, some returns trigger a secondary automated review even after posting.
That review is identified on transcripts by Transaction Code 922.
Understanding the Transaction Code 922 meaning helps explain why a return that appeared to be moving normally can suddenly pause—without being audited, rejected, or pulled for identity verification.
What Is Transaction Code 922?
TC 922 indicates that the IRS has initiated an automated post-posting review on a return that has already been accepted and recorded on the Master File.
Key points about TC 922:
- The return has already posted
- Processing reached a valid checkpoint
- The IRS system flagged a specific item for review
- No refund freeze has been applied yet
TC 922 is informational first, restrictive only if something fails later.
Why the IRS Runs a “Second Look” Review
The IRS uses TC 922 when certain items cannot be fully validated during initial processing.
Common triggers include:
- Specific schedules with higher error rates
- Attachments that require delayed matching
- Credits or deductions needing secondary verification
- Forms dependent on downstream data
This review happens after posting, which is why it surprises many taxpayers.
What TC 922 Is — and Is Not
TC 922 Is:
- An automated review marker
- A system-generated checkpoint
- A signal that something is being re-verified
TC 922 Is Not:
- An audit
- A manual review
- An identity verification hold
- A refund freeze by itself
The presence of TC 922 alone does not stop a refund.
How TC 922 Appears on Transcripts
On an Account Transcript, TC 922 usually:
- Appears after TC 150 (Return Filed)
- Has a posting date
- Shows no dollar amount
- Does not change the account balance
Because it does not alter balances, many taxpayers overlook it.
What Happens Next?
After TC 922 posts, one of two outcomes occurs:
If the Review Passes
- No additional action is taken
- The TC 922 remains as a historical marker
- Processing continues normally
- Refund issuance proceeds if no other holds exist
In many cases, taxpayers never know the review occurred.
If the Review Fails
- A TC 570 (Additional Account Action Pending) posts
- Refund issuance is temporarily frozen
- The IRS may request more information
- A notice or letter may follow
This is when the review becomes visible to the taxpayer.
Why TC 922 Does Not Always Generate a Notice
The IRS only contacts taxpayers when:
- The issue cannot be resolved internally
- Documentation is required
- The adjustment affects tax liability or refund
If the system resolves the review automatically, no notice is issued.
How TC 922 Differs from Pre-Posting Reviews
Unlike ERS, IVO, or RIVO actions:
- TC 922 occurs after posting
- The return already exists on the Master File
- The IRS is validating a specific component, not the entire return
This makes TC 922 more targeted and often less disruptive.
What You Should Do If You See TC 922
You Should:
- Continue monitoring your Account Transcript
- Watch for follow-up codes like TC 570 or TC 846
- Allow processing time for the review to complete
You Should Not:
- Amend the return immediately
- Contact the IRS solely due to TC 922
- Assume an audit is underway
Most TC 922 reviews resolve quietly.
The Transaction Code 922 meaning is simple but often misunderstood.
TC 922 means:
- Your return posted successfully
- The IRS is taking a second automated look
- Processing is not blocked unless a later code appears
If nothing follows, the review passed.
If a TC 570 follows, the issue requires attention.
