1. What Code 350 Means
Code 350 records the IRS recomputing the return as filed - the system re-running your numbers through its own processing logic. The recomputation family sits between ordinary processing and formal assessment: it is the machinery checking, normalizing, and recalculating what a return produced, typically around events that change the inputs - amended-return processing, corrections of earlier processing errors, exam-related recomputation, or system-level reprocessing of the return's figures. As with the adjustment family, the IRS does not publish taxpayer-facing definitions of 350, and the practitioner reading is consensus: recomputation mechanics rather than a discrete taxpayer event. What makes the code worth an article is precisely its ambiguity: a 350 can be pure plumbing (the re-run changed nothing), a documentation step inside a larger event (the amendment or exam that triggered it), or the visible edge of a difference between your numbers and the system's - and telling those three apart is the reading task this article equips you for.
2. When Recomputations Happen
The triggers cluster into recognizable scenarios, and each carries its own reading. Amended returns are the most common companion: when a 1040-X processes, the system recomputes the return's figures to incorporate the changes - a 350 near a 977 is usually the amendment's arithmetic in motion, reconciling the original with the amended reality. Processing corrections are the second: when earlier processing made an error - misapplied documents, dropped schedules, wrong-year postings - the correction cycle re-runs the return, and the recomputation documents the re-run. Examination contexts are the third: exam-related recomputation of the return as filed, where the exam's numbers are run through the system to produce the assessment figures. System-level reprocessing rounds out the set: software-era corrections, mass corrections, and format migrations occasionally re-run batches of returns with no individual event behind them. The date and neighbors are the decoder: a 350's meaning is always "why now," and the answer is on the lines around it or in the mailbox.
3. Reading a 350 Against Your Own Numbers
The verification discipline for recomputations is line-by-line arithmetic against your copy of the return. Most recomputations change nothing a taxpayer would notice - the re-run confirms the figures. When amounts move, the differences have known shapes: computed credits that post differently than software estimated (timing and phase-out differences), allocation changes between years (estimated payments and applied overpayments moving in the re-run), rounding and schedule-level differences, and - the important category - figures that reflect documents the system had that differ from your records. That last one is the finding to chase: a recomputation built on a mismatched document means the underlying data disagree with your paper, and the disagreement is what needs resolving, through the notice response, a correction, or an amendment with substantiation. The transcript's own structure helps: recomputation entries near refund or balance changes show what the re-run concluded; notices explain changes that reached a threshold worth telling you about. The rule that protects you: never pay, and never ignore, a recomputed figure you cannot reconcile - reconciliation is the action.
4. How Recomputations Differ From Assessments
The distinction matters legally and practically. An assessment - the 150 original or the 290-family additional - is the formal determination of tax owed, with notice obligations, dispute windows, and collection authority attached. A recomputation is processing mechanics - the system re-running figures, often inside an event whose formal side is handled by other codes (the amendment's own processing, the exam's assessment machinery). Practically: a 350 by itself generates no bill, no deadline, and no collection; if the re-run surfaced a difference that matters, the difference graduates into the formal channels - a notice explaining a corrected refund or balance, an additional assessment with its own rights, or an amendment cycle. That is why the reading order for a 350 is: neighbors first (what event is this inside?), amounts second (did anything change?), mailbox third (did a notice explain it?) - and only if all three come up empty does the code itself deserve an inquiry. The assessment-family articles in this series cover the formal side; the 350 is the backstage entry that occasionally peeks out.
5. What To Do With a 350 on Your Account
Run the same three-step read. Identify the event: check the surrounding codes - 977 amendments, 971 notices, exam-family entries - for the context the recomputation sits inside. Check the arithmetic: compare any changed amounts against your copy of the return and your bank records; matching figures close the inquiry, mismatched figures open it. Check the mail: a notice explaining the recomputation converts mystery into paperwork with its own instructions. If the recomputation surfaced changes you dispute, the response runs through the formal channels - notice responses with documentation, amendments with substantiation, or preparer-negotiated corrections - not through paying unverified figures. And if the 350 sits with no neighbors, no amounts, and no mail, file the transcript and move on: silent recomputations are the system keeping its arithmetic honest, and honest arithmetic asks nothing of you. The recurring prescription of this series applies one final time: dated transcript pulls turn every future recomputation into a lookup instead of a mystery.
6. When a 350 Needs Professional Help
Most recomputations are self-verifying, and the professional cases are the ones where the re-run and your records tell different stories: recomputed figures that produce balances or reduced refunds you cannot trace to any document you recognize (the mismatch needs professional tracing across years and modules); recomputations inside exam or amended-return events where the arithmetic feeds assessments that matter; repeated recomputations of the same year suggesting unresolved data conflicts; and recomputation-driven notices with deadlines already attached, where the response channels and their rights need sequencing. In those cases the 350 is the fingerprint of an event worth managing - and the professional's value is managing the event, with the recomputation as the trail head.